Please click on "Refresh" action on Updater Service Context.
If "Refresh" does not solve the problem, check the state of the Updater Service (on the server mentioned in the error dialog). If the service is stopped for some reason, restarting the Updater Service should solve the problem.
Hope this helps,
Refresh doesn't correct it, and the Updater Service is running (and is the updated version) on the servers that successfully updated ... but on the systems that will not update, the Updater Service tries to start but stops... Which 'inspired' me to look in the Event Viewer, System logs which I found:
Service cannot be started. System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\WINDOWS\TEMP\nuget'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
at System.IO.Directory.GetDirectories(String path)
at PharosSystems.Updater.Server.Service.OnStart(String args)
at (Object , String )
at A.CK.B(Object A, String B)
at PharosSystems.Updater.Service.Service.OnStart(String args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
The weird thing is, as far as I know there has never been a folder on the system named "C:\WINDOWS\TEMP\nuget", but what do I know? We're talking about how Windows (a Microsoft "product") handles System level temp files.
Should mention, Windows 10 for the two workstations, Server 2012 R2 for the Print Center server.
- Paul L.
The C:\windows\temp\nuget folder is inherited with the use of Nuget for handling package downloads. The folder is created by Nuget for temporary files, the packages are initially downloaded into that location by Nuget and then they are unpacked to the Updater's \ProgramData\... location.
Can I suggest a temporary workaround to try? Could you please manually create this folder on one of the workstations and see if this allows the Updater Service to start and allows Nuget to use the location for downloads. We have not seen this issue in-house with either of the operating systems you mentioned, but will investigate this further.
Also, just to clarify - on the workstations/server where the updater service won't start - those have not yet been updated, correct? Could you please advise what version those instances are running? Thanks. Katherine
I added that folder to one of the workstations, after which the updater successfully started and stayed running and that workstation has now updated the Administrator. The other workstation has also updated now, but I have no idea why it had refused to update for a while.
All that's left now (to finish the Pre-SP3 steps) is to update my Print Center system's Administrator. The Print Center system's Pharos Administrator is version 9.0.8959.157 R2, but it's lists in the "Installed Packages" Administrator version 9.0.8959.223 (see attached jpeg).
I'll be communicating with Jeff Herald about the Print Center system as I suspect it's failure to update to be related to something else. I'll flag your suggestion to create the c:\windows\temp\nuget folder as a Correct Answer as that seemed to solve the issue for the workstation I was most troubled with.
- Paul L.
AdminUpdateVersionMismatch.jpg 55.4 KB
I just sent a message to you, Paul. I can help. If you don't already have a Support Ticket open, please respond to my email to you. Thanks.
Thanks Jeff, I'll do that.