SAP PCo 2.1 - Error Retrieving destination systems

Hi All,
I've configured source and destination systems successfully in PCo Mgmt console and created an agent instance.
While creating notification under agent instance, I'm getting an error - "Error retrieving destination systems \[key not valid for use in specified state\]".
Can anyone guide over this error ?
Thanks and Regards,
Sumit.

Hi Tony,
From your error description, I suspect that the management console is starting without administrative priviledges. Can you check and make sure you are starting the management console with administrator rights?
You may also want to take a look at the PCo Security Guide available at [http://help.sap.com].
Kind Regards,
Diana Hoppe
Edited by: Diana Hoppe on May 23, 2011 8:21 AM

Similar Messages

SAP PCo, OLEDB Source Error

Hi gurus,
I'm trying to start a PCo agent using a OLEDB connection and I'm getting the following error. All the "Connection Check" buttons (At ODBC DSN and at PCo) says the connection is OK.
At PCo, I have created the OLEDB source and selected the default provider, there is no .Net Framework Data Provider for ODBC on the list.
Any suggestion? I didn't even find where to download this .Net Framework Data Provider for ODBC.
26/5/2011 14:24:04,.,1,2244,Teste,Error,Host,failed to create ConnectivityAgentProxy,"General PCo Fault: The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not support the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net Framework Data Provider for ODBC (System.Data.Odbc).

Diana,
When trying to connect UDS to IP21 using the "xMII OLE DB UDS" server type in UDS, I'm getting the following error:
Start of Exception Stack Trace **********
            1)         [06/09/2011-10:47:05.374] OLEDBTU [P:3268, T:5580,       UDS, ] 0x0      HRESULT: 0x80004005 [[AspenTech][SQLplus] SQLplus Access Denied - No read access]           [Connection.cpp @ 85, COleDbConnection::FinalInitialize]
            2)         [06/09/2011-10:47:05.374] OLEDBTU [P:3268, T:5580,       UDS, RETHROW] 0x0 Rethrowing exception.            [Connection.cpp @ 111, COleDbConnection::FinalInitialize]
            3)         [06/09/2011-10:47:05.374] OLEDBTU [P:3268, T:5580,       UDS, RETHROW] 0x0 Rethrowing exception over COM.    [sqlUtil/lhdsBasicConnection.h @ 290, lhds::LHDSBasicConnectionImpl<class COleDbConnection>::Initialize]
            4)         [06/09/2011-10:47:05.374] OLEDBTU [P:3268, T:5580,       UDS, ] 0x0      Caught exception over a COM boundry.            [sqlUtil/lhdsBasicConnectedDs.h @ 65, lhds::LHBasicDataServerImpl<class CLHOleDbDataServer>::InitializeRuntime]
            5)         [06/09/2011-10:47:05.374] OLEDBTU [P:3268, T:5580,       UDS, RETHROW] 0x0 Rethrowing exception over COM.    [sqlUtil/lhdsBasicConnectedDs.h @ 100, lhds::LHBasicDataServerImpl<class CLHOleDbDataServer>::InitializeRuntime]
            6)         [06/09/2011-10:47:05.374] OLEDBTU [P:3268, T:5580,       UDS, ] 0x0      Caught exception over a COM boundry.            [sqlUtil/lhdsBasicConnectedDs.h @ 292, lhds::LHBasicDataServerImpl<class CLHOleDbDataServer>::Initialize]
            7)         [06/09/2011-10:47:05.374] OLEDBTU [P:3268, T:5580,       UDS, RETHROW] 0x0 Rethrowing exception.            [sqlUtil/lhdsBasicConnectedDs.h @ 294, lhds::LHBasicDataServerImpl<class CLHOleDbDataServer>::Initialize]
            8)         [06/09/2011-10:47:05.374] OLEDBTU [P:3268, T:5580,      Host, HANDLED] 0x0    Handled exception.            [DataServerThread.cpp @ 117, DataServerThread::SpawnServer]
