Sage 100

v4.4 std, via terminal server session. User was having IT issues so staff created a new remote user profile. Now when she logs into MAS the following message appears. Unable to do anything in MAS. I think it is some type of Windows rights issues, but their IT staff is stumped. Any terminal services guru's out there?

Are the security rights congruent? If file security on the MAS installation uses domain security is she logging into the TS as a domain user that has rights to the MAS install? Myron Stevenson

I'm thinking the failed to create key has to do with writing a record to the workstation file? Seems vaguely familiar

I would make her an administrator and then try to run the app. If it works, then we know it is security. If it is security, I would try and edit a text file in the MAS folders on the server and on the workstation to see if either are read only. If you can write to both of those locations, my next guess would be security in the registry.

@JeffSchwenk Just wondering how you resolved this issue? I have one user having this same message, this just started happening on an existing workstation with existing user network profile, but they are not connecting through via terminal server. Security does not seem to be the issue??; they can create/edit/save a text document under the MAS200 client on the workstation. TIA

My notes are sketchy so I am not sure what really happened. I talked to the guy who fixed it he wasn't sure what happened either. I have to get better at posting solutions. So Sorry....