JCo Error in Mii 12.1.4

I am having problems with JCo in Mii 12.1.4. When the JCo Function builds the Output XML structure properly but does not build the Input Structure at all. When I look at the Log Viewer I see this error:
JCO Proxy Error: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.
[EXCEPTION]
org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified.
If I try to use JRA the Input and Output structures are generated correctly. In this case the same message is inserted into the log but only as a warning.
What is going on here? Can someone please help?
Thanks

Jeremy,
We are calling a custom BAPI. I had the ABAP developer change one of the inputs in ABAP function module from a table to a flat structure and it is now working. Very strange, indeed.
The input table contained only one field with a length of 2 characters.
Thanks

Similar Messages

Error while deploying the aplication-jco error

Hello Experts,
i know   thousends of questions in jco error. I have followed that threads , still i am getting an error.
Plz help me out from that error.
My EP server is running on was 6.20,
and xi server is running on was 6.40.
what i have done:
I have downloaded fightslist application from sdn.
i have deployed that application to was 6.40.
i created one technical system for abap.
i configured sld.
i entered service name(sapms147 3600/tcp(this is ides(4.7) serversid and port)) in servicefile in was 6.40 machine.
when maintaing jco connections the following error has come:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=mlbpsap06 GROUP=PUBLIC R3NAME=I47 MSSERV=sapmsI47 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapmsI47' unknown TIME        Fri Dec 01 15:27:10 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 MODULE      ninti.c LINE        494 DETAIL      NiPGetServByName2: service 'sapmsI47' not found SYSTEM CALL getservbyname_r COUNTER     7
My doubts are:
1.where i have to enter service i.e which machine (6.40 or 4.7 machine).
2.while creating technicalsystem which product i have to choose).
3while creating jco connection
    whichone i have to choose either dictinory mata data or applicationdata.
    in message server connection which user id & password i have to give means 4.7 userid or xiserver userid & password.
Plz helpme out from this.
Thanks in advance.

Hello Sai,
NWDS is local means which machine i am using.
My EP 6.0 SP2 in 172....202 but it is reunning on was 6.20.(mlbpsap02)
and here was 6.40 ip is 172.....203 IP ,but XI is installed on this server)(mlbpsap03)
and R/3 ECC ip is 172......201.(mlbpsap01)
no sneak preview edition and all.
I have downloaded application(sample flight) in webdynpro.
and i configured sld in 203(cim test connection is successfull) ip.and also entered the service name(sapmsecc 3600/tcp).After entering the service name i restarted the server
and created technical system for abap (and here selectiong products ecc components are not there.)
in webdynpro content admin while maintaing jco , the above error is coming.
i am unable to find where the problem is
the main thing is ep is not in was 6.40
further what i do
and where i enter the host ip and aliases.

Org.apache.jasper.JasperException; JCO error when Importing SAP Roles in C

Hello experts,
I have installed BOXI 3.1 SP3, Integration kit SP2, BW/BI 7.0 and ECC 6.0 on Windows 2008/64bit.
My goal is to import the roles into CMS from SAP BW/BI but getting the follwoing errors:
JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc
C:\Windows\SysWOW64\sapjcorfc.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform.
java.library.path [C:\Windows\SysWOW64\;D:\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\]
org.apache.jasper.JasperException
I followed the note 1292144 - JCO error when Importing SAP Roles in CMC,but unfortunately without success.
I installed SAP JCo Release 2.1.9 (64bit)
Best regards
Lutz
Edited by: Lutz Heinrich on Aug 12, 2010 4:17 PM

Install the 32bit version of the Java connector. BOBJ is 32bit so even on 64bit Windows you need the 32bit version of the Java Connector.
Regards,
Stratos

JCo error when calling from webmethods sap adapter to SAP BAPI

Hi,
I am getting an error "[SAP.102.9000] JCo error: (104) RFC_ERROR_SYSTEM_FAILURE - connection closed without message (CM_NO_DATA_RECEIVED)" when webmethods sap adapter is calling BAPI in SAP. The BAPI is working fine in SAP.
Can anyone suggest me a possible solution.
Thanks,
Sarath.