End of Exception Trace **************
Do you have any clue of what is wrong?
Until now I do not have a historical connection with IP21 since PCo and UDS return errors.
Thank you in advance

Error while starting SAP PCo 2.1

Hi,
When i start the Management Console of SAP PCo 2.1, I get an error which says 'Error Retreiving Destination Systems. [Access to the database file is not allowed. [File Name: C:\Program Files ....\Configuration.sdf' ]].
Any clue of why this happens. It was working fine earlier, but suddenly I get this error msg.
Regards,
Tony.

Hi Tony,
From your error description, I suspect that the management console is starting without administrative priviledges. Can you check and make sure you are starting the management console with administrator rights?
You may also want to take a look at the PCo Security Guide available at [http://help.sap.com].
Kind Regards,
Diana Hoppe
Edited by: Diana Hoppe on May 23, 2011 8:21 AM

*Error retrieving some or all of your defaults from the SAP SRM system*

NULL Value in field when user tries to update their MYDEFAULT personal details in the MYBUSINESS webportal
http://imageshack.us/photo/my-images/62/mydefaults.png/
Error retrieving some or all of your defaults from the SAP SRM system
SAP 640 GUi on WINXP
any ideas?

Hi,
Are you enable POP account in internal Exchange server or using POP from ISP outside?
Check File > Accounts Setting > Email > Select this account > Change > More Setting... > Outgoing Server tab > Check the first box: My outgoing server (smtp) requires authentication and don’t circle: Log on to incoming mail server before
sending e-mail.
If you are using check the LDAP, please also check the server address is correct or connection port is right.
If there is nothing wrong with your client. The problem could be on the mail server. Sometimes it could be due to maintain of the mail server of your recipient, and it is not available . You can give a try other time. If still failing, very possible the
email is no longer available.
Please let me know the result and feel free to post back.
Tony Chen
TechNet Community Support

Error: Could not retrieve deployment system configuration

Hi,
when I'm trying to list deployed components in the deployment perspective of my NW Developer Studio (7.2), I get the following error. It seems that the NW server is not reachable, but I had a look at the management console on the server - everything is running.
Exception occurred during the 'List Components' operation.
Cause:Could not retrieve deployment system configuration for CE1. Please check if the system is running.
Exception:
com.sap.ide.eclipse.deployer.api.APIException: Could not retrieve deployment system configuration for CE1. Please check if the system is running.
     at com.sap.ide.eclipse.deployer.DeployerPlugin.getCurrentServerInfo(DeployerPlugin.java:105)
     at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:201)
     at com.sap.ide.eclipse.deployer.ui.UIUtils.getClient(UIUtils.java:212)
     at com.sap.deployment.ui.nodes.SystemNode.fetchData(SystemNode.java:84)
     at com.sap.deployment.ui.nodes.SystemNode.refresh(SystemNode.java:78)
     at com.sap.deployment.ui.view.RepositoryJob.run(RepositoryJob.java:26)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
In addition, I noticed that if I add the NW server in the developer studio (preferences > SAP Java AS), only on server instance is listed (SCS01). Normally (after NW installation), two instances have been listed there.
The error prevents to deploy anything from within the developer studio. Does anyone have a clue about that? Thanks in advance!

