Sage 100

Same Client that was having the missing company problem is now having an issue with only one user logging in (MAS 200 SQL v4.5). He is getting a ""File 'CI_Option' not found"" when logging into Mas. They are using Terminal Server, and it is only the ONE user that cannot log in.. here are the details from the error log: Error #12: File does not exist (or already exists) Program IM_Options_svc.pvc Line 67 General Information: File CI_Options Last Key Value Last Key Text Last Channel Opened 32755 Last Channel Accessed 32754 Object Number 100014 Object Method BuildTermString Object Text IM_Options_svc Since it is only the one user having an issue I am not sure where to start. I have verified the user is not using a unique role or company, and that both company attempting to be accessed and role in play are currently being used by other users. Can I reset just one users account?

First I'd make sure to check if the user can get in via a local login vs Terminal Server. Two things that I'd check are: a. Is this user defaulting to a ""bad"" company upon login? b. Does this user have proper network rights? c. Can any other Sage 100 user sit down at this users Terminal Server connection and without logging out from TS can they login to Sage 100 using their user login?

I will check on those issues and report back, Thanks Wayne :)

Is it happening on login or after login when they try to open a task in MAS? If the latter it could be this. For this user in the location where Workstation Setup was run (on the TS in this case) in the local /mas90/Launcher/sota.ini file in the [Config] section there is a line that contains the server connect info. On that line there is a PATH= clause. Usually it's a UNC path. Whatever is in there it must be valid relative to the server. One client got is error from their remote location going in over VPN because the path= said M:\Apps\Mas90 - that was valid from the remote location but not from the app server. If I mapped a M: drive on server error went away. Eventually had IT guy use UNC using a IP address instead of server name as the permanent solution. Hope that helps.

I was just informed they have Unified Logon turned on, so it appears it may be an issue with Active Directory? Once again... putting this on hold until potential network issues are ruled out. Thanks again for your help everyone. I will keep you posted!

Ensure there is not a password specified in User maintenance for the user account. Temporarily give the user's active directory account admin rights to rule out a permissions issue.