New RPM 7 Beta is now available — try the new release →

Unable to launch rpmgui

Every time I try to start the RPM GUI, it’s crashing. This is RPM Elite 6.1.0.439 on Windows Server 2012 R2 Standard. I’ve tried excluding the RPM installation folder from my anti-virus software’s real-time scanning features, but that made no difference.

Below is the text of the Windows Application log entries associated with my most recent attempt. If you’d like to see a copy of the Windows Error Reporting log for the crash, please let me know where I should send it.

Do you have any suggestions, or would you recommend just upgrading to 6.2?

Log Name:Application
Source:Application Error
Date:7/18/2018 10:56:20 AM
Event ID:1000
Task Category: (100)
Level:Error
Keywords:Classic
User:;N/A
Computer:
Description:
Faulting application name:rpmgui.exe, version: 0.0.0.0, time stamp: 0x515c4cfe
Faulting module name:rpm.dll, version: 6.1.0.439, time stamp: 0x57ab9963
Exception code:0xc0000005
Fault offset:0x000000000000651e
Faulting process id:0x7a0
Faulting application start time:0x01d41ec0a0d658a4
Faulting application path:C:\Program Files\Brooks Internet Software\RPM\rpmgui.exe
Faulting module path:C:\Program Files\Brooks Internet Software\RPM\rpm.dll
Report Id:df9bb721-8ab3-11e8-80c9-00155da70c41
Faulting package full name:
Faulting package-relative application ID:
Log Name:Application
Source:Windows Error Reporting
Date:/td>7/18/2018 10:56:24 AM
Event ID:1001
Task Category:None
Level:Information
Keywords:Classic
User:N/A
Computer:
Description:
Fault bucket120532643571, type 4
Event Name:APPCRASH
Response:Not available
Cab Id:0

Problem signature:

P1:rpmgui.exe
P2:0.0.0.0
P3:515c4cfe
P4:rpm.dll
P5:6.1.0.439
P6:57ab9963
P7:c0000005
P8:000000000000651e
P9:
P10:

Attached files:

C:\Users<removed>\AppData\Local\Temp\WER65B8.tmp.WERInternalMetadata.xml

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_rpmgui.exe_b91b76cf1272addc645ddde6f3dcd3d79248f1a_3e96432c_178a77b9

Analysis symbol:

Rechecking for solution:0
Report Id:df9bb721-8ab3-11e8-80c9-00155da70c41
Report Status:0
Hashed bucket:2a7aa0502fcc2301ed1f1199d66b0fa1

Licensing problem

What you have here is most likely a license problem. This is probably caused by having RPM on a virtual machine and moving that virtual machine from one host to another. It could also be caused by hardware changes on a physical machine. To resolve, open the Brooks License Manager. If it opens, it will have reinitialized the license with an expired trial license. However, with a valid license, the RPM UI should be able to open. You will need to activate the license again.

Wed, 07/18/2018 - 12:18

Leroy