Sage 300 Constant Database Locks in Azure

[jamescoppernoll (James)]

Just curious if anyone else has had an issue with Sage 300 locking the database for users constantly.

We tried moving Sage to an Azure IaaS environment with a file/SQL server, 3 terminal servers, and a cloud PC. Everything tested fine, but now the users constantly receive messages that the database is locked by another process and to try again later. The only way they can continue to work is to close the module and restart it. It only seems to occur when at least 2 people are using the software.

I’ve tried making sure the environment is set up the way it was in their previous physical infrastructure and added additional resources to each server, but the errors seem to occur at the same rate. SQL has plenty of RAM and has not reached the max memory assigned to it.

We’ve tried everything we can find in Sage KB articles and called their support to speak with an engineer. We’re about to migrate everything out to a different host. Has anyone else experienced these problems with Sage 300?

[spiceuser-hrtgs]

Have you tried to run SQL profiler? That might provide some detail.

[jamescoppernoll (James)]

Sorry, need to bump this since it’s not resolved. I’ve been doing intense troubleshooting for days. The issue is not with the database despite Sage’s confusing error messages. The error occurs when the SMB share with the app server closes.

We see an event 1905 in the SMBServer Operational logs that states the session is closed as part of periodic system cleanup, which breaks the connection to the semaphor.bin file that’s being accessed. The reason in the event is “Kickoff time expired.”

This happens while the connection is very active. We’re seeing TCP Keep-Alives and acknowledgements back and forth without issues. We’re not seeing retransmits. I haven’t been able to find anything that explains why active SMB connections are being marked for closure. We’ve edited the autodisconnect value, but this does not appear to change anything.

[adrian_ych]

@jamescoppernoll

It only seems to occur when at least 2 people are using the software.

If you are trying to use SAGE on RDS (Terminal Server)…

1. did you install all applications, DB, drivers etc using Terminal Server mode (“Change /user” + install & reboot if required “change user /install”)

2. did you test if 1 user logs in, log off (not disconnect) then 2nd user logs in ?
   Did the previous users logoff (not disconnect or close RDP client or just click X on RDP client ??

3. why not use Sage Online (you save RDS CALs licensing, VM licensing, OS licensing) ?