Sage 100

Workstation out of sync Last thing yesterday we installed Sage Payment and Billing on our in-house system. This morning when we fired up Sage 100 Advanced 2013 5.00.0.9, we get the attached message on every workstation. Nothing in the knowledge base. Ronnie Aspe, Sage Senior Support Specialist says it is a coincidence because noting gets installed on the ERP side. I have uninstalled the workstation setup and reinstalled from the server with no success. If I start Sage 100 Advance in MAS90 mode (pvxwin32.exe) from the Home directory, it opens. Any suggestions.

What is version 5.00.0.9? Only 4 product updates available for 2013.

Is that the version which shows if you have no product updates?

I don't recall installing any updates yet.

What happens if you put in the latest product update?

Yes, that is the default without updates. The updates appear as 5.00.X, one decimal to the left, I believe.

It hell being a pioneer. They tend to get shot with arrows (or is it errors??).

Are there 2 installs running? Sounds like client server application needs reinstalling. Check the port. But definitely PU4 plus hot fix (LM5002 or LM5004, can't remember which right now)

@JoanSerr - What hot fix are you referring to? I just looked at PU 4 and there is only one hot fix referenced for it - BM-5001.

My question to support was if fix applicable for PU's above PU2 then KB should reference so. Per Sage Analyst (Carmen): ""The LM5002-T would go with any of the levels but they should be on at least 3 in my opinion. "" But I don't think that this applies to PU4 & Adv/Pre versions.

LM5002 is for PU 1, should be rolled into PU 2 and above. LM5004 is for PU 2 and should be in PU 3 5.00.0.9 is an un-patched Sage 100 2013 system. I agree with @WayneShultz that you should reapply PU 4 and then rerun workstation setup.

I don't know if it's still true for 2013 but this is how it worked in the past. When you start up MAS 200, the status.flp file from server's \Home folder is always copied to client side \Home folder. Then on client side, status.flp is compared to wkstatus.flp (you can view them yourself in Notepad). If they don't match you get the message. This checking isn't done when starting up MAS 90 style. So check out the FLP files. You know I remember somebody posted this error in 90 Minds a long time ago but can't remember who. The end result turned out to be that MAS was copying the correct file over to client side but due to permissions errors it couldn't overwrite the status.flp on client side. Once permissions fixed problem went away.

Well the problem is solved. There were two services running: one was named MAS 200 9991 and the other named Sage 100 Advanced ERP 2013 ( 9991). How two services were created and with the same port is beyond me. Disabled the one and all started working. Alnoor, could this be a way to get around the ability to have only one 2013 system running on a server? Actually have several installations but just change the Startup Type in Services to ""Disable"" for the ones not being used and ""Automatic"" to one being run. Sort of like a toggle switch

I just used Alnoor's and Harold's advice here to solve a similar problem. Thanks guys.