Skip to Content

SAP Lumira Refresh Error HDB 00055 An error occurred while saving document on BI 4.1.7

I have saved a Lumira document into BI Platform and scheduled for refresh but it failed. I got this error:

I couldn't find any KBA. There are few KBA for error HDB 00055 but they are for Lumira Desktop. In my case it happens on the server.

I see that refresh process creates temporary LUMS file on the LS4BIP server and though the error says "error while saving document", I have seen the files in the folder for while and the file is gone later. Is it something between BI Server and Lumira Server file read/write rights? Any recommendations, idea for the error?

BI Platform: 4.1.7

LS4BIP: 1.31.4

Add comment
10|10000 characters needed characters exceeded

  • Additional note: I have realized that the error comes for only Lumira documents with large data (for example 16 million cells), small data Lumira documents are fine! Also when I open Lumira document on BI platform and after refreshing if I save it, I got failed document save error! So it's same same error in logs. Here is log:

    6A344516921A4BF79936BBB2D0367A582642a|2017 06 08 19:08:39.660|-0700|Information| |>>| | |LS_xxxxServer.LumiraServer|13752| 810|Transport:Shared-40/56| |59|0|1|1|BIlaunchpad.WebApp|saltbien02:1560:11468.46967:1|BIlaunchpad.WebApp|saltbien02:1560:11468.46967:1|.post|saltbilm01:13752:810.7455:1|CujcDR804kqPnkj5cACtBXQb90a|||||||||com.sap.hilo.service.persistence.internal.PersistenceServiceImpl|| An error occurred while saving document "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\java\pjs\container\temp\SALTBILM01.LumiraServer\uploadTmp3704019092229163870.lums497117422277887210.lums". (HDB 00055) at com.sap.hilo.service.persistence.internal.PersistenceServiceImpl.save(PersistenceServiceImpl.java:173) at com.sap.teamserver.server.services.platform.BOEPlatormWorkspace.saveWorkspace(BOEPlatormWorkspace.java:565) at com.sap.teamserver.server.services.workspace.WorkspaceManager.saveWorkspace(WorkspaceManager.java:311) at com.sap.teamserver.server.services.SessionContext.saveWorkspace(SessionContext.java:166) at com.sap.teamserver.server.services.service.SaveWorkspace.execute(SaveWorkspace.java:298) at com.sap.teamserver.server.wrapper.AbstractService.execute(AbstractService.java:33) at com.sap.teamserver.server.wrapper.pjsservice.PJSAdapter.execute(PJSAdapter.java:73) at com.sap.teamserver.service.TeamServerPJSService.doService(TeamServerPJSService.java:193) at com.sap.teamserver.service.TeamServerPJSService.process(TeamServerPJSService.java:139) at com.businessobjects.framework.servers.platform.transport.internal.TransportRequestInterceptor.process(TransportRequestInterceptor.java:128) at com.crystaldecisions.sdk.occa.transport.internal.BIPTransportImpl.post(BIPTransportImpl.java:90) at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at com.businessobjects.framework.servers.platform.adapters.ebus.orb.CommonTransportInterceptor.invokeHelper(CommonTransportInterceptor.java:118) at com.businessobjects.framework.servers.platform.adapters.ebus.orb.CommonTransportInterceptor.invoke(CommonTransportInterceptor.java:87) at com.businessobjects.framework.servers.common.proxy.cglib.MethodInterceptorChain.intercept(MethodInterceptorChain.java:136) at com.crystaldecisions.enterprise.ocaframework.idl.OCA2.BIPTransportPOA$EnhancerByCGLIB$fe952c1b.post(<generated>) at com.crystaldecisions.enterprise.ocaframework.idl.OCA2.BIPTransportPOA._OB_op_post(BIPTransportPOA.java:120) at com.crystaldecisions.enterprise.ocaframework.idl.OCA2.BIPTransportPOA._invoke(BIPTransportPOA.java:87) at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.ServantDispatcher.dispatch(ServantDispatcher.java:234) at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POA_impl._do_OB_dispatch(POA_impl.java:1980) at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POA_impl._OB_dispatch(POA_impl.java:1916) at com.crystaldecisions.thirdparty.com.ooc.OB.DispatchRequest_impl.invoke(DispatchRequest_impl.java:122) at com.businessobjects.framework.servers.platform.adapters.ebus.orb.ThreadPoolDispatchStrategy$Dispatcher.run(ThreadPoolDispatchStrategy.java:271) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:791) Caused by: java.lang.RuntimeException: Unexpected throwable caugth at com.sap.hilo.service.persistence.internal.DocumentManager.save(DocumentManager.java:536) at com.sap.hilo.service.persistence.internal.PersistenceServiceImpl.save(PersistenceServiceImpl.java:161) ... 30 more Caused by: java.lang.Error: Invalid memory access at sap.hanavora.jdbc.driver.inproc.hlapi.HLLibraryDirect.v2_print_get_lines(Native Method) at sap.hanavora.jdbc.driver.inproc.hlapi.HanaVora.v2_print_get_lines(HanaVora.java:342) at sap.hanavora.jdbc.driver.inproc.InProcDriver.getNextChunk(InProcDriver.java:102) at sap.hanavora.jdbc.driver.inproc.ChunkedInProcRowResult.getNextChunk(ChunkedInProcRowResult.java:33) at sap.hanavora.jdbc.driver.AbstractResult.next(AbstractResult.java:55) at sap.hanavora.jdbc.AbstractHLResultSet.next(AbstractHLResultSet.java:107) at com.sap.hilo.util.instrumentation.ResultSetProfiler.next(ResultSetProfiler.java:89) at com.sap.hilo.engine.common.DataIterator.moveNext(DataIterator.java:371) at com.sap.hilo.engine.common.DataIterator.hasNext(DataIterator.java:74) at com.sap.hilo.model.toolkit.DataFlowToolkit.dump(DataFlowToolkit.java:309) at com.sap.hilo.model.toolkit.DataFlowToolkit.dump(DataFlowToolkit.java:185) at com.sap.hilo.service.persistence.internal.dump.DataFlowSerializer.serializeCsv(DataFlowSerializer.java:314) at com.sap.hilo.service.persistence.internal.dump.DataFlowSerializer.dumpStreamFromDataBaseWithFetch(DataFlowSerializer.java:290) at com.sap.hilo.service.persistence.internal.dump.DataFlowSerializer.dumpStreamFromDataBase(DataFlowSerializer.java:203) at com.sap.hilo.service.persistence.internal.dump.DataFlowSerializer.dumpStream(DataFlowSerializer.java:94) at com.sap.hilo.service.persistence.internal.dump.DocumentSerializer.dumpDataFlow(DocumentSerializer.java:3192) at com.sap.hilo.service.persistence.internal.dump.DocumentSerializer.serialize(DocumentSerializer.java:254) at com.sap.hilo.service.persistence.internal.dump.DocumentSerializer.write(DocumentSerializer.java:222) at com.sap.hilo.service.persistence.internal.DocumentManager$SaveWorkflow.retryableWorkflow(DocumentManager.java:944) at com.sap.hilo.service.persistence.internal.DocumentManager$SaveWorkflow.retryableWorkflow(DocumentManager.java:1) at com.sap.hilo.common.query.WorkflowController.startWorkflow(WorkflowController.java:49) at com.sap.hilo.service.persistence.internal.DocumentManager.save(DocumentManager.java:528) ... 31 more

  • It seems the problem is

    "Caused by: java.lang.Error: Invalid memory access at sap.hanavora.jdbc.driver.inproc.hlapi.HLLibraryDirect.v2_print_get_lines(Native Method)"

    If I search about "Invalid memory access" error in java generally, there is a possibility that there is something wrong in java code, here is our error probably in sap.hanavora.jdbc.driver.inproc.hlapi.HLLibraryDirect.v2_print_get_lines method.

    If you wonder if we have opened a SAP ticket, yes we have an open ticket for a while and waiting a response from SAP.

    Appreciate for any inputs.

  • Get RSS Feed

1 Answer

  • Oct 02, 2017 at 07:39 PM

    Found the root cause for the issue! It was all about data quality, nothing directly about Lumira & BI Platform, etc... I was expecting SAP could recommend something!

    The issue was related to a bad -maybe out of limit- date field! To me BI & Lumira logs should display more clear error messages for these type of data issues! At the end JRE gives runtime error, that's my understanding! SAP Lumira & BI should catch these runtime errors -exceptions- and make more meaningful errors for users.

    Add comment
    10|10000 characters needed characters exceeded