Problems after installing SP17

[Former Member]

Hello all,

after upgrading the client software from SP13 to SP17 I get the following erros in trace file after restarting the client:

[20060919 09:20:38:537] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20060919 09:20:38:537] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 17 Patch 04 Build 200609070522

[20060919 09:20:38:537] I [MI/API/Logging ] ***** Current timezone: Europe/Berlin

[20060919 09:20:39:168] E [AppLog/MI/API/Services ] Problems while saving D:\Programme\SAPMI\sync\inboundProcessors\5.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:871)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:797)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors(ApplicationManager.java:198)

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework(FrameworkInitializer.java:377)

at com.sap.ip.me.core.FrameworkInitializer.main(FrameworkInitializer.java:124)

at com.sap.ip.me.core.Startup.main(Startup.java:334)

[20060919 09:20:39:188] E [AppLog/MI/API/Services ] Problems while saving D:\Programme\SAPMI\sync\inboundProcessors\5.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:871)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:797)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors(ApplicationManager.java:200)

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework(FrameworkInitializer.java:377)

at com.sap.ip.me.core.FrameworkInitializer.main(FrameworkInitializer.java:124)

at com.sap.ip.me.core.Startup.main(Startup.java:334)

[20060919 09:20:39:198] E [AppLog/MI/API/Services ] Problems while saving D:\Programme\SAPMI\sync\inboundProcessors\5.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:871)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:797)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework(FrameworkInitializer.java:380)

at com.sap.ip.me.core.FrameworkInitializer.main(FrameworkInitializer.java:124)

at com.sap.ip.me.core.Startup.main(Startup.java:334)

[20060919 09:20:46:318] E [MI/Core ] Exception while reading installation log file (root cause: D:\Programme\SAPMI\bin\ci\archives\SP17\17\install.log (Das System kann den angegebenen Pfad nicht finden) [java.io.FileNotFoundException])

[20060919 09:20:46:358] E [AppLog/MI/API/Services ] Problems while saving D:\Programme\SAPMI\sync\inboundProcessors\6.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1369)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1341)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1284)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:291)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:871)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:797)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.mi.systemnews.NewsImpl.create(NewsImpl.java:313)

at com.sap.ip.mi.systemnews.StartListener.userLoggedOn(StartListener.java:24)

at com.sap.ip.me.core.UserManagerImpl.fireLogon(UserManagerImpl.java:2291)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:766)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:744)

at com.sap.ip.me.apps.jsp.LoginServlet.doHandleEvent(LoginServlet.java:274)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe(AbstractMEHttpServlet.java:347)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet(AbstractMEHttpServlet.java:689)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost(AbstractMEHttpServlet.java:706)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service(AbstractMEHttpServlet.java:313)

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:595)

I'm sorry, the trace is a little bit long (as usual ).

It seems like the client is not able to save the X.value files. I did not synchronize after installing SP17, so why does the client write into the ...\sync\inboundProcessors\ directory? Or does this error occur during the installation/download of SP17?

Many thanks for your help.

[Former Member · Accepted solution]

Hi Edgar,

Do you have any problems after the upgrade or is it only the error logs you see in the trace file? The log cleanup has been done in SP18 patch01. If you find any error which says "not able to save" you can ignore it as it will not cause any harm to the client.

Best Regards,

Karthik

[Former Member · Accepted solution]

Hello Karthik,

I haven't installed any applications because i don't want to get aftereffects from this errors. So I can't say anything about any other problems so far.

I get these errors now everytime I start the client.

So do you think i should just ignore them?

[Former Member · Accepted solution]

Hi Edgar,

If you really do not want to see these logs I recommend that you upgrade to SP18 Patch01.

As long as the log has something to do with "not able to save the X.value" you can safely ignore them.

Hopefully you should have a patch on SP17 which removes the unwanted logs from the trace file soon.

Best Regards,

Karthik

[Former Member · Accepted solution]

Ok, I will ignore the errors and my assumed problem should be solved

Thanks for your help, I'll asign you some points.