This message can be caused by a problem with the assembly cache within the file contained in the local user's profile settings. To resolve this, carry out the following steps:
- Close any open instances of Sage 200 System Administrator and the client.
- Browse to the following location - C:\Users\username\AppData\Local\Sage. Rename the Sage200 folder to 'OldSage'.
- Log in to System Administrator and wait until all necessary components are loaded and installed.
- You should now be able to log in to the Sage 200 Extra Client.
If this doesn't resolve the problem, you will need to suspend and resume the site which 'hard resets' the server. To do this, ensure all users are logged out of the application, login in to Sage Provisioning Portal then browse to the site. Within the Operations section, click Suspend.
Once suspended, refresh the page and click Resume. The site will show a status of resuming. This process usually takes about 15-30 minutes to complete. Once the status of the site shows as Ready, users can log back in to Sage 200 Extra Online.