Error while creating SOURCE SYSTEM

Hi All,
I have a problem while creating Source System to a Solman syatem configured with BW content. I have configured few some source systems already in the same Solman System.The system shows the following error, previous to this i get the message a "generating connection to the source system"
<b>Error in source system RXX_100
Message no. RSAR502
Diagnosis
With Remote Function Call to system RXX_100 error Screen output without connection to user. ccurred.
Procedure
Remove the cause of the error.</b>
Kindly provide me suggestions and DOCS related to the same.
Suitable points will be awarded for replies.
Expecting your kind reply,
Vineeth

Hi ,
In SCC4 the source client should not set as production when creating the source system connection between two systems.Please check below SAP note
973555 - System must be open for creating/connecting source systems
Thanks,
Shanaka

Similar Messages

Error while creating source system entry in SAP BW system

Hi,
I am creating source system entry in SAP BW system for ECC system.In T-Code RSA1 i entered all the details of source system and BW system like RFC destination of source system and RFC user passowrd.
After clicking on enter system is promting me to enter into the souce system using administrator user.but i don't have admin user with SAP_ALL and SAP_NEW profiles because in my organisation they don't assign these profiles to any user.
So can you please update me what are the authorization required for dialog user in source system.
Regards,
Gaurav

I would recommend to create a USER ID as COMMUNICATION type and assign SAP_ALL for it... this way, it can never be misused..
This will ensure that the user ID will have correct authorization in the source system and will not face any authorization related errors later on

Error while creating source system in BI: Modification not possible

Hi All,
We are about to move to production, and therefore it's necessary to create in BI the source system related to our ECC (R/3). While trying to perform this action from BI side we received the error message:
SAP system has status 'not modifiable'. Because of this, and following with known consultants practices we've changed the client to customazing but it still not working although the message at this time is: Changes to repository or cross-client Customazing are not permitted. We have also verified transaction SE06 but it's not possible to change the Cross-Application Component to Modifiable.
Did someone face with this same problem before?
Thanks to all in advance,
Regards,
José.-

Hi Rick,
I really appreciate your quick response. We followed your recommendation and could create the source system without problems. Thanks once again!
Best Regards,
José.-

Portal Runtime Error while creating new system in portal content

Hi
Can anyone solve my problem, i am geting error while creating new system in p ortal content
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file

Hi,
Check this link for creating system object
http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
Regards
Arun

RUNTIME ERROR WHILE CREATING NEW SYSTEM IN EP6

Hi
Can anyone solve my problem, i am geting error while creating new system PORTAL FOR to connect biw 3.5 system
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.templateSelection
Component Name : com.sap.portal.admin.templateselectionwizard.default
com/sap/portal/iviewserver/cache/OClass.
Exception id: 11:29_26/12/06_0014_5891950
See the details for the exception ID in the log file
thanks in advance
Rock

hi,
check the log file and let me the the error.
manish

CIM_ERR_ALREADY_EXISTS: Error while creating Business System

Hi,
I am getting following error while creating Business System in SLD, the Technical System is already created from RZ70 transaction in the IDES system
Error Creating business system: CIM_ERR_ALREADY_EXISTS: Instance already exists://inbbssun01/sld/active:SAP_LogicalALESystem.CreattionClassName="SAP_LogicalALESystem", Name = "LSIDES800.SystemName.800.SystemName.IDS.SystemNumber.0020224902.SystemHome.idesecc"
Thanks,
RP

Hi,
This error means that a business system with this name(or associated with this technical system) is already there in SLD.
You need to check that before you try creating it (might be someone else have created it before)
Updated
If you have created and deleted a business system and then trying to recreate one then you need to delete all the instance of it from Content Management (in SLD)
Regards
Suraj
Edited by: S.R.Suraj on Nov 9, 2009 12:34 AM

Error msg RSAR502,while creating source system?

Hello Gurus,
when i am creating source system i got error msg called RSAR502,can any one solve this issue..
Thanks in Advance

Hi,
Check the OSS note : 184586,493422.
Take the help of ur Basis support.
Hope it helps-
MM

Error while activating source system

Dear friends,
I am getting Error ' Basic type does not exit' while activating source system in RSA1.
please give the solution .
Regards,
D.prabhu

Hello,
this is due to incomplete partner profiles;
When createing your source system you have to ensure that your source system is open for modifications (transaction SCC4) and that you have administrative rights in this system. Indeed the creation of a source system will create all partners profiles in both systems thus the source system needs to be open for modification.
ensure this and "restore" your source system from RSA1
hope this helps...
Olivier.

