Did you upgrade from an older version of Sage 300?

Yes, I have had the exact same issue for a long time on Terminal Server installations. It is clearly a permissions issue as the only way to stop that from happening is to make the user an administrator on the local machine, which is very much not what you want on a TS. Sage Support (both local & NA) has been unable to resolve this issue.

I've run into this, it's an unsuccessful upgrade, some old components were not uninstalled and the new components were not installed. I had to wipe Sage 300 completely and clean up the computer, then do a fresh install.

We are getting the issue on fresh installs and upgrades so perhaps there is more than one cause.

When you run the BX workstation install you get errors that some DLL/OCX will not register?

Had that as well, format C: fixed it. Sometimes it is much faster to format C: than to try fix weird DLL errors.

We have also had this problem with a TS installation.  They are currently on 6.0, but from the sound of it we are still going to have the same issue after upgrading.

I have tried this on a fresh install of windows, and still receive the error. During install no errors are shown or pop up. So far the only way this has been resolved is either removing the workstation install for intelligence or providing admin permissions to the users. Neither of which are good options.

Ettienne you mention you have it working with Sage 300 ERP 2014? This is with non admin users, just the basic permissions provided in windows?

99% of computers work fine, the odd one throws a fit and will not.

Unfortunately that is not my experience with the newer versions of Sage Ettienne. Every new site I setup and have had Sage login and check has this issue, and they are unable to resolve. We have multiple sites with the problem.

However you did not answer my question about the users accessing Sage. To add to that question are your setups with terminal server or workstation installs?

Contact Sage support.

Ettienne, if you re-read my previous post it indicates I have and they havent resolved. I am just trying to compare configurations with you to see if I have done something wrong.

Perhaps I should consult with someone else at this point who may be of some help.

There are a mix of terminal server and workstations.

Important steps are to disable UAC, install Sage 300 using "Run As Administrator" and then install Intelligence from the BX62a\WSSETUP folder using "Run As Administrator". Then run REGACC.EXE using "Run As Administrator". The first time you open Sage 300 you need to right-click the icon and "Run As Administrator", open Sage Intelligence and make sure you get in. These are the steps I follow, that works.

Ettienne, that post was extremely helpful! I may have found where my issue lies. Thanks.

I've posted a possible solution\workaround for this on another thread:

sagecity.na.sage.com/.../windows-installer-keeps-appearing-on-w2012-r2-remote-desktop-services-terminal-server