Discoverer 3i connection error.

I got a error message, when I click the "Click to Start" button,
the message is "cannot connect to Oracle Discoverer Application Server: oracle/discoverer/corba/_st_DCILocator
please contact Oracle Discoverer administrator, is there any solution?
null

Edit the ApacheJserve 'jserv.properties file' found in <ApacheJserve_install_directory/conf>
Find the section for the 'CLASSPATH environment value's passed to the JVM'
Ensure that wrapper.classpath= includes the following: -
<ORACLE_HOME>\vbroker\lib\vbjorb.jar
<ORACLE_HOME>\vbroker\lib\vbjapp.jar
and ensure that these files are present.
Following the editing of the jserv.properties file, stop the Apache NT
service. Wait for 10 seconds before restarting it.
null

Similar Messages

Discoverer Plus connection error

Hi all,
I installed the Oracle Business Intelligence and its Tools and I created BI_ADMIN for EUL in Discoverer Administrator. But I get the following error when I connect to Discoverer Plus:
The application encountered an invalid state.
- - Nested exception: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
OracleBI Discoverer Viewer was unable to find the necessary data for displaying the results of this event. Please correct any errors and try again.
Please guide me for solving this error.
Thanks

Hi
To follow up on the link posted by CD, summarized here:
"The Discoverer network connection configuration uses a DHCP server to get its IP address. In the insallation instructions for the Application Server it suggests using a Microsoft Loopback Adapter and add a line in the HOSTS file to map the host name with the loopback IP.
This procedure appears to work fine with Discoverer 9.0.4, but doesn't always work with Discoverer 10.1.2
The workaround then is to try assigning a static IP to the server and uninstall the loopback adapter. With a static IP most of these connection errors should go away."
I would also add that you have to make sure that a fully qualified domain name is used on the server. If you have already installed Discoverer without a fully qualified domain name you will probably have to wipe the installation and start again.
Best wishes
Michael

Discoverer server connection error

Hi,
I am having a specific problem with web version of discoverer plus. Whenever I connect to discoverer plus and start working on it for few minutes I am losing connection to discoverer server. The exact error message what I am getting is "CONNECTION TO DISCOVERER SERVER IS LOST. PLEASE EXIT AND RESTART YOUR APPLICATION AND IF THE PROBLEM PERSISTS CONTACT YOUR ORACLE APPLICATION SERVER ADMINISTRATOR". When I look at the java console of the applet that is downloaded on my machine I see 'DiscoNetworkException' being thrown. Has anybody got any idea about why this is happening? if so, what do I need to do to prevent it from happening.
Thanks in advance,
Mythili.

We have seen similar behavior on the product. We are running Discoverer Plus 10.1.2.48.18. The problem is reproducable if we have both a CASE statement and a Sort in a worksheet, then try to Save or view the SQL. I have seen the error that begins with "Error: DiscoNetworkException IDL:DCCORBAException:1.0", however, this error is occuring independent of the "dropped connection" error. We have seen it occur before the actual "dropped connection" error occurs. Also, if we only examine the SQL and don't save the worksheet, the error is displayed, but the connection remains intact (we can continue to work with the worksheet).
Don't know if this is helpful, but its what we're seeing.

Discoverer Plus connecting error

Dear All,
I installed O9iAS release 2 BI installation type successfully but when i tried to invoke discoverer plus
for the first time i got the following error :
CORBA protocol error : Failed to connect to session <server_name>OracleDiscoverer session902 using OSAgent
any help will be appreciated.
Regards,
Mohammed Amin

Hi Christian
In your connection to the database are you using a DNS named server or are you using an actual IP address?
By this I mean, when you launch Discoverer, do you do it this way:
http://servername.domain.com:7777/discoverer/plus
or this way:
http://ipaddress:7777/discoverer/plus
If you are using the former, can you go to the server itself and run Discoverer ok? If you can then it is a case that your local machine cannot work out what the IP address is. Let's say, for arguements sake, that you server is http://myserver.mydomain.com and that the IP is 192.168.1.100
You could try editing your HOSTS file and inserting a line in there to associate the IP with the domain. To do this, follow this workflow:
1. Right click on Windows Start button and from pop upmenu select Explore
2. Navigate to the folder called Windows/system32/drivers/etc
3. Locate the file called HOSTS
4. Edit this file with Notepad
5. Insert a line like this:
myserver.mydomain.com 192.168.1.100
6 Save the HOSTS file and exit Explorer
This associates the IP with the server name.
Does this help
Regards
Michael

