Forum Discussion
Content Library Cleanup - System.NullReferenceException: Object reference not set to an instance of
@Michiel Overweel @Nick-86 - I got my answer from Microsoft so posting here. basically told that it was too hard to fix and they will refund for our case. Seems like maybe related to some sort of corruption and suggested I would need a SQL query to go through each entry in the content library and clean out of the DB, but the query was too complicated for them to do.
**********************
Last email from Microsoft....
I apologize for the delayed response. We wouldn't be able to prepare the query as it needs the testing for all the package's (More than 150 Packages) and it would take months to check and then deliver the result to you.
I would ask my manager to approve the refund on this case as we were not able to resolve your query.
Microsoft thanks for your time and patience in this matter.
**********************
I'll focus on getting our retired apps processed - nearly have a script completed that will do that which may help get rid of some of the corruption. Then I'll come back to this later.
- According to Microsoft Support, the content Library cleanup tool logs and from my experience, the Content Library Cleanup Tool Does not work for a single server set up. (or single server with CMG)
- Greyed out entries in Content Library explorer indicate EITHER MECM having a record of content in the Database, but there isn't any content actually there in the content library OR the applications are retired.
After going through all this, I located a script that assisted with retiring some of our applications which took me several weeks to get the way I liked and run for each application. Part of the script is to rename the application which made it very easy to identify them in the content library explorer.
I still get the error message when running content library cleanup tool with the message in the logfile being "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."
What I found when running my retirement script is that a large number of our retired applications didn't have content on the DP's or DPG's and the original content had also been deleted or moved. I believe our move to a restored server highlighted these issues in the content library explorer and by running my script which cleans any content from the Dp's and DPG's as well as updating the content path, this has cleared up most of the issues being seen.