Hi Nelson,

How did you verify the MAS_User password? If you didn't use the SQL Settings Utility in Sage you should double check using that?

I'm assuming you've read KBs 75325 & 111140.

Your SQL Instance is setup using Mixed Mode, not NT Authentication, right?

Thanks for the response.  We used the SQL setting utility to verify the password and test the connection.  SQL is using mixed mode.  Can you email me link to KB 75325 and 111140.  We looked at all the Sage 100 premium articles on Sage's knowledgebase but just want to confirm.  And how do you search the KB number directly?  I tried searching for KB 75325 and nothing comes up.  Thanks again.

Here is 111140:

Summary

Cause

Resolution

Delete the User in User Maintenance with the dash and create a new User code without the dash in User Maintenance.

And here is 75325:

Summary

Error: "15 SY_ReportCommon.pvc 1688" when printing for a specific company

Cause

The SQL instance name has the company code as part of the name.

• Instance Name = MAS_ABX_2016 and Company Code is ABX
• Instance Name = MAS_123 and Company code is 123 

Resolution

Change the SQL Instance Name or the Company code

Obviously there is not a whole lot of info in these 2 KBs, but you never know. Back in the old days we used to see where someone would have the MAS90 folder in a MAS90 directory, or a company code of SOA, etc. Caused odd problems. I always recommend that people stick with 3 character user codes, company codes, etc. just out of habit.

To answer your other question, I just originally entered the text of your error (with the Statement number I didn't get any results, so I removed that):

If you want to search for a specific KB # you should just be able to key in that number:

 

Thanks.  Yes we did look at those 2 articles prior.  There are 2 companies setup in this fresh install, ABX and TST and we're getting the error on both companies.  The user code is all chars, no special characters. 

Figured those were long shots. Hopefully your SQL Admin will be able to track down the issue and resolve it. You may also want to open a ticket with Sage Support, if you haven't already done so.

Try this on all your MAS_* databases (including system) to ensure MAS_Reports has correct permissions to them.  Also ensure your tempdb has enough disk space to grow as needed.

use MAS_xxx

exec sp_dropuser 'MAS_Reports'

exec sp_grantdbaccess 'MAS_Reports'

exec sp_addrolemember 'db_datareader', 'MAS_Reports'

Try this on all your MAS_* databases (including system) to ensure MAS_Reports has correct permissions to them.  Also ensure your tempdb has enough disk space to grow as needed.

use MAS_xxx

exec sp_dropuser 'MAS_Reports'

exec sp_grantdbaccess 'MAS_Reports'

exec sp_addrolemember 'db_datareader', 'MAS_Reports'

Still no luck.  We opened a case with Sage support.  Will post the resolution as soon as the issue is resolved.  Thanks.