Sage 100

This just started happening at a 4.50 client: after they run the PO Daily Receipts Registers and the update completes, they then get a message pop up ""SY_Role Security does not have correct permissions"". The message has an Info and an End button. Clicking the Info button does nothing; clicking the End button makes the error go away - the receipt register has already updated and it udpated correctly. They print to Paperless, the Sage PDF printer is all good. The user has full security on everything - all boxes are checked on in their role. I have tried rerunning the workstation setup but that did not help. I looked in the System activity log and no error posted. I've searched Sage and Google and here and can't find any postings on this issue. What the heck is this error message?

It sounds like 1 of 2 things. Incorrect system permissions. or Could be related to file corruption in one or all the following files: SY_User.m4t SY_UserSecurity.m4t SY_Role.m4t SY_Role Security.m4t Restore these files from backup or install MAS 90 into new location to create new files, then copy those file into production system and recreate roles and users.

Thanks @BuffyLubinski I will give that a try.

Is ODBC security in use?

It hasn't happened to me in a 4.50 install, but I used to run into issues where I would have to turn ODBC security off and back on again. (more of a ""grasping at straws"" approach)

No ODBC security is in use - never has been at this client so this should not be an issue.

That is not the complete set of security files. It also includes sy_surrogate and Sy_ODBCSecurity. They should be treated as a single set. There might be more security files in 2013. Also sometimes these descriptive errors are a red herring so be careful.

OK, thanks @AlnoorCassim. Appreciate the additional info.

Jane, Do you know if there is a variance created by the receipt register? It could be security for the Variance Register... just a thought.

I experienced this error at one client with ""beefy workstation security"". All we had to do to eliminate the error was turn on ODBC security, and turn it back off again. Best of luck to you.....

@RichardBryant the role has rights to everything, so that is not the problem. But your mentioning the variance file made me check the data file to see if there were any leftover records in there because I remembered another problem where records were actually left in that .wrk file .. but there were none this time. @KathleenMatthews I'm giving the turning on the ODBC security a shot, and then turning it off. Thanks for the suggestion.

We had a problem with a mangled security situation. We recreated a role and user and that solved it.