SOLVED

MECM Content Library Explorer not working - RESOLVED

Iron Contributor

 

Hi,

(I posted this over on the system center area before I realized there was this area - https://techcommunity.microsoft.com/t5/system-center/content-library-explorer-not-working/m-p/166682...) - just copied here in case any regulars here have any ideas?

 

 

     We recently had to migrate to new hardware after a failure, most things seem to have survived or been revived, however content library explorer will not run. After entering the DP fqdn, it attempts to load and returns an error "An item with the same key has already been added"

Any ideas appreciated.  

We have MECM 2002, server 2019 standard and Sql 2019 all on same server. 

 I have run a site reset - no change. 

 

event logs show this

Application: contentlibraryexplorer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
at Microsoft.ConfigurationManager.ContentLibraryExplorer.Program.Main()

 

followed by this

 

Faulting application name: contentlibraryexplorer.exe, version: 5.0.8968.1000, time stamp: 0x5e5b947a
Faulting module name: KERNELBASE.dll, version: 10.0.17763.1369, time stamp: 0xb99aaceb
Exception code: 0xe0434352
Fault offset: 0x00122452
Faulting process id: 0x3b50
Faulting application start time: 0x01d68aef710141d1
Faulting application path: C:\Program Files\Microsoft Configuration Manager\tools\ServerTools\contentlibraryexplorer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: a4c3c7bb-b0bd-48d6-b689-1f9344ce191e
Faulting package full name:
Faulting package-relative application ID:

 

in case relevant I have checked and we have dotnet 4.7 installed with only the following components not checked

  • Message Queueing (MSMQ) Activation
  • Named Pipe Activation
  • TCP Activation

 

I tried running Procmon and only found one section that might be indicative of an issue.  I am in the administrators group on the machine and am MECM admin also, 

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

CreateFile

\\OURMECMSERVERfqdn\SCCMContentLibG$\

BAD NETWORK NAME

Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

CreateFile

\\OURMECMSERVERfqdn\SCCMContentLibG$\

BAD NETWORK NAME

Desired Access: Read Data/List Directory, Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

CreateFile

\\OURMECMSERVERfqdn\SCCMContentLibG$\

BAD NETWORK NAME

Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

CreateFile

\\OURMECMSERVERfqdn\SCCMContentLibG$\

BAD NETWORK NAME

Desired Access: Read Data/List Directory, Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

CreateFile

\\OURMECMSERVERfqdn\SCCMContentLibH$\

BAD NETWORK NAME

Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

CreateFile

\\OURMECMSERVERfqdn\SCCMContentLibH$\

BAD NETWORK NAME

Desired Access: Read Data/List Directory, Synchronize, Disposition: Open, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

FileSystemControl

\\OURMECMSERVERfqdn\IPC$

FS DRIVER REQUIRED

Control: FSCTL_DFS_GET_REFERRALS

CloseFile

\\OURMECMSERVERfqdn\IPC$

SUCCESS

 

 

Neither of these shares exist.  there was a "SCCMContentLib$" which pointed to the content Library

I created another share to the same path for "SCCMContentLibG$" but that doesn't appear to have helped.  

there is an "IPC$" share with no folder path. (which appear to be the way it should be)

 

any ideas appreciated, thankyou. 

 

 

3 Replies

@PaulKlerkx 

 

hi 

well i guess the best way to restore the DP is

remove the Role

restart the server

install the role as DP

add the DP to the DP Group

the rest will SCCM / MS for you

 

@Klaus_Bilger thanks for the reply, I have removed and re-added the DP as suggested but it didn’t help.  Since posting, I have identified system file corruption so am looking at that.  SFC check found corruption and DIsm failed with the source not found message. That was Friday afternoon, will be looking at sorting the DIsm repair next week.  

best response confirmed by PaulKlerkx (Iron Contributor)
Solution

@PaulKlerkx  I found the solution - search your applications for a duplicate PkgID. under monitoring – distribution status – content status. use Ctrl + A to select all, paste into an excel spreadsheet. then use conditional formatting to identify any duplicate entries in the package ID column. if you find any, start by deleting all revisions except the latest to see if that helps, but more likely you will need to delete and recreate the applications so they get unique package ID’s. Also, in Sql I found the duplicates listed in dbo.vPkgStatusSummaryDistPts (under Views). - didn't change anything in the DB, this is just fyi.  

1 best response

Accepted Solutions
best response confirmed by PaulKlerkx (Iron Contributor)
Solution

@PaulKlerkx  I found the solution - search your applications for a duplicate PkgID. under monitoring – distribution status – content status. use Ctrl + A to select all, paste into an excel spreadsheet. then use conditional formatting to identify any duplicate entries in the package ID column. if you find any, start by deleting all revisions except the latest to see if that helps, but more likely you will need to delete and recreate the applications so they get unique package ID’s. Also, in Sql I found the duplicates listed in dbo.vPkgStatusSummaryDistPts (under Views). - didn't change anything in the DB, this is just fyi.  

View solution in original post