Sage 100

Working on a little baby fricking upgrade (4.4-4.5) from hell. Seemed to have finished OK finally, but trying to run MAS90 it says ""SQL is not enabled"". NOW WHAT???????

Keys?

Not changed.

I had that same issue with a MAS200 SQL 4.50 upgrade a few weeks ago and it WAS the keys. Sage ended up issuing me 4 sets of keys over a 2 week period. You can test this theory by renaming the Uninstall and Uninstall Information folder of the current install, re-install program files with your own ""demo"" SQL keys and then try to launch MAS200. That ""SQL is not enabled"" was throwing me for a loop though because I have never seen that message before.

See, the thing is - this is a MAS90 upgrade. It is NOT an SQL upgrade.

I still wouldn't trust the keys I guess. But that's the only time I've ever seen that was with a 4.40 PVX > 4.50 SQL upgrade.

I didn't even have to put the keys in - I was just loading over the 4.4. Thank goodness I made a backup on the drive. Looks like we'll be trying this again after my vacation. This is a single user system with just 7 modules, of which they only use 4. One would have thought this would be a slam dunk. AAAAHHHHHHH!

Can you rename the activate.pvx from the home\_lib\keys folder on 4.50 and then copy in the activate.pvx from the 4.40 install?

OK, talked to my MD friend and here's what it was - there is a file SY_SQL.pvc in the SY folder (that should not be there - I have about 10 SY_SQL files in there that shouldn't be there) and startup was looking at that to determine it was an SQL installation - it wasn't even looking at the activation key yet! I renamed that file and now it's running on the same keys it had been running on. I have no idea how those SQL programs got in there - they have no mods, and like I said - I think I would have noticed if I accidentally clicked on the Install SQL option instead of MAS90... Converting files now. We shall see how it goes.

FWIW, every MAS 200 install I have done in 4.5 shows the Application Server service as 'Sage ERP MAS 200 SQL' followed by the port number in the Services app. On the first one I thought I had made the wrong choice. Everything works normally, it just appears to be labled wrong.

@BethBowers Are you really going on vacation or are you bringing your laptop for just a change of scenery?

I AM SO GOING ON VACATION! No laptop for me! (But I will take my phone and I have done support at Animal Kingdom before...)

@BethBowers Good for You! We all need to ""unplug"" once in a while.

I wonder if these SQL files are being put out there for the CRM integration...............

I would have gone with that, if I hadn't checked my 4.50.3 folder and none of them were in there...

@JohnBroadfoot, I just noticed that same thing this past Tuesday on a MAS 200 4.5 upgrade - that the Service name for MAS 200 shows as ""Sage ERP MAS 200 SQL 9222"". A first I too thought that we somhow installed the SQL version but knew that didn't happen. I never noticed it before but maybe that's because it's been a pretty long time since I ran the Appl Serv as a Service and/or that this is a 4.5-specific thing. Their IT guy decided to enable the Service after the fact so that's how it got in there.