on 09-20-2005 10:35 AM
I am having a couple of problems with the MAM25 (installed on a WAS640) using MI25. The application installs on the device succesfully it seems. I can see the start screen with the links to orders, notfications and so on. I cannot see any orders or notifications being synced down to the device though.
When I try to create a local order on the device I get the following error.
Any ideas?
Thanks.
-
An error has occured
Error Code E503
Error Message Failed calling event handler(InvocationTargetException) onLoad in com.sap.mbs.mam.order.control.OrderDetail.
com.sap.mbs.core.api.CAFException: Failed calling event handler(InvocationTargetException) onLoad in com.sap.mbs.mam.order.control.OrderDetail.
at com.sap.mbs.core.control.AbstractViewController.process(Unknown Source)
at com.sap.mbs.core.control.DefaultStateMachine.process(Unknown Source)
at com.sap.mbs.core.control.DefaultStateMachine.process(Unknown Source)
at com.sap.mbs.core.web.FrontServlet.doHandleEvent(Unknown Source)
at com.sap.mbs.mam.application.web.FrontServlet.doHandleEvent(Unknown Source)
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe(AbstractMEHttpServlet.java:346)
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet(AbstractMEHttpServlet.java:678)
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost(AbstractMEHttpServlet.java:695)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service(AbstractMEHttpServlet.java:326)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
at org.apache.tomcat.core.Handler.service(Handler.java:287)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:806)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Thread.java:479)
java.lang.IllegalArgumentException: String length exceeds max length of 2
at com.sap.ip.me.persist.fileio.spi.AttributeTypeExt$AttributeTypeString.toByte(AttributeTypeExt.java:1295)
at com.sap.ip.me.persist.fileio.spi.AttributeTypeExt$AttributeTypeString.toByte(AttributeTypeExt.java:1327)
at com.sap.ip.me.persist.fileio.spi.AttributeDescriptorImpl.toByte(AttributeDescriptorImpl.java:245)
at com.sap.ip.me.persist.fileio.spi.QueryConditionSingle.(QueryConditionSingle.java:36)
at com.sap.ip.me.persist.fileio.spi.QueryRuntimeImpl.createICondition(QueryRuntimeImpl.java:38)
at com.sap.ip.me.smartsync.data.QueryFactoryImpl.createCondition(QueryFactoryImpl.java:60)
at com.sap.mbs.mam.bo.query.impl.AbstractQueryBuilder.getCondition(Unknown Source)
at com.sap.mbs.mam.bo.query.impl.Mam095QueryBuilderImpl.getPrioritiesByKeyCondition(Unknown Source)
at com.sap.mbs.mam.cstm.impl.CstmCustomControllerImpl.getPriorityByKey(Unknown Source)
at com.sap.mbs.mam.order.control.OrderDetail.onLoad(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.sap.mbs.core.control.AbstractViewController.process(Unknown Source)
at com.sap.mbs.core.control.DefaultStateMachine.process(Unknown Source)
at com.sap.mbs.core.control.DefaultStateMachine.process(Unknown Source)
at com.sap.mbs.core.web.FrontServlet.doHandleEvent(Unknown Source)
at com.sap.mbs.mam.application.web.FrontServlet.doHandleEvent(Unknown Source)
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe(AbstractMEHttpServlet.java:346)
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet(AbstractMEHttpServlet.java:678)
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost(AbstractMEHttpServlet.java:695)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service(AbstractMEHttpServlet.java:326)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)
at org.apache.tomcat.core.Handler.service(Handler.java:287)
at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:806)
at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)
at java.lang.Thread.run(Thread.java:479)
I have had the same problem. The hotfix for MAM25 will solve this problem.
See for more info SAPNote: 868708
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi R. Kleijn
Could please give me a little help. I can see that the hotfix solve your problem about display order details!
Im running a system with MAM2.5 SR SP13 and MI 2.5 SP13 and i have deployed the hotfix as described, everything looks ok, but i stil have the error? Any Idea? Maybe theres a special way to do the Add-on in the webconsole?
Please advice
BR
Rolf
It did fix the problem for me.
To deploy an add-on
http://help.sap.com/saphelp_nw04/helpdata/en/a7/893a5889e08b41b615688b1a93b559/frameset.htm
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.