Discoverer 4i Viewer Error

In our company we installed the Oracle Discoverer 4i Early Adpator and, when we try to use the Discoverer Viewer, an error occurs.
This error happens when I apply the parameters of a worksheet and the symptom is like a download of a file, named "ca54zrse.txt". The content of this file is:
"java.lang.NullPointerException
at oracle.discoiv.session.model.ModelQuery.run(ModelQuery.java, Compiled Code)
at oracle.discoiv.session.model.ModelQuery.run(ModelQuery.java, Compiled Code)
at java.lang.Thread.run(Thread.java, Compiled Code)"
When it occurs, the connection with the database is dropped and I have to connect again.
I'm using Oracle Database Enterprise version 8.1.7.
What can I do? Is it a network error or a database error?
Please, help me!
[email protected]
[email protected]
null

Check your jserv.conf as well as zone.props
Check these area closly
CHW
null

Attaching a Discoverer Private Connection via role

Is it possible to define a discoverer viewer private connection that everyone attached to a specific role can view? So far we have seen that a private connection needs to be attached to a username and this can be very problematic if you have 600 users.

I hope this can helu u!!!
SET DEFINE OFF;
CREATE OR REPLACE PACKAGE DISCO_PRIV_CONN IS
/**********************************************************************=
* DISCLAIMER: You may be use this AS-IS. There is no support involved=
and
* you may use at your own risk.
* AUTHOR : Caroline Cintra
* DATE : 27-FEB-03
* PURPOSE : Currently there is no means provided to create Discoverer c=
onnections
* (public or private) in a programmatical way. The below PLS=
QL
* package is used to create private connections in Oracle9iAS=
Release 2
* 9.0.2.x.
* Private connections are defined on a per user basis specify=
ing the
* user/pwd/connect string to run a Discoverer Report through =
Viewer.
* This can be called in a batch program to create multiple Di=
scoverer
* connections in bulk.
* This package must be owned by ORASSO.
***********************************************************************=
-- Error code returned when exceptions are raised in this package
g_error_code NUMBER := -20220;
-- Variables used to handle Discoverer private connections (fix values)=
g_subscriber_id orasso.wwsso_psex_user_info$.subscriber_id%TYPE := 1;
g_app_id orasso.wwsso_psex_user_info$.app_id%TYPE := '1325';
g_app_creator orasso.wwsso_psex_user_info$.app_creator%TYPE := 'ORASSO_DS';
/**********************************************************************=
* PARAMETERS:
* p_sso_username IN orasso.wwsso_psex_user_info$.sso_username%type
* Oracle Single Sign On user name
* p_db_username IN orasso.wwsso_psex_user_info$.app_username%type
* Discoverer (DW) database username
* p_db_password IN orasso.wwsso_psex_user_info$.app_password%type
* Discoverer (DW) database password
* p_eul IN orasso.wwsso_psex_user_info$.fval1%type
* Discoverer End User Layer in the <p_db_username> sc=
hema
* p_conn_name IN orasso.wwsso_psex_user_info$.fval1%type
* Name of the Discoverer private connection being cre=
ated
* p_conn_desc IN orasso.wwsso_psex_user_info$.fval1%type
* Name of the Discoverer private connection being cre=
ated
* p_db_name IN orasso.wwsso_psex_user_info$.fval1%type
* Discoverer (DW) database name
* (tnsnames entry defined in the server)
* EXAMPLE USE: ORASSO.DISCO_PRIV_CONN.CREATE_PRIVATE_CONNECTION (
* 'JP111111' -- p_sso_username
* , 'global_user' -- p_db_username
* , 'global_user_pwd' -- p_db_password
* , 'EUL9I' -- p_eul
* , 'default_priv_conn' -- p_conn_name
* , 'Connection created via API' -- p_conn_name
* , 'devap' -- p_db_name
* NOTES:
* 1) This procedure does not perform a COMMIT of the database transac=
tions
* it executes. The reaon for this decision is the fact that this
* procedure is designed to be called as part of a Single Sign On u=
ser
* set up. Therefore, the database operations performed here must o=
nly
* be commited when the user set up entire process was successful.
* 2) If there is a problem creating the connection (e.g. this connect=
ion
* already exists), an application exception is raised with the err=
or
* code of DISCO_PRIV_CONN.g_error_code.
***********************************************************************=
PROCEDURE CREATE_PRIVATE_CONNECTION(
p_sso_username IN orasso.wwsso_psex_user_info$.sso_username%TYPE
, p_db_username IN orasso.wwsso_psex_user_info$.app_username%TYPE
, p_db_password IN orasso.wwsso_psex_user_info$.app_password%TYPE
, p_eul IN orasso.wwsso_psex_user_info$.fval1%TYPE
, p_conn_name IN orasso.wwsso_psex_user_info$.fval1%TYPE
, p_conn_desc IN orasso.wwsso_psex_user_info$.fval1%TYPE
, p_db_name IN orasso.wwsso_psex_user_info$.fval1%TYPE
/**********************************************************************=
* PARAMETERS:
* p_fld_index IN orasso.wwsso_psex_user_info$.fld_index%type
* Connection identifier
* EXAMPLE USE: DISCO_PRIV_CONN.REMOVE_PRIVATE_CONNECTION(
* 'a170' -- p_fld_index
* NOTES:
* 1) This procedure does not perform a COMMIT of the database transac=
tions
* it executes. The reaon for this decision is the fact that this
* procedure is designed to be called as part of more complex
* processes. Therefore, the database operations performed here mus=
t
* only be commited when the complete process was successful.
* 2) If there is a problem creating the connection (no connection was=
* found based on the input parameters), an application exception i=
s
* raised with the error code of DISCO_PRIV_CONN.g_error_code.
***********************************************************************=
PROCEDURE REMOVE_PRIVATE_CONNECTION(
p_fld_index IN orasso.wwsso_psex_user_info$.fld_index%TYPE
/**********************************************************************=
* PARAMETERS:
* p_fld_index IN orasso.wwsso_psex_user_info$.fld_index%type
* Connection identifier
* p_new_password IN orasso.wwsso_psex_user_info$.app_password%type
* Discoverer (DW) database new password
* EXAMPLE USE: DISCO_PRIV_CONN.UPDATE_PRIVATE_CONNECTION_PWD(
* 'a170' -- p_fld_index
* , 'new_global_user_pwd' -- p_new_password
* NOTES:
* 1) This procedure does not perform a COMMIT of the database transac=
tions
* it executes. The reaon for this decision is the fact that this
* procedure is designed to be called as part of more complex
* processes. Therefore, the database operations performed here mus=
t
* only be commited when the complete process was successful.
* 2) If there is a problem creating the connection (no connection was=
* found based on the input parameters), an application exception i=
s
* raised with the error code of DISCO_PRIV_CONN.g_error_code.
***********************************************************************=
PROCEDURE UPDATE_PRIVATE_CONNECTION_PWD(
p_fld_index IN orasso.wwsso_psex_user_info$.fld_index%TYPE
 , p_new_password IN orasso.wwsso_psex_user_info$.app_password%TYPE
/**********************************************************************=
* PARAMETERS:
* p_fld_index IN orasso.wwsso_psex_user_info$.fld_index%type
* Connection identifier
* p_new_password IN orasso.wwsso_psex_user_info$.app_password%type
* Discoverer (DW) database new password
* RETURN:
* The connection unique identifier (wwsso_psex_user_info$.fld_index)
* EXAMPLE USE: DISCO_PRIV_CONN.SELECT_PRIVATE_CONNECTION_ID(
* 'JP111111' -- sso_username
* , 'my_connection' -- p_conn_name
***********************************************************************=
FUNCTION SELECT_PRIVATE_CONNECTION_ID(
p_sso_username IN orasso.wwsso_psex_user_info$.sso_username%TYPE
 , p_conn_name IN orasso.wwsso_psex_user_info$.fval1%TYPE
) RETURN VARCHAR2;
END DISCO_PRIV_CONN;
CREATE OR REPLACE PACKAGE BODY DISCO_PRIV_CONN IS
PROCEDURE CREATE_PRIVATE_CONNECTION(
p_sso_username IN orasso.wwsso_psex_user_info$.sso_username%TYPE
, p_db_username IN orasso.wwsso_psex_user_info$.app_username%TYPE
, p_db_password IN orasso.wwsso_psex_user_info$.app_password%TYPE
, p_eul IN orasso.wwsso_psex_user_info$.fval1%TYPE
, p_conn_name IN orasso.wwsso_psex_user_info$.fval1%TYPE
, p_conn_desc IN orasso.wwsso_psex_user_info$.fval1%TYPE
, p_db_name IN orasso.wwsso_psex_user_info$.fval1%TYPE
) IS
BEGIN
INSERT INTO
orasso.wwsso_psex_user_info$ (
subscriber_id
, sso_username
, app_id
, app_creator
, fld_index
, app_username
, app_password
, user_prefs
, fname1, fval1, fname2, fval2 , fname3, fval3, fname4, fval4
, fname5, fval5, fname6, fval6, fname7, fval7, fname8, fval8
, fname9, fval9
VALUES (
g_subscriber_id -- subscriber_id
, p_sso_username -- sso_username
, g_app_id -- app_id
, g_app_creator -- app_creator
, 'a' || orasso.wwsso_jps_seq.NEXTVAL -- fld_index
, orasso.wwsso_api_private.ENCRYPT_STRING(p_db_username) -- app=_username
, orasso.wwsso_api_private.ENCRYPT_STRING(p_db_password) -- app=_password
, '' -- user_prefs
, 'discard_password' -- fname1
, 'false' -- fval1
, 'eul' -- fname2
, p_eul -- fval2
, 'connection_name' -- fname3
, p_conn_name -- fval3
, 'show_details' -- fname4
, 'true' -- fval4
, 'database' -- fname5
, p_db_name -- fval5
, 'description' -- fname6
, p_conn_desc -- fval6
, 'default_locale' -- fname7
, 'en-US' -- fval7
, 'null' -- fname8
, 'null' -- fval8
, 'null' -- fname9
, 'null' -- fval9
 -- If there is a problem, raise exception
EXCEPTION
WHEN OTHERS THEN
RAISE_APPLICATION_ERROR(g_error_code,SQLERRM,TRUE);
END;-- of PROCEDURE CREATE_PRIVATE_CONNECTION
PROCEDURE REMOVE_PRIVATE_CONNECTION (
p_fld_index IN orasso.wwsso_psex_user_info$.fld_index%TYPE
) IS
 l_rowid ROWID := '0';
BEGIN
SELECT ROWID
INTO l_rowid
 FROM orasso.wwsso_psex_user_info$
 WHERE fld_index = p_fld_index;
DELETE FROM orasso.wwsso_psex_user_info$
WHERE ROWID = l_rowid;
 -- If there is a problem, raise exception
EXCEPTION
 WHEN NO_DATA_FOUND THEN
RAISE_APPLICATION_ERROR(
 g_error_code
 , 'Discoverer private connection to be deleted does not exist.'
 , TRUE);
 WHEN TOO_MANY_ROWS THEN
RAISE_APPLICATION_ERROR(
 g_error_code
 , 'Too many Discoverer private connections were found (delete).'
 , TRUE);
WHEN OTHERS THEN
RAISE_APPLICATION_ERROR(g_error_code,SQLERRM,TRUE);
END;-- of PROCEDURE REMOVE_PRIVATE_CONNECTION
PROCEDURE UPDATE_PRIVATE_CONNECTION_PWD (
p_fld_index IN orasso.wwsso_psex_user_info$.fld_index%TYPE
 , p_new_password IN orasso.wwsso_psex_user_info$.app_password%TYPE
) IS
 l_rowid ROWID := '0';
BEGIN
SELECT ROWID
INTO l_rowid
 FROM orasso.wwsso_psex_user_info$
 WHERE fld_index = p_fld_index;
UPDATE orasso.wwsso_psex_user_info$
SET app_password = orasso.wwsso_api_private.ENCRYPT_STRING(p_new_password)
WHERE ROWID = l_rowid;
 -- If there is a problem, raise exception
EXCEPTION
 WHEN NO_DATA_FOUND THEN
RAISE_APPLICATION_ERROR(g_error_code,'Discoverer private connec=
tion TO be updated does NOT exist.',TRUE);
 WHEN TOO_MANY_ROWS THEN
RAISE_APPLICATION_ERROR(g_error_code,'Too many Discoverer priva=
te connections were FOUND (UPDATE).',TRUE);
WHEN OTHERS THEN
RAISE_APPLICATION_ERROR(g_error_code,SQLERRM,TRUE);
END;-- of UPDATE_PRIVATE_CONNECTION_PWD
FUNCTION SELECT_PRIVATE_CONNECTION_ID(
p_sso_username IN orasso.wwsso_psex_user_info$.sso_username%TYPE
 , p_conn_name IN orasso.wwsso_psex_user_info$.fval1%TYPE
) RETURN VARCHAR2 IS
 identifier orasso.wwsso_psex_user_info$.fval1%TYPE;
BEGIN
SELECT fld_index
INTO identifier
 FROM orasso.wwsso_psex_user_info$
 WHERE
 sso_username = p_sso_username
 AND app_id = g_app_id
 AND p_conn_name = DECODE(
 fname1
 , 'connection_name'
 , fval1
 , DECODE(
 fname2
 , 'connection_name'
 , fval2
 , DECODE(
 fname3
 , 'connection_name'
 , fval3
 , DECODE(
 fname4
 , 'connection_name'
 , fval4
 , DECODE(
 fname5
 , 'connection_name'
 , fval5
 , DECODE(
 fname6
 , 'connection_name'
 , fval6
 , DECODE(
 fname7
 , 'connection_name'
 , fval7
 , DECODE(
 fname8
 , 'connection_name'
 , fval8
 , DECODE(
 fname9
 , 'connection_name'
 , fval9
 , 'INVALIDVALUE'
 ) --fname9
 ) --fname8
 ) --fname7
 ) --fname7
 ) --fname5
 ) --fname4
 ) --fname3
 ) --fname2
); --fname1
 RETURN identifier;
 -- If there is a problem, raise exception
EXCEPTION
 WHEN NO_DATA_FOUND THEN
RAISE_APPLICATION_ERROR(
 g_error_code
 , 'Discoverer private connection not found (select).'
 , TRUE);
 WHEN TOO_MANY_ROWS THEN
RAISE_APPLICATION_ERROR(
 g_error_code
 , 'Too many Discoverer private connections were found (select).'
 , TRUE);
WHEN OTHERS THEN
RAISE_APPLICATION_ERROR(g_error_code,SQLERRM,TRUE);
END;-- of PROCEDURE REMOVE_PRIVATE_CONNECTION
END DISCO_PRIV_CONN;
SHOW ERRORS;

Connection error to OAS

hi,
the following error occurs when i try to connect discoverer plus to OAS10g.
A connection error has occurred.
- An error occurred while creating the session. Please check for other errors.
- oracle.discoiv.connections.ConnectionStoreException: Unable to establish secure connection to Oracle Internet Directory Server ldap://mildd1110:636/ Base Exception : javax.naming.CommunicationException: mildd1110:636 [Root exception is java.net.ConnectException: Connection refused: connect]
help me to resolve this.
Thanks,
VPreetha

Hi, I also have the same error message:
A connection error has occurred.
- An error occurred while creating the session. Please check for other errors.
- oracle.discoiv.connections.ConnectionStoreException: Unable to establish secure connection to Oracle Internet Directory Server ldap://misap.ote.gr:636/ Base Exception : javax.naming.CommunicationException: misap.ote.gr:636 [Root exception is java.net.ConnectException: Connection refused]
- Unable to establish secure connection to Oracle Internet Directory Server ldap://misap.ote.gr:636/ Base Exception : javax.naming.CommunicationException: misap.ote.gr:636 [Root exception is java.net.ConnectException: Connection refused]
- Unable to establish secure connection to Oracle Internet Directory Server ldap://misap.ote.gr:636/ Base Exception : javax.naming.CommunicationException: misap.ote.gr:636 [Root exception is java.net.ConnectException: Connection refused]
Unable to retrieve connection list
- The connection list could not be retrieved. See other error messages for details.
....but I don't need to use neither the SSO nor the Oracle Internet Directory Server !
Where is located this property to set to false ???
Thanks in advance
Alex

Data Federator data source not available causes Universe Connection error

I created a Data Federator project that connects to 20 servers across US and Canada. All data sources are SQL Server 2005. The DF project maps 40 source objects into 4 target objects. I created a universe based on the DF project and we have been quite pleased with Webi query response. Today one of the source servers was taken off line and this generated a connection error when trying to access the universe (not trying to access the data source that failed). We do not want the universe connection to error when one source server is not available u2013 is that possible?
If the answer is no then I see us abandoning what appears to be a great solution for real time distributed reporting and resorting to ETL and moving data.

Hi Chapman,
Can you be little elobrate on what you have done to solve the issue.
Thanks,
Dayanand

RFC connection Error in SLDCheck

Hi All,
I am trying to logon to Integration builder for that i getting the ESR builder address is not maintain. for this i have chk in SLDCheck t code ,there i am getting LCRSAPRFC connection error.I have test the RFC connection in that i am getting the
the error in register server program
Error Details     ERROR: program LCRSAPRFC_XID not registered
now wht i have to do for troubleshooting
Regards

Thanx for reply
when I test connection to Connection Test SLD_UC     error
Logon     Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: program SLD_UC not registered
Error Details     LOCATION: SAP-Gateway on host sapdevpi / sapgw00
Error Details     DETAIL: TP SLD_UC not registered
Error Details     COMPONENT: SAP-Gateway
Error Details     COUNTER: 62
Error Details     MODULE: gwr3cpic.c
Error Details     LINE: 1778
Error Details     RETURN CODE: 679
Error Details     SUBRC: 0
Error Details     RELEASE: 701
Error Details     TIME: Fri Jan 8 11:05:42 2010
Error Details     VERSION: 2
RFC SLD_UC is connection T
Gateway Host sapdevpi
Gateway server sapgw00
same error with
Connection Test SLD_NUC
Connection Test SAPSLDAPI   ( program Id SAPSLDAPI_DPI )
Connection Test SAPJ2EE
In Connection Test LCRSAPRFC error program id LCRSAPRFC_DPI
Logon     Cancel
Error Details     max no of 100 conversations exceeded / CPIC-CALL: 'ThSAPCMRCV' : cmRc=17 thRc=45
Error Details     ERROR: max no of 100 conversations exceeded
Error Details     LOCATION: CPIC (TCP/IP) on host sapdevpi
Error Details     COMPONENT: CPIC (TCP/IP) with Unicode
Error Details     COUNTER: 82
Error Details     MODULE: r3cpic_mt.c
Error Details     LINE: 10791
Error Details     RETURN CODE: 466
Error Details     SUBRC: 0
Error Details     RELEASE: 701
Error Details     TIME: Fri Jan 8 11:12:56 2010
Error Details     VERSION: 3
Regards
shahid

RFC connection error between Netweaver 7 EHP1 and Ides ECC6

Hi Friends,
I try to create source system in BI from Netwever EHP1 to IDES ECC6 EHP3.
During the creation I get a connection error, says. check connction parameter.
I checked the parameter, everything is fine. Server, System and number.
When I went to the SM59 and created a connction.
I.E. with the same parameter like system = 06 and server = compi9 gave client 800 etc.
The Host name is resolved to 192.168.2.111 wich is OK.
But when I run the connection test it shows me "ERROR: partner '80.156.86.78:sapgw06' not reached"
I have no idea where this IP '80.156.86.78" is comming from.
No Problem with the opposite way, from Ides to NW and login to the System is OK too.
Can anybody help me with this problem.
RG. Jimbob

Hi,
What is the next screen that comes up when you click on remote logon.
If no screen comes up then:
Check the user type of the user id used for this RFC.
It should be either dialog or service user for able to remote login.
If it open a new window and asks for password, then its excatly password issue.
Also make sure that the password is in numeric and correct.
Also make sure that the current user check box is unchecked.
Even if it dosent work, delete the connection and create again.
Please award points if helps.
Thanks
Santhosh

RFC connection Error

Dear All,
    when i connect our BI System to R/3 system via RFC in SM59 ,i am getting following error in BI system and also The problem occur in particular instance .(Other instance working fine in BI system)
Logon     Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: timeout during allocate
Error Details     LOCATION: SAP-Gateway on host chwslp05 / sapgw01
Error Details     DETAIL: no connect of TP sapdp15 from host sapp3b.eame.syngenta.org after 20 s
Error Details     COMPONENT: SAP-Gateway
Error Details     COUNTER: 162003
Error Details     MODULE: gwr3cpic.c
Error Details     LINE: 1973
Error Details     RETURN CODE: 242
Error Details     SUBRC: 0
Error Details     RELEASE: 700
Error Details     TIME: Mon Apr 27 14:29:33 2009
Error Details     VERSION: 2
Any one please suggest.
Thanks,
Thirumoorthy.

mostly your gateway servicve is not working check smgw tcode on that instance
you can do this goto sm59->select the instace execute tcode smgw
easy way is restart the instance
it will start working
Samrat

RFC Connection error in SM59 for SAP J2EE

Hi All,
i am getting the following error description while testing the connection for
SAP J2EE ...
Connection Test SAPJ2EE
Connection Type TCP/IP Connection
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program sapfallback not registered
Error Details LOCATION: SAP-Gateway on host filip / sapgw00
Error Details DETAIL: TP sapfallback not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 1483
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1694
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Tue Mar 31 02:44:35 2009
Error Details VERSION: 2
Help me resolve this
Regards,
Mahesh.

Hi,
Please follow this steps:
Creating RFC Destinations in the ABAP and Java Environment
You need to create the following RFC destinations in transaction SM59 (ABAP) and the Visual Administrator (Java):
u2022 AI_RUNTIME_JCOSERVER
u2022 AI_DIRECTORY_JCOSERVER
u2022 LCRSAPRFC
u2022 SAPSLDAPI
Depending on your client settings, it may be necessary to be logged on your SAP Exchange Infrastructure host as SAP system user with the authorization to maintain customizing tables and to release transport orders. Note, that user "SAP*" or "DDIC" does not have these authorizations.
Maintaining the RFC Connections (Transaction SM59)
1. Log on to your SAP Exchange Infrastructure central instance host.
2. Call transaction SM59.
3. Choose Create.
4. Enter at least the following:
RFC destination: AI_RUNTIME_JCOSERVER
Connection type: T
Description: <your description>
5. Choose ENTER
6. Choose the tab Technical settings and do the following:
a. Select Registered Server Program
b. In the Program ID field, enter: AI_RUNTIME_<SID> where <SID> is the SAP system ID of your Integration Server host. Use uppercase letters only.
c. Enter Gateway host and Gateway service of your Integration Server host. To find out the required parameters:
a. On the Integration Server host, call transaction SMGW
b. Choose Goto u2192 Parameters u2192 Display (see entries for gateway hostname and gateway service)
7. Choose tab Special Options and select the flag Unicode in the box Character Width in Target System.
8. Save your settings.
9. Repeat the steps 3 u2013 8 for the remaining destinations:
Destination
Values
AI_DIRECTORY_JCOSERVER
Program ID: AI_DIRECTORY_<SID>, where <SID> is the SAP system ID of your SAP XI host
LCRSAPRFC
Program ID: LCRSAPRFC_<SID>, where <SID> is the SAP system ID of your SAP XI host.
SAPSLDAPI
Program ID: SAPSLDAPI_<SID>, where <SID> is the SAP system ID of your SAP XI host.
10. Leave the transaction SM59 open for later tests.
J2EE Configuration for the Destinations (Visual Administrator)
1. On your SAP Exchange Infrastructure central instance host, start the J2EE Engine administration tool.
2. Choose Cluster u2192 Server u2192 Services u2192 JCo RFC Provider
3. In the section RFC destination, enter exactly the same program ID and gateway options for AI_RUNTIME_JCOSERVER that you used in the step Maintaining the RFC connection above. Additionally, set the number of processes to 10.
4. In the section Repository, do the following:
a. Enter the parameter for the SAP XI host: Application Server, System Number, Client and Language.
b. For User and Password maintain the login parameters for the user SAPJSF.
c. Select the flag Unicode.
6. Choose Set.
7. Repeat the steps 3 u2013 6 for the remaining destinations:
Destination
Values
AI_DIRECTORY_JCOSERVER
u2022 Corresponding values from SM59
u2022 Number of processes: 10
LCRSAPRFC
u2022 Corresponding values from SM59
u2022 Number of processes: 3
SAPSLDAPI
u2022 Corresponding values from SM59
u2022 Number of processes: 3
Testing the RFC Destination
After you have maintained all RFC destinations in both the ABAP and Java environment, you can check all the connections above as follows:
1. Call transaction SM59 again.
2. Open your RFC destination.
3. Choose Test Connection. No error should be displayed.
This will solve your problem.
Thanks
Laxmi Bhushan

RFC connection error (VPN-access)

Hi!
I have the following error for the RFC connection:
The RFC connection is setup as follows.
/H/10.101.7.1/S/3299/H/10.151.6.194
10.101.7.1 = IP of our SAP Router
10.151.6.194 = IP of customer system
The RFC connection is established:
SAP Router (intern) --> Target systems
The error is:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: partner not reached (host 10.151.6.194, service sapgw20)
Error Details LOCATION: SAP-Gateway on host bksapp01 / sapgw20
Error Details DETAIL: NiPConnect2
Error Details CALL: SiPeekPendConn
Error Details COMPONENT: NI (network interface)
Error Details COUNTER: 592
Error Details ERROR NUMBER: 10060
Error Details ERROR TEXT: WSAETIMEDOUT: Connection timed out
Error Details MODULE: nixxi.cpp
Error Details LINE: 8777
Error Details RETURN CODE: -10
Error Details SUBRC: 0
Error Details RELEASE: 640
Error Details TIME: Thu Jun 19 10:42:42 2008
Error Details VERSION: 37
Can some one help to solve the problem?
Thank you very much
Thom

Hi
Change the saprouter string to
/H/10.101.7.1/S/3299/H/10.151.6.194/S/32<system number>
and try !!!

RFC connection error when registering PROGRAM ID.

Hi,
I created a RFC connection of type T.
I gave the following parameters ->
gateway host: hostname and then ip-address
gateway service: sapgwxx
Registered program id: xxx
It is giving me the following error:
Error Details Error when opening an RFC connection
Error Details ERROR: program sapgwxx not registered
Error Details LOCATION: SAP-Gateway on host <hostname> / sapgwxx
Error Details DETAIL: TP sapgwxx not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 2696
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1777
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Can anyone help me in troubleshooting the issue.
Also I am not able to register this program id in Visual Admin -> Services -> JCo RFC Provider. Here it is giving me an error. Can anyone guide me in this?
Points to be rewarded for any kind of small help.

Thanks Ramesh.
I followed the blog. Here are the steps that I did.
RFC destination:
1. To create the RFC go to TCODE: SM59 -> Done2. Create new destination of type T (TCP/IP) -> Done
3. Make sure you select Registered Server Program option before writing your program ID -> Done
4. Write you program ID (remember it's case-sensitive) -> gave the SID name
5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server) -> Typed the gateway hostname and gateway service "sapgw<instance no>", that I got from SMGW.
But still I face the same problem. It get the following error:
Logon Connection Error
Error Details Error when opening an RFC connection
Error Details ERROR: program <SID name> not registered
Error Details LOCATION: SAP-Gateway on host xxxxx / sapgwxx
Error Details DETAIL: TP <SID Name> not registered
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 2719
Error Details MODULE: gwr3cpic.c
Error Details LINE: 1777
Error Details RETURN CODE: 679
Error Details SUBRC: 0
Error Details RELEASE: 700
Error Details TIME: Thu Nov 1 10:39:43 2007
Error Details VERSION: 2
Kindly help me out.

RFC Connection Error during Web AS ABAP Database Instance

I keep getting RFC Connection error installing the database instance. The following are the pertinent logs:
INFO 2007-05-09 20:10:04
Working directory changed to C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\MSS\UC\DB.
INFO 2007-05-09 20:10:04
Output of C:\usr\sap\X22\SYS\exe\run\r3trans.exe -u 1 -i "C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\MSS\UC\DB\mssprocs640.dat" is written to the logfile r3trans.exe.log.
INFO 2007-05-09 20:10:22
Execution of the command "C:\usr\sap\X22\SYS\exe\run\r3trans.exe -u 1 -i "C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\MSS\UC\DB\mssprocs640.dat"" finished with return code 0. Output: This is C:\usr\sap\X22\SYS\exe\run\r3trans.exe version 6.13 (release 640 - 03.06.05 - 17:04:00).unicode enabled versionC:\usr\sap\X22\SYS\exe\run\r3trans.exe finished (0000).
INFO 2007-05-09 20:12:23
RFC parameter CLIENT set to value 000.
INFO 2007-05-09 20:12:23
RFC parameter USER set to value DDIC.
INFO 2007-05-09 20:12:23
RFC parameter LCHECK set to value 1.
INFO 2007-05-09 20:12:23
RFC parameter PCS set to value 1.
INFO 2007-05-09 20:12:23
RFC parameter LANG set to value EN.
INFO 2007-05-09 20:12:23
RFC parameter ASHOST set to value cix22.
INFO 2007-05-09 20:12:23
RFC parameter SYSNR set to value 00.
INFO 2007-05-09 20:12:23
RFC connection information checked successfully.
ERROR 2007-05-09 20:12:24
FRF-00007 Unable to open RFC connection.
I tried the following fixes spread across different threads in this Expert Forums:
1. Someone said network problem. I rebooted, restarted the install and even redo it.
2. Another suggestion was to use caps on the password. Didnt work.
3. One suggestion was to update the keydb.xml file. However, I could find such property name:
search for the table t_SAPComponent_SAPSystemLogon_SHARED
then look for <fld name="pPW">, <properties>,
<property name ="GUIENG_USER_INPUT" and set the value
"GUINEG_TRUE" to "GUIENG_FALSE".
4. I even used the ddic password 19920706 which is supposed to be the default.
5. Restarted the instance and applied all the fixes above.
Does anyone know what is going on base on the logs above? Thanks.

try moving all your install disk onto local file system then rerun the install. That might work....

Discoverer 3i connection error.

Similar Messages

Maybe you are looking for