Sage 100

Hi all,

New install of Sage 100 Premium.

when trying to run any reports get the following error:

The database login failed.  error in file sy_installedmoduleslisting.  etc

see attached screen print of error message.

What we have tried:  verified the sql user MAS_Reports password is correct.  Tested the user/pw in sql studio.  copied/pasted password into the SQL Settings Utility screen.  click test connection, just get the spooling round icon, never get a confirmation message.

Made sure sql browser is running.

check sql error logs - no logon errors appear there.

Any ideas?

thank you,
Marc

------------------------------
Marc Cregan
Technology Integrators
------------------------------

I had success with my recent SQL test upgrade and reports by adding a firewall Program inbound rule on the server that pointed to the C:\Program Files\MASSQL\Binn\sqlsrvr.exe.

------------------------------
Amber Prayfrock, Blytheco
------------------------------

Are Sage and SQL on the same server?  If not, is the server hosting SQL pingable?

Make sure SQL Settings is pointing to the SQL Server Instance Name and not localhost.

------------------------------
Steve Iwanowski, NextStep Technology Advisors, aka DSD Lancaster PA ¯\_(ツ)_/¯
------------------------------

I had a somewhat similar issue but it was Business Insight Explorer kicking out the error. My notes indicate the issue went away when I removed “run in compatibility mode” from the Sage 100 workstation icon properties.

Just an FYI as this may not apply to your situation.

---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
---------------------------------

Original Message:
Sent: 9/4/2020 3:32:00 PM
From: Wayne Schulz
Subject: RE: Sage 100 Premium - Report printing error

I had a somewhat similar issue but it was Business Insight Explorer kicking out the error. My notes indicate the issue went away when I removed “run in compatibility mode” from the Sage 100 workstation icon properties.

Just an FYI as this may not apply to your situation.

---------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
---------------------------------

Run the Sage utility to change the SQL password, but do not test (because there is a bug... documented in the Sage KB).
Use SSMS to log in using MAS_Reports with the password you configured and confirm that allows you to access data.
Make sure the report you are running doesn't have a weird data source (like a DSN).
Recently I had to use the IPAddress/InstanceName in SQL settings (instead of the servername).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Oh, and if you have moved the databases around, run this against all the MAS_* databases (including MAS_SYSTEM).

use MAS_###;

exec sp_changedbowner 'MAS_User';

exec sp_dropuser 'MAS_Reports';

exec sp_grantdbaccess 'MAS_Reports';

exec sp_addrolemember 'db_datareader', 'MAS_Reports';

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 09-04-2020 16:20
From: Kevin Moyes
Subject: Sage 100 Premium - Report printing error

Run the Sage utility to change the SQL password, but do not test (because there is a bug... documented in the Sage KB).
Use SSMS to log in using MAS_Reports with the password you configured and confirm that allows you to access data.
Make sure the report you are running doesn't have a weird data source (like a DSN).
Recently I had to use the IPAddress/InstanceName in SQL settings (instead of the servername).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Hi there, I tried the allow external access. No change still get the error. I tried logging into sql management studio directly as the MAS_Reports user with the pw and am able to login to sql without issue. I ran the sql script to grant access on all the dbs. Still get the same error when trying to run reports. So strange. I'll keep workin' on it here and report back what fixed it. thank you for all the ideas! Marc

------------------------------
Marc Cregan
Technology Integrators
------------------------------

Original Message:
Sent: 09-04-2020 16:23
From: Kevin Moyes
Subject: Sage 100 Premium - Report printing error

Oh, and if you have moved the databases around, run this against all the MAS_* databases (including MAS_SYSTEM).

use MAS_###;

exec sp_changedbowner 'MAS_User';

exec sp_dropuser 'MAS_Reports';

exec sp_grantdbaccess 'MAS_Reports';

exec sp_addrolemember 'db_datareader', 'MAS_Reports';

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 09-04-2020 16:20
From: Kevin Moyes
Subject: Sage 100 Premium - Report printing error

Run the Sage utility to change the SQL password, but do not test (because there is a bug... documented in the Sage KB).
Use SSMS to log in using MAS_Reports with the password you configured and confirm that allows you to access data.
Make sure the report you are running doesn't have a weird data source (like a DSN).
Recently I had to use the IPAddress/InstanceName in SQL settings (instead of the servername).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Hi all - 

