This is usually a sign that the catalog.z file in the root of the master repo (..\DB\Software) has become damaged or is missing.
Is that file present?
Can you restore it from backup?
If you have any distributed repositories, there may be a valid copy in the root of the distributed repo - try renaming the copy in the master repo and copying in the version from the distributed repo...
Thanks for replying
C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\catalog.z is still there and present.
I should have a backup of that file from last night though i should try two nights ago.
I dont know about distributed repositories.
Should i rename the C:\Program Files\McAfee\ePolicy Orchestrator\DB\Software\catalog.z as catalog.old and retore the catalog.z from two nights ago?
Is there anything else I would need to restore?
That should be enough to start with - if all goes well you should be able to see the contents of the repository again. If you can, I would recommend immediately doing a pull task.
happy Joe you are a professional who knows your craft!
That sorted it out and i ran an update and I now have the latest DAT installed.
The only thing that need worry me is if my install of Endpoint caused this corruption or if the SFDBBack (safeboot database backup i think) backup schedule locked the database/system causing the corruption.
Is there anything else i should look at on epo before i celebrate and enjoy the rest of my Friday?
I can't think of a reason off the top of my head why either of those operations would cause catalog.z to get bent... about the only additional check I would do is pick a test machine and make sure you can deploy software to it from the master repo, and that it can update itself from the master as well.
Then I'd head for the pub :)
Nice! Deployed EPO to a new client and checked that the DAT has updated on existing client too.
I think ill get working on that pub visit you mentioned too.:D
My Master Repository is getting empty about every two weeks (ePO 4.5 on Windows 2008 with SQL Server Express 2008); I have to restart the server to get it back.
I've already posted a thread about this problem:
My catalog.z file is present in DB\Software but I don't know how to determine if it's corrupted (for example, WinRAR cannot open it)...