03-22-2017 12:35 AM
Hi,
We have Proximity app installed on a few machines and on all the machines, after it has been running for some time, CPU for proximity.exe goes up to 25% and sits there. We are running the latest version (2.0.4) on Windows 7 SP1. After the exe hits 25% CPU, you can no longer exit from Proximity either. Only way to exit the application is by killing it.
Been trying to identify why this happens, but haven't found anything that would point me to this behavior except for Information logs in Application log (Below):
Log Name: Application
Source: MsiInstaller
Date: 22/3/2017 3:03:40 PM
Event ID: 11729
Task Category: None
Level: Information
Keywords: Classic
User: <UserName>
Computer: MACHINE NAME
Description:
Product: Proximity-132178 -- Configuration failed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">11729</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-22T07:03:40.000000000Z" />
<EventRecordID>26814</EventRecordID>
<Channel>Application</Channel>
<Computer>MACHINE NAME</Computer>
<Security UserID="S-1-5-21-1379841381-2888069222-2292527902-2396509" />
</System>
<EventData>
<Data>Product: Proximity-132178 -- Configuration failed.</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B36383536334342452D424239442D343338422D393831312D4331443141353441354437467D2C2031363032</Binary>
</EventData>
</Event>
Log Name: Application
Source: MsiInstaller
Date: 22/3/2017 3:03:40 PM
Event ID: 1035
Task Category: None
Level: Information
Keywords: Classic
User: USERNAME
Computer: MACHINE NAME
Description:
Windows Installer reconfigured the product. Product Name: Proximity-132178. Product Version: 2.0.4.0. Product Language: 1033. Manufacturer: Cisco Systems, Inc.. Reconfiguration success or error status: 1602.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">1035</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-03-22T07:03:40.000000000Z" />
<EventRecordID>26815</EventRecordID>
<Channel>Application</Channel>
<Computer>MACHINE NAME</Computer>
<Security UserID="S-1-5-21-1379841381-2888069222-2292527902-2396509" />
</System>
<EventData>
<Data>Proximity-132178</Data>
<Data>2.0.4.0</Data>
<Data>1033</Data>
<Data>1602</Data>
<Data>Cisco Systems, Inc.</Data>
<Data>(NULL)</Data>
<Data>
</Data>
<Binary>7B36383536334342452D424239442D343338422D393831312D4331443141353441354437467D3030303064613861663333373366633733373264323766383539363031353263336233383030303030393034</Binary>
</EventData>
</Event>
06-29-2017 06:30 AM
Hi Mahesh, thank you for the report. We are investigating this issue. If you have any further observations on what sequence of events (beyond just running for some time) that triggers this, please let us know. Thanks.
Update: Proximity 2.0.5 was released with fixes for this issue.
Thanks again for reporting.
Regards,
Stian
09-20-2017 05:00 AM
10-16-2017 08:04 AM
10-16-2017 08:12 AM
Having same issue, please respond with fix.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide