SOLVED SCCM Content Library Cleanup Tool Question

[matteobarreo]

Good afternoon,

I am currently working cleaning up my Content Library, using the Content Library Cleanup Tool. I have used the tool before and understand how it works and what the errors mean, however I'm stuck on a tough on here. Here is a run-down of exactly what I am doing:
1) I run the content library cleanup tool in what-if mode through and admin cmd prompt (ContentLibraryCleanup.exe /dp Distribution Point /whatif
2) I receive the error: "The content library cannot be cleaned up right now because the package ABC12345 is not fully installed." I understand what this error means, it is supposed to mean that package ABC12345 is not fully distributed - either it failed or is in progress.
3) I go to my software library and search all objects for ABC12345, and it doesn't come up. I even physically went into the content library folder and searched for that package ID, still nothing. That package that is being referenced doesn't exist anywhere on my System Center Console. It is as if the package is in limbo. This technique worked for me when cleaning up my old server and for the first couple of "not fully installed" packages. It is as if I deleted the package already, but it didn't fully distribute, so it's just in la-la land somewhere. Does anybody know have any ideas how I can find this phantom package?

 

[Prajwal Desai]

Can you try finding out what this package is by running any of the below commands.

Using PowerShell - Get-CMPackage -ID "packageid" | Select -expand Name

Using SQL - Select * from smspackages where pkgid='packageid'

Reference - https://www.prajwaldesai.com/conten...ntent-library-cannot-be-cleaned-up-right-now/

 

[matteobarreo]

I already did that and it returned nothing. I will try again just to make sure...

 

[matteobarreo]

Correction: I haven't run that command yet. I am currently updating PowerShell, as it is only on V 4. I'll be back once it's updated and I have run that command.

 

[Prajwal Desai]

Ok let me know the result.

 

[matteobarreo]

Alright, I've got an update. I was able to find the package and re-distribute it. Running the tool again with logging, the log shows the following error: "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 can gather from this error is that you cannot run this tool when your distribution point is also your primary site server.

Seeing as how we are a smaller environment, we have all of our roles installed on one server. Is there a recommended way to manually clean up content?

 

[THamlin]

Alright, I've got an update. I was able to find the package and re-distribute it. Running the tool again with logging, the log shows the following error: "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 can gather from this error is that you cannot run this tool when your distribution point is also your primary site server.

Seeing as how we are a smaller environment, we have all of our roles installed on one server. Is there a recommended way to manually clean up content?

I was wondering if you ever got an answer to this. We are in the exact same situation needing to cleanup content, but are getting the error due to having a single site/server. I'd like to know how to do content cleanup if this tool can't be used.