ADS error 5381

[#1]

Does anyone know what causes Advantage Database Server to return error code 5381? I cannot find any documentation regarding this error code. I'm seeing this with multiple versions of ADS - 9.x, 10.0, 11.0

I have several client who are getting this error. The application will work fine for a while, then the 5381 errors will appear when (I'm guessing) the application attempts to open new tables. Restarting the ADS service usually fixes the issue, but that's very annoying (and sometime impractical) during the business day when many users are in the system.

My application typically runs in a Windows Server remote desktop environment, with users logging into the server remotely to run the application. The server OS can be Windows Sever 2008, 2021, 2016, or 2019. Sometimes the server is a virtual server, and other times it's configured as a physical server.

Any insight anyone can provide will be greatly appreciated. Thanks!

[carmacchris]

When I posted my original question I neglected to mention that my application is developed with Xbase++ 2.0 from Alaska Software. I checked the Alaska Software support newsgroups and found some additional information about error code 5381.

The posts said that 5381 is not an ADS error code, but a Xbase++ sub-system error code, which explains why I could not find 5381 in any of the ADS documentation. The posts also said that the 5381 error is caused by SMB1 restrictions in Windows 10 and newer operating systems. One poster said he was able to eliminate the 5381 error by using a UNC path and port number to connect to the ADS database (example: "DBE=ADSDBE; SERVER=\\192.168.2.206:6262\...").

Another poster added the following comment:

"Yes, it seems your error is caused by the restriction introduced in Win10 1803: a process is not allowed to create a socket under this version of Win10 if it launched from a share (file server) that is only SMB1 capable. (Win 2003 Small Business, Win XP, Samba 3.2 are examples of such file servers). At least SMB2 should be the protocol used between Win10 1803 client and the file server."

The information above was found in the Alaska Software "bugreport" newsgroup, entry dated 05/14/2018 with title "URGENT: ADS Error 5381 after installation of Windows 10 version 1803", and the "data-access" newsgroup, entry dated 08/13/2020, with title "Error 5381".