Error while creating MDM system on Portal

Hi All,
I am trying to create MDM system in EP. MDM is 5.5 SP06. EP is 7.0 . We have upgraded the MDM sca files on Portal from SP05 to SP06.
While creating the system , after entering the server, we are getting the following error.
com.sap.mdm.internal.protocol.manual.ServerException: File failed a crc check
Please help
Regards
Shilpa

Hi Shilpa,
If this is your MDM build version 5.5.63.80 SP06. It means you are using MDM 5.5 SP06 Patch3 hotfix 80.
You need to find the Sca file of compatible with this version.
So they should be
- MDMJAVAAPI06_03.sca
- BPMDMAPPLN06_03.sca
- BPMDMTECHN06_03.sca
The hotfix number can slightly differ but the Support pack and patch number must match.
You need to follow this link:
http://service.sap.com/swdc
(download MDM support packages) Download>support packages and patches>entry by application
group>sap netweaver>sap mdm>sap mdm 5.5>Entry by component>Portal content
Then select which MDM portal content you want and check what is the version of those available sca files.
based on the availablity of the sca files you need to upgrade/downgrade or server.
As compatibility between the server version and sca files is a must for proper functioning.If its not possible to change your mdm server version then you can ask your Basis team to hunt the matching sca files for you.
Hope It Helped
Thanks & Regards
Simona Pinto

Authorization for user in ECC while creating source system in RSA1 in BW

Hello All..
We are trying to create source system from BW(7.0) system using transaction code rsa1 to R/3 Production server.
After providing details in RSA1->Source system ; Remote logon screen of Production server pops up ...and ask to login thru admistrator Id..
To achieve the above task,, what authorization user should have in R/3 system..
Thanks

Hi,
Hope you are using the RFCUSER with these profile SAP_ALL , SAP_NEW , S_BI-WX_RFC in SAP ECC. Please create the RFCUSER with above profiles in ECC and BW (SAP_ALL , SAP_NEW and S_BI-WHM_RFC).
Pls follow the below steps for source system connection
In ECC side
1.) Client administration SCC4 ( select your client and allow changes to repository and cross client customizing)
2.) Define a logical system in ECC
3.) Assign a logical system in ECC
4.) Creating RFC user with system user type and give these profiles SAP_ALL, SAP_NEW, S_BI-WX_RFC
In SAP BI Side
1.) Client administration SCC4 ( select your client and allow changes to repository and cross client customizing)
2.) Define a logical system
3.) Assign a logical system
4.) Creating RFC user with system user type and give these profiles SAP_ALL, SAP_NEW, S_BI-WHM_RFC)
5.) Define RFC user as default (Click RSA1> Global Settings/Customizing dialog box> Glob. Settings)
Connection of SAP BI with ECC
RSA1> Source System>SAP>create>Enter the below entries
Target computer (server) Server of the SAP ECC
System ID System ID of the SAP ECC
System number System number of the SAP ECC
Background user in source system RFCUSER
Password for source system Password
Background user in BW RFCUSER (can not be changed in this activity)
Password for BW user Password
Select unicode in RFC destination and don't select the checkbox in logic screen.
On the dialog box Please log on as an basis administrator in the following screen choose Continue.
Log on to the Source System with your administrator user. Choose the correct client.
On the Replicate Metadata dialog box, choose Only Activate.
Make sure ECC client will allow changes in cross customizing client. It is one time activity once success then deselect the entry.
Hope this will help you to connect the system.
Rgs,
Ambuj Kathuria

"Error in source system" while creating source system