Some progress -  in working with the internal i/t dept, it was discovered that on this new server TLS 1.0 and 1.1 were disabled.  We enabled them and now the Crystal reports run as they should with no error.

see this article from SAP discussing the issue with MSSQL, Crystal and TLS:  https://apps.support.sap.com/sap/support/knowledge/en/2269180

Still working with Sage to sort out the issue as they would prefer 1.0 and 1.1 be disabled on their network.

Thank you,
Marc

------------------------------
Marc Cregan
Technology Integrators
------------------------------

Original Message:
Sent: 09-08-2020 18:50
From: Marc Cregan
Subject: Sage 100 Premium - Report printing error

Hi there, I tried the allow external access. No change still get the error. I tried logging into sql management studio directly as the MAS_Reports user with the pw and am able to login to sql without issue. I ran the sql script to grant access on all the dbs. Still get the same error when trying to run reports. So strange. I'll keep workin' on it here and report back what fixed it. thank you for all the ideas! Marc

------------------------------
Marc Cregan
Technology Integrators
------------------------------


Original Message:
Sent: 09-04-2020 16:23
From: Kevin Moyes
Subject: Sage 100 Premium - Report printing error

Oh, and if you have moved the databases around, run this against all the MAS_* databases (including MAS_SYSTEM).

use MAS_###;

exec sp_changedbowner 'MAS_User';

exec sp_dropuser 'MAS_Reports';

exec sp_grantdbaccess 'MAS_Reports';

exec sp_addrolemember 'db_datareader', 'MAS_Reports';

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 09-04-2020 16:20
From: Kevin Moyes
Subject: Sage 100 Premium - Report printing error

Run the Sage utility to change the SQL password, but do not test (because there is a bug... documented in the Sage KB).
Use SSMS to log in using MAS_Reports with the password you configured and confirm that allows you to access data.
Make sure the report you are running doesn't have a weird data source (like a DSN).
Recently I had to use the IPAddress/InstanceName in SQL settings (instead of the servername).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Old post.  Moved to Sage 100 Discussion.

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------

Original Message:
Sent: 09-09-2020 09:48
From: Marc Cregan
Subject: Sage 100 Premium - Report printing error

Hi all -

Some progress -  in working with the internal i/t dept, it was discovered that on this new server TLS 1.0 and 1.1 were disabled.  We enabled them and now the Crystal reports run as they should with no error.

see this article from SAP discussing the issue with MSSQL, Crystal and TLS:  https://apps.support.sap.com/sap/support/knowledge/en/2269180

Still working with Sage to sort out the issue as they would prefer 1.0 and 1.1 be disabled on their network.

Thank you,
Marc

------------------------------
Marc Cregan
Technology Integrators
------------------------------


Original Message:
Sent: 09-08-2020 18:50
From: Marc Cregan
Subject: Sage 100 Premium - Report printing error

Hi there, I tried the allow external access. No change still get the error. I tried logging into sql management studio directly as the MAS_Reports user with the pw and am able to login to sql without issue. I ran the sql script to grant access on all the dbs. Still get the same error when trying to run reports. So strange. I'll keep workin' on it here and report back what fixed it. thank you for all the ideas! Marc

------------------------------
Marc Cregan
Technology Integrators


Original Message:
Sent: 09-04-2020 16:23
From: Kevin Moyes
Subject: Sage 100 Premium - Report printing error

Oh, and if you have moved the databases around, run this against all the MAS_* databases (including MAS_SYSTEM).

use MAS_###;

exec sp_changedbowner 'MAS_User';

exec sp_dropuser 'MAS_Reports';

exec sp_grantdbaccess 'MAS_Reports';

exec sp_addrolemember 'db_datareader', 'MAS_Reports';

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 09-04-2020 16:20
From: Kevin Moyes
Subject: Sage 100 Premium - Report printing error

Run the Sage utility to change the SQL password, but do not test (because there is a bug... documented in the Sage KB).
Use SSMS to log in using MAS_Reports with the password you configured and confirm that allows you to access data.
Make sure the report you are running doesn't have a weird data source (like a DSN).
Recently I had to use the IPAddress/InstanceName in SQL settings (instead of the servername).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON