Sage 100

Long painful story short, I had to register a client's upgraded MAS200 SQL 4.50 earlier this week with my own keys while Sage took 3 days to get me a new set. I connected to the client's system last night to plug in the new keys...activation is successful. However, upon logging in again, I get a message that says ""your product key is not authorized for MAS 200"". I try restoring, reinstalling, etc. and now I get ""SQL is not enabled"" every time I try to launch, which I cannot find anything on Google or Sage KB for. Does anyone have any ideas at all what I could try next to at least get them back on my keys?

Did you go back to your keys or are you still using theirs? It wouldn't be the first time Sage issued bad registration keys.

If you have your own 4.50 SQL system working where you can start up without error then as a temporary measure you could make a backup of clients sy_system table in mas_system database and their activate.pvx file. Then replace these with yours.

Well guys - it didn't seem to matter what combination of files I restored, copied, etc. until I renamed the Uninstall and Uninstall Information folders and then was able to perform an in-place install with my demo keys again. Thank you both for responding.

I recently had a client who re-instated their maintenance. Their new reg keys would not work either - after similar painful attempts and calls to Sage I found that I had to use the clients ""old"" Sage customer account number. (Even though they sent me the registration info using the ""new"" customer account number. I tried to get clarification from sales and support about when we should use ""old"" or ""new"" account numbers for the client. I did not get a clear answer I'm not sure if that will help here or not, but it was suprising to me so thought I'd pass it on.

I've done multiple upgrades and installs since the move to the new portal and customer number, and I do not believe I've ever been successful with the new 400 customer number yet. I do not understand what the problems with their key generation are, but it's irritating and now I can see a little dangerous to change the keys and hope that they work. I had never seen these particular errors before.

My recommendation is to contact Sage a couple days ahead of time and have them test the keys. I did that with a recent client upgrade, and got a new set of keys in advance.

We had a really nasty wrong keys issue with a new MAS client (good first impression of Sage). First set of keys were invalids, second set of keys only unlocked 3 users (they bought 5) and didn't unlock their PO or VI modules they purchased. Finally got new keys on the second day of implementation because Sage said their 'system was down' when trying to generate the final good set of keys.

Story #2...client was renewing maintenance and wanted to save some money (since the price increase on maintenance) so they wanted to deactivate some modules they were no longer using. Took approx a month between our CAM, registration and Sales Advisor to get the modules deactivated and a good set of keys with the deactivated modules (2 attempts to get correct keys as well).

I feel like I'm beating a dead horse but... Story #3. - Client was off maintenance - got back on maintenance and upgraded from 90 to 200 - unlocking keys did not work during installation process (message one or more fields is invalid). Contacted Sage and 2 days later they told us to try using the customers ""old"" customer account number - that got us through the message during installation but - then when we tried to launch MAS200 application server configuration we get ""NO Valid activation found"" I thought it was a rights issue and went through all the troubleshooting for that just to discover that it is NOT rights issue but actually the keys are invalid. Now 24 hours and several e-mails later I'm still waiting on new keys (our Cam also mentioned that her system was down when I first called). Sage needs to get their new system working!

Has everyone seen this?

Yep! Finally hopefully they have a handle on the key fiasco.