x Want to participate? Join the group to interact
  • State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 60 subscribers
  • Views 2661 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
996
replies
Reporting and Analytics
207
topics
400
replies
Soutien Technique - Français
628
topics
1k
replies
Year End Activities
224
topics
596
replies
Kys

database engine reported an error - server 2020 - client 2019

SUGGESTED
Posted By

Clients are unable to open the data files located on the server. 

The Database connection manager service is running(automatic) on the server and currently the firewall is turned off. I noted when clients attempt to open the file, no connections appear to be in use on the server side according to the Sage 50 Connection Manager running on the server.

the error message on the client computers point me to look at the errorlog.txt file, which has alot of information, but means very little to me:

2019-11-20T16:25:05.888690Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-11-20T16:25:05.888690Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-11-20T16:25:05.888690Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2019-11-20T16:25:05.888690Z 0 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.7.18\mysql\mysqld.exe (mysqld 5.7.18-enterprise-commercial-advanced) starting as process 2968 ...
2019-11-20T16:25:44.762853Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-11-20T16:25:44.762853Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2019-11-20T16:25:44.762853Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2019-11-20T16:25:44.763852Z 0 [Note] C:\Program Files (x86)\Winsim\ConnectionManager\MySqlBinary\5.7.18\mysql\mysqld.exe (mysqld 5.7.18-enterprise-commercial-advanced) starting as process 5660

since I am encountering this issue on multiple clients, I am inclined to think something is broked on the server side, but I am unsure what to look for beyond the connection manager. It had been working up til yesterday, but as far as I know nothing has changed on the server.

the data and 'server' are on a windows 10 pro computer, there is no local client software on the computer, only on other devices on the network.

I would greatly appreciate any incites on this issue. possibly upgrading the clients to 2020 may help, but they did not want to change over yet.

  • 0
    SUGGESTED

    Hi Kys

    Assuming all security is off, and firewall are configured 

    Did you try make a test copy of the file to local workstation C:\sage data, if it does opens up then you might have network issue, I would try install sage on server as well, just to test see if data open locally on server, if both computer can open data locally , and you still cant open data across network , then for sure you have network issue.    You can check article 10303  (if file doesn't open locally and you can open sample then you might have a data issue, need go backup)

    hope this helps

  • 0 in reply to Jason.

    I did try copying across to local machine and was unable to open the file. my next step was to restore the backup from the previous day but would not allow the users to login with any of the credentials. going back one day further revealed corrupt file that would not restore; which in turn led me to think there was file corruption on the RAID array the data was sitting on. I went to a server backup which contained the Sage backups and was able to restore a file that did work.

    So they are functional now, but I am confused as to why/how the files corrupted on the server in a RAID1. I did also find errors relating to mysql in the event viewer, but reinstalling sage did not fix these mysql errors, and yet connection from clients is working fine with the restored data file.

  • 0

    Instead of starting my own thread I thought I'd respond to this one.

    I have similar error messages.  The "server" is also a computer used to access SAGE50 and there are a total of 4 users.  My google searching has lead me to thinking this is an issue with packets getting lost in the network, however I find it hard to believe that packet loss is causing these issues since we had these issues in our old office but now we've moved to a new office with new routers/switches/cables and the error messages are still being written to the errorlog and occasionally users have to exit SAGE because "the database could not be found, or the database engine is not running"

*Community Hub is the new name for Sage City