Hello,
I don't know what's our general problem (I suppose that it's ageneral problem) but we always have the following eror while creating a source system:
When we want to create a source system on BI, we first get an error "No connection to source system possible". After checking the RFC connection and correct the password of the remote user on the automatically created _DIALOG RFC connection the exception changes to "Error in source system".
The error occurs after the information "Please log on as an administrator in the following screen".
The remote user on R/3 side has got profiles S_BI-WHM_RFC and S_BI-WX_RFC (found two conflicting statements regarding this profiles), on BI side it has got SAP_ALL and some more profiles
What else could be the problem?
Greetings & Thanks
Bettina

Hello,
now we know that
1. the remote user needs profiles SAP_ALL and SAP_NEW and has to be dialog user with a password unequal that password it should have in the future (otherwise you don't see the error messages that appear during the login process)
2. the system has to be changeable (scc4 and se03)
After the source system is created the changeability can be changed to the original values and the remote user can be changed to a communication user again.
Thanks for the tip regarding the authorizations.
Greetings
Bettina

Error : Modification not possible- while creating source system in BI7

Hi BI Guru's,
We are using BI7 and source system ECC6 ,We are about to move to production, When creating the source system in BI PRD system we getting the Error Modification not possible.we created RFC connection, background user and remote connection works fine.
Is there any body put some light on this issue
thanks in advance,
Regards,
Mohan

Mohan,
Check if your logical systems are in place in SCC4 and also in the transport connection.
Also check if you are connecting to the source system by IP Address or by logical name.
Accordingly you would have to maintain the source system connections.
Arun

Error while creating a system object for R3 in portal

Hi,
I am getting error while trying to create a system object in portal.
Following are the details I used :
Under WAS...
Web AS Host Name :<XXXX>:8001
Web AS path: /sap/bc/bsp/sap/
Web AS protocol : http
Under User management:
Authentication Ticket Type : SAP Logon Ticket
Logon Method :SAPLOGONTICKET
User Mapping Type : admin,user
Under Connector:
SAP Client : <Client NO>
SAP System ID : <System ID>
SAP System No : <System No>
System Type : SAP_R3
While trying with connection test... I am getting like this:
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
5. The host name <FQDN Server Name> was resolved successfully.
6. The server sapdwh01 could not be pinged successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
Kindly help.
Regards,
Niraj
Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

I created a SAP Transactional iView for transaction SE80.
Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
Got portal Runtime error :
Portal Runtime Error
An exception occurred while processing your request
Exception id: 12:57_11/12/08_0003_2795650
See the details for the exception ID in the log file.
Regards,
Niraj

Error while creating Technical System

Hi
i am creating Technical system in SLD. I gave all inputs for host name, Instance, License correctly.
When i press next, It is throwing this error. Do anyone have any idea about this.
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
    at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
    at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
    at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
    at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
    ... 27 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0006.20060302084208.0000 (release=NW04S_06_REL, buildtime=2006-03-04:17:33:21[UTC], changelist=10570, host=pwdfm114), build date: Sat Oct 14 19:38:14 GMT+05:30 2006
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en
Time of Failure Sat Nov 11 14:04:06 GMT+05:30 2006 (Java Time: 1163234046750)
Web Dynpro Code Generation Infos
sap.com/tcsldwd~main
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~landscape
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcwddispwda
No information available null
sap.com/tcsldwd~businesssystem
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~technicalsystem
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcwdcorecomp
No information available null
sap.com/tcsldwd~softwarecatalog
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
sap.com/tcsldwd~namereservation
SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
Detailed Error Information
Detailed Exception Chain
java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
     at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
     at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
     at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
     at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks in Advance
Vijay Raheja

HI Michal Krawczyk,
Thanks for your response. i am working on XI 7.0 and when i go to SLD-> Adminitsrtion-> SLD Data Supplier. There i tried to add SLD CLient.
It is asking me for :
-URL of target SLD system, e.g. http://host:port/
-User
-Password.
What should i give here. WHat will be port for R/3 system to which i want to connect.
Just to add: I have already created Technical system for R/3(CLient 600). I added this through SLD only. But now it is giving error for Technical SYstem for same R/3(Clinet 812).
Thanks,
Vijay Raheja

Error when creating source system

Hi,
Could someone help me to solve this issue :When I want to create a source system D99100 in BI , I get the following message:
the test and remore connection via sm59 in BI are OK.
Source system cannot use any of the proposed connection names
Message no. RSAR362
Diagnosis
Every connection to a source system is named using a unique two-digit identifier. Source system D99100 does not accept any of the proposed values.
The last proposed value was B9.
System Response
Source system has not been connected.
Procedure
If you want to recreate the source system from BI information, then you can only use a single value, namely B9, because the connection already has this name in BI.
Delete the existing connections in the source system or contact a BI consultant.

Hello,
By this time your issue might be resolved.
When you are trying to Connect or Reactivate source systems you might get this error. In the source system (R/3) check the table entries RSBASIDOC. Some reason after system copy, these entries should correct if you run BDLS and some time it mess up.
Go the table and go to the edit mode and change the entrie for that RFC destination. Change the filed TSPREFIX to some thing else and save it. Go back to BW and try to reconnect and you will be able to connect it.
Hope this helps in the future for this thread.
PREDDY.

Error while creating SOURCE SYSTEM

Similar Messages

Maybe you are looking for