Error when connecting via ODBC connections

Alright, so....
I have a Windows 7, 64 bit OS. I installed Oracle 10g, I installed Crystal Reports Xi release 2.
Via ODBC Administrator, I set up my data sources, and they all connect successfully.
I go into Crystal Reports, create a new report, and attempt to set a new connect and use those same data sources. I get prompted for my user name and password. I get the error:
Logon failed.
Details: IM004:[Microsoft][ODBC Driver Manager] Driver's SQLAllocHandel on SQL_HANDEL_ENV failed
HELP! I've changed security settings, I've wiped my machine and started over from scratch, I've even installed Oracle 11g. Please help! I'm about to pull my hair out. I am sure this is probably something easy or something I've overlooked, but I give up and throw the towel in.

Go into \windows\syswow64 and use the odbcadm32.exe located in there. It's the 32 bit version of the ODBC Administrator.
Also, search before posting and this has been answered.
And you need Service Pack 6 to be supported on Windows 7.
Thank you
Don
Edited by: Don Williams on Aug 27, 2010 2:31 PM

Similar Messages

Can SQL*Plus connect via ODBC to NON-Oracle data source?????

I am struggling to understand something. I downloaded Oracle instance client, SQL*Plus and ODBC components with the hopes of being able to connect via SQL*Plus to a non-Oracle/ODBC compliant database.
Is this possible? Or is SQL*Plus ability to connect via ODBC only to an Oracle data source??
Thanks...

sqlplus only connects to oracle. you can use the odbc driver from instant client to allow other applications to access oracle via odbc (e.g. excel). if you need to connect to non-oracle odbc database (ms-access, foxpro, etc.) you need odbc driver for those sources.
you can use sqldeveloper to connect to oracle and non-oracle databases. check otn product info for sqldeveloper for more details.

Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679

Hi,
We update the BW landscape for version 7.4 suppport package 4 (whitout HANA).
We use a external system connection to extract data from a SQLServer database (Microsoft Connector 1.1 for SAP/BW)
In the previous version (BW 7.0.1 SP 10) run correctly, but now is in error.
Below the BW error log:
Error: COMMUNICATION_FAILURE with function RSB_API_OHS_3RDPARTY_NOTIFY and target system SQLIS.
Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679 Transaction program not regist).
Error log of Integrations Services
[SAP BI Destination 1 [476]] Error: Microsoft.SqlServer.Dts.SapBw.Connectivity.ERPException: An error occurred during the dispatch of the incoming function. The last return code was "RFC_FAILURE".
em Microsoft.SqlServer.Dts.SapBw.Components.SapBwSourceBWLoader.ProcessInput(Int32 inputID, PipelineBuffer buffer)
em Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100 wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket)
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "SAP BI Destination 1" (476) failed with error code 0x80131500 while processing input "SAP BI Destination Input" (491). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.
I checked the topic and notes below, but without success
CPIC Return Code 679 - Transaction Program not Registered - ABAP Connectivity - SCN Wiki
Note 1480644 - gw/acl_mode versus gw/reg_no_conn_info.
Note 353597 - Registering RFC server programs
Regards,
Bruno

Hi Bruno,
We were able to resolve the issue. SAP RDS is assisting us with our upgrade and one of their consultants gave us this fix/workaround.
Edit and add an entry into P:\usr\sap\<SID>\DVEBMGS00\data\reginfo.dat on your BW host server.
Below is the entry I added.
P TP=<NAME OF PROGRAM ID> HOST=<remote hostname where you creating the RFC to> CANCEL=<remote hostname> ACCESS=*
P TP=CTSAPNPSCI_PORTAL_FPS HOST=ctsapnpsci CANCEL=ctsapnpsci ACCESS=*
Then in BW system goto smgw > goto > Expert Funtions > External Security > ReRead ACL (N) & Globally
I hope that this works for you.
Regards
James

