Hope someone can help!
After a recent upgrade from Win 8.1 Pro to Win 10 Pro, my VIP Access client simply crashes when I attempt to execute it.
It was working fine prior to the Win 10 upgrade.
The application event log has two entries when the crash occurs, one "error" and one "information" which are reproduced below.
Any assistance gratefully accepted.
Cheers,
Chris.
Log Name: Application
Source: Application Error
Date: 25/09/2015 11:40:43 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: CTH-PC
Description:
Faulting application name: VIPUIManager.exe, version: 2.2.1.13, time stamp: 0x53c3acdd
Faulting module name: VIPUIManager.exe, version: 2.2.1.13, time stamp: 0x53c3acdd
Exception code: 0xc0000409
Fault offset: 0x000b43dd
Faulting process id: 0x1308
Faulting application start time: 0x01d0f733313e972b
Faulting application path: C:\Program Files (x86)\Symantec\VIP Access Client\VIPUIManager.exe
Faulting module path: C:\Program Files (x86)\Symantec\VIP Access Client\VIPUIManager.exe
Report Id: 8f308e52-734c-481b-a06b-3f7463891b3f
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-09-25T01:40:43.000000000Z" />
<EventRecordID>12642</EventRecordID>
<Channel>Application</Channel>
<Computer>CTH-PC</Computer>
<Security />
</System>
<EventData>
<Data>VIPUIManager.exe</Data>
<Data>2.2.1.13</Data>
<Data>53c3acdd</Data>
<Data>VIPUIManager.exe</Data>
<Data>2.2.1.13</Data>
<Data>53c3acdd</Data>
<Data>c0000409</Data>
<Data>000b43dd</Data>
<Data>1308</Data>
<Data>01d0f733313e972b</Data>
<Data>C:\Program Files (x86)\Symantec\VIP Access Client\VIPUIManager.exe</Data>
<Data>C:\Program Files (x86)\Symantec\VIP Access Client\VIPUIManager.exe</Data>
<Data>8f308e52-734c-481b-a06b-3f7463891b3f</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>
Log Name: Application
Source: Windows Error Reporting
Date: 25/09/2015 11:40:48 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: CTH-PC
Description:
Fault bucket 81695427294, type 5
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: VIPUIManager.exe
P2: 2.2.1.13
P3: 53c3acdd
P4: VIPUIManager.exe
P5: 2.2.1.13
P6: 53c3acdd
P7: 000b43dd
P8: c0000409
P9: 00000000
P10:
Attached files:
C:\Users\Chris\AppData\Local\Temp\WERFE35.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_VIPUIManager.exe_7a463ef217dd1b2517111f302ed9779d955199_efe55b98_2dcc0fc9
Analysis symbol:
Rechecking for solution: 0
Report Id: 8f308e52-734c-481b-a06b-3f7463891b3f
Report Status: 0
Hashed bucket: fcb032b89a2c44f48cc4d5007f816cec
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-09-25T01:40:48.000000000Z" />
<EventRecordID>12643</EventRecordID>
<Channel>Application</Channel>
<Computer>CTH-PC</Computer>
<Security />
</System>
<EventData>
<Data>81695427294</Data>
<Data>5</Data>
<Data>BEX</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>VIPUIManager.exe</Data>
<Data>2.2.1.13</Data>
<Data>53c3acdd</Data>
<Data>VIPUIManager.exe</Data>
<Data>2.2.1.13</Data>
<Data>53c3acdd</Data>
<Data>000b43dd</Data>
<Data>c0000409</Data>
<Data>00000000</Data>
<Data>
</Data>
<Data>
C:\Users\Chris\AppData\Local\Temp\WERFE35.tmp.WERInternalMetadata.xml</Data>
<Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_VIPUIManager.exe_7a463ef217dd1b2517111f302ed9779d955199_efe55b98_2dcc0fc9</Data>
<Data>
</Data>
<Data>0</Data>
<Data>8f308e52-734c-481b-a06b-3f7463891b3f</Data>
<Data>0</Data>
<Data>fcb032b89a2c44f48cc4d5007f816cec</Data>
</EventData>
</Event>