cancel
Showing results for 
Search instead for 
Did you mean: 

SAP not able to talk to MSSQL Database

Former Member
0 Kudos
342

we have a NW 2004s Dual stack ssystem

disp+work is down after few minutes into the SAP tart

when i issue r3trans -d, I get the folloing

4 ETW000 [dev trc ,00000] OpenOledbConnection: line 23715. hr: 0x8000ffff Cannot generate SSPI context

4 ETW000 6176 0.223439

4 ETW000 [dev trc ,00000] sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err -2146893022, sev 0), Cannot generate SSPI context

4 ETW000 31 0.223470

4 ETW000 [dev trc ,00000] Procname: [OpenOledbConnection - no proc] 12 0.223482

4 ETW000 [dev trc ,00000] sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err -2146893022, sev 0), SQL Network Interfaces: The target principal name is incorrect.

4 ETW000 59 0.223541

4 ETW000 [dev trc ,00000] Procname: [OpenOledbConnection - no proc] 12 0.223553

4 ETW000 [dev trc ,00000] sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 0, sev 0), Invalid connection string attribute

4 ETW000 57 0.223610

4 ETW000 [dev trc ,00000] Procname: [OpenOledbConnection - no proc] 11 0.223621

4 ETW000 [dev trc ,00000] Using Provider SQLNCLI 9173 0.232794

4 ETW000 [dev trc ,00000] OpenOledbConnection: MARS property was set successfully.

DNS and other things are all fine...

service user account also fine

Any thoughts or directions wopuld be appreciated

regards

Kalyan

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

the problem was that SQL FPN was never registered in DC.

Former Member
0 Kudos

Thanks for your help. I am looking into the note and the link as well

Just some more background on our environment.

MSSQL is on one host and SAP CI is on another.

When we run r3trans on MSSQL host, the return code is 0 and when we run on the SAP CI, the return code is 12 however in both cases as you would imagine, the libraries are used from the CI.

Regards

Kalyan

Former Member
0 Kudos

please go through MS document:

http://support.microsoft.com/kb/811889

also consider about note 551915 if it's database copy