Skip to Content

Cause:-

There was an problem in SAPMMC as disp+wotk not started R3trans error as

2EETW169 no connect possible: “connect failed with DBLI_RC_LOAD_LIB_FAILED

server details win 2003 std + sql 2005

Possible solutions:-

1. Check the dev_w0 trace file

2. Please check below note

556232 – Environment settings for R/3/Oracle on Windows

Yes its is for oracle and your is mss but still u can check this.

Also please check DBSL library in your kernel .

3. If below found in dev_w0 file:-

OpenOledbConnection: line 23918. hr: 0x8000ffff Login failed for user ‘SAPDEV\SAPServiceDEV’.

C  sloledb.cpp [OpenOledbConnection,line 23918]: Error/Message: (err 18456, sev 0), Login failed for user ‘SAPDEV\SAPServiceDEV’.

Is this user account locked ?

4. Try updating the kernel.  We tried all solutions found in different forums, which were similar to the one above, but nothing worked.  Only when you update the kernel, the problem will resolve.

also check the link, which is similar…

http://social.msdn.microsoft.com/Forums/en-US/8319b3d7-f2c2-4752-8b6c-8b918a10be7c/ms-sql-related-error-during-sap-system-upgrade-mssql-2005

5. If you find the below problem:-

I HAVE ERROR IN MSSQL2005 DATABASE DATABASE IS IN SUSPECT MODE

Then the solution will be:-

a) Check this SAP note

          1221541  – Getting corrupt SQL server databases back online

b) When the database is in SUSPECT mode, you can change the database status to the EMERGENCY mode. This could permit the system administrator read-only access to the database. Only members of the sysadmin fixed server role can set a database to the EMERGENCY state.

You can run the following SQL query to get the database to the EMERGENCY mode.

ALTER DATABASE  dbName  SET  EMERGENCY

After that, you set the database to the single-user mode. Single user mode allows you to recover the damaged database.

ALTER DATABASE  dbName   SET SINGLE_USER

Then you can run DBCC CheckDB command. This command checks the allocation, structural, logical integrity and errors of all the objects in the database. When you specify “REPAIR_ALLOW_DATA_LOSS” as an argument of the DBCC CheckDB command, the procedure will check and repair the reported errors. But these repairs can cause some data to be lost.

DBCC CheckDB (dbName , REPAIR_ALLOW_DATA_LOSS)

If the above script runs without any problems, you can bring your database back to the multi user mode by running the following SQL command:

ALTER DATABASE  dbName  SET MULTI_USER

For more info please go through the below links:-

http://www.codeproject.com/Articles/42736/Recover-SQL-Server-2005-Database-from-SUSPECT-Mode

http://www.sapbasiscorner.com/2013/06/26/recover-sql-suspect-mode/

http://blogs.microsoft.co.il/blogs/dbaces/archive/2008/12/28/how-to-repair-sql-server-2005-suspect-database.aspx

This document was generated from the following discussion: 2EETW169 no connect possible: “connect failed with DBLI_RC_LOAD_LIB_FAILED

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply