DS XI3.2 SP1 - Problem when starting RFC server from management console

[Former Member]

Hi,

We're using DataServices XI 3.2 SP1 FP1 on a windows 2008 server 64bits to load SAP BW. We have set up an external system in SAP BW called "DI_SOURCE" and then successfully created a RFC server interface (DI_SOURCE) within the management console.

When we try to start this RFC server from the management console, we immediately get the following error message : "An internal error occurred in: server.start()::rfc_bad_connection".

On the other hand, when we follow the "old method" (pre SP2) and start the RFC server from a command window, it works : we have "CONNECTION DI_SOURCE OK" in SAP BW.

Any ideas how to solve this ?

Thanks,

Olivier

[Former Member · Accepted solution]

check the service name is it correct ? you can use service name or if you know the port you can use that also for example: 3301

since you are able to save the configuration the problem is most likely with the wrong value of parameters

[Former Member · Accepted solution]

As I managed to register a RFC server with the following command line :

"rfcsvr -aDI_SOURCE -g/H/192.168.xxx.xxx/S/3310 -xsapgw10"

I assumed that I was using good parameters values for SAP Application Server, SAP Gateway, Port number and External System. But you think it is not necessarily the case ?

[Former Member · Accepted solution]

check if there is any JCO trace and log file getting generated in <tomcat>\bin folder ?

the file will be named JCO<.....>.trc.txt and dev_jco*

[Former Member · Accepted solution]

Unfortunately, we have not such trace files generated in <Tomcat>\bin folder. Could they be somewhere else ?

Btw, could it be related to the fact that Data Services runs on a W2K8 64-bit server ?

[Former Member · Accepted solution]

can you do a search for those log files in where DS in installed ?

or you can also try by adding following additional JVM params to the catalina.bat file which is used to start the tomcat

-Djco.trace_level=10 -Djco.trace_path=C:\temp

for Configuring RFC Interface from Management Console, DS uses sapjco3.jar file which will be in tomcat\webapps\DataServices\WEB-INF\lib folder

this jar file loads sapjco3.dll this DLL will be %LINK_DIR%\bin\jco3\lib32 folder

do you see any error messages in %LINK_DIR%\log\web_admin log file ?

to check if jco jar has no problem loading the DLL, use the following command

open a command window

cd to tomcat\webapps\DataServices\WEB-INF\lib

run the following command

java -Djava.library.path="%LINK_DIR%\bin\jco3\lib32" -jar sapjco3.jar

[Former Member · Accepted solution]

Hi,

- No log files were found in the DS directory

- java -Djava.library.path="%LINK_DIR%\bin\jco3\lib32" -jar sapjco3.jar was successful

But finally, we made it work by changing the "SAP Gateway Service name" parameter: instead of entering "SAPGW10", we entered "3310" (the port number) and the interface started.

Do you think it's a normal behavior ?

[Former Member · Accepted solution]

check if SAPGW10 is defined in services file located in

C:\WINDOWS\system32\drivers\etc

you should see a entry

SAPGW10 3310/tcp

if its not there then add it and see if it works if you enter SAPGW10 as service

[dielom · Accepted solution]

Hi Olivier,

I'm running DS on win 2008 64b and it works fine.

Your parameters should be:

RFC Program ID: DI_SOURCE

Username & password: a username with enough auth in BW (i would start with a dialog user with SAP_ALL)

SAP application server name: 192.168.xxx.xxx. I would also try with the server name, not only the IP.

Client: your client number

System Number: 10

Sap Gateway Hostname: = SAP Gateway Hostname (unless you have a complex server environment)

SAP Gateway service name: SAPGW10

Make sure the old rfc server is not running.

Hope this helps.

Cheers,

Diego

[thomas_madsen]

Hi,

We have tried your suggestions above.

Instead of just crashing we now get an error from designer (before closing down). Seems as if our librfc32.dll has a problem.

We have verified that the librfc32.dll from the Data Services package is the only one on the server.

Problem signature:

Problem Event Name: BEX

Application Name: al_designer.exe

Application Version: 12.2.2.0

Application Timestamp: 4b99c5ef

Fault Module Name: LIBRFC32.DLL

Fault Module Version: 7100.3.144.6097

Fault Module Timestamp: 49bec8be

Exception Offset: 000179a4

Exception Code: c0000409

Exception Data: 00000000

OS Version: 6.1.7600.2.0.0.272.7

Locale ID: 1030

Additional Information 1: 4b85

Additional Information 2: 4b85a4b06dde50b4e092d24f447efca0

Additional Information 3: 45fe

Additional Information 4: 45feda9db76a48384005c14dafbddc29

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

[Former Member]

I have the same version of librfc32.dll installed on windows 2003 and I don't see this issue

what is your windows OS ? and what is the OS locale ? I tried with US English, in you case the Locale ID is 1030 (Dutch/Danish) ?

do you have SAP GUI 7.1 installed in anyother system ? if yes, can you try copying the LIBRFC32.DLL from that env to this machine ? copy the DLL in %LINK_DIR%\bin folder, take backup of the existing one first

[Former Member]

If you are still struggling with getting the RFC server up and running you might simply have the same issue as I had: the services file on the RFC server machine didn't include SAP gateways. Easy to test if this is the issue as you don't have to insert the gateway name, you could simply put the port number in there like 3350.

In my experience most errors are to do with incorrect information about the source system. I found the following SAP guide really good in understanding where to get the information from: https://wiki.sdn.sap.com/wiki/display/BOBJ/RuntheDataServices3.2RFC+Server

If only someone could tell me how to prepare the InfoSource in BW to receive data in the lastest BW version? The SAP article I found (included in the above link) seems outdated. With the new one I seemingly need to create a DataSource?

[thomas_madsen]

Hi,

SAPGUI is not installed.

I tried inserting the library path, but placed at the end of the PATH variable.

Will try to move it up front and launch designer from the command line.

/Thomas

[thomas_madsen]

Hi,

Have installed DS 3.2 SP2 on 64 bit windows server 2008 R2, and had the same problem as described in this thread.

We solved the rfc issue as descibed in the thread (entering 3310 instead of sapgw10), but when attempting create a BW target data store the DS designer crashes.

Was wondering whether you had a similar problem.

Best regards

Thomas

[Former Member]

is SAPGUI also installed on the same machine ? if so ? which version ?

the problem could be because of conflicting version of librfc32.dll

DS will also ship this lib and it will be in %LINK_DIR%\bin, try following

open a cmd, and set the %LINK_DIR% as the first thing in the PATH

set PATH=%LINK_DIR%\bin;%PATH%

cd to %LINK_DIR%\bin

and open the Designer from the command line and see if it works (type AL_Designer.exe on the command line)

[Former Member]

Hi Thomas,

On our side, we didn't experience any problems with Designer when creating a target BW datasore. Perhaps you should check if the sap jco librairies are correctly installed as described in the thread.

Regards,

Olivier