BAPI-step by step procedure
http://www.sapgenie.com/abap/bapi/example.htm
list of all BAPI's
http://www.planetsap.com/LIST_ALL_BAPIs.htm

JCO Error in Quality Portal

Hi ,
When i am running WDJ apps in dev portal , it's working fine . But when i am running through QA , it's showing the following JCO error .
Could not create JCO connection .Please ensure that you have nesured RFC destinations and/or logical system name properly for this model .
I tested the JCO in QA and it's working fine . Can anybody help me out regarding this .
And one more question , how to check JCO connections for WDJ apps inside NWDS ?
Thanks a lot .

Hi Jain,
While using RFC Models in the WD application, we maintain JCo dstinations.
These are specifically used to create a JCo Connection between 1 Web Application Server and 1 R/3 System. If any one of them changes, you need to update the same in the JCo destinations created.
The point here is, as you have changed the Dev System to QA System, i.e. your Web Application Server, you will need to create / maintain the JCo Destination with the same name on the Quality System for use of the application.
The JCo connection that you have been testing, is, may be on your developemnt system.
Hope it helps.
Regards,
Alka.

Java portal to bw hana sp08 JCO error

Dear Team
I am facing an issue after BW Hana migration.
Senario:1(BEFORE MIGRATION)
ORACLE DB/ BW NW 7.3+ JAVA PORTAL 7.01, EACH ON SINGLE STACK
HOSTNAME: xxxxx
DOMAIN: xxx.LOCAL
DATABASE: ORACLE11G
SYSTEM : ABAP + JAVA SEPARATE STACKS
PLATFORM: NW 7.3
JAVA 7.01
Senario 2
( MIGRATION ENTIRE ABAP STACK)
HDB/ BW NW 7.3
HOSTNAME: YYYYY
DOMAIN: xxxx.LOCAL
DATABASE: HDB SP08
SYSTEM : ABAP
PLATFORM: NW 7.3
Migrated only Abap stack and Java portal still runs with older database(oracle)in Older system(Xxxxx). I did the re-deployment on java portal with new HANA db configuration and it was success but.
When connecting Jco it is throwing error
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
only the issue with Jco rest of all connectivity working fine, anybody face the same issue ?

Hi,
Issue got resolved .
OOPS N BUGS !!!: Java portal to bw hana JCO error / Connection failed. Make sure that Single Sign-On is configured corre…
Thanks
Yoonus

Using JCO error Wrong repository version = 0 encountered.

Hi Guru,
We convert our existing Java Jco program to call RFC Sender adapter and XI should forward the request to RFC receiver adapter to our ECC.
We found that when we create client connection using gwhost, gwserv and tpname which is config in RFC sender adapter.
In our Java program throw error in the step of mRepository.getFunctionTemplate.
The error is "Wrong repository version = 0 encountered.".
It seems the program can not access function template from repository.
Anyone have this experience before, please advise
Thanks you.

It's working now.
For your knowledge, it seems it was something wrong inside the jrfc.jar.
The problem is not exactly the same but the solution is to apply OSS note 816491.

Jco: Error Connecting using sapgw04

Hi,
I have a problem using Jco to connect to a SAP-System.
I'm trying to connect to SAP using the following configuartions:
     sysnr:           04
     GWServ:      sapgw00
     GWHost:      XXX.YYY.com
     ASHost:      XXX.YYY.com
The code to create a repository for this configuration is:
     JCO.addClientPool(poolname, maxpoolsize, "538", "username", "password", "DE",
               "XXX.YYY.com", "04", "XXX.YYY.com", "sapgw00");
When I use this pool to get a function I get an Exception:
com.sap.mw.jco.JCO$Exception: (123) JCO_ERROR_FUNCTION_NOT_FOUND: Server repository could not create function template '[FUNCTIONNAME]'
caused by: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect from SAP gateway to RFC server failed
Connect_PM
     GWHOST=XXX.YYY.com , GWSERV=sapgw00, ASHOST=XXX.YYY.com , SYSNR=04
