x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 6 replies
  • Subscribers 76 subscribers
  • Views 2858 views
  • Users 0 members are here
Browse Forums
Announcements
78
topics
166
replies
General Discussion
5k
topics
16k
replies
Installation and Upgrades
978
topics
2k
replies
Inventory, Projects, and Departments
339
topics
1k
replies
Payables and Receivables
1k
topics
4k
replies
Payroll
1k
topics
3k
replies
Reconciliation and Banking
318
topics
995
replies
Reporting and Analytics
207
topics
400
replies
Soutien Technique - Français
628
topics
1k
replies
Year End Activities
224
topics
596
replies
Greycat

Trouble running sage over our network

Posted By

Currently we are moving our Sage client to a Win 7 machine and I would like to put the database on a Win XP machine.  I have gotten the Sage client working with the data if it is stored locally (on new Win 7 machine) but when I move the data to the Win XP machine, It gives me a error.


We are running Sage 50 2013 R4 and I have installed the connection manager on the Server (Win XP) machine from the installation disk.  I have shut down the firewalls on both computers (both avg and windows).  The Server is also used as a document server for us so as far as working on the network - this has been established .. all sharing and security permissions are in place (full rights for this user).

I have read through the forum as much as I can and I can't seem to find an answer.


The error that gets displayed it this

"Sage 50 cannot open the database because the database engine reported an error"


I have tried looking for a error log for the connection manager on the server but I can't find one.

The connection manager version we are using is 2.5


I'm the IT guys for a small company not the person who uses Sage  so ....

Thanks in advance for any advice you can give.

Parents
  • 0

    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

  • 0 in reply to Irwin Tech

    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.  

Reply
  • 0 in reply to Irwin Tech

    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.  

Children

*Community Hub is the new name for Sage City