Sage 500 Database Install message: The following error occurred in the routing GetSQLServerNames [53] File not found: SOADBLIB.DLL

SUGGESTED

We have a Sage Partner Account, and I'm attempting to install Sage 500 ERP 2021. I installed the Database Utilities, but when I run Database Creation Utility I get the message:

The following error occurred in the routing GetSQLServerNames

[53] File not found: SOADBLIB.DLL

When I click 'OK', the message appears again; click 'OK' again, and it appears again. Clicking 'OK' then leaves me at the Sage 500 ERP Database Install Login dialog.

At that point, the SQL Server Name dropdown contains nothing, so I enter my server name, then the Login Name and Password for SQL Server Authentication. and click 'Proceed'.

This produces a message: 

The following error occurred in the routine cbConnect_Click

[53]  Fuke nit fiyndL  TRGEN.DLL.

I'm at a total loss here.  I am logged into Windows with the local Administrator's account, and ran the Database Creation Utility "as Administrator'.  Could this still be a security issue?

I have not dealt with Sage 500 for about 6 years, but seem to recall a top-level installation dialog that contained a number of selections, including one for creating a new database, and another for installing other pieces, such as the Sage 500 Client; however, I haven't found such an installer.  Anybody got any ideas?

Thank you to anyone who can help.

Parents
  • 0

    Part of this might depend on the operating system you are using as well, I've had strange problems with both Azure and Windows 11. That brings up the point that if you are trying this on Windows 11, you might not be successful, it doesn't appear Sage has tested or approved that platform nor Windows Server 2022 or SQL Server 2022.

    You can always use the old tried and true method of installing the utilities on a client and creating the databases from there. The full installation of the utilities is not necessary on the server hosting SQL, it just makes it a little easier sometimes. Most of those components are 32-bt and sometimes compatibility is a problem as well.

Reply
  • 0

    Part of this might depend on the operating system you are using as well, I've had strange problems with both Azure and Windows 11. That brings up the point that if you are trying this on Windows 11, you might not be successful, it doesn't appear Sage has tested or approved that platform nor Windows Server 2022 or SQL Server 2022.

    You can always use the old tried and true method of installing the utilities on a client and creating the databases from there. The full installation of the utilities is not necessary on the server hosting SQL, it just makes it a little easier sometimes. Most of those components are 32-bt and sometimes compatibility is a problem as well.

Children
No Data