Not that I've noticed. Is this on Mac or PC? What symptoms are you seeing to indicate it needs a reboot? Service/process not running?
It’s on PC and the LANrev Service is stopped and will not start unless rebooted.
So far I haven't seen that but I haven't look very closely. I do see I have a lot of PC's that are updated to 6.9.3 and are checking in and their "computer boot time" is before the agent was updated.
Is this happening on all your PC's? What version did you upgrade from?
Have you checked the LANrev Log and the application event log?
Not all PC’s are experiencing the needed reboot, just some. The upgrade wipes out the previous history entries in the LANrev Log.
Ouch. How are the upgrades being performed? Via the normal agent update process from the server? Or some other means?
Normal agent update process from the server
Was this another report of the same problem?:
I didn't see any of these symptoms on the Mac side, log history was retained and Heartbeats continued as normal.
Upgrade was pushed from OS X Server/LANrev Server.
Now that I look closer, I'm seeing the same problem. I have over 200 PC's that are showing the agent updater in the "installation in progress" folder. Upon further inspection, I see the service is running, but restarting service has no effect, there is still a c:\LANrevAgentUpdater folder present. Heartbeats are not coming in.
Event logs look ok, except this:
The description for Event ID 4 from source Absolute Manage Agent Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Absolute Manage Agent Service
the message resource is present but the message is not found in the string/message table
Here is a LANrev Agent.log:
2016-02-17 15:52:40.352 [880:1438] <5> - LANrev Agent 6.9.3 (v4802) on Windows 7 (Enterprise) [64-bit] 6.1 started. Agent serial: E4A1A495-CE4C-40B8-86E8-38B54A30793A; Timezone: GMT-05:00
2016-02-17 15:52:40.367 [880:1438] <5> - Version Info: 6.9.3 (v4802), Copyright 2009-2016 FrontRange Solutions Inc. All rights reserved.
2016-02-17 15:52:41.507 [880:1438] <5> - LANrev Agent 6.9.3 (v4802) on Windows 7 (Enterprise) [64-bit] 6.1 with 184.108.40.206 is listening on port 3970...
2016-02-18 10:10:25.078 [880:1438] <5> - LANrev Agent is starting shutdown...
2016-02-18 10:10:25.998 [880:1438] <2> - IsLANrevRemoteRunning: StdErrStreams: Failed to query the service status.
2016-02-18 10:10:26.107 [880:1438] <2> - Could not open service manager.
2016-02-18 10:10:26.170 [880:1438] <2> -
2016-02-18 10:10:26.825 [880:1438] <5> - LANrev Agent shutdown finished
2016-02-18 10:11:40.837 [1848:748] <5> - LANrev Agent 6.9.3 (v4802) on Windows 7 (Enterprise) [64-bit] 6.1 started. Agent serial: E4A1A495-CE4C-40B8-86E8-38B54A30793A; Timezone: GMT-05:00
2016-02-18 10:11:41.305 [1848:748] <5> - Version Info: 6.9.3 (v4802), Copyright 2009-2016 FrontRange Solutions Inc. All rights reserved.
2016-02-18 10:11:42.381 [1848:748] <5> - LANrev Agent 6.9.3 (v4802) on Windows 7 (Enterprise) [64-bit] 6.1 with 220.127.116.11 is listening on port 3970...
2016-02-18 10:11:43.380 [1848:b54] <2> - The following error occurred while registering with Bonjour: Unknown error (Error=-65563).
sgillaspy Yes it does look like that other post is the same problem.
I am attempting to reproduce, but at this point, I cannot find the steps to get the agent into this condition. All of my Windows 7 agents have made the upgrade to 6.9.3. Were the agents previously running the 6.9 version or some other older version?
In my case, I had 6.9.
I upgraded two Windows 7x86 from 6.9 and saw this issue on one of them. I have not yet upgraded my production environment, this is using the 10 user license in the 30 day trial install.
Yes version 6.9.2
In my case 6.8.2
Just want to give everyone an update that we are still investigating this. I still cannot reproduce internally, but I may be able to get further information with and .evt log that shows a potential error.
If you can see the following error in your application .evt, this would help me narrow things down:
Product: LANrev Agent -- Error 1714. The older version of LANrev Agent cannot be removed. Contact your technical support group. System Error 1612
As part of the upgrade to 6.9.3, there is a complete uninstall/reinstall and migration of agent settings that takes place because of the rebranding. From the event viewer log, if there is a problem with permissions in removing the backup data, perhaps the install is halted in a way that it shouldn't be, leaving the agent partially installed.
If anyone can provide a full event viewer log and LANrev Agent.log, this would really help us narrow down the issue.