Sage 100

Next Sage 100 Premium migration adventure. 2016 install fails on every Crystal print job that it can't find the work table it just created. Tables are there in tempdb, and MAS_User and MAS_Reports permissions are exactly the same as in the 2014 install that works. Sage support is unable to resolve.

What version of SQL? In Mgmt Studio / Security is the password (lockout) policy set for the MAS_Reports account? It sounds like the MAS_Reports section of the settings file in /mas90/home may have something weird stored in there. If you use the Sage SQL Settings utility to change the MAS_Reports password (then change it back afterwards) that should rewrite that part of the Settings file.

Enforce password policy was set, but changing that and resetting the password in SSMS and SQL Settings Utility did not fix the problem. SQL 2008 R2 SP3

So, the company code with the issue is CPA. The IT guy installed the instance as ""MAS_CPA_2016"". Only way to change an instance name is to uninstall and reinstall. #dumbanddumber

Ha!! I could not have guessed that!

@AlnoorCassim - I knew I was screwed when your suggestions didn't work out...