Sage 100

 View Only
  • 1.  IT rampaging about changing passwords in 4.5 SQL.

    Posted 02-12-2016 09:49
    IT rampaging about changing passwords in 4.5 SQL. Now when attempting to start up we get SY_SQLNotEnabled. WTF?


  • 2.  RE: IT rampaging about changing passwords in 4.5 SQL.

    Posted 02-12-2016 10:00
    Was it changed directly in SQL or through Sage's SQL settings utility on the start menu?


  • 3.  RE: IT rampaging about changing passwords in 4.5 SQL.

    Posted 02-12-2016 10:08
    First it was changed directly in SQL, then we found instructions on Sage's web site. The instructions have you change both for the MAS User and the MAS Reports. I didn't watch him, so who knows what he did.


  • 4.  RE: IT rampaging about changing passwords in 4.5 SQL.

    Posted 02-12-2016 10:21
    On hold at Sage now. I'm getting out of this sh*t storm as fast as possible.


  • 5.  RE: IT rampaging about changing passwords in 4.5 SQL.

    Posted 02-12-2016 10:38
    OK, there seems to be a solution. I'm letting Sage and the IT guy fix it up.


  • 6.  RE: IT rampaging about changing passwords in 4.5 SQL.

    Posted 02-13-2016 15:40
    and the answer was????


  • 7.  RE: IT rampaging about changing passwords in 4.5 SQL.

    Posted 02-14-2016 07:03
    I do not know for sure if this is what they did, but it was on the KB - UNDER a different message, which is why I did not find it. Or because I suck at searching the Sage KB. Whatevs. Sage Premium uses MAS_User, a SQL user account, to connect to the SQL Server's databases. This user account is mapped to MAS_XXX and MAS_System databases and is created during installation phase. Also a random password is also created at that time. This message ""SQL is not enabled"" occurs when the ""MAS_User"" on the SQL server cannot connect the databases. This happens if the user or the password are not synchronized between the application and the SQL server. Typically this happens after one of the following: 1) After a new installation of Sage Premium and these objects where not created properly. 2) Restoring database (s) from back up. And the MAS_User needs to be remapped 3) Restoring database (s) from another server. And the MAS_User needs to be remapped The function of keeping ""SQL Users and passwords"" in sync is managed by a System Administrator Resolution To map MAS_User to the databases 1 From SQL Server Management Studio map the SQL Login ""MAS_USER"" to MAS_XXX and MAS_System databases 2 Select the Database > Files > Owner and browse to MAS_User and select and OK ????