Running VSE 8.0i on Windows server 2003.
Updates have been running daily fine, but last update failed and continues to fail, even when trying to do manually. Have been no updates to server or changes, so not sure what has failed here.
Any insight would be appreciated. I just recently stepped into this role and haven't personally setup this program.
Event Type: Error
Event Source: Alert Manager Event Interface
Event Category: None
Event ID: 257
Time: 7:47:33 AM
VirusScan Enterprise: The update failed; see event log.(from XXXXXX IP 192.168.0.1 user XXXXX running VirusScan EntSv 8.0.0 UPD)
Any thoughts would be appreciated.Message was edited by: jreed on 6/13/13 10:49:35 AM CDT
As I mentioned I just stepped into a pre-existing configuration
The only reason I can see that they may have stayed with this , is because using server 2003 sbs.
I have not done any research as of yet as a viable upgrade that supports this configuration. Any suggestions would be welcome!
I'm sure any update or change of software could be easily justified to the powers that be.
However, in short term would still like to solve this problemMessage was edited by: jreed on 6/13/13 12:14:25 PM CDT
Out of support (since March 31, 2010) as per: https://kc.mcafee.com/corporate/index?page=content&id=KB52201 means no support at all, here or elsewhere at McAfee, sorry.
There's no way around it unfortunately. As it is no longer protecting you at all you'll have to uninstall the product in the normal manner or as per: https://kc.mcafee.com/corporate/index?page=content&id=KB58597
Then obtain a valid, current product.
If anyone wants to offer their advice here then it's completely unofficial of course.
Meanwhile FYI current version is 8.8 patch 3.
Server 2003 also ended it's lifecycle some time ago.
Message was edited by: Ex_Brit on 13/06/13 3:56:39 EDT PM
Server 2003 is actually until 2015 supported by Microsoft (means supplied with security hotfixes): http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Windows+Server+2003&Filter=...
Server 2003 is actually until 2015 supported by Microsoft (means supplied with security hotfixes): http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Windows +Server+2003&Filter...
My error, sorry. I guess it depends which version you look at.
Thanks Folks. I will be looking into newer version, solution. However, I did manage to get it up and going again. One I found corrct service associated with problem, and stopped and restarted. It seems to be ok again. Kinda one of those services with no branding attached to it and no description to lead you to it.