LOCATION
     SAP-Gateway on host h33e / sapgw00
ERROR       partner not reached
     (host XXX.YYY.com , service <b>sapgw04</b>)
The strange thing is the sapgw04 in the error-message.
Somehow JCO wants to use sapgw04 to connect to the RFC-Server. Is this an error in the SAP-Configuration or do I have to change the configuration of Jco?
How can I tell Jco not to use sapgw04 but sapgw00?
Any help would be appreciated!
Thanks
Torsten

Hi Torsten,
please check how you log on to your system. You are giving a system number 04, which corresponds to sapgw04. I'm not sure why the method needs all the information, seems to be duplicate to me (please comment if I'm wrong); it should be sufficient to use:
addClientPool(String key,
   int max_connections,
   String client,
   String user,
   String passwd,
   String lang,
   String ashost,
   String sysnr)
If you don't want to use sapgw04, just specify "00" for the sysnr.
Hope this helps, harald

JCO Error - SAP ER

Dear all,
I'm facing this issue during the SAP reconciliation.
Could you please help me?
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] ================= Start Stack Trace =======================
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] oracle.iam.connectors.sap.common.parser.SAPIDOCListener$ThrowableListener : serverExceptionOccurred
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] Description : (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
[2012-09-18T13:54:32.480+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable. (raised by system hgrs-hbk-s0340|a_rfc)[[
     at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:664)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2443)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
     at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
     at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
     at java.lang.Thread.run(Thread.java:736)
Caused by: RfcException: [hgrs-hbk-s0340|a_rfc]
message: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
Return code: RFC_FAILURE(1)
error group: 104
key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by hgrs-hbk-s0340|a_rfc
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2832)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2646)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2537)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2358)
     ... 4 more
Caused by: RfcException: [hgrs-hbk-s0340|a_rfc]
message: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
Return code: RFC_FAILURE(1)
error group: 104
key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by hgrs-hbk-s0340|a_rfc
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3378)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2827)
     ... 7 more
Caused by: com.sap.conn.idoc.IDocRuntimeException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
     at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:240)
     at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
     at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3349)
     ... 8 more
Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "HRMD_A07" with extension "ZIAM_HRMD_A07" is unavailable.
     at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:126)
     at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
     at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
     at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:143)
     at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.createIDocDocumentList(DefaultJCoIDocServerWorker.java:301)
     at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:199)
     ... 10 more
