Greycat:

I have encountered many network issues with multi-user Sage 50 installs. I would be more than happy to help but this is a chargeable service. Call me if you need my assistance.

I have also worked on a lot of issues with networks and DB structures..  If you need help send me an email at [email protected]

thanks

Casey

Hi,

On the server machine, the Connection Manager may create an Event that you can view.  

There's also an error log stored in the data folder.    

i.e. if the 'filename' is NASA.SAI, the data folder is NASA.SAJ

If the volume is NTFS, and the program works from the XP machine with the user ID that you're connecting from the other machine with, it should work.  If that's checked, the problem is a network issue.

Starting the database server daemon can be a rights issue, it seems to use the same share access rights as were used to make the SMB connection. 

sometimes the communication problem is a firewall or other networking problem.  Sage 50 uses SMB to establish the connection, then TCP/IP to connect the MySQL db to the client.

I've worked on  a lot of issues with Sage 50 too, but I'm not really set up to do consulting and support.

I hope that helps, please post back.  

Although you can setup an XP as a server, its not a good idea with Windows 7 environment

Thanks for the advise ... I tryed a few things, but none of them worked ... I will be on holidays for the next 10 days so I will address this problem again when I get back ...

Hi Creycat,

You may also want to have a look at this knowledge base article when you have time.

11112 Error: "The Connection Manager could not start the database engine. The database engine reported an error" or "Cannot open company, there is an error connecting to a database"

Hope this helps.