RDT Error - Failed to load sql

[DellSC]

Version: BI Platform 4.0 SP12
Server OS: Windows 2008 r2
Database: SQL Server 2008

I'm running the RDT with the following parameters (in an options file):

-dbdriver sqlserverdatabasesubsytem
-connect "UID=<user>;PWD=<password>;DSN=BOBIPCMS-Native"
-dbkey kne$532m4(*7^(@vbZp080&@!#ba345D
-inputfrsdir "\\FHLBSF-i.com\DFS\BOBIP$\Input"
-outputfrsdir "\\FHLBSF-i.com\DFS\BOBIP$\Output"
-outputdir "D:\ReposcanOutput"
-scanfrs
-scancms

I have both 32-bit and 64-bit ODBC DSNs with the same name using the SQL Server native client 10.0.

When I run this, I get the following error:

RepoScan error: The database subsystem could not be loaded. Make sure that the database client is installed. The message returned was The library named sqlserverdatabasesubsytem could not be loaded. The system error message is Loading shared object failed. First tried to load library sqlserverdatabasesubsytem and failed because of error: [The specified module could not be found.]. Second tried to load library D:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64\sqlserverdatabasesubsytem.dll and failed because of error: [The specified module could not be found.]..

I'm running this in prep for an upgrade migration, so upgrading the current version is not an option.

[DellSC]

The thing I didn't mention is that the database uses Trusted Authentication with the service account that runs the SIA. There is no SQL Server account for accessing the database. I think this is where the issue is, but I'm not sure how to resolve it. I've searched for an answer, but I'm not finding anything.

-Dell

[DellSC · Accepted solution]

I am logged in to the server using the service account. However, support was able to point out my stupid typo that was causing the error - it's supposed to be sqlserverdatabasesubsystem. I was missing an "s".

-Dell

[denis_konovalov · Accepted solution]

well, I didn't see it either.... so we both need thicker glasses 🙂

[denis_konovalov]

If the trusted auth to DB is the problem, then maybe you need to login into windows on which you run this command as the account that has access to the DB....
Or, try to create a SQL server account just for this task.