Error when opening an RFC connection (LB : Hostname or service of the messa

Hi All,
Im trying to transport datasources in BW, they are 7.x RSDS datasources. but we did not change the source system, it was existing and we are using the same source for older BW version. we now installing new BW 7.x system.
These transports went fine in BQ system but failing in BP system with the below error :
Error when opening an RFC connection (LB : Hostname or service of the message ser
Error when activating DataSource 2LIS_17_I0NOTIF RP1CLT100
Error when opening an RFC connection (LB : Hostname or service of the message ser
Error when resetting DataSource 2LIS_17_I0NOTIF RP1CLT100 to the active version
the datasource 2LIS_17_I0NOTIF is active in RP1CLT100 system. when this transport goes to prod it tries to overwrite the existing one, as there are no changes to the datasource the structure will be the same.
but after that it cant able to activate that datasource.
so my question is can we able to activate this datasource in RP rather than doing transport again from R/3 Dev---R/3 PRD.
i tried RSDS_DATASOURCE_ACTIVATE_ALL but it doesn't help.
another question is when we migrate from 3.x datasource to 7.x, does this change any metadata in R/3 system as well.
Best Regards
Robyn.

Hi Rizwan,
Looking at the error message it seems like there is some issue with RFC connection and whatever objects you are trying to move are not reaching to target system. Just have a check with basis team.
Once you migrate DS from 3.x to 7.0 yes there will be some meta data changes e.g. the DS type will be changed from ISFS to RSDS. You will have to send the migration along with current data source.
Regards,
Durgesh.

Error when opening an RFC connection in IDT

Hi Experts,
I m trying to create a relational connection (JCO) from IDT to BW 7.4, and I m getting the following error:
Error when opening an RFC connection (CPIC-CALL: ' ThSAPOCMINIT', communication
I searched this error in Internet and I found many discussions about it ...And I think it's about autorizations in BW system that by default dosen't allow external servers to connect to it.
So, I changed the values for the following parameters in RZ11 t-code:
gw/acl_mode = 0
gw/reg_no_conn_info = 0
But I still get the same error ...When I checked the SM59 t-code I found that IDT create an entry in TCP/Ip connections ...
Can you guide me to solve this issue...
BW server is 7.4 version on AIX OS
BO server is 4.1 SP05 on windows system
Thank's a lot for your help.
Abdess,

Hi,
test the RFC connection in sm59.If it is sussecfull then try to create conneciton otherwise see the error message.
Amit

Error when opening an RFC connection

Hello Team,
We are facing "Error when opening an RFC connection" when we are executing RFC . I checked JCO connections . its working . What could be the reason ?
Regards,
Mayank

Hi Santosh,
But If I will delete or rebind again , it may happen that I miss some mappings and it will create other errors then. As I mentioned earlier from code perspective it was working good. We had Host name migration and it stopped working. I guess I am or Basis is missing some configuration. What do you think Playing with Model will be a good idea ?
Regards,
Mayank

"Unauthorized Host" error when you try to connect to the admin server

"Unauthorized Host" error when you try to connect to the admin server

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
Here is how to solve the problem and gain access. First you should
temporarily open access to all sites, and then once you make sure that
this lets you get into your administration server, try again to set up
the domain name or IP address access restrictions you want.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<OL>
<LI>Open the "ns-admin.conf" file with a text editor. You can
find this file in the "admserv" directory under your Netscape
server root. The directory is named "admin-serv" in 3.x servers.
<LI>Delete the "Hosts" and "Addresses" lines you see there (either one
of them might not be present). Don't confuse the "Addresses" line,
which you should delete, with the "Address" line, which you should NOT
delete.
<LI>Save the file, then restart your administration server (on Unix run
"stop-admin" then "start-admin"; on Windows NT go into the Services
control panel and stop/start the "Netscape Admin Server" service).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<LI>Delete the "Hosts" and "Addresses" entries you see there (either one
of them might not be present). Don't confuse the "Addresses" entry,
which you should delete, with the "Address" entry, which you should NOT
delete.
<LI>Close the registry editor, then restart your administration server
by going into the Services control panel and stopping then starting the
"Netscape Administration" service.
</OL>
Now try again to access your administration server. Remember, the URL
will be something like "http://servername:12345/", where
"12345" is where the administration server's port number goes.
If you still get the same "Unauthorized host" error, then make sure that
your "ns-admin.conf" file really doesn't contain any "Hosts" or
"Addresses" lines any more, and try stopping your administration server
again then starting it back up.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<UL>
<LI>For the administration server on a 3.x server installation, select
"Admin Preferences" from the General Administration page (the first page
you see when you connect to the admin server), then click on "Superuser Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 2.x server installation, select
"Configure Administration" from the Server Selector page (the first page
you see when you connect to the admin server), then click on "Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 1.x server installation, select
"Configure Administration Server" from the bottom of the Server Manager
page, then enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the substrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that your
DNS can resolve those hostnames -- it's generally safer to stick with IP address
restrictions.
When you're finished configuring this, click "Make These Changes" then
restart your admin server.
</UL>
If you still find yourself getting an "Unauthorized host" error message,
you can use the above steps to open up access and try different
settings.

"Unauthorized Host" error when you try to connect to the admin server

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
Here is how to solve the problem and gain access. First you should
temporarily open access to all sites, and then once you make sure that
this lets you get into your administration server, try again to set up
the domain name or IP address access restrictions you want.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<OL>
<LI>Open the "ns-admin.conf" file with a text editor. You can
find this file in the "admserv" directory under your Netscape
server root. The directory is named "admin-serv" in 3.x servers.
<LI>Delete the "Hosts" and "Addresses" lines you see there (either one
of them might not be present). Don't confuse the "Addresses" line,
which you should delete, with the "Address" line, which you should NOT
delete.
<LI>Save the file, then restart your administration server (on Unix run
"stop-admin" then "start-admin"; on Windows NT go into the Services
control panel and stop/start the "Netscape Admin Server" service).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<LI>Delete the "Hosts" and "Addresses" entries you see there (either one
of them might not be present). Don't confuse the "Addresses" entry,
which you should delete, with the "Address" entry, which you should NOT
delete.
<LI>Close the registry editor, then restart your administration server
by going into the Services control panel and stopping then starting the
"Netscape Administration" service.
</OL>
Now try again to access your administration server. Remember, the URL
will be something like "http://servername:12345/", where
"12345" is where the administration server's port number goes.
If you still get the same "Unauthorized host" error, then make sure that
your "ns-admin.conf" file really doesn't contain any "Hosts" or
"Addresses" lines any more, and try stopping your administration server
again then starting it back up.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<UL>
<LI>For the administration server on a 3.x server installation, select
"Admin Preferences" from the General Administration page (the first page
you see when you connect to the admin server), then click on "Superuser Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 2.x server installation, select
"Configure Administration" from the Server Selector page (the first page
you see when you connect to the admin server), then click on "Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 1.x server installation, select
"Configure Administration Server" from the bottom of the Server Manager
page, then enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the substrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that your
DNS can resolve those hostnames -- it's generally safer to stick with IP address
restrictions.
When you're finished configuring this, click "Make These Changes" then
restart your admin server.
</UL>
If you still find yourself getting an "Unauthorized host" error message,
you can use the above steps to open up access and try different
settings.

Error in Local Message System: Error when opening an RFC connection Message

Hi Gurus,
We are not able to create support messages in our ECC production system but it can created in Development and Quality. Support message created appears in solution manager system. ECC System displays error message as
Error in Local Message System: Error when opening
an RFC connection Message was Not Created
I have checked RFC connection between ECC and Solution Manager which displays following message
Logon     Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: partner "local:sapgw00' not reached
Error Details     LOCATION: SAP-Gateway on host local / sapgw05
Error Details     DETAIL: NiPConnect2
Error Details     CALL: connect
Error Details     COMPONENT: NI (network interface)
Error Details     COUNTER: 40142
Error Details     ERROR NUMBER: 10060
Error Details     ERROR TEXT: WSAETIMEDOUT: Connection timed out
Error Details     MODULE: nixxi.cpp
Error Details     LINE: 2835
Error Details     RETURN CODE: -10
Error Details     SUBRC: 0
Error Details     RELEASE: 701
Error Details     TIME: Wed Jan 11 23:26:54 2012
Error Details     VERSION: 38
Kindly Help.....

Hi
Based on the instance number of the servers, you can determine the gateway to be used.
IF your ECC instance number is , 01 then gateway would be , sapgw01 (in ECC system)
So check and change the settings accordingly, in the RFC connection. Also check, if this entry sapgw01 is made in /etc/service file. Also check, in transaction smgw for gateway parameters.
Hope this info helps,
~ Raj

STMS: RFC error: Error when opening an RFC connection

Hello ,
I was wondering if you could help me with this TMS issue.
The transport system is not working properly.
The fallowing error is shown:
Could not start transport control program tp
RFC error: Error when opening an RFC connection
There was an attempt to start the transport control program tp using the local RFC interface. An error occurred here.
Error code: 3
RFC error text: Error when opening an RFC connection
Meaning of the error codes:
03 RFC system failure
04 RFC communication failure
System Response
The function terminates. Details about the error can be found in the trace file of the Gateway Monitor (SMGW).
Procedure
Contact your system administrator or use report RSTPTEST to localize the error. You can then execute the command again.
When I test the tp tools:
tp Call and RFC Ping: Error when opening an RFC connection
Another thing would be that when testing the RFC connection CALLTP_Linux I have the error:
ERROR: user XXX is not authorized to start TP /usr/sap/SID/DVEBMGS53/exe
And I have to say that the user has maximum authorizations.
I also checked the permissions of the tp at OS level but everything seems to be ok.
Can you help me with this?
BR,
Manoliv

Dear Manoliv,
Firstly please check if you have enough space in /usr/sap/trans file system.
If OK, please run RSTPTEST report from SE38 and check the log file in SMGW => Goto => Trace => Gateways => Display file
and paste the log here.
Also, I assume filesystem permissions are OK.
Regards,
Sujit.

Got Error when creating application server connection

Hi Guys...I am using SOA 10.1.3.1.0
I got the following error when creating application server connection
In Step 1:
I selected the Connection type as Standalone OC4J 10.1.3 (Why because I use this one)
In Step 2:
In this step I gave username and password (same username and password to connect to BPEL console)to authenticate connection
In step 3:
It is asking for Hostname, RMI port and URL path. My computer name is gopal-computer. I gave this hostname. RMI port number is 23791 by default. I kept this one as it is and URL path optional I think. I did not give any thing.
In step 4:
When I hit the test connection button its giving the following error
Error while getting remote MBeanServer for url: ormi://gopal-computer:23791/default:
Error reading application-client descriptor: Error communicating with server: Connection refused: connect; nested exception is:
javax.naming.CommunicationException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
Please help me.
Thanks,
Gopal.....

For SOA Suite connection you should choose "Oracle application server 10g 10.1.3"

WORKLOAD ANALYSIS (INTROSCOPE DATA) - Error when opening an RFC connection

Hi all SDNers,
Help is needed on error "WORKLOAD ANALYSIS (INTROSCOPE DATA) - Error when opening an RFC connection".
This error occured on RCA -> Extractor FWK administration and go to managed system (PI) and from the log, i can see some extraction failed due to error message " Error when opening an RFC connection"
consequently, JAVA performance data is not appearing in RCA -> workload analysis but work fine for ABAP and adapter engine.
I've followed below notes and perform the troubleshooting step by step by still to no avail:
Note 1332428 - Missing data in service sessions from BI/CCDB
Note 1257308 - FAQ: Using EarlyWatch Alert
Note 1274287 - End-to-End Diagnostics 7.0 EHP1 SP18 to SP27
Note 1265070 - Diagnostics - Setup of Managed Systems
Note 1010428 - End-to-End Diagnostics
http://wiki.sdn.sap.com/wiki/display/SMSETUP/WorkloadAnalysis-Noapplicabledatafound
steps that have performed:
restarted agent
enlarge RFC resource cap for solmandiag and none
delete entire SID in SMSY and pull again from SLD, re-setup managed system
restart PI system
i've spent 2 days on troubleshooting this issue but lack of information in SMP and SDN, even in google.
in table E2E_EFWK_STATUS and extractor E2E_JAVA_EXTRACTOR_IF, i see all WLI_ID ended with RC 96, MESSAGE = Error when opening an RFC connection and LASTRECORDS = 0
I strongly believe this is the issue that causing no applicable data found for JAVA data.
fyi, we are on SOLMAN EHP1 SPS27.
Any kind advise is most welcome.
Thanks,
Nicholas Chang

Gosh! at last i found the solution!!
I appreciate those who tried to help and i''m sharing the solution as i believe this is the purpose of SDN Forum and help others Netweaver Chap who facing the same problem:
Problem faced:
Extractor failed intermittently for WORKLOAD ANALYSIS (Introscope Data) due to error message "Error when opening an RFC connection"
Due to the above error, performance data is not available in RCA workload analysis for J2EE engine.
Possible Solution:
1) Ensure both webadmin & SOLMANDIAG RFC working fine -> SM59 -> TCP/IP
2) go to SE16 -> E2E_RESOURCES and change the resourcecap to 10 for SOLMANDIAG
3) go to /smd/services -> Diagnostic System -> Advanced Setup -> Abap connectivity -> Connection Configuration and change server count to 10
4) Restart webadmin (step 3 & 4 can perform in VA too)
5) set gw/keepalive & gw/reg_keepalive to value 0 in RZ11 (without reboot of instance)
5) again go to SM59 -> TCP/IP -> SOLMANDIAG and put in the gateway host and gateway service correctly, don't leave this empty!!!! -
> This is the main solution to solve intermittent failed RFC for extractor.
Now, go back and monitor the extractor log and you should see no RFC error anymore and wait for 1 hour for the data to populate.
Thanks!
Nicholas Chang,

