I was examining our DP configuration status and looked at some of the content that was generating errors. I then used the package ID to identify what content was the issue. However, the IDs are not valid in that these IDs do not exist in the content status
node. I am assuming they were deleted long ago, and the last status time bears that out because it is not recent.
How can I clean up these bogus packages? I am hoping to not have to run queries directly on the DB.
Well, I did some DB querying and did in fact find the package. It's a package that references a file (a batch file) but whoever added it did not check the "This package contains source files" box. That would explain why it did not show up in the content
It does strike me as odd that it generates an error; I suppose it is because the batch file specified did not have a full file path.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.