The problem I faced was related but just slightly different - solution is below. This is really only an issue if your AS Java server is on a different server than your NWDS and a firewall is active.
Error when trying to publish ConverterWeb demo project from local dev machine CE 7.2 Netweaver Developer Studio to server CE 7.2 AS Java was:
Could not retrieve deployment system configuration for CE1. Please check if the system is running.
[ERROR: 7/10/10 10:58 PM /userOut/daView_category (eclipse.UserOutLocation)
Thread[Thread-22,5,main]]
Issue is a firewall problem. Solution is:
1) remove default SAP AS Java from NW Developer Studio (Windows -> Preferences -> SAP AS Java
2) shutdown NWDS
3) open ports 50113 (port for instance 1), 50013 (port for instance 0), 50004 (deploy port) and 5000 (http for NWASJAVA) on the AS Java server.
4) open NWDS
5) add SAP AS Java in NWDS (Windows -> Preferences -> SAP AS Java: host - 192.168.1.16, instance - 1, Domain - Default
6) add SAP AS Java in NWDS (Windows -> Preferences -> SAP AS Java: host - 192.168.1.16, instance - 0, Domain - Default
7) publish ear.
8) navigate to: http://192.168.1.16:50000/ConverterWeb/
obviously you'll need to replace the internal ip with the ip of your server.
I think this firewall info is somewhere in the docs.
Edited by: adamtarshis on Jul 11, 2010 8:16 AM

RFC system error for destination GTADIR_SERVER

I just installed trial version 7.0 ABAP SP12. I started the learning path displayed in SE80, create a table and some class for working with it.
When trying to create a data-element I get the error "RFC system error for destination GTADIR_SERVER". Any hints about what this server is and how to set it up?

This message is not supposed to appear for customers, but it doesn't cause any harm either. You can click through and ignore it.
The message is removed for customers in SP13. Check OSS Note 1063482.

"RFC system error for destination GTADIR_SERVER",why?

RFC system error for destination GTADIR_SERVER
Hi AlL,
We are working in CRM 6.0.
While creating the Components and Views,i am encounter this Error.
<<
"RFC system error for destination GTADIR_SERVER"
Message no. SGSUB104
Diagnosis
Access to destination GTADIR_SERVER is currently not possible.
System Response
There was a problem with the execution of the function through a Remote Function Call (error in commmunication or communication setup).
The entered destination was GTADIR_SERVER.
The RFC error message reads:
RFC destination GTADIR_SERVER does not exist.
Die Aktion wurde deshalb abgebrochen.
Procedure
Wiederholen Sie die Aktion sp鋞er.
Wenn die Destination GTADIR_SERVER 黚er einen l鋘geren Zeitraum hinweg nicht erreichbar ist, dann verst鋘digen Sie die Systemadministration f黵 GTADIR_SERVER.
Procedure for System Administration
Weitere Informationen - siehe Systemprotokoll in Destination GTADIR_SERVER.
>>
Any ideas?
Thanks & Regards
Edited by: Autumn of Desert on Oct 12, 2009 8:33 AM

Cancelled

CCC or Disk Utility to clone a Mac HD of one new iMac to another, over ThunderBolt, we are getting I/O errors. Even though the clone fails, the destination system does boot and log in, however, the logins take a very very very long time.

When using CCC (Carbon Cophy Cloner) or Disk Utility to clone a Mac HD of one new iMac to another, over ThunderBolt, we are getting I/O errors. Even though the clone fails, the destination system does boot and log in, however, the logins take a very very very long time.
Thoughts.
Edit: Already ran Disk Utility. Also reinstalled a fresh OS on top of the cloned OS and it seemed to remedy the problem. Then, cloned to next machine in the row of the lab. Same problem.

OK, by that I assume that you used Disk Utility to repair the subject disk and it reported "The volume (name) appears to be OK" in green.
Also verify you followed the instructions here: http://help.bombich.com/kb/usage-scenarios/i-want-to-clone-my-entire-hard-drive- to-a-new-hard-drive-or-a-new-machine
If so, the Thunderbolt connection begins to look suspicious.
Reinstalling OS X subsequent to the "clone" operation may be an acceptable workaround but you should not have had the I/O errors you describe, nor should the login times (subsequent to the initial login, that is) be unacceptably long. It calls into question the integrity of all the information that was transferrred.
I'll try to attract the attention of a CCC expert who will likely provide more competent assistance. You can also try the Bombich support site: http://help.bombich.com

