Server side SNC
2009-08-14 02:17:35 Witold Drozdzynski
Business Card
[Reply]
Ingo,
I have followed your blogs, but I still unable to get a connection to SAP when I login to BO with AD credentials.
When I resfresh my BO report I get an error message: "Unable to connect SAP BW. Incomplete logon data. (WIS 10901)"
There's also an error on the SAP side:
Name or runtime error: CALL_FUNCTION_SIGNON_INCOMPL
Short text: "Incomplete logon data."
User and Transaction:
Client.............. 000
User................ "SAPSYS"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "75A188DE799DF15FA3690007E9066E44"
Program............. "SAPMSSY1"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "########"
Database Release.... 640
Kernel Release...... 640
Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. "###"
User................ "############"
Transaction......... " "
Call Program........."wireportserver"
Function Module..... "RFCPING"
Call Destination.... "<unknown>"
Source Server....... "hacom"
Source IP Address... "15.98.88.55"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Client and user seem to be empty.
In the BO SNC setting, the "SNC library settings" points to sapcrypto.dll.
In the R3 in a profile (RZ10) properties sec/libsapsecu, ssf/ssfapi_lib and snc/gssapi_lib point to gi64krb5.dll.
May it be the cause of the problems ?
I'd be very grateful for any hints.
Best regards,
Witold
Previous Message
