Moving this post to the Sage 50 CA Support Group since it was posted in the incorrect forum.

Thanks,
Derek

Hi,

Before you go much further in troubleshooting, shut down everything (including the workstation / server where the data is stored), and start it back up again.

The 'errorlog.txt' is just a startup log for the database. All the log messages you posted are normal.

(Including the one regarding the RSA private key file, it doesn't seem to be required for Sage 50 on Windows.)

If there was a problem, instead of [Note] it would show [Error], like this attempt to open the database, I think this was after someone left the file open in Single User Mode and went on vacation:

2016-03-07 08:24:05 7924 [ERROR] InnoDB: read can't be opened in .\ibdata1 mode
2016-03-07 08:24:05 7924 [ERROR] InnoDB: The system tablespace must be writable!
2016-03-07 08:24:05 7924 [ERROR] Plugin 'InnoDB' init function returned error.
2016-03-07 08:24:05 7924 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2016-03-07 08:24:05 7924 [ERROR] Unknown/unsupported storage engine: InnoDB
2016-03-07 08:24:05 7924 [ERROR] Aborting

There is another 'ExceptionError.log' file that may show what happened if there was a crash.

The Check and Repair tool makes a backup and writes a log file somewhere in the My Documents / Documents, in a folder under 'dbVerifier'.

I hope that helps, please post back.

Randy

Thank you Randy.

I did shut down everything, and restarted, then sage worked fine with no data loss.

But this situation seems keep happening.

Now I got this msg again:
Sage 50 can't open the database because the data engine reported an error. Please see the error log for more information.

.....................
Now I am thinking to make random backup in case the situation keep happening then data loss............

What is the problem?

Please help ！
Judy

JUDY@RIVER said:

I did shut down everything, and restarted, then sage worked fine with no data loss.

It sometimes works

JUDY@RIVER said:

But this situation seems keep happening.

And it sometimes doesn't work, or stops working.

From here, I can't guess what the cause of the problem is, there are too many possibilities to list them all.   If this is happening to a single workstation that is also the place where the data is, there could be a hardware problem, malware, or antimalware, or some configuration issue that's causing the disconnection.

If this is happening between workstations where data is on a separate workstation from the one the data is entered on, then it could be any combination of network, firewall, malware, hardware, software, and configuration issues.

It's important to turn on the automatic  backup, so that you have a good backup from each day time you close the company file, and at least once a week or so, make another one to a portable device such as a memory stick.

Computers are pretty cheap compared with troubleshooting time.  If the thing is old, it might be cheaper to swap in a new one. 

<edit>

Unfortunately, if it's new, you're not guaranteed that there will be no problems, either.  Today's workstations are generally configured to get you to the 'Store' to buy 'Apps'  (FreeCell now costs *money*.)    Some of our desktop applications that were designed around Windows 3, in 1990, barely work.

At one time, Accountants and Engineers probably bought most, if not nearly all, new computers.  It's now nearly the opposite.  

RandyW said:

It's important to turn on the automatic  backup, so that you have a good backup from each time you close the company file...

Randy,

This is a picky, picky point, but if you are talking about the red area of the Backup settings in the image below then please be aware this is NOT every time you close the file, all the time.  As it says, "when the file is FIRST closed for the day".  When people leave for lunch and close the program, they will get the backup done (I believe) if they are the last person closing.  If that backup has been done, it won't happen at the end of the day.  If someone keeps the file open at all times during the day, then the backup will happen at the end of the day but only if everyone exits the program.  Some companies will keep the program open on one or more computers 24 hours a day.  This backup will never happen under those circumstances.

For others looking on, these are not my default settings in my file.  They are the settings from my 2016 reporting sample file.  I'm in and out of it several times during a day and don't wish to wait for the backup to happen.  I believe any backup at any time is a good backup when you need to recover.  It allows you to have the most options, and as Randy says turn it on in a live file, even if the tech people are doing server backups each day.

As for Judy's original problem, if the Connection Manager is having a problem starting or keeping the file open, then there is probably a problem with the firewalls or some network connectivity between the workstation and the server.  I don't know the setup or circumstances, so I can't really help much further but it is possible there is some information in the Windows Event Viewer.  I believe there is a Knowledgebase article about getting that information somewhere.

One thing that has been coming up again recently must be because people are starting to get new computers again.  Many computers defaults or initial setup scheme involves turning on all energy conservation possible.  When computer's hard drives and network cards are set to sleep after unused time, they will stop the flow of information from the workstation to the server where the data file is located.  When the Connection Manager senses the works station stops answering it's requests, then it assumes it's not there and if no one is there, the Connection Manager is set to shut down the database.  If Sage 50 is really still open on a workstation where the hard drive has slowed or stopped turning, then it will error and crash when it attempts to find the file again.

Richard S. Ridings said:

I don't know the setup or circumstances, so I can't really help much

I did some time in telephone support in the mid-1990's.  Communication technology has improved, but the level of detail that a lay person first communicates about a problem has not.

More often than not, walking someone through how all the parts of a system work together, leads to a solution.  

i.e. "Everything was working until my partner left for the day.  "

"Is the data on a network?"

"Not really, it's a LanTastic setup where... Ohhhh, I bet he shut off his computer again..."

The original post is a "usually works, sometimes doesn't" but it's not entirely clear when / how it works, and doesn't.   With a jumble of default configured automated parts that can turn themselves on and off at random times, from the person at the keyboard the problem looks as random as a lightning strike. 

The best troubleshooting tool is a piece of paper.   Write down who, what, when, where, and why.  

There's always a pattern.

P.S.  If you don't think your desktop computer needs a UPS, think again - it's thunderstorm season!