on 03-10-2016 4:36 PM
Hello,
We are executing Configuration Task “PI Upgrade” after upgrading our
development SAP PI 7.11 system to SAP PI 7.4. In follow up activities
for
system landscape directory, the process fails during execution of step
“Assign Product to the Technical System”. It returns an error because
itis unable to find product SAP NETWEAVER 7.31 in SLD and recommends to
follow note 1305716. According to this note, we should Update CIM Model
version. Our CIM model version is currently 1.6.43 and the content
SAP_CR
6.10 (produced 2011-03-03).
We have downloaded all the cimsap and cdelta files to update the model
up
to 2015 version. However, when we try to import the first file, we get
the following error:
com.sap.tc.webdynpro.services.exceptions.WDNonFatalException: Error
preparing import: com.sap.sld.api.wbem.exception.CIMException:
CIM_ERR_FAILED: CIM Error during import preparation
If we check SLD logs, we can see the following java stack error:
---------------- STACK TRACE ------------------
[HTTP Worker [@1795011435]] ERROR com.sap.sld.wd.admin.ImportView: Error during prepare import
Thrown:
com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: CIM Error during import preparation
at com.sap.cim.lib.admin.ImportImpl.logCreateError(ImportImpl.java:473)
at com.sap.cim.lib.admin.ImportImpl.prepare(ImportImpl.java:117)
at com.sap.cim.lib.admin.CIMAdminImport.prepareImportImpl(CIMAdminImport.java:283)
at com.sap.cim.lib.admin.CIMAdminImport.prepareImport(CIMAdminImport.java:252)
at com.sap.cim.lib.admin.CIMAdminImport.prepareImport(CIMAdminImport.java:73)
at com.sap.cim.lib.admin.CIMAdminImport.prepareImport(CIMAdminImport.java:39)
at com.sap.sld.wd.admin.ImportView.onActionPrepareImport(ImportView.java:725)
at com.sap.sld.wd.admin.wdp.InternalImportView.wdInvokeEventHandler(InternalImportView.java:383)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:75)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.doHandleActionEvent(ProcessingEventPhase.java:159)
at com.sap.tc.webdynpro.clientserver.phases.ProcessingEventPhase.execute(ProcessingEventPhase.java:94)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:908)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:880)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:326)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:101)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:373)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:499)
at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:77)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: invalid literal/lengths set
at com.sap.cim.lib.pers.delta.importing.ImportHandler.extractManifest(ImportHandler.java:1297)
at com.sap.cim.lib.pers.delta.importing.ImportHandler.extractManifest(ImportHandler.java:1269)
at com.sap.cim.lib.pers.delta.importing.ImportHandler.prepareZipFile(ImportHandler.java:314)
at com.sap.cim.lib.pers.delta.importing.ImportHandler.prepareImpl(ImportHandler.java:219)
at com.sap.cim.lib.pers.delta.importing.ImportHandler.prepare(ImportHandler.java:191)
at com.sap.cim.lib.admin.ImportImpl.prepare(ImportImpl.java:109)
... 71 more
Caused by: java.util.zip.ZipException: invalid literal/lengths set
at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:147)
at java.io.FilterInputStream.read(FilterInputStream.java:97)
at java.util.Properties$LineReader.readLine(Properties.java:434)
at java.util.Properties.load0(Properties.java:353)
at java.util.Properties.load(Properties.java:341)
at com.sap.cim.lib.pers.delta.importing.ImportHandler.extractManifest(ImportHandler.java:1293)
... 76 more
---------------- STACK TRACE ------------------
The whole trace is included in additional data file attached to the
incident.
The first thing we thought was that the zip file was corrupt, but we
have
been able to uncompress it manually. Additionally, we imported i into
another System and it succeeded. Does anybody could help us? We are
currently stuck and we can’t continue post-upgrade activities.
Best Regards
Roger Allué i Vall.
Hi all,
This is what SAP answered:
Hello,
After brief consultation with the Development Support, it turned out
that the file might have been corrupted during the upload:
In order to confirm this would you please implement the following note:
2297508 - The content of uploaded file is corrupted
Please do not forget to implement the SCA dependencies as well:
1974464 - SMP: Information on SCA Dependency Analysis for Java
download objects
If the problem still occurs after the installation of the software
fixes, please provide the system information as per note:
1757810 - 'How to get the complete list of software components on your
NetWeaver Application Server Java' .
Thank you.
Updating ENGINEAPI component solved the issue.
Regards!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Roger,
This issue also occurs on SPS 13 for NW7.4.
Once u have a solution from SAP it might work as well for NW 7.4
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Roger,
we run into a almost similar problem. After SPS17 on PI 7.31 the upload function of the SLD CIM update stores a zip file in the filesystem which is corrupted. The size of the file differs from my workplace pc in comparison to the file stored on the SAP server. In my case the manual unzip does not work.
Import into a "old" SPS10 on 7.31 was sucessful.
Strangely enough as I searched for the CIM version 1.6.43 I could only find the following CIM versions downloadable from SAP.
cimsap111601_0-70000709.zip 1.6.42
cimsap111602_0-70000709.zip 1.6.44
In case you found a solution it would be appreciated if you could post the way you solved the problem. It may give a hint on what is wrong in our case, too.
Kind regards, Hinrich
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Hinrich,
I found a workaround to update the CIM model and CR content. However, we still can't import any zip file to the sld, not even normal transport files (technical systems, business systems, etc...). What I did to update the cim model was to create a new namespace. Once created go to import view and import CIM model and CR content from the server. Then go to Administration --> Maintenance --> Repair Component Repository content. In the productive namespace, set your namespace. And in the reference namespace, the one you recently created. It won't fix the problem with zip files, but it will update your CR content at least. I still have an open message with SAP to solve this issue. As soon as they give me a solution, I will post it here.
Regards!
Hello Roger,
thank you for the quick reply. Good idea to import the data into a parallel namespace. I tried this but I ran into the same problem as before. So the problem sounds similar but it is a bit different...
So I decided to give SAP a nice bunch of traces from SLD and XPI inspector to examine the cause within a newly created incident...
And for the next systems that are scheduled to go up to SPS17 we will do the SLD CIM / CR update before we start with SPS.
Kind regards, Hinrich
Hello Roger,
2297508 did it for us, too. After implementing all new Java patches for our software components (1,4 G ) the upload was possible again. Nice idea to implement new code in good running functions in new releases. Sometimes I have the feeling there is nobody who does a test on such elementary functionality. Ok, some patchlevel later the fix is available...
Kind regards, Hinrich
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
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.