Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Configuring connection DBCON to MSSQL database failed with error -1

former_member117942
Participant
0 Likes
1,268

Dear all,

we have configure DB conection as described in Note 738371 - Creating DBCON multiconnect entries for SQL Server.

When we try to access to our SQL Server named instance we got the error below.

Any idea ?

Thanks

Maurizio Manera

DBCON table

Conn. info MSSQL_SERVER=tcp:breton52\SQL_CYB_SAP MSSQL_DBNAME=SVIL

Error in disp+work process:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

B Thu May 06 16:21:45 2010

B create_con (con_name=CYB)

B Loading DB library 'S:\usr\sap\TST\DVEBMGS00\exe\dbmssslib.dll' ...

B Library 'S:\usr\sap\TST\DVEBMGS00\exe\dbmssslib.dll' loaded

B Version of 'S:\usr\sap\TST\DVEBMGS00\exe\dbmssslib.dll' is "700.08", patchlevel (0.69)

B New connection 1 created

B Connect to CYB as cybsvil with MSSQL_SERVER=breton52\SQL_CYB_SAP MSSQL_DBNAME=SVIL

C Thread ID:3660

C dbmssslib.dll patch info

C patchlevel 0

C patchno 69

C patchcomment DbSlControl(DBSL_CMD_DBNAME_GET): RFC-'Fingerprint' (1405158)

C Network connection used from SAP4 to breton52\SQL_CYB_SAP using tcp:breton52\SQL_CYB_SAP

C OpenOledbConnection : CoCreateInstance failed. rc: 8007007e.

C failed to establish conn to tcp:breton52\SQL_CYB_SAP.

C Retrying without protocol specifier: breton52\SQL_CYB_SAP

C OpenOledbConnection : CoCreateInstance failed. rc: 8007007e.

C failed to establish conn. 0

B ***LOG BY2=> sql error -1 performing CON [dbds#2 @ 1056] [dbds 1056 ]

B ***LOG BY0=> <message text not available> [dbds#2 @ 1056] [dbds 1056 ]

B ***LOG BY1=> sql error -1 [dbacds#2 @ 1433] [dbacds 1433 ]

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Dear all,

we have configure DB conection as described in Note 738371 - Creating DBCON multiconnect entries for SQL Server.

When we try to access to our SQL Server named instance we got the error below.

Any idea ?

Thanks

Maurizio Manera

DBCON table

Conn. info MSSQL_SERVER=tcp:breton52\SQL_CYB_SAP MSSQL_DBNAME=SVIL

Error in disp+work process:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

B Thu May 06 16:21:45 2010

B create_con (con_name=CYB)

B Loading DB library 'S:\usr\sap\TST\DVEBMGS00\exe\dbmssslib.dll' ...

B Library 'S:\usr\sap\TST\DVEBMGS00\exe\dbmssslib.dll' loaded

B Version of 'S:\usr\sap\TST\DVEBMGS00\exe\dbmssslib.dll' is "700.08", patchlevel (0.69)

B New connection 1 created

B Connect to CYB as cybsvil with MSSQL_SERVER=breton52\SQL_CYB_SAP MSSQL_DBNAME=SVIL

C Thread ID:3660

C dbmssslib.dll patch info

C patchlevel 0

C patchno 69

C patchcomment DbSlControl(DBSL_CMD_DBNAME_GET): RFC-'Fingerprint' (1405158)

C Network connection used from SAP4 to breton52\SQL_CYB_SAP using tcp:breton52\SQL_CYB_SAP

C OpenOledbConnection : CoCreateInstance failed. rc: 8007007e.

C failed to establish conn to tcp:breton52\SQL_CYB_SAP.

C Retrying without protocol specifier: breton52\SQL_CYB_SAP

C OpenOledbConnection : CoCreateInstance failed. rc: 8007007e.

C failed to establish conn. 0

B ***LOG BY2=> sql error -1 performing CON [dbds#2 @ 1056] [dbds 1056 ]

B ***LOG BY0=> <message text not available> [dbds#2 @ 1056] [dbds 1056 ]

B ***LOG BY1=> sql error -1 [dbacds#2 @ 1433] [dbacds 1433 ]

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

3 REPLIES 3
Read only

Udo_Ahle
Explorer
0 Likes
816

Hello,

i have exactly the same problem. Is there any solution yet?

Read only

Former Member
0 Likes
816

I think I have a solution. We had the same problem connecting to a MS SQL 2000 from a Windows 2008 R1 64 Bit, and SAP support gave us the hint to download the client from http://www.microsoft.com/downloads/en/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&dis... (scroll down to "Microsoft SQL Server 2008 Native Client"). After a reboot the problem was solved.

Read only

0 Likes
816

I came across the same problem. Installing "Microsoft SQL Server 2008 Native Client" helped. A reboot is not necessary. Restarting the work processes is sufficient.