Sage 200 Troubleshooting

Object Reference Not Set to an Instance of an Object

When Zynk or any other third party application connects to the Sage 200 SDK, it creates a temporary login file in the %TEMP% directory of the machine

This is located at C:\Users\USERNAME\AppData\Local\Temp

Each file is give a uniform filename similar to tmpXXXX.tmp

The XXXX in the above is appended based on the hexadecimal system up to a maximum of FFFF

This means that the upper limit is 65355 files (the total possible combinations of 0-9 and A-F)

These files are normally cleared down by Windows but in this case they have not been.

This means Sage 200 can no longer create the necessary login token and the workflow will fail to complete.

The next steps are for whoever provides you IT support to add a routine that clears down these temporary files before they hit this upper limit.

Solution

There are many ways to approach this issue.

The most common option customers choose is to ask their IT Team to create a Windows Batch file (.bat)

This can be configured to run via Windows Task Scheduler and clears down these files.

An example of this would be:

@echo off

cd C:\Users\ZYNKUSER\AppData\Local\Temp

del tmp*.tmp

Note: ZYNKUSER would need to be replaced with whichever Windows User runs the Zynk scheduled task.

Please note, we are not responsible for any adverse effects resulting from the use of the above batch file.

This should only be implemented by your IT Team after a full impact assessment has been carried out.