Sage 100

Just found out about this. The article has not yet been made public as it is still in technical review. SAGE is working on making it available. INFORMATIONAL ** THIS INFORMATION HAS NOT BEEN VERIFIED ** ""Unlock Region Failure"" or ""'AP_Options file not found"" in various tasks in MAS when using Windows Server 2008 Domain Controllers Entry Type: Informational Product: Sage MAS 90 ERP Sage MAS 200 ERP Sage MAS 90 Extended Enterprise Suite Sage MAS 200 Extended Enterprise Suite Application: Library Master Version Reported: 4.40 Subject: ""Unlock Region Failure"" or ""'AP_Options file not found"" in various tasks in MAS when using Windows Server 2008 Domain Controllers Possible Resolution: The error is not caused by a MAS setting. This will occur if the Microsoft Kerberos ticket policy is set to the default renewal time of10 hours (600 minutes) and users have been logged into their workstations for more than 10 hours. Messages that occur: ""Unlock Region Failure"" will appear if users are logged into their workstation longer than 10 hours. ""AP_Options file not found"" or""Activation file not found"" etc if users are logged into their workstationovernight. Note: Sage Customer Support is not responsible for assisting with system issues and takes no responsibility for changes made to your operating system or for errors in these instructions. Consult your computer technician or network administrator before making changes. Increase the ""Maximum lifetime for user ticket"" to greater than10 hours or instruct users to log off their computers each night. NOTE: Do not disable or set the value to unlimited. Click Start, and then click Run. In the Open box, type Gpedit.msc, and then click OK. In the Group Policy Management Editor console, expand Default Domain Policy, expand Computer Configuration, expand Policies, expand Windows Settings, expand Security Settings, expand Account Policies, click Kerberos Policyand then double-click Maximum lifetime for user ticket. In the Properties dialog box, increase the Policy Setting, and then click OK. Related Articles: ""Unlock Region Failure - Likely Network / Hardware Failure"" in various tasks Note: Sage cannot guarantee nor be responsible for the content of third party Internet sites. Contact that site's webmaster with questions or problems. Microsoft knowledge base article on Windows Server 2008 Account Policies

I think this is one that I saw during an upgrade. It was almost impossible to debug until I asked the customer to please log out at night. They were not logging out nightly and just kept their computers logged in continuously. As a side note the IT person (some cowboy subcontractor) totally attempted to throw us under the bus with a 15 person cc: about how MAS90 was definitely the culprit an it was definitely a MAS error and not the network. Ultimately these types of issues which are largely IT / network related are what I'm using to justify prices increases on support plans.

In the hosted environment we automatically disconnect a session after an hour and then reset it after 2 hours. We did this for security, but also we found 1) fewer session errors and 2) in larger environments where we were able to load balance people often didn't reconnect properly and would have 2 sessions and licenses if they logged in from home, etc.

@GaryFeldman - I assume you mean after an hour of inactivity? I assume this is also a MAS 200 environment. How do you determine inactivity. Are you using the MAS functionality?

So what happens is a 2003 server is the domain controller and MAS is now on the 2008 Standard server? Which is the issue with my client....

Sorry i didn't reply last year... lol. Our timeouts are Citrix based inactivity, but It can be also be domain wide policy or adjusted in the group or individual through terminal services profile as well. We never put the application on a domain server, but on-premise in small companies that is not always an ""affordable luxury

@JimWoodhead - Do you mind if this KB is posted over on the OASIS side?

Not at all.

Keep me informed, as my client thinks I am totally whacko at this point and the IT guy says MAS90 all the way - no big surprise there...we've all been here..........

New Update: they just keep coming...............It appears we have a couple of issues. User logging in via Terminal Server (RDP to Windows 2008 Server) has a stuck session @14k KB......how can that be. First of all he only has rights to inquiry, so there is no freakin' way he can do anything to generate a task that large. But I just saw UAC is turned on. Should this be turned off at the Server as well as all workstations?

See other thread: https://90minds-com.socialcast.com/messages/15679651