[2012-09-18T13:54:32.482+02:00] [oim] [ERROR] [] [OIMCP.SAPH] [tid: JCoServerThread-1] [userId: oiminternal] [ecid: 0000JbPDKdbEWN05zzP5iW1GM5y7000002,1:28079] [APP: oim#11.1.1.3.0] ================= End Stack Trace =======================

Hi Arun,
I did that step as well,
4.copy the Sapjco3.jar into the "CIA" directory of mercury folder and copy the sapjco.dll into the c:\windows\system32 file.
Any clues?
why this error?

Jco error

Hi Friends,
Itu2019s a support issue. Messages have failed in integration engine and inbound queues
I am getting different errors in different areas of xiu2014
In Integration engine Problem while determining receivers using interface mapping u201CCommunication failureu201D during JCO CALL
Similarly another error in other message in Integration engine unable to find URL for adapter engine.
In SMQ2 error is XI Error JCO_SYSTEM_FAILURE.MAPPING: Queue stopped.
Pls help !!

As suggested by Prateek, please check whether the SM59 destination AI_RUNTIME_JCOSERVER is working or not. If this is not working, search for AI_RUNTIME_ZX2 in smgw=>Goto=>Logged on Clients.
If you find the program ID AI_RUNTIME_ZX2 in TP name column and still have issue, please ensure that the user-id id PI_JCO_USER is not locked or the password has not been changed.
If you can not find the AI_RUNTIME_ZX2 in TP Name column, that means there is an issue with JCo RFC provider. In Visual Admin(PI 7.0) / NWA (PI 7.1), do the necessary stuff which makes the program ids to appear in smgw logged on clients. Basis should know about this.
Hope this helps.

JCo Error in EP6.0

Hi All,
I have developed a custom iview in EP6.0 which retireves data from R/3 using Jco and display the data in various controls like dropdown.
When I try to run the application I am getting a runtime error (while accessing the model).
I am using a JSPDynPage with a java bean for pulling the data thru JCo.
When run as a standalone the the java class for JCo is working fine, and the bean is also working fine with static data.
Is there is anything that needs to be added in portalapp.xml file?.
Any help is greatly appericiated.
Thanks,
Vasu.

Vasu,
This is what I picked up in the EP6->Java Development->Documentation area.
"JCo in the Portal Platform
JCo is included in the portal platform. However SAP JCO/ JCOClientService should not be used anymore in Enterprise Portal 6.0 and above.
Webservices or the "Java Connectivity Architecture" implementation "SAP Connectorframework" is recommended instead. This Framework provides additional functionality, especially the connection management, which allow tp programm scalable connections "
You should probably follow the example code to connect to SAP using Java Connector functionality as suggested by SAP.
Hope this helps.
Thanks
GO.

JCO error when calling BAPI

Hello guys,
I have an scenario R3 -> XI -> R3.
From the first R/3 we call a function in a program to execute a BAPI in the second R/3, so the BAPI doesn't exist in the R/3 that starts the interface.
We have configured the TCP/IP connection and with the same program ID in the Sender RFC adapter. All the connectios are running successfully but when we execute the program we have the error:
JCO.Server could not find server function 'Z_TEST'
Do you know if the BAPI has to be created in both systems, or it's only necessary in the R/3 destination to run.
All connections are running so the question is what we remarked before, the BAPI must be created in both R/3 systems?
Regards,
Xavier.

Hi Xavier,
strange, i answered to a very similar question a hour before, there was no reaction by Gerardo Mondragon .
How can the sender adapter get the metadata? If the FM is just in the receiver system? Maintain the meta data connection at Communication Channel to the receiver system...
Regards,
Udo

JCo error while viewing MSS iviews

Dear SDN Community,
When I am trying to view any of the MSS iViews like photo, orgchart, personal data, I get the following error message.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=sapdev GROUP=ED0LG R3NAME=ED0 MSSERV=sapmsED0 PCS=1 ERROR service 'sapmsED0' unknown TIME Fri Aug 03 11:59:07 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE nixxhsl.cpp LINE 776 DETAIL NiHsLGetServNo: service name cached as unknown COUNTER 4
The JCo connections SAP_R3_HumanResources and SAP_R3_HumanResources_Metadata are tested successfully and I see the gree light for these 2 in the WebDynpro console.
Can you please advice me here.
Thanks,
Vivek.

Vivek,
open the services file of your portal server box. This file will be in the location C:\WINDOWS or WINNT\system32\drivers\etc folder. In that enter an entry as below:
sapmsED0 36XX/tcp
where XX is the system no of your R/3 system. So if R/3 system number is 30 the line would be sapmsED0 3630/tcp.
Save the file and then try accessing iView again. This error message would be going off.
Regards,
Shubhadip

Error deploying MII 12.1.8

Hi,
after deploying successfully Netweaver 7.11 SP 05 SAP EHP1, I'm trying to deploy MII 12.1.8 (upgrading 12.1.0) with JSPM.After putting MII 12.1.8 .SCA file into inbox and running JSPM, I can see I should upgrade three "elements":
J2EEFRMW
LMCORE0
XMII
Looking at the logs, J2EEFRMW and LMCORE0 aren't really deployed, I can see multiple lines saying for example...
tcmonitoringapi.sda for component sap.com/tcmonitoringapi is rejected because it is already deployed
and at the end J2EEFRMW and LMCORE0 are resulting with status DEPLOYED.
But when the system is trying to deploy XMII, i'm getting error:
see follwing post

Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA for component sap.com/XMII aborted
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
          2. Contains Aborted deployment component:
sap.com_xappsxmiijraapp
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> sapjraxMIIIDOC07.sda for component sap.com/sapjraxMIIIDOC07 is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> xappsxmiiear.sda for component sap.com/xappsxmiiear is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> xappsxmiijraapp.sda for component sap.com/xappsxmiijraapp aborted
Error: Detailed message:
          1. Exception.
           -> Policy configuration "eis/XMIIRFC08" does not exist in security context "SAP-J2EE-Engine" for connector "eis/XMIIRFC08" in application "null".
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> sapjraxMIIIDOC08.sda for component sap.com/sapjraxMIIIDOC08 is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> sapjraxMIIIDOC04.sda for component sap.com/sapjraxMIIIDOC04 is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> sapjraxMIIIDOC03.sda for component sap.com/sapjraxMIIIDOC03 is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> sapjraxMIIIDOC10.sda for component sap.com/sapjraxMIIIDOC10 is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> xappsxmiidbinit.sda for component sap.com/xappsxmiidbinit is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> sapjraxMIIIDOC02.sda for component sap.com/sapjraxMIIIDOC02 is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> sapjraxMIIIDOC01.sda for component sap.com/sapjraxMIIIDOC01 is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> xappsxmiiumeactions.sda for component sap.com/xappsxmiiumeactions is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Error: Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA --> sapjraxMIIIDOC05.sda for component sap.com/sapjraxMIIIDOC05 is rejected because deployment of other component it depends on is rejected
Error: Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
Info: Deployment message for component J2EE-FRMW : See Deploy Controller log E:\usr\sap\CE1\J00\j2ee\JSPM\log\log_2011_02_25_19_33_23\deploy_2011-02-25_19-42-07.log for details.. Detailed message:
          1. Already deployed component has version:1000.7.11.5.0.20100502230600
          2. Already deployed component has version:1000.7.11.5.0.20100502230600. Archive
MIIQATEMP\sapmnt\trans\EPS\in\J2EEFRMW05_0-20002637.SCA for component sap.com/J2EE-FRMW was deployed successfully.
Info: Deployment message for component LM-CORE : See Deploy Controller log E:\usr\sap\CE1\J00\j2ee\JSPM\log\log_2011_02_25_19_33_23\deploy_2011-02-25_19-42-07.log for details.. Detailed message:
          1. Already deployed component has version:1000.7.11.5.0.20100502230600
          2. Already deployed component has version:1000.7.11.5.0.20100502230600. Archive
MIIQATEMP\sapmnt\trans\EPS\in\LMCORE05_0-20002600.SCA for component sap.com/LM-CORE was deployed successfully.
Info: Deployment message for component XMII : See Deploy Controller log E:\usr\sap\CE1\J00\j2ee\JSPM\log\log_2011_02_25_19_33_23\deploy_2011-02-25_19-42-07.log for details.. Create an OSS message in component: XAP-MII for support.. Detailed message:
          1. Item is skipped because of failed deployment of item 'sap.com_xappsxmiijraapp' and because the applied error strategy is OnErrorStop
          2. Contains Aborted deployment component:
sap.com_xappsxmiijraapp. Deployment of archive
MIIQATEMP\sapmnt\trans\EPS\in\XMII08_0-20004625.SCA for component sap.com/XMII aborted.
Error: com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_xappsxmiijraapp].
; nested exception is:
     com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_xappsxmiijraapp]
sdu file path: [E:\usr\sap\CE1\J00\j2ee\cluster\server0\.\temp\tcbldeploy_controller\archives\92\XMII08_0-20004625_SCA1298691730328\DEPLOYARCHIVES\xappsxmiijraapp.sda]
version status: [HIGHER]
deployment status: [Admitted]
description: []

Log Viewer Error In MII 12.1

Hi All,
I am getting an error in log viewer in SAP MII 12.1 version(Netweaver 7.1).
When I am tring to open the log viewer ,It is giving the error Connection refuse.
Please do let me know if someone know anything about issue.
Thanks,
Ritim Jain

Hi Ritim,
As I think its roles issue with your user ID
Can let us know the what roles has been assigned to that user ID
Regards,
Praveen Reddy

JCo Error in Mii 12.1.4

Similar Messages

Maybe you are looking for