Sage 100

What is going on? All I did was reinstall 4.50 and PU6 (they were on PU5) because this client was getting some odd security errors when running various tasks in MAS. I have uninstalled and reinstalled the workstation setup and now I can't launch MAS because it says SQL is not enabled. This is not a SQL install of MAS. Why does MAS call the service SQL now? I've seen this before and am at a loss to understand this. Even the workstation setup under the Start menu refers to the shortcut to MAS as Sage ERP MAS 200 SQL Desktop. This is only a MAS 200 install and I did not choose the wrong option when installing the software - I am dumbfounded as to why it thinks it is SQL and why it gives the message the SQL is not enabled when trying to launch MAS. Heeellllpppp!!

I did not enter any new keys.

Could this be a keys issue? Did you use new keys? Assuming know but taking a wild guess. I could swear I've seen this error kicking around somewhere.

Is it possible someone at the customer tried reinstalling before you did?

Not at all possible.

Does ACOM use SQL server?

Yes, ACOM is SQL based but that shouldn't affect MAS.

So when I launch MAS and it says SQL is not enabled, could it really be a SQL server issue? I saw a posting on the MAS forum about that same message appearing when there was a firewall problem.

Sorry, not my area of expertise. I have one client using ACOM. Because they are heavily modifed for a warehouse management software, I don't stay current with the PU's. What if you launch in 90 mode?

PU6 probably put down a patch for Sy_Sql.pvc in the SY folder. It's signals to the start up program that it's on a SQL system. So rename it.

@AlnoorCassim you are worth a bouillion of gold ... that worked! I can get into MAS now. PHEW!

That's good to know. I ran into this the other day with a client adding a new workstation - the WKSETUP kept saying SQL.

@BethBowers I'm glad to hear that you saw this too on a workstation setup. This sounds like something PU6 must have added in for some reason. It is VERY CONFUSING to see SQL come up!

I don't remember for sure how we got around it - I think we found another WKSETUP somewhere and ran it. But of course that meant something that should have taken 3 minutes took a half hour...

@JaneScanlan and @BethBowers did you notice that the services also say SQL - this is definitely from sp 6.

@DianeRuth Yes I saw that too - SQL everywhere! Not sure why Sage would have done this .. all it did was set alarm bells off for me, especially when I couldn't launch MAS!

It is just sloppy SP that we are getting. Fix one thing and break or change something else.. Nothing is just easy anymore.

Agreed!

I've said this before sort of jokingly, but I seriously think we should start sending Sage invoices for doing their QA work for them.

On the flip side we should be appreciative that Sage looks to be unable to get their act together. There is virtually no way I can see them offering the majority of our support customers (people large enough to pay us for ongoing annual plans) the ability to self-upgrade. New round of executives in Irvine but same old problem. They come in all full of enthusiasm. They're going to change the world. Then in 2 years it's reorganization time and all those EVP start to trickle out and new ones come in with the same bluster but essentially retread the old ideas of past regimes. This whole cross-sell thing has been tried and done. I distinctly remember the push to sell fixed assets and MAS 500. Once the low hanging fruit was picked the whole campaign dried up and blew away.

This bunch seems to have their noise-cancelling headphones screwed in so tight they might implement the automatic upgrades anyway...

Let me know when this gets posted on linked in so we can see someone dancing around it...

Hmmm...do I want to work with software so buggy my clients need me or do I want to work with software so capable and multifaceted my clients need me?

Just wanted to mention I got this when I added CRM to a client on 4.5 - and did NOT put them on SP6. I got it from the original install.

So it is the addition of CRM that makes MAS thinks it is SQL? Is that because CRM is SQL-based?

Beats the hell out of me - just pissed it took me a while to find this thread again. :-(