Hello everyone,

Does anyone know why the following error occurs in my workflow?

ERROR: W3610 : Error opening database: Catastrophic failure
ERROR: PlanetPress Database: W1603 : Plugin failed

This error occurs irregularly. When this error occurs, the email database cannot be read and the workflow will stop.

Now my temporary solution is to restart the server. After the server restarts, run this workflow again, and no error will occur at this time.

However, after somehow, this error may happen again.

My planetpress runs under VM, and the operating system is windows server 2016 64bit. Planetpress version is 7.6.2.9999

Can anyone give me advice or suggestions to solve my problem?

My working flow
===============
Folder Capture
|
Change Emulation(ASCII)
|
Set Job Infos and Variables
|
|-----------|
| Planetpress Database
| |
| Change Emulation(Database)
| |
| Set Job Infos and Variables
| |
| Delete
|
|-----------|
| |
| Change Emulation(ASCII)
| |
| Digital Action
| |
| Send Email
|
Delete


Many thanks.

Regards,
Andy

seems the database connection is crashing.
What database you're connecting to?

Hello Martins,

My database is created by Microsoft Access, this access database is already started to use in few years ago.

There is a ODBC system DSN to connect this access database.

This "Error opening database:Catastrophic failure" happen irregularly.

Now, when this error occur, my temporary solution is restarted the server.

However, I really want to know why this error
"Error opening database:Catastrophic failure" occur and how can I solve this problem.

Any idea of my problem ?

Many thanks!

Regards,
Andy

there's not enough information about this error yet to get to the source of the issue.

It may be just an instability of the database driver, which crashes when called too often in a short time.
You should check the Windows event log if there are corresponding messages.

You may also analyse the watch and messenger logs (best after you've increased the logs to the highest level), and try to find out if there's any rule behind that (e.g. big data, calling the database very frequently, …).

And as it may be an issue with the database driver itself, it could be worth to consider an update of the driver.

Hi Martin,

Many thanks your reply. I'll try to do it.

Regard,
Andy