Sage 50 Quantum Accounting Remote Desktop

[Jaxon]

Sorry for the long-winded post, but...

I have a client for whom I setup an Amazon virtual SBS 2008 R2 instance to host QuickBooks. I created RemoteApp shortcuts so it looks to the user like they are just using a regular piece of software. The users login from all over the country and it has worked great.

The client has now asked me to setup Sage 50 Quantum Accounting 2016 the same way. I have Sage installed on the server, but when I use the RemoteApp shortcut I get an error message which states "Sage 50 Accounting could not be started. Please try again. If you continue to have problems" blah, blah, blah contact Customer Support. The funny thing is that if I use the built-in Administrator account login credentials the RemoteApp shortcut works and the software runs without a hitch. I have tried both Standard user accounts and Administrator accounts.

What am I missing?

 

[TurricanII]

Have you seen this:

https://support.na.sage.com/selfser...36A8660841AE1312E92.worker1j?externalId=10533

"The following article is intended to be a guide on enabling users to use Sage 50 in a terminal server environment using a Windows 2008 server...
...Terminal Services have been tested and are supported for Quantum edition of Sage 50 Accounting only"

You might have missed something like making the users Power Users.

 

[Jaxon]

Have you seen this:

https://support.na.sage.com/selfser...36A8660841AE1312E92.worker1j?externalId=10533

"The following article is intended to be a guide on enabling users to use Sage 50 in a terminal server environment using a Windows 2008 server...
...Terminal Services have been tested and are supported for Quantum edition of Sage 50 Accounting only"

You might have missed something like making the users Power Users.

I saw that page and tried making the users Power Users, but it didn't work. Thanks for the response. I will keep playing with it.

 

[TurricanII]

Did you put the RDS server into install mode rather than execute mode before installing?

I would log to a full desktop session as the failing user and then run Sage - does the problem persist? If so then I would fire up processmon or process explorer from sysinternals (can't remember which one shows file and registry activity) and would filter to see what Sage is doing right up to the point that the error appears.

You might find a file, folder or reg key that is inaccessible.

I'd also make the failing user a domain admin - does it then work? If so then take them back out of domain admins and see if it still works. There might be a final per-user setup step that is trying to run.

Finally, perhaps run as Administrator and disable any Sage auto updates upon startup. Does that fix anything?

 

[YeOldeStonecat]

Is this a dedicated terminal server along with SBS08? Or..(gasp!)..are they logging into the SBS08 server itself? If so..I wonder if there is a "log in as a service" permission that SBS isn't allowing, due to...it not really wanting to allow terminal server behavior on itself for direct logins.

 

[Jaxon]

In the end the problem was the UAC. Once it was disabled everything worked fine.


Sent from my iPhone using Tapatalk