Error in source system in BI 7.0...

Hi,
When creating a source system in Bi 7.0, when i am going to t code- rsa1- client-right click and then check,it's giving an error like:
EDI- partner profile not available and then detail for this error is-- a partner profile cannot be found with this key- /DBICLNT300/LS
THIS INVLOVES THE KEY FIELD OF THE TABLE EDPP1-
PARNUM-PARTNER NUMBER
PARTYP-PARTNER TYPE
Please help me in solving this. Thank You.

Hello,
Try a restore on your source system (rightclick -> restore) This way idoc ports and agreements are regenerated between BW and R/3. If this does not solve the problem ceck this:
Hi,
Did you do a system copy for BW ?
Try a restore (rightclick on your source system) in most cases this will solve the problem.
If not check the notes below:
184322 Procedure after DB copy of BW source systems
886102 System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
325470 Activities after client copy in BW source systems
325525 Copying and renaming systems in a BW environment
184754 Procedure after BW database copy
184447 Building a BW-system landscape
184971 Notes on BW source system connections
140276 Error in source system assignment
524554 Storing destinations in the BW environment
538052 Maintenance of Myself destination in BW
Regards, Patrick Rieken

Error while source system creation/Source system transport

Hi,
     In our BW implementation, the system landscape is only 2 servers. One is BW Dev, another is BW Prd. All configurations are done in BW Dev and I extracted the data from QAS for this BW Dev system.
     Since we cant create the source systems in the BW Production system, I tried to create the source system for the SAP R3 Production system in BW Dev and trying to transport this to BW Production Instance.
     I have two queries.
1. Is this way is correct for creating the Source System for BW Production system?
2. When I tried to activate the source system I am getting the following error messages. (I tested the RFC Destinations. There is no problem, I also done the configurations for logical system creation and client assignment in both the systems).
Error in source system GWPCLNT900
     Message no. RSAR502
Diagnosis
     With Remote Function Call to system GWPCLNT900 error connection closed
     (no data) ccurred.
Procedure
     Remove the cause of the error.
When tried again I got the following error message
Basic type ZSBB030 doesnt exist. EA 447
Result of the destination check: Timeout RSAR 375.
Could anyone throw some light on these errors?
Thanks in advance.
Krishna

Hi,
you need to maintain the logical systems on both R/3 and BW. You also need to set up the RFC connection with users that can log in to the other system. The R/3 system must be open for customizing in scc4.
In transaction se03 the system change options for 'Business Information Warehouse: SAP Namespace' and 'Business Information Warehouse: Customer Namespace' may need to be modifiable. I am not completely sure about this.
The last thing I will mention is that I have seen source system creation fail when the RFC-users are system users, and the source system creation worked if the RFC-users was display user while creating the source system. The RFC-users must be changed back to system user later...
Please look at best practice documents on a more step-by-step guide...
Best regards,
Christian Frier

IDOC not reaching destination system

Hello,
I am trying to send DOCMAS type IDOC from one SAP sys to another SAP sys.The IDOC has the status 03 (The IDoc was sent to an SAP system or an external program via a transactional RFC) but i dont see the IDOC in the target sys.
Please let me know what could have gone wrong.
Thanks,
Rakesh.

Hello Rakesh More ,
First let us know how you corrected the previous error???. What was wrong?
Then talk about the next issue.
If you maintain properly the Inbound IDOC partner profile this error should not come. Make sure you have the below things set-up properly:-
1) In the inbound IDOC in the destination system there should be a partner receiver in the IDOC control data. Make sure you have maintained the partner profile for that partner and for the partner type as well.
2) For the partner make sure you have maintained the proper inbound mesaage type and process code properly.
Thanks,
Greetson
Edited by: Greetson Shunmugasundaram on Aug 1, 2011 9:47 PM

Any SAP Note for RFC Error between BI and ECC 5.0

