Skip to Content
0

SAP Lumira Discovery 2.1 SP1 crashing when exporting

Apr 16 at 07:07 PM

72

avatar image
Former Member

When exporting to Excel from Lumira, the Lumira application crashes immediately. It does create the Excel file (sometimes it will open, sometimes it will not), however, the file does not retain the filters set within Lumira. The Lumira application must then be terminated in task manager and relaunched to run another export. The crash happens every time. I had the same issue with the older version prior to upgrading to 2.1. Event logs are below.

The program SAPLumiraDiscovery.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 26ac
Start Time: 01d3d5a642f05d0b
Termination Time: 4294967295
Application Path: C:\Program Files\SAP BusinessObjects Lumira\Lumira Discovery\Desktop\cefframe\SAPLumiraDiscovery.exe
Report Id: ba6139ca-419a-11e8-8277-340286437514
Faulting package full name:
Faulting package-relative application ID:

_________________________________________________________________________

Faulting application name: SAPLumiraDiscovery.exe, version: 0.0.0.0, time stamp: 0x5aa11618
Faulting module name: SHELL32.dll, version: 6.3.9600.18895, time stamp: 0x5a4b0584
Exception code: 0xc0000005
Fault offset: 0x006527f5
Faulting process id: 0x2114
Faulting application start time: 0x01d3d5a6430e21cb
Faulting application path: C:\Program Files\SAP BusinessObjects Lumira\Lumira Discovery\Desktop\cefframe\SAPLumiraDiscovery.exe
Faulting module path: C:\windows\SYSTEM32\SHELL32.dll
Report Id: 7b41751c-419a-11e8-8277-340286437514
Faulting package full name:
Faulting package-relative application ID:

___________________________________________________________________

Fault bucket 2139084491730381334, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: SAPLumiraDiscovery.exe
P2: 0.0.0.0
P3: 5aa11618
P4: f799
P5: 67246080
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Users\tyates\AppData\Local\Temp\WER22E2.tmp.WERDataCollectionFailure.txt

These files may be available here:
C:\Users\tyates\AppData\Local\Microsoft\Windows\WER\ReportArchive\Critical_SAPLumiraDiscove_7042ffb570879ad33b8acfff3973e8b208bf_73137530_39032301

Analysis symbol:
Rechecking for solution: 0
Report Id: ba6139ca-419a-11e8-8277-340286437514
Report Status: 4104
Hashed bucket: 0168b288139ac11eedaf8e030a22ea16

System:

Lenovo W550s, i7, 16GB

Windows 8.1 Pro

Office365 - MS Office Suite 2016 (This was recently upgraded from a retail copy of Office 2013)

Has anyone experienced this issue?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Tammy Powlas
Apr 16 at 07:17 PM
0

Hello Thomas - It is not happening to me; the main difference is you are using Windows 8.1 and I am on the Windows 2012 Server. I also use MS Office 2016.

Are you exporting out of the client or on the BI Platform?

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Tammy,


Thanks for the response. I'm exporting out of the client. I'm glad to hear that you are not seeing the issue in MS Office 2016 as that is the only recent change to the system and I was afraid there was potentially some type of compatibility issue.


We will continue to troubleshoot.

Kind Regards

0