Hi,

I've seen similar with a customer who had a certain version of two Sicon modules. The Sicon addon would attempt to login to the Sage 200 Configuration database as the local user, who as you would expect is not setup with access to the Configuration database.

My case was with the following Sicon addons/versions:

Sicon Common Components -    2017.18.01
Sicon Enhancment pack            2017.18.0.0

If you have Sicon you may want to check your versions are upto date, or, run the Sage 200 application without addons temporarily to see if the issue persist. Else set Sage 200 logging level in the local workstations Sage200Desktop.exe.config file to DEBUG > attempt to login as the non admin user > check the Sage200Desktop.log file for something similar to:

WARN  13  Sage.ObjectStore.Database[Connection] IsTransient, error: 4060, Cannot open database "Sage200Configuration" requested by the login. The login failed. 
WARN  13  Sage.ObjectStore.Database[Connection] IsTransient, error: 18456, Login failed for user "DOMAIN\USERNAME"

If you have no Sicon addons you may be best off checking the log file anyway to see if it sheds insight to the issue.

thanks! it is probably exactly the same issue as we have just got Sicon Kitting installed.... will get back to you with results. Thanks again!

I assume this has probably been resolved, but just to confirm Sicon released a fix for this issue back in April (i.e. Sicon Common Components v190.0.11, or later)