Hi..
the RFC Destination between BI and ECC 5.0 is giving errors.
Plz let me know if there is any Support pack or any solution to fix this error.
thanks..

Hi,
pls find the RFC connection details
1 Prerequisites
1.1 User Roles
Use
With the Building Block Connectivity a configuration role for each component is provided to access all transactions relevant for the installation. The following roles are available:
Technical name Description File name for upload
B02_01C B02 - Connectivity Configuration Role (SAP R/3) B02_01C.SAP
B02_03C B02 - Connectivity Configuration Role (SAP BW) B02_03C.SAP
C71_04C B02 - Connectivity Configuration Role (SAP CRM) C71_04C.SAP
B02_04C_SRM B02 - Connectivity Configuration Role (SAP SRM) B02_04C_SRM.SAP
Procedure
Please upload the necessary roles and add them to your user, using transactions PFCG (Role Maintenance).
2 Local Settings
This chapter describes all local settings that are necessary for each component like SAP R/3, SAP SCM, SAP BW, SAP CRM or SAP SRM.
2.1 SAP R/3
2.1.1 Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu Define Client Administration (SAP R/3)
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1. Choose Display  Change.
2. Confirm the warning message Caution: The table is cross client.
3. Select your SAP R/3 client and choose Details.
4. In the Change View Clients: Details screen, activate the following settings:
u2022 Automatic recording of changes
u2022 Changes to Repository and cross-client Customizing allowed
u2022 eCATT and CATT allowed.
5. Save.
6. Go back to the SAP Easy Access menu.
2.1.2 Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1. Define the systems as logical systems.
2. Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code SPRO
SAP R/3
IMG Menu Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2. Choose New entries.
3. In the column Log System, enter a name for the logical system that you want to create.
4. In the column Name, enter a description of the logical system.
Log. System Name
where XXX is the system name
and NNN is the client.
5. Save your entries.
A transport request for Workbench appears.
6. Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7. Select an existing request or create a new request, if necessary.
2.1.3 Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Assign Logical System to Client
Transaction Code SCC4
SAP R/3 Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Choose Display ® Change.
3. Confirm the warning message The table is cross client.
4. Select your R/3 client and choose Details.
5. Enter the name of the logical system of your SAP R/3 client.
6. Save and confirm the warning message Be careful when changing the logical system.
7. Choose Back twice.
2.1.4 Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1. Access the transaction using:
SAP R/3 Role Menu Creating an RFC User (SAP R/3)
Transaction Code SU01
SAP R/3 Menu Tools  Administration  User Maintenance  Users
2. In the User field, enter RFCUSER.
3. Choose Create.
4. On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type System
Password LOGIN
Profile
Profiles SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language EN
5. Save your entries.
2.3 SAP BW
2.3.1 Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1. To perform this activity, choose one of the following navigation options:
SAP BW Role Menu Local Settings ® Define Client Administration
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
2. Switch to change mode.
3. Select your client.
4. Choose details.
5. In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6. In field Client Role enter Customizing
7. Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), u201CAutomatic recording of changesu201D and u201CChanges to Repository object and cross-client Customizing allowedu201D is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2 Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Defining a Logical System for SAP BW (SAP BW)
Transaction Code SPRO
IMG Menu SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1. A dialog box informs you that the table is cross-client. Choose Continue.
2. On the Change View u201CLogical Systemsu201D: Overview screen, choose New entries.
3. On the New Entries: Overview of Added Entries screen enter the following data:
Field name Description R/O/C User action and values Note
Log. System Technical Name of the Logical System Enter a name for the logical BW system that you want to create
Name Textual Description of the Logical System Enter a clear description for the logical BW system
4. Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3 Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu Assigning Logical System to Client (SAP BW)
Transaction Code SCC4
SAP BW Menu Tools  Administration  Administration  Client Administration  Client Maintenance
1. In the view Display View "Clients": Overview, choose Display.  Change
2. Confirm the message.
3. Select your BW client.
4. Choose Details.
5. In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6. Save the entries and go back.
2.3.4 Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Modeling  Administrator Workbench: Modeling
Transaction Code RSA1
1. In the Replicate Metadata dialog box, choose Only Activate.
2. If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5 Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu Creating RFC User
Transaction Code SU01
SAP BW Menu Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1. On the User Maintenance: Initial Screen screen:
a. Enter the following data:
Field Entry
User RFCUSER
b. Choose Create.
2. On the Maintain User screen:
a. Choose the Address tab.
b. Enter the following data:
Field Entry
Last Name RFCUSER
Function Default-User for RFC connection
c. Choose the Logon data tab.
d. Enter the following data:
Field Entry
Password LOGIN
User type System
e. Choose the Profiles tab.
f. Enter the following data:
Field Entry
Profiles SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g. Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6 Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu Define RFC-USER as default (SAP BW)
Transaction Code RSA1
SAP BW Menu Modeling  Administrator Workbench: Modeling
1. On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2. In the Global Settings/Customizing dialog box choose Glob. Settings.
3. On the Display View u201CRSADMINA Maintenance Viewu201D: Details screen:
a. Choose Display  Change.
b. Enter RFCUSER in the BW User ALE field.
c. Choose Save.
Hope this helps in solving u r problem
Regards
Ramakrishna Kamurthy

