Sage 100

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

Sorry @Greg Stiles, I had missed your reply. 

A couple additional questions, recommendations:
1- just so that you're not spinning your wheels on the wrong solutions, can you try to make the user local admin temporarily and try again? My guess is that it won't work either, because I'm not convinced your issue is permissions related. But this will give you a definite answer regarding that.

2- I'm not sure you mentioned the method of connection to the RemoteApp. Are you using the traditional connection (via Internet Explorer or the Control Panel), or are you using the HTML5 WebClient?

the WebClient only works with Sage 100 Standard, but it can't even launch the Sage client for Advanced or Premium, so just in case you are using it, I wouldn't be surprised if you see weird behavior in it, so perhaps switch to the more mature control panel connection instead and try again.

As far as the installation; we normally still do the change user /install for good measure. I'm not 100% certain whether it's still required​. 

Another couple notes:
- Though we don't have any clients with Paya Published, you can try this suggestion: Launch it first, then Launch the Sage client. 

Some applications don't show their icon in the task tray, even though they are running, can you check the task manager and see if the process is running for that user? (In RemoteApp, In HTML5 and in full desktop) 

- Have you tried clearing the user's Windows Profile (and possibly their Sage 100 folder?)

Hope some of the above suggestions shed some more light on the situation.

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

...I'm not convinced your issue is permissions related...   -  I agree, I don't think it is permissions related either because Paya does launch when a non-admin user RDP's in with a full desktop, but does not launch when we use the RemoteApp.

...I'm not sure you mentioned the method of connection to the RemoteApp...  -   I am not sure, as their IT setup the RDS Server. They sent us a certificate to install, and an RDP icon to copy to the desktop. Not sure if this matters but, Sage is on a remote server on our sister company's LAN, not on our own LAN, and we connect via the internet without a VPN.

...we normally still do the change user /install for good measure...  -   Good to know, I'll go back to doing that as well.

...Launch it first, then Launch the Sage client...   -   I am going to have them publish the Paya app and try that.

...can you check the task manager and see if the process is running...   -   As per task manager, the Paya process is not running when using the RemoteApp, bit it is when on a full desktop.

- Have you tried clearing the user's Windows Profile (and possibly their Sage 100 folder?)  -  I have not, I will try that.

Sorry @Greg Stiles, I had missed your reply. 

A couple additional questions, recommendations:
1- just so that you're not spinning your wheels on the wrong solutions, can you try to make the user local admin temporarily and try again? My guess is that it won't work either, because I'm not convinced your issue is permissions related. But this will give you a definite answer regarding that.

2- I'm not sure you mentioned the method of connection to the RemoteApp. Are you using the traditional connection (via Internet Explorer or the Control Panel), or are you using the HTML5 WebClient?

the WebClient only works with Sage 100 Standard, but it can't even launch the Sage client for Advanced or Premium, so just in case you are using it, I wouldn't be surprised if you see weird behavior in it, so perhaps switch to the more mature control panel connection instead and try again.

As far as the installation; we normally still do the change user /install for good measure. I'm not 100% certain whether it's still required​. 

Another couple notes:
- Though we don't have any clients with Paya Published, you can try this suggestion: Launch it first, then Launch the Sage client. 

Some applications don't show their icon in the task tray, even though they are running, can you check the task manager and see if the process is running for that user? (In RemoteApp, In HTML5 and in full desktop) 

- Have you tried clearing the user's Windows Profile (and possibly their Sage 100 folder?)

Hope some of the above suggestions shed some more light on the situation.

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

...I'm not convinced your issue is permissions related...   -  I agree, I don't think it is permissions related either because Paya does launch when a non-admin user RDP's in with a full desktop, but does not launch when we use the RemoteApp.

...I'm not sure you mentioned the method of connection to the RemoteApp...  -   I am not sure, as their IT setup the RDS Server. They sent us a certificate to install, and an RDP icon to copy to the desktop. Not sure if this matters but, Sage is on a remote server on our sister company's LAN, not on our own LAN, and we connect via the internet without a VPN.

...we normally still do the change user /install for good measure...  -   Good to know, I'll go back to doing that as well.

...Launch it first, then Launch the Sage client...   -   I am going to have them publish the Paya app and try that.

...can you check the task manager and see if the process is running...   -   As per task manager, the Paya process is not running when using the RemoteApp, bit it is when on a full desktop.

- Have you tried clearing the user's Windows Profile (and possibly their Sage 100 folder?)  -  I have not, I will try that.

Sorry @Greg Stiles, I had missed your reply. 

A couple additional questions, recommendations:
1- just so that you're not spinning your wheels on the wrong solutions, can you try to make the user local admin temporarily and try again? My guess is that it won't work either, because I'm not convinced your issue is permissions related. But this will give you a definite answer regarding that.

2- I'm not sure you mentioned the method of connection to the RemoteApp. Are you using the traditional connection (via Internet Explorer or the Control Panel), or are you using the HTML5 WebClient?

the WebClient only works with Sage 100 Standard, but it can't even launch the Sage client for Advanced or Premium, so just in case you are using it, I wouldn't be surprised if you see weird behavior in it, so perhaps switch to the more mature control panel connection instead and try again.

As far as the installation; we normally still do the change user /install for good measure. I'm not 100% certain whether it's still required​. 

Another couple notes:
- Though we don't have any clients with Paya Published, you can try this suggestion: Launch it first, then Launch the Sage client. 

Some applications don't show their icon in the task tray, even though they are running, can you check the task manager and see if the process is running for that user? (In RemoteApp, In HTML5 and in full desktop) 

- Have you tried clearing the user's Windows Profile (and possibly their Sage 100 folder?)

Hope some of the above suggestions shed some more light on the situation.

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders. 

That's a good question Beth. 

I can't say with 100% certainty, as we've had hit or miss success with updating Aatrix. We usually assist clients if they aren't able to update it themselves.

I will take this to our engineering team and we'll test it out, and if we find consistent success with a change of ACL related to Aatrix, I will update this thread. 

We have it running for all our clients in an RDS environment using a published app. We don't publish the Paya app, just Sage 100. 

We also don't use anything unusual for the installation process's we simply run the bootstrapper and update to the latest. 

If your users are not admins on the server, you want to make sure to correctly ACL the appropriate folders.