SageForum for UK versions of Sage 50- Help and support.

Good Day!

We have recently started using Sage 50 2013 and are running in a client server configuration. We have about 5 windows 7 workstations connecting to a Server 2008 R2 virtual server. We are fully patched on the server and the workstations, but it seems the server eventually pegs on the w3dbsmgr.exe process after about 3-4 days of running. We do a restart on the server and the sage services on the clients and all is well until the about the 4 th day..then it pegs again. We only have one company file, have the sage automated backup set up, and are backing up the server in general with Data Protection Manager. The cpu seems to peg early in the morning after a DPM backup. The server is not on the same subnet as the clients.

Any help would be appreciated.

Can you give the full version number.

Are you sure you are running Sage 50, it sounds to me like you might be running Sage50US which is a totally different product with an almost identical name (Thanks Sage!)

w3dbsmgr.exe is part of the persvasive SQL engine, Sage50 does not use that.

If this is the Sage50US version please write to Sage and complain about the confusion created by having 2 products with the same name.

Sorry for the delay in responding...you are correct we have the US version not your version. I will tell them..this is my first experience with Sage and I cannot say I am pleased. I talked with tech support and they basically said they will not support me as long as a run the server on a VM and not a physical box.

Thanks Again !