Symptoms

Today we've attempted to open up the connection to their SAP system in the RTE environment.
Unfortunately the attempt was not successful (see screenshot attached), because we’ve tried to connect directly to one of the instances that does not have a dialog service.

According to the local SAP basis guy, the SAP environment has a so named standalone central services design:
• ASCS00 providing message service, enqueue service and gateway service, but NO dialog service – running with instance number 00
• D02 providing dialog services only, running on instance number 02

So K2 Connect attempts to connect directly to a dialog instance to run a login program and is assuming that the instance number 00. Since this request is handled by ASC002, that does not have a dialog service, the below error will occur.

Just to give it a try we’ve changed the SYSNR from 00 to 02 in the connection string in the K2 Connect admin tool , after which the connection was successful.
Anyhow according to the customer’s guidelines and best practices, this is a quick and dirty workaround that should under any circumstances be avoided.
 

Diagnoses

See resolution
 

Resolution

So we’ve managed to set the connection to the SAP message server and the trick was to
1. Add the message service name to the system service file (located in %windir%system32driversetcservices - see screenshot K2Connect_MSGService.png)
2. Apply the logon group name (GROUP=USERS) in the connection string

So the full connection string looks like this: "MSHOST={SAPDOMAINNAME} R3NAME=00 CLIENT=152 GROUP=USERS"