Deployed with warning

[former_member1103699]

Hi,
when i deployed EAR application , it end with warning ,could someone tell me how to do. Thanks

Description:
1. Warning occurred on server 3490251 during deploy of sap.com/SofiaEAR : JSF Application Test: schema_reference.4: Failed to read schema document 'http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd', 
because 
1) could not find the document; 
2) the document could not be read;
 3) the root element of the document is not <xsd:schema>., 
file: SofiaWEB.war#faces-config.xml, column 169, line 4, severity: warning


Warning occurred on server 3490251 during deploy of sap.com/SofiaEAR : JSF Application Test: schema_reference.4: Failed to read schema document 'http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd',
 because 
1) could not find the document; 
2) the document could not be read; 
3) the root element of the document is not <xsd:schema>., 
file: SofiaWEB.war#META-INF/faces-config.xml, column 115, line 4, severity: warning


CSN component of deployment item is not available


2. Exception has been returned while the [sap.com/SofiaEAR] was starting. Warning/Exception :
[][ASJ.dpl_ds.006153 Error occurred while starting application [sap.com/SofiaEAR]: It is not started successfully on server nodes [3490250, 3490252, 3490251].
 In order to bring the server in consistent state stop operation will be performed.

[oppancs]

Dear Juan,

I guess you deploy the ear file with NWDS. In this case please do the followings:

1. Open the eclipse.ini file, which is located in the SAP NetWeaver Developer Studio directory.
2. Add the following line under vm arguments:
-Djavax.xml.accessExternalSchema=all
3. Restart SAP NetWeaver Developer Studio
4. Redeploy the .ear file.

It it does not help please try to redeploy the .ear file with Telnet. For Telnet deployment please check the KBA's "Shell console administrator via the telnet protocol" part: 1715441 - Deploy/Undeploy/Force Redeploy WAR/EAR/RAR/SDA/SCA files on SAP AS JAVA

In case it does not help either you can further check reasons from the timestamp of the deploy try in deploy.log and deploy.trc files (path: "\usr\sap\<SID>\<instnr>\work" and/or in defaultTrace files (path: \usr\sap\<SID>\<INSTANCE NUMBER>\j2ee\cluster\server<X>\log")

Best Regards,
Barnabás Paksi
SAP Product Support