SMQ1 status CPICERR - Error when opening an RFC connection

Hie we have all our out bound queus failing with status CPICERR - Error when opening an RFC connection..
I checked RFC connections from CRM - R3 and everything looked ok..
Can anyone guess what is the problem?
Regards,
Lata.

Hi,
Test the connection once again and it can be a problem sometimes with other server also.I would suggest make a new connection, test it and if its fine try ur work wid this connection.
Regards.

Test conn. SAPOSS error when opening an RFC connection SNC processing fail

Dear all,
 I configured a Saprouter in DMZ with SNC connection type to establish connection from my company to SAP and vice-versa. Also I accept connection from external company to our SAP systems. During the test in SM59 SAPOSS connection I receive the following error:
Logon Errore di colleg.
Dettagli err. Error when opening an RFC connection
Dettagli err. ERROR: SNC processing failed: SncSessionInitiatorAK
Dettagli err. LOCAZ.: SAProuter 39.1 (SP3) on 'srvsaprouter1'
Dettagli err. DETT.: NiSncIInitHdlSecurity: sncrc=-4;0x9d9350
Dettagli err. COMPONENT: NI (network interface)
Dettagli err. CONTAT.: 209
Dettagli err. MODULE: nisnc.c
Dettagli err. RIGA: 1091
Dettagli err. VALORE RIT.: -104
Dettagli err. SUBRC: 0
Dettagli err. RELEASE: 710
Dettagli err. ORA: Fri Jul 17 11:01:22 2009
Dettagli err. VERS.: 39
My saprouttab for SAP AG connection is the following:
#SNC-connection from and to SAP
#KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * *
KT "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 194.39.131.34 *
SNC-connection from SAP to local R/3-System for Support
#KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * *
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.229 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.229 3201
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.211 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.211 3600
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.209 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.210 3201
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.231 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.231 50000
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" epe0s.calpeda.priv 50000
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" epe0sc.calpeda.priv 50000
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.242 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.242 50000
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" epe0t.calpeda.priv 50000
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" epe0tc.calpeda.priv 50000
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.215 3200
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.101.111.215 50100
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" epe0p.calpeda.priv 50100
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" epe0pc.calpeda.priv 50100
SNC-connection from SAP to local R/3-System for NetMeeting, if it is needed
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * 1503
SNC-connection from SAP to local R/3-System for saptelnet, if it is needed
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" * 23
Access from the local Network to SAPNet - R/3 Frontend (OSS)
#P <IP-addess of a local PC> 194.39.131.34 3299
P * * *
P * 194.39.131.34 3299
D * * *
Any suggestions?
Thanks in advance.

