ePO Repository Replication Failures 2

[bugguy51]

For all of you ePO users that pulled the McAfee emergency virus profile released 10/29 at 8 AM EST, you will probably experience repository replication failures from that point forward. Whoever built the SpamAssassin update package at their commonupdater sites didn't account for a file in Replica.log, therefore, it won't replicate or even delete from the Master Repository (failure to decrypt error).

The solution is to drill down (on your ePO server) to ...\ePO\3.(whatever)\DB\Software\Current and rename Spamsafe 1000. Once the application can't find the directory, it will delete the package just fine.

Hope this didn't wreck anyone else's morning the way it did mine--

The Bug Guy

 

[jfp23]

I got this mornings update and just got the current update and it has replicated to repositories fine.

 

[bugguy51]

Good! Looks like they replaced it while I was sitting in the PrimeSupport queue. Am about to try the next emergency release (4403)--will notify back if it blows up.....

The Bug Guy

 

[JimmyZ1]

Thanks for the info

Doh!!

 

[Lordyboy]

Bugguy51 - stunning piece of info, this has stopped me from going mad!!

Just spent two hours trying to work out while this was happening!

Renamed and deleted the package everything is now OK

Brilliant!

 

[bugguy51]

Lordyboy:

Maybe not brilliant--I had a lot of time sitting on the PrimeSupport queue that I spent futzing with it. 1% inspiration, 99% perspiration!

BugGuy

 

[simonjcook]

Well done Bugguy51.

I found deleting the offending package from the repository solved the issue for me.

You deserve a star.

Regards

Simon J Cook

< Keyboard Error - Press F1 to continue >

 

[morp]

Hi everybody,

Help! Im quite new in EPO...
Could anyone of you guys teach or give me some guides or basic steps on how to automate printed generation of reports daily on an EPO 3.02a.


Your advice and guidance is greatly appreciated.




The few the Proud...