Forum Discussion
Content Library Cleanup - System.NullReferenceException: Object reference not set to an instance of
PaulKlerkx I would disagree with that statement... I am able to run the tool against my co-located site server/distribution point content library just fine. As a matter of fact, when I tried last week, it successfully deleted about 6 GB worth of orphaned software update-related content. Having said that, I also have a couple of these disabled (greyed-out) packages in my library, just like you do, and these weren't deleted. However, I didn't run into the error that you experienced either. In my opinion, even though it might not fix your problem, you should be able to run the tool successfully nevertheless.
Michiel Overweel - MS called this afternoon while I was grabbing a drink so I missed it. I did a bit of a read through the doco on contentlibrarycleanup and found there is an option for a log file. initially I figured that would just return what is shown in the cmd window, however for me it came back with one line.
"Because this distribution point is co-located with its site server, packages may correctly exist in the content library that are not distributed to the distribution point. Package deletion has been disabled."
I don't understand that, in what situation would I correctly have a package in the content library that isn't distributed to a DP.
I also figured out that if I locate the package ID referenced in content library explorer for a greyed out app, then look that up in content status, that will give me the app name. If I then go and delete that application, that will remove it from content status in the console, however the greyed out entry remains in content library explorer so now I have an entry in content library explorer for an application that doesn't exist anywhere in my console. I did a count too, I have 152 greyed out entries in content library explorer.