Update directory does not exist, how do I translate that to the update that it can't find.

I have an error that one of the update source locations in an update package can't be found.  The path in the content status even shows what it should be, and sure enough it doesn't exist. The path is the location designated for the package plus a GUID.  My problem is I can't find a way to translate that GUID into which update I'm having a problem with.  The console doesn't show any information and the GUID doesn't match any of the updates.  I went poking around in the database but couldn't find anything obvious.  The log files unfortunately weren't any help either.

Does anyone know a way to figure out what update this is.  My only other alternative is to delete the package and start over from sc

June 25th, 2013 12:36am

Yes, I know this is an old post, just trying to clean up old posts. Did you figure this out, if so how did you solve it?

Free Windows Admin Tool Kit Click here and download it now
July 6th, 2013 11:46am

We ended up deleting the update package and the source directory and starting from scratch.  I wonder if we could get Ballmer to issue an exective order that any developer putting out an error message without information to help someone troubleshoot the problem be ineligible for a bonus that year.  Knowing the path to a GUID directory isn't very helpful.
July 6th, 2013 4:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics