Sage 100

This is my demo environment. I don't see my Sage 2019 SQL database in here.  I had loads of problems with my NFR keys, but I got the SQL version installed, for sure, because I had to provide my SQL information ( I think I chose SQLEXPRESS local, and authenticated with the sa login) during install of Sage 100.  But on launching Sage 100, I get "SQL is not enabled."
#Sage100 #SQL #2019​​​

------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

During the install MAS_SYSTEM should have been created in the SQL instance provided.  Check the Sage 100 Premium 2019 SQL Settings utility, which should tell you the name of the SQL server/instance.  Perhaps you used something different, and that SQL Service is not running.

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

Ah-hah, no worky!  Thank you, Kevin.  What does the MAS_REPORTS login represent?  UPDATED:  You know, I created a password for sa during my install because it wasn't accepting a blank password.  I am not sure that password stuck, now. I can't authenticate with it. PLUS, it has an X. 


------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

Original Message:
Sent: 05-10-2019 09:57
From: Kevin Moyes
Subject: First SQL install question

During the install MAS_SYSTEM should have been created in the SQL instance provided.  Check the Sage 100 Premium 2019 SQL Settings utility, which should tell you the name of the SQL server/instance.  Perhaps you used something different, and that SQL Service is not running.

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

When installing, don't use "local" or anything like that... use the server name.  We've had problems like that before.  You're going to have to re-install.
MAS_User is the database owner, used by the Sage service to read-write data during normal operations.
MAS_Reports is used as the ODBC authentication when printing a report from within Sage 100.
If your Windows login is sysadmin, you can probably reset the sa password through SSMS.

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

Original Message:
Sent: 05-10-2019 10:04
From: Rhonda McNamara
Subject: First SQL install question

Ah-hah, no worky!  Thank you, Kevin.  What does the MAS_REPORTS login represent?  UPDATED:  You know, I created a password for sa during my install because it wasn't accepting a blank password.  I am not sure that password stuck, now. I can't authenticate with it. PLUS, it has an X. 


------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------


Original Message:
Sent: 05-10-2019 09:57
From: Kevin Moyes
Subject: First SQL install question

During the install MAS_SYSTEM should have been created in the SQL instance provided.  Check the Sage 100 Premium 2019 SQL Settings utility, which should tell you the name of the SQL server/instance.  Perhaps you used something different, and that SQL Service is not running.

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

------Original Message------

When installing, don't use "local" or anything like that... use the server name.  We've had problems like that before.  You're going to have to re-install.
MAS_User is the database owner, used by the Sage service to read-write data during normal operations.
MAS_Reports is used as the ODBC authentication when printing a report from within Sage 100.
If your Windows login is sysadmin, you can probably reset the sa password through SSMS.

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

After changing many things to no avail, I had success. Probably something that didn't really change til I rebooted. I think the main things that resolved this were:
Changing SQL authentication to BOTH Windows & SQL authentication
Changes to Windows Firewall and Norton
Installing Sage to the server: <Computername>/SQLEXPRESS. 
Thanks, Kevin! I hope this helps someone else try the SQL version. :-P



------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------

Yes, mixed mode authentication is required.  Sage uses SQL logins to do everything.
One other setting which is less obvious, and 100% required is the SQL collation method.  Without this being correct, there will be data corruption.


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

Original Message:
Sent: 05-13-2019 10:14
From: Rhonda McNamara
Subject: First SQL install question

After changing many things to no avail, I had success. Probably something that didn't really change til I rebooted. I think the main things that resolved this were:
Changing SQL authentication to BOTH Windows & SQL authentication
Changes to Windows Firewall and Norton
Installing Sage to the server: <Computername>/SQLEXPRESS.
Thanks, Kevin! I hope this helps someone else try the SQL version. :-P



------------------------------
==================
Rhonda McNamara
Customer Success Manager
Stewart Technologies, Inc.
rsm@stewarttechnologies.com
------------------------------