cancel
Showing results for 
Search instead for 
Did you mean: 

Error after deploying

Former Member
0 Kudos

Hi All,

I have created a adaptive RFC Model. But when I am deploying the application, I am getting following error. Please help in resolving it.

We recently moved from HTTP to HTTPS. Is this because of this change?

org.xml.sax.SAXException: Fatal Error: URI=:main: Line=7: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:7, col:67)

at com.sap.dictionary.runtime.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)

at com.sap.dictionary.runtime.XmlExtractor.map(XmlExtractor.java:130)

at com.sap.dictionary.runtime.DdJavaProvider.getDataType(DdJavaProvider.java:68)

at com.sap.dictionary.runtime.DdNameTranslator.<init>(DdNameTranslator.java:53)

Detailed Exception Chain

com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type extern:com.mindtree.loanmodel.types.LoanModel:com.mindtree.loanmodel.types.Zloan_Pri_App could not be loaded: com.sap.dictionary.runtime.DdException: Fatal Error: URI=:main: Line=7: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:7, col:67)

at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)

at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:234)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:659)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:662)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:662)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:662)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)

at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:436)

Regards,

Vaibhav

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

Was this deploying correctly before the change?

If so, as suggested, remove the ear from the server.(Use SDM undeployment). Rebuild and redeploy the application.

If not, there can be many reasons for this error. Check with some other RFC. If it works, then there is some problem with this RFC only.

Regards,

Harini S

Former Member
0 Kudos

Hi,

I tried with other RFCs, still I am getting the same error. But the existing models are working fine.

Former Member
0 Kudos

Hi,

In that case, make sure u r using compatible NWDS. If u use NWDS for 04s but try to deploy in NW04 server, then such issies may come. Check with NWDS and NW version. That could be the problem.

Regards,

Harini S

Message was edited by:

Armin Reichert

Former Member
0 Kudos

We are using NWDS 2.0.9 and EP 6.4.

Former Member
0 Kudos

Any Updates?

former_member751941
Active Contributor
0 Kudos

Hi Vaibhav,

Make ensure you have installed <b>MSXML Parser</b> on you desktop/TP.

If not you can download it from following link http://msdn2.microsoft.com/en-us/downloads/default.aspx

(Microsoft Core XML Services (MSXML) 6.0)

After installation just do quick reboot your system and then try.

Regards,

Mithu

Former Member
0 Kudos

Hi

Delete the deployed application from the server and redeploy the app.

Regards

Abhijith YS