YES! I have this problem with multiple users EVERY TIME we reboot our dedicated server. Some times it takes multiple reboots of workstations before they will connect. I DREAD having to reboot the server for updates, because I know everyone will be calling me because they can't run Timberline or Timberscan. 

Thanks for your reply, Barb.  Have you raised this issue with Sage Support before?  If so, did they provide any advice other than to restart the clients?

No, I have not pursued with Sage. I presumed it was something wonky on our network/server that was causing the issue. Telling users to reboot at the end of every day or after the server is rebooted after hours is not going to cut it because you know they won't remember to do it. Until they can't get TL to run. Then they'll call me complaining that they can't get in. I don't remember having this problem before upgrading to 20.3.

3012, 3014, 94, 170, 171 PSC Pervasive/Actian Error Transaction or Relational Engine (Desktop hangs)

How do I uninstall Pervasive/Actian?

How do I manually install Actian PSQL version 12?

I had a similar issue and tech support sent the following links. They worked for me.

3012, 3014, 94, 170, 171 PSC Pervasive/Actian Error Transaction or Relational Engine (Desktop hangs)

How do I uninstall Pervasive/Actian?

How do I manually install Actian PSQL version 12?

Thank you for all of your replies.  We've done some additional investigation and testing and found that the subset of affected users are those who have Sage 300 CRE & TimberScan but do NOT have Sage Estimating.  Estimating removes the Actian Client v12 and installs an Actian Server Engine v12.

The same Server Engine v12 is also the recommended installation for running Sage 300 CRE on a RDS server.  Our RDS users also have never had a problem.

This evening we are going to remove the client version and install the server version on an impacted PC and keep the PC logged in, restart the Sage server and then test the connection from the test PC.  If it works, we will consider rolling out the Server Engine v12 to the PC's who have this problem.

Normally, we'd just tell the users to restart at the end of the day, but when one of the complaining users is the CEO of one of your best and biggest clients then you make concessions and chase things down.

3012, 3014, 94, 170, 171 PSC Pervasive/Actian Error Transaction or Relational Engine (Desktop hangs)

How do I uninstall Pervasive/Actian?

How do I manually install Actian PSQL version 12?

3012, 3014, 94, 170, 171 PSC Pervasive/Actian Error Transaction or Relational Engine (Desktop hangs)

How do I uninstall Pervasive/Actian?

How do I manually install Actian PSQL version 12?

Our testing last night confirmed that installing the "Actian PSQL v12 Server Engine SP1" instead of the "Actian PSQL v12 Client SP1" eliminates the connection problems if the server restarts while a user is logged into their PC (with or without Sage running).

Options 2 and 3 in the article below will resolve this problem on a PC that the user routinely does not restart or logoff at end of day OR the Sage Server is restarted mid-day to address another issue.

View Document - Sage Knowledgebase