Destination system cannot be used for classic qRFC by activating integration models

Hi All,
I am trying to connect ECC Release 702 to SAP TM 8.0 but by activating integration models(CFM2) i got following runtime error:
Error analysis
    Short text of error message:
    Destination TMCLNT100 cannot be used for classic qRFC
    Long text of error message:
    Technical information about the message:
    Message class....... "SR"
    Number.............. 320
    Variable 1.......... "TMCLNT100"
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
any one has idea how to solve that?
Thanks a lot!
Kind regards
RW

RW,
I am definitely not an expert on SAP Transportation Management. However, maybe your destination system has been set up as bgRFC instead of qRFC?
bgRFC (Background Remote Function Call) - Connectivity - SAP Library
Best Regards,
DB49

Java communication error - RFC destination NOT_CONFIGURED does not exist

Hello,
We are facing problem when sending reports(BEx Quert) through broadcasting to the users. We are getting the error "Java communication error RFC destination NOT_CONFIGURED does not exist" in the Log Display (Tcode: RSRD_ADMIN).
In the broadcasting setting, if we select variable values in the tab "General Precalculation" then we can able to send the report to user, instead of selecting variable values, if we use the option "User Specific" check box in the tab Receipient(s) (which will take selection from the role authorizations defined in the respective user roles), then we are getting the above error.
Recently we have upgraded suppor package, please find the system details below
P_BASIS - SAPKB70025
PI_BASIS - SAPKIPYM12
SAP_BW - SAPKW70027
Java - Support Package 25
We didn't change any roles and authorizations recently, just upgraded to latest SP. Can anyone suggest if any steps or checks need to be perfomed after applying these SP or missing anything?
Thanks in advance
Regards,
Venkatesh

Hi,
This is configuration issue. Please check the configuration between BW and EP below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0a5216a-349c-2a10-9baf-9d4797349f6a?QuickLink=index&overridelayout=true
Thanks,
Venkat

Sm 59 error in r3 system

hai friends
iam creating RFC destinaton in r3 system
test connection is working good
but remote logon is not working .
it is giving error like this
you are not authorized to usee function network administation.
iam using ecc6.0
destination system is XI system .
what is the problem.
with regards
srikanth vipparla

Hi,
you should try to call the rfc with a service user:
Differences from "communication" and "service" users
http://help.sap.com/saphelp_nw04s/helpdata/en/76/562041c877f623e10000000a155106/frameset.htm
Regards
Patrick

SAP PCo 2.1 - Error Retrieving destination systems

Similar Messages

Maybe you are looking for