SNC processing failed could mean lots of things... did you installed the SAPcrypto library?.. did you created the certificates correctly?...
Read SAP notes 812386 and 33135.
Regards
Juan

HTTP_POST - Error when opening an RFC connection

Performing POST-query. Works well in simple program, and in WebDynpro application:
Error when opening an RFC connection
l_dest = 'SAPHTTP'.
 CALL FUNCTION 'HTTP_POST'
 EXPORTING
 absolute_uri = l_uri
 rfc_destination = l_dest
 user = l_username
 password = l_password
 blankstocrlf = 'Y'
 REQUEST_ENTITY_BODY_LENGTH =
 PROXY =
 PROXY_USER =
 PROXY_PASSWORD =
 IMPORTING
 status_code = l_status
 status_text = l_statustext
 response_entity_body_length = l_rlength
 TABLES
 request_entity_body = req_body
 request_headers = req_headers
 response_entity_body = res_body
 response_headers = res_headers
 EXCEPTIONS
 connect_failed = 1
 timeout = 2
 internal_error = 3
 tcpip_error = 4
 system_failure = 5
 communication_failure = 6
 OTHERS = 7
Edited by: S S on Nov 28, 2008 4:01 PM

You can't use SAPHTTP for the destination. This RFC destination uses the SAPGUI to make the HTTP call. Either use SAPHTTPA (the A stands for Application Server) or better yet use the newer CL_HTTP_CLIENT class. The class uses the ICM instead of a standalone executable to make HTTP calls.

TMS - Error when opening an RFC connection

Hi,
TMS communication error with TMSADM@<SID>.DOMAIN_<SID>
Message no. XT153
Diagnosis
There was an error during communication with the RFC destination
TMSADM@<SID>.DOMAIN_<SID>
System Response
The exact error message of the system is:
Error when opening an RFC connection
Procedure
The function terminates.
Procedure for System Administration
Check your TMS configuration with the transaction STMS.
when i check RFC connections through sm59 its working fine.
plz advise.
Thanks in advance.

try to reconfigure STMS easy way to soluve your problem
or goto STMS -> system overview try to update the configuration
Samrat

Error when connecting via ODBC connections

Similar Messages

Maybe you are looking for