Sage 100

When accessing Application Server Configuration for Sage 100 ERP Advanced (formerly MAS 200) receiving Error: ""Error #11: Record not found or Duplicate key on write"". Details on error: ""Error occurred processing: PERFORM ""config;SessionsFolderDisplay"". NOMADS Stack was: Stmt# 00820, Program (path to) ""..\MAS90\Home\Lib\_Appserv\Config"" accessing Application Server Configuration for Sage ERP MAS 200 The only available option to select is the OK button.

I found this[ KB article ](https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=26302&sliceId=1&cmd=displayKC&dialogID=41266&docType=kc&isLoadPublishedVer=&stateId=41267&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl)and step one (replace config) did not work. Customer only has backup from September 2015 so wondering if anyone has encountered this with more specific resolution than restoring HOME.

Restoring \HOME seems to resolve Customer has lengthy (15-30 second) lag when switching tables between SESSIONS and SERVER Naturally, per customer - AV/MALWARE is absolutely not the cause

Looks as if this is recurring - customer just called again with the happy news that all 30 people in the warehouse were bounced from Sage 100 Advanced

Can run as application. Will not start as service. Are there any different files to clear out that would impact the ability to start as service?

This is the point where I start thinking about punting and use one of the client's five tech support calls and let Sage deal with it. But it is NOT something your client wants to hear.

That's pretty much what I did. Called Sage. They had to put me down for a callback. In the meantime, we figured out the app server would run (just not as service). They're going to watch it a couple days. When there are 40 people suddenly kicked out of Sage and no shipping can happen - customers get a little anxious.

Just a little.....

I know this is an old thread but I had a client hit with this today and Sage (*disbelieving gasp*) was able to resolve without restoring the whole \Home folder so I wanted to share in case it helps anyone. We renamed \Home\Lib\_appserv\Locate.PVK and Sessions.PVK. Then renamed MAS_SYSTEM\SY_Console and SY_Workstation, restarted the service and everything was rainbows...so far.

Just as FYI if happens again you can rename sessions.pvk alone then by starting App Server Config, it will create the new sessions.pvk and fix locate.pvk. Then start App Server service or application. No need to touch sy_console and sy_workstation. But that's just my method. Maybe it's because subconsciously I don't like rainbows.