Updates stuck at 20070228? A fix.

Hi all,

I had a problem where all my clients were getting stuck at definitions dated 20070228. Turns out that I hadn't upgraded the program code of the servers, so I was stuck on old definitions that weren't updating past this date.

If you look on the update server under Update/Update/Setup, you'll see that there's an option for 'Type of update' - click Change, and ensure you're happy with these results.

All I needed to do was to force an update at this point, but restarting the server actually installed the new program code update. This is probably only a problem for people moving from 2.5 to 2.7.

Regards
Craig

 

This happens every time there is an engine update. If any machine (servers included) is showing "Waiting for restart," it will stop downloading and/or mirroring definition updates until it gets restarted.

 

so you might reconsider the settings for program components on your lan update version (the local mirror)... perhaps doing that machine manually.

 

What I found is that the "Location>Server" setting got corrupted/changed from the <CHOOSE AUTOMATICALLY>, and was set to some "other" server location. Moving it back to <CHOOSE AUTOMATICALLY> solved the problem for me...