For further information about any of the issues mentioned in this article, please search for the relevant Known Issue number in the Known Issues Database.

CAUTION: It is recommended to ensure no users are logged in and using the system and IIS is stopped while these changes are applied.

Issue 8329: Unable to add a target to features within System Administration.

The instructions to resolve this issue are as follows:

On your Sage server navigate to \\Sage\Installers\Sage 200 Administration replace this folder with what is in the zip Sage-Installers-Sage 200 Administration.zip

1. Navigate to \\Sage\Installers.
2. Locate the Sage 200 Administration folder.
3. Overwrite this with the Sage 200 Administration found in the zip file below.

On the web server replace the 'Sage.MMS.Admin.SystemAdminClientService.dll' with what is in the zip inetpub-Sage 200 App Services-Sage200Services-Bin.zip

1. Navigate to \\inetpub\Sage 200 App Services\Sage200Services\Bin.
2. Locate the Sage.MMS.Admin.SystemAdminClientService.dll.
3. Overwrite this with Sage.MMS.Admin.SystemAdminClientService.dll contained in the zip file provided below.

Sage 200 Professional 2020 R2 >>

Issue 8330: Object Reference not set to instance of an object Error in Intrastat

NOTE: The dlls included the below zip files are specifc to each version , please ensure you apply the correct dll for you version of the software.

The instructions to resolve this issue are as follows:

Replace the \\Sage\Installers\Sage 200 Client with what is in the zip Sage-Installers-Sage 200 Client.zip

1. Navigate to \\Sage\Installers.
2. Locate the Sage 200 Client folder.
3. Overwrite this with the Sage 200 Client folder found in the zip file below.

If using Manufacturing the steps below should be followed:

Replace the \\Sage\Installers\Sage 200 MFG Client with what is in the zip Sage-Installers-Sage 200 MFG Client.zip.

1. Navigate to \\Sage\Installers.
2. Locate the Sage200 MFG Client Folder.
3. Overwrite this with the Sage200 MFG Client Folder found in the zip file below.

Sage 200 Professional 2020 R2 >>

Sage 200 Professional 2020 R1 >>

Sage 200 Professional Summer 2019 >>

Sage 200 Professional Spring 2019 >>

Sage 200 Professional Winter 2018 >> TIP: This hotfix resolves both issues 8330 and 8343 for Winter 2018.

Sage 200 Professional Summer 2018 RM >>

Sage 200 Professional Summer 2018 >>

Sage 200 Professional Spring 2018 >>

Sage 200 Professional Winter 2017 >>

Sage 200 Professional Summer 2017 RM >>

Sage 200 Professional Summer 2017 >>

NOTE: In some instances, you may also be required to reinstall the client from the updated folders if it does not auto update upon next log in.

CAUTION: The steps to resolve 8330 on Sage 200 2016 SP2 RM are specific to that versions architecture and must be followed as below.

Issue 8330: Object Reference not set to instance of an object Error in Intrastat

The instructions to resolve this issue are as follows :

Prerequisites

The customer must have upgraded to Sage 200 v2016 SP2 RM.

Contained in the zip file below you will find 2 .dll files to update Client and Web/Application Server please ensure you do this on all the locations mentioned below:

Sage 200 Professional 2016 SP2 RM >>

Sage.MMS.SystemManager.Commercials.dll:

This DLL file needs to be copied:

Onto each Client installation, i.e. into the GAC (Note: For Sage 200 v2016 this is different to earlier versions – See the example below).

Copying files to the GAC on Sage 200 v2016:

On each machine go to C:\Windows\Microsoft.NET\Assembly\GAC_MSIL – Find the relevant file name folder i.e. Sage.Accounting.Financials.dll – the actual DLL file that needs to be updated will be held in a sub-folder (e.g. in this example v4.0_19.0.0.0__56cc4aa2c6a12364).

TIP: The File Version number will now be 19.0.21006.1.

Sage.Accounting.Financials.dll:

This DLL file needs to be copied into 4 different places:

Onto each Client installation, i.e. into the GAC (Note: For Sage 200 v2016 this is different to earlier versions – See the example below).

Copying files to the GAC on Sage 200 v2016:

On each machine go to C:\Windows\Microsoft.NET\Assembly\GAC_MSIL – Find the relevant file name folder i.e. Sage.Accounting.Financials.dll – the actual DLL file that needs to be updated will be held in a sub-folder (e.g. in this example v4.0_19.0.0.0__56cc4aa2c6a12364).

TIP: The File Version number will now be 19.0.21006.1.

Onto the machine classed as the Web/Application server, in the folder path C:\Inetpub\Sage 200 App Services\Sage200SecuredServices\Bin.

Onto the machine classed as the Web/Application server, in the folder path C:\Inetpub\Sage 200 App Services\Sage200Services\Bin.

Onto the machine classed as the Web/Application server, in the folder path C:\Inetpub\Sage 200 Self Service\Sage200SelfService\Bin.

CAUTION: We would recommend that the above processes are done with no other users in the system. An IISReset will likely need to be performed to allow the copying of the files to take place.