Run the workstation setup for Sage Intelligence under the BX62A folder.

I gave that a try and it didn't work. I changed the permissions of the user to domain admin and ran it. Changed it back and still have that loading problem.

Thanks for the time/reply.

We have experienced the exact same issue with V2012 in a terminal server environment, and the issue is still unresolved. The only way we are getting around this is by making the Sage 300 users Administrators on the Local Machine, ie the TS. But that is far from an ideal situation, we would really like to have it resolved and to set the users' permissions back to what it should be.

Any assistance will be greatly appreciated.

Thanks for reminding me Jurgen, I have updated my post with our setup. We also have a terminal server that we use.

When we upgraded from 2012 to 2014 I noticed that in the local users; domain user had administrative rights so anybody could have switched off the terminal server.... I of course revoked that capability, but now we run into this situation. It might also explain why 2012 ran smoothly. Everybody had administration rights.

Thanks for reminding me Jurgen, I have updated my post with our setup. We also have a terminal server that we use.

When we upgraded from 2012 to 2014 I noticed that in the local users; domain user had administrative rights so anybody could have switched off the terminal server.... I of course revoked that capability, but now we run into this situation. It might also explain why 2012 ran smoothly. Everybody had administration rights.

Contact Sage tech support.

Did that long ago, they have been zero help.

I have asked for their help as well in which it still has gone unsolved.

Hi,  

It is damaged installation; you can uninstall all versions of Sage 300 ERP, rename the folder\registry related to Sage 300 ERP, and reinstall Sage 300 ERP.

The folders\ registry to rename if they still exist:

- Rename Sage folder to Old-Sage in C:\Program Files (x86)\Sage

- Rename Program Directory  ( Go to help-> system information to confirm the Program directory)

- Rename the folder ACCPAC International, Inc. from the registry to old-ACCPAC International, Inc.: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ACCPAC International, Inc.

If you still have same issue, please call us back, Sage 300 ERP support 800-253-1372, we can run process monitor and COM spy to investigate.

Thanks.

Thank you for the suggestion Mahi, but if it is a damaged installation how do you explain that the issue does not occur when the TS users are given Administrative rights on the local machine/terminal server?

Rgds

Jurgen

Mahi from Sage tech support gave you a fix and you question that? Now I understand why your site is a mess.

Yes I believe it is a legitimate question as it doesn't make sense that a re-install of the complete system can fix what is clearly a permissions issue.

Your continuous derogatory answers to some valid questions on this forum is not appreciated by anyone. You would do better by rather keeping quiet when you have nothing positive to say.

You're welcome :)

I will take a serious look at this and see. Thank you for your suggestion/help.