Sage 100

We have a client that has upgraded from 4.10 to 2013 SQL and is running into an issue in the Explore View of all modules. When they access any of the views, they are receiving a message that ""login failed for user MAS_Reports"". In addition when trying to run any standard reports, they are receiving the message ""keyset not defined"". Has anyone run into either of these issues before?

Shawn , there is a login manager routine on the 2013 SQL server. You use it to setup and maintain the MAS_Reports logon.

FYI, it's called SQL Settings Utility and it's in the programs under the Sage folders.

Brett, thanks for the information. I changed the passwords for both MAS_USER and MAS_Reports through this utility, but am still running into the same error message. Can you think of any other area I should check?

Any luck Shawn? I've not seen your issue but I am curious what's causing it.

I am having the keyset is not defined error as well. How was this solved?

We ended up having to totally uninstall and re-install Sage 100 and that resolved the issue.

Is 3 times an epidemic? I'm happily going along upgrading MAS 90 4.10 to Sage 100 Standard 5.00.4, using RDP to connect into a Windows 2012 Server and I have been working on Crystal Reports all day, previewing and designing without any problems. All of a sudden I start getting ""The keyset is not defined."" Now getting it in every report, reran workstation setup, reran WKSUpdate, even installed the 64-bit ODBC driver. Nada. I seem to recall this is essentially the O/S screaming at Crystal but I can't remember how I have resolved this previously. No Sage KB and this is the only post here that references it. I'm asking their IT guy to help, and reports are fine on workstations, just wondering what happened on this server. I would rather not do a complete re-install, probably will just go to workstation for remote connections from now on.