SM59 not working with SNC

[former_member205400]

I have a SM59 connection that works fine. However when I try to enable it for SNC the connection test fails with a:

Logon Cancel

Error Details SNC disabled for conversation 52128155, tp = BXXSND02_BO_SB2 / CPIC-CALL: 'ThSAP

Error Details ERROR: SNC disabled for conversation 52128155, tp = BXXSND02_BO_SB2

Error Details LOCATION: CPIC (TCP/IP) on host MYBOXI01

This is a connection to my BOE server

I was looking at smgw and show listening on port 3306 and snc on port 4806.

I checked my BOE server and it didn't have anything in the services file and I didn't see port 4806 listening using netstat -an either.

Do you think that if I enabled port 4806 on my BOE server that this would function?

Mike

[Former Member · Accepted solution]

check note 505296

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_sec/~...

[former_member205400 · Accepted solution]

Thanks for the response, but we are not using LDAP.

BTW, we have "snc/enable" and "snc/identity/as" both set properly. You are right though "disabled for conversation" is the msg I am getting.

Mike

[former_member205400 · Accepted solution]

I'm thinking I was getting this message "disabled for conversation" because my SNC partner name was incorrect.

I changed the name to what it should be and when i click on "Test Connection" then I continue to get the clock on the screen, i.e. it never comes back.

What does that sound like an indication of?

So,

a) When SNC is "Inactive" then the test connection works

b) When SNC is "Active" and I test the connection then it hangs up.

I need some help with that. Appreciate it. Points rewarded!!

Mike

Edited by: Michael Hill on Aug 21, 2008 5:36 PM

[former_member205400 · Accepted solution]

I'm still trying to get this connection to function. My snc rz10 settings are:

snc/permit_insecure_start 1

snc/r3int_rfc_qop 3

snc/r3int_rfc_insecure 0

snc/accept_insecure_rfc 1

snc/accept_insecure_cpic 1

snc/accept_insecure_gui 1

snc/data_protection/use 3

snc/data_protection/max 3

snc/accept_insecure_r3int_rfc 1

snc/data_protection/min 1

snc/enable 1

I have made several changes to the SNC partner name but I still get the error message:

"SNC Disable for conversation" then my registered server progam id.

To make sure my snc partner name I'm connecting to is correct I go to my windows server box I am connecting to and execute "setspn -L myservername" to get my spn and I use this as my SNC Partner Name.

Anyone see where I am running amiss?

Mike

[former_member205400 · Accepted solution]

Update on my problem. I enabled a trace on my service process on the BOE box and Im seeing:

"bwcepub.exe -aMY_PROG_ID -gaersnd02.mycomp.com -xsapgw06 -t"

So, we see there are no SNC params there in that option list. The RFC API talks about using a destination like:

"bwcepub.exe -Dmy_destination" with an entry in the saprfc.ini file like:

DEST=my_destination

TYPE=R

PRGOGID=p10234.rfcexec

GWHOST=hs0311

GWSERV=sapgw53

RFC_TRACE=1

SNC_MODE=1

SNC_LIB=C:\WINDOWS\system32\gsskrb5.dll

Only problem is that bwcepub.exe is not taking the options -Dmy_destination.