SCCM Distribution Manager Failed to access source directory...

Hi guys....
Im in a desperate position at the moment. I joined a small company a short while ago as an infrastructure engineer but have never had hands on experience with sccm 2012. The guy I was working with left
at short notice and never had time to show me the system.
I am now trying to image some new systems but for some reason I keep getting the above error message. I have checked share and NTFS permissions and ensured that all the SMS accounts have a minimum of modify
if not full rights including the local administrator account. The drives also have sufficient disk space. I am finding it impossible to update the distribution point (even though the wizards says successful).
Each time i try to run the task from the client I get Failed to run Task sequence, "This task sequence cannot be run because the program files for DI100005 cannot be located on a distribution point."
I have also ensured that Site system installation account is set to
Use the site server's computer account to install the site system
Please can someone point me in the right direction and help me to resolve this issue.
Many Thanks

Hi Torsten,
I have checked the log but not really sure what i am looking for. It tells me that a task has filed but not sure why? Is SMS_Distribution _Manager a generic name used for whatever account its supposed to be using?
Here is a snippet of the log from this morning. If you could please decypher it for me I would be very grateful.
---------Log Start ----------
Found package properties updated notification for package 'DI100005' $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:01.967-60><thread=7128 (0x1BD8)>
Found notification for package 'DI100005' $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:06.969-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.032-60><thread=7128 (0x1BD8)>
~Starting package processing thread, thread ID = 0xCC0 (3264) $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.550-60><thread=7128 (0x1BD8)>
~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.552-60><thread=7128 (0x1BD8)>
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:07.720 2014 ISTR0="Boot image (x64)" ISTR1="DI100005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.720-60><thread=3264 (0xCC0)>
Start updating the package DI100005... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.721-60><thread=3264 (0xCC0)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100005, Version=14, Status=2300 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:07.728-60><thread=3264 (0xCC0)>
Taking package snapshot for package DI100005 from source \\DI-WSUS-SRV.di.local\SMS_DI1\OSD\boot\x64\boot.DI100005.wim $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.115-60><thread=3264 (0xCC0)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.120-60><thread=3264 (0xCC0)>
~Cannot create \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.]. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.189-60><thread=3264 (0xCC0)>
~Cannot create the content library storage directory \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, use the default directory. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.190-60><thread=3264 (0xCC0)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.191-60><thread=3264 (0xCC0)>
Failed to get the content library path. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.200-60><thread=3264 (0xCC0)>
SnapshotPackage() failed. Error = 0x80004005 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.200-60><thread=3264 (0xCC0)>
STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:08.201 2014 ISTR0="\\DI-WSUS-SRV.di.local\SMS_DI1\OSD\boot\x64\boot.DI100005.wim" ISTR1="Boot image
(x64)" ISTR2="DI100005" ISTR3="30" ISTR4="100" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.201-60><thread=3264 (0xCC0)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100005, Version=13, Status=2302 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.201-60><thread=3264 (0xCC0)>
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3264 GMTDATE=Tue Aug 26 08:18:08.363 2014 ISTR0="Boot image (x64)" ISTR1="DI100005" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100005" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.363-60><thread=3264 (0xCC0)>
~Failed to process package DI100005 after 0 retries, will retry 100 more times $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.364-60><thread=3264 (0xCC0)>
~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:08.381-60><thread=3264 (0xCC0)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.018-60><thread=8392 (0x20C8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.566-60><thread=7128 (0x1BD8)>
~Sleep 1826 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:12.591-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:17.611-60><thread=7128 (0x1BD8)>
~Sleep 1821 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:18:17.621-60><thread=7128 (0x1BD8)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:42.490-60><thread=8392 (0x20C8)>
Found package properties updated notification for package 'DI100004' $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:47.491-60><thread=7128 (0x1BD8)>
Found notification for package 'DI100004' $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.425-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.450-60><thread=7128 (0x1BD8)>
~Starting package processing thread, thread ID = 0xE0C (3596) $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.950-60><thread=7128 (0x1BD8)>
~Sleep 585 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:53.952-60><thread=7128 (0x1BD8)>
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.072 2014 ISTR0="Boot image (x86)" ISTR1="DI100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.072-60><thread=3596 (0xE0C)>
Start updating the package DI100004... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.073-60><thread=3596 (0xE0C)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100004, Version=5, Status=2300 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.074-60><thread=3596 (0xE0C)>
Taking package snapshot for package DI100004 from source \\DI-WSUS-SRV.di.local\SMS_DI1\osd\boot\i386\boot.DI100004.wim $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.104-60><thread=3596 (0xE0C)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.108-60><thread=3596 (0xE0C)>
~Cannot create \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, [error code: 67, error message: The network name cannot be found.]. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.120-60><thread=3596 (0xE0C)>
~Cannot create the content library storage directory \\DI-WSUS-SRV.di.local\D$\SCCMContentLib, use the default directory. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.120-60><thread=3596 (0xE0C)>
~Share folder \\DI-WSUS-SRV.di.local\D$\SCCMContentLib does not exist or is not accessible. Error code = 67 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.122-60><thread=3596 (0xE0C)>
Failed to get the content library path. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
SnapshotPackage() failed. Error = 0x80004005 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.131 2014 ISTR0="\\DI-WSUS-SRV.di.local\SMS_DI1\osd\boot\i386\boot.DI100004.wim" ISTR1="Boot image
(x86)" ISTR2="DI100004" ISTR3="30" ISTR4="100" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.131-60><thread=3596 (0xE0C)>
~CDistributionSrcSQL::UpdateAvailableVersion PackageID=DI100004, Version=4, Status=2302 $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.132-60><thread=3596 (0xE0C)>
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DI-WSUS-SRV.di.local SITE=DI1 PID=916 TID=3596 GMTDATE=Tue Aug 26 08:38:54.221 2014 ISTR0="Boot image (x86)" ISTR1="DI100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DI100004" $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.221-60><thread=3596 (0xE0C)>
~Failed to process package DI100004 after 0 retries, will retry 100 more times $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.222-60><thread=3596 (0xE0C)>
~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:54.222-60><thread=3596 (0xE0C)>
Sleep 30 minutes... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.439-60><thread=8392 (0x20C8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.965-60><thread=7128 (0x1BD8)>
~Sleep 580 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:38:58.966-60><thread=7128 (0x1BD8)>
~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:39:03.979-60><thread=7128 (0x1BD8)>
~Sleep 575 seconds... $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:39:03.980-60><thread=7128 (0x1BD8)>
Sleeping for 60 minutes before content cleanup task starts.~ $$<SMS_DISTRIBUTION_MANAGER><08-26-2014 09:42:35.263-60><thread=3480 (0xD98)>
---------Log Finish ----------
Cheers,
Aaron

Similar Messages

Distribution Manager Failed To Access The Source Directory

Hello All,
I have this issue distributing content to my Distribution Points for months now. I keep running into this error below:
Distribution Manager Failed to Access the source directory (\\share\folder\file.wim)
Possible Cause: Distribution Manager does not have sufficient rights to the source directory.
Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.
Possible Cause: There is not enough disk space available on the site server.
Solution: Verify that there is enough free disk space available on the site server.
I checked the distmgr.log file and received these messages:
GetTempFileNameA failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
CFileLibrary::AddFile failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
CContentDefinition::AddFile failed; 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
Failed to add the file. Please check if this file exists.   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
SnapshotPackage() failed. Error = 0x80004005   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
Failed to take snapshot of package CSU0006A   SMS_DISTRIBUTION_MANAGER   3/24/2015 2:15:38 PM   13952 (0x3680)
There is enough space on the site server and the site server has full control over the source directory. I wish I can give you more information but I'm hoping this is enough info to get some assistance. If more information is needed please let me know!

We usually give the DP's computer account and the site server computer account read access to these shares in our environment.
... which is not enough for drivers and updates (as there will also files be added).
Torsten Meringer | http://www.mssccmfaq.de
... And for capture Image too if your capture destination points on that share

SCCM 2012 SP1 Distribution Manager Failed

I am getting the error below when I send the package to the Distribution point:
" Distribution Manager failed to find or create the defined share or volume on distribution point"

Hi,
Please check Distmgr.log to find the problem.
The blog that Paul provided seems to be helpful.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Distribution Manager failed to process package triggers an update of the packages

Hi all,
we have randomly following issue:
SCCM 2012 Sp1 CAS, takes a snapshot of a Windows update package in the morning (not sure how the frequency of this check is done). If for any reason it fails, SCCM automatically redistributes the package to all sites. This happened this morning again for 5
Windows updates packages. You understand that this means GB sent to all Secondary sites (66) with an useles amount of data sent out.
From the Status messages I see
Information Milestone RC0 06.11.2014 07:12:11 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2300 Distribution Manager is beginning to process package "SUP-2014.09" (package ID = RC00017B).
Then lot of updates lists with comment taking a snapshot and finally
Error Milestone RC0 06.11.2014 07:12:29 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2302 Distribution Manager failed to process package "SUP-2014.09" (package ID = RC00017B). Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Possible cause: The package source directory contains files that might be in use by an active process. Solution: Close any processes that maybe using files in the source directory. If this failure persists, create an alternate copy of the source directory and update the package source to point to it.
This triggers immediately an update of all DPs
Information Milestone RC0 06.11.2014 07:43:52 SCHVSGGSC600.rccad.net SMS_DISTRIBUTION_MANAGER 2304 Distribution Manager is retrying to distribute package "RC00017B". Wait to see if the package is successfully distributed on the retry.
Any idea
How this can be avoided, since nobody changed the package and we suppose it was a temp connection issue between the CAS and the package repository server
If this check can be set up to once a week for instance or even less?
Thanks,
Marco

Hi Daniel,
thanks for the prompt answer. Actually I saw it yesterday at least for 1 package (the last one). The error is generate by SQL killing a task
Adding these contents to the package RC00010D version 347.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:23
7796 (0x1E74)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:23 3652 (0x0E44)
*** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 152) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCHVSGGSC600.rccad.net SITE=RC0 PID=2144 TID=5460 GMTDATE=jeu. nov. 06 06:12:25.422 2014 ISTR0="SUP-2012.Q4" ISTR1="RC000068" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC000068"
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
Failed to process package RC000068 after 0 retries, will retry 100 more times
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:25
5460 (0x1554)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:25 5460 (0x1554)
Used 4 out of 5 allowed processing threads.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:26
3300 (0x0CE4)
Starting package processing thread, thread ID = 0x894 (2196)
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
3300 (0x0CE4)
Used all 5 allowed processing threads, won't process any more packages.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
3300 (0x0CE4)
Sleep 1828 seconds... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:27 3300 (0x0CE4)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCHVSGGSC600.rccad.net SITE=RC0 PID=2144 TID=2196 GMTDATE=jeu. nov. 06 06:12:27.716 2014 ISTR0="SUP-2014.M05" ISTR1="RC00011D" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RC00011D"
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
Start updating the package RC00011D... SMS_DISTRIBUTION_MANAGER
06.11.2014 07:12:27 2196 (0x0894)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=RC00011D, Version=14, Status=2300
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
*** [40001][1205][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 154) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
1424 (0x0590)
Taking package snapshot for package RC00011D
SMS_DISTRIBUTION_MANAGER 06.11.2014 07:12:27
2196 (0x0894)
Now as I mentioned it was probably an SQL (more likely) or networ issue, however the question was more about how to avoid that. Finally the packages were not changed and if possible I would avoid any automatic SCCM action on packages unless an operator manually
triggers them.
I didn't see any error today, so it should not be a configuration issue.
Is this possible?

Distribution manager failed to connect to the distribution point

After upgrading my distribution point to windows server 2012 standard I can't distribute content to my distribution point.
I see the following error.
source: SMS Server
Component: SMS_DISTRIBUTION_MANAGER
message id 2391
Distribution Manager failed to connect to the distribution point Check your network and firewall settings.
The firewall is not enabled.
wbemtest is able to connect to the remote server that has the distribution point role installed.
The network access account is working.
How do I fix this?

but why does it most of the time work? I did inplace upgrade at least 6 times from 2008 R2 to 2012 R2 and every DP except one works fine.
I'm not completely sure, but I think, my faulty one, that I'm trying to get working, was working correctly after the inplace upgrade. But as I said, that is only a theory, I'm just curious if that's possible.
I have the same issue as described above.
The IT guys from LukOIL

Distribution manager failed to create the defined share or folder on distribution point and failed to connect to remote distribution point

We have recently upgraded remote distribution point to SCCM 2012 R2 CU4. when i try to distribute the package getting the error on the distribution point configuration status "Distribution manager failed to create the defined share or folder on distribution
point and failed to connect to remote distribution point"
Errors on the package transfer log file.
CWmi::Connect() could not connect to \\XXXXXXXX.COM\root\SCCMDP. error = The operation completed successfully.. Will try FQDN
CWmi::Connect() failed to connect to \\XXXXXXX.COM\root\SCCMDP. error = The RPC server is unavailable.
Failed to connect to the DP WMI namespace on the remote DP

Thanks Sandys for your suggestions.
i have tried wbemtest from site server(Secondary site) and remote DP server. Receiving the "The RPC
server is unavailable" from both ends.
error:0x800706ba - The RPC server is unavailable

Operations Manager Failed to Access the Windows Event Log and management server is showing warning state

Hi,
I am monitoring AD server from SCOM 2012 R2. My management server goes into waning state. When i run Health explorer then it come back in the healthy state but after some time it again goes into warning state. After seeing alert i found that a alert is coming
again and again i.e. Operations Manager Failed to Access the Windows Event Log.The description of alert is mention below
The Windows Event Log Provider is still unable to open the DhcpAdminEvents event log on computer 'nc2vws12ad5.corp.nathcorp.com'.
The Provider has been unable to open the DhcpAdminEvents event log for 64080 seconds.
Most recent error details: The RPC server is unavailable.
Please suggest me how to resolve this so that my management server will again come back in healthy state.
Thanks
Abhishek

Hi Abhishek,
As i mentioned earlier the Alert resolution says the same points.
Can you give details on the below ?
Is there really a log named "Dhcpadminevents" in the MS's Event viewer ?
Did you recently configure any new alert where you mentioned "Dhcpadminevents"
as a event log location ?
If yes then what is the target you selected for the rule / monitor there ?
Can you post the results for analysis ?
Gautam.75801

Access Manager Failed to Connect to Directory Server

Dear All,
I have problem with Directory Server connection in Access Manager. This happened in Production site, all application that integrated with Oracle Access Manager (OAM) for Single Sign On are not accessible after the Directory Server connection problem occur in OAM. The problem has only started occurring suddenly, before it the all service including the OAM and Directory Server is running well. Below are the error messages that appear in WebGate log file (ohs1.log) and OAM log file (oblog.log) :
>> OHS/WebGate (ohs1.log) :
[2014-01-21T09:25:12.0053+07:00] https://community.oracle.com/OHS https://community.oracle.com/OHS-9999 https://community.oracle.com/apache2entry_web_gate.cpp host_id: <WEBGATE_HOSTNAME> [host_addr:10.10.254.178] [ecid: 004w76rlRYt0NuapxKL6iW0000sE001oGY] The host and port from the requested URL could not be found in the Policy database. Check if the corresponding directory service is up.
>> OAM (Oblog.log):
2014/01/15@03:12:23.833746 [30573 30606 | tel:30573%20%20%2030606] DB_RUNTIME ERROR 0x000008C1 ../ldap_connection_mngr.cpp:443 "Failed to connect to directory server" lpszHost<LDAP_HOSTNAME_VIA_LOADBALANCER> port<LDAP_PORT_VIA_LOAD_BALANCER>
The OAM using the Load Balancer between the LDAP Directory Server to OAM's component. When the error appears, there are no problem with the Load Balancer and all of Directory Sever services is up. There are two Directory Server servers in Multi Master Replication and 14 WebGate servers that integrated with OAM. Is there a limitation number of WebGate for integrated to the OAM?
I have tried to set some parameters in OAM configuration to solve this problem. I set the Maximum Connection of Directory Server parameter to 10 value (in OAM Console), the LDAPOperationTimeout paramater to 1 hour value and the LDAPMaxNoOfRetries parameter to 2 value (in the globalparams.xml). After set these parameters, the error is not appear in some days, but suddenly appear again in the same error message. May be set these parameters is not appropriate solution for the problem or the value that I set is not correct. Any experience with this?
I still don't know what the root cause of this problem. Restart all of OAM services (including the WebGate) is temporary solution when the error appear.
Any idea for this problem?
Thanks in advice.

Hi Jun-Y,
Thank you for your answer.
What do you means with the Directory Server's idle timeout is the "Idle Timeout" parameter in LDAP Client Control Settings?
I use Oracle Directory Server Enterprise 11.1.1.5.0. Now, the Directory Server's idle timeout parameter is "unlimited" value.
If the idle timeout of the load balancer set 1 hour, it means that I must change the directory server's idle timeout to be less than 1 hour. Isn't right?

Distribution manager failed to process package - the source directory does not exist

Hi,
I have the following behaviour:
A Software Update Deployment Package is not distributing because of the following error:
I have found the following query (http://blogs.technet.com/b/ken_brumfield/archive/2013/01/10/troubleshooting-sccm-software-update-deployment-package-distribution-due-to-missing-directories.aspx) to
determine which update is missing.
It is about update KB978601. If we search this update in the console, we see this:
The update is not required, not downloaded, not deployed and superseeded.
If we look into the members of the Update deployment package, we can't find this update.
When I was digging into the database, I found this:
SELECT
distinct cp.Content_ID,
cp.ContentSubFolder,cp.PkgID,
con.ContentProvisioned
FROM
[dbo].[vCI_ContentPackages] cp
INNER
JOIN [dbo].[CI_ConfigurationItemContents]cic
ON cp.Content_ID
= cic.Content_ID
inner
join dbo.v_CIContents_All
con on con.Content_ID
= cp.Content_ID
where cp.PkgID
=
'XXX002BA'
and cp.ContentSubFolder
=
'39b46f0a-7244-48a6-b795-119ac74009f9'
which resulted in:
Content_ID ContentSubFolder PkgID ContentProvisioned
16828355 39b46f0a-7244-48a6-b795-119ac74009f9 BP1002BA 1
I found the "ContentProvisioned = 1 " a little bit strange.
So, my question is:
Why SCCM is thinking of distributing the content although it is not downloaded or deployed and how can we fix this?
Has it something todo with the "ContentProvisioned" or is it something else?
Thanks,
Sem

I can tell you why CM wants to distribute it, but the easiest way would be downloading that patch thus adding it to the package (so that it can be distributed) and remove it afterwards.
Torsten Meringer | http://www.mssccmfaq.de

Distribution Point creation failed. possible cause : distribution manager does not have the sufficient access right to the computer

Hi All,
I had this really disturbing experience with
SCCM 2012 SP1.
OD : 2008r2 Enterprise 64bit
Possible cause: Distribution Manager does not have sufficient rights to the computer.
Solution: Verify that the site server computer account is administrator of the computer.
in Distmgr.log says :
DPConnection::Disconnect: Revert to self
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Connect: For ["Display=\\PNGBRANCHSERVER.xxx\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.xxx\, logged-on as ssm\sccmadmin
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Connect: For ["Display=\\PNGBRANCHSERVER.xxx\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.x\, logged-on as ssm\sccmadmin
SMS_DISTRIBUxxx ON_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
Failed to find a valid drive on the distribution point ["Display=\\PNGBRANCHSERVER.xxx"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.ssm.com.myx
DPConnection::Disconnect: Revert to selfxxx
MS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
DPConnection::Disconnect: Revert to self SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
GetContentLibLocation() failed SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
Failed to get the content library path on server PNGBRANCHSERVER. SMS_DISTRIBUTION_MANAGER
5/26/2014 7:34:30 AM 16280 (0x3F98)
Failed to install DP files on the remote DP. Error code = 16389
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
STATMSG: ID=2370 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCMSVR. SITE=SSM PID=2660 TID=16280 GMTDATE=Sun May 25 23:34:30.428 2014 ISTR0="["Display=\\PNGBRANCHSERVER.ssm.com.my\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.\"
ISTR1="PNGBRANCHSERVER.S" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\PNGBRANCHSERVER.\"]MSWNET:["SMS_SITE=SSM"]\\PNGBRANCHSERVER.ssm.com.my\"
SMS_DISTRIBUTION_MANAGER 5/26/2014 7:34:30 AM
16280 (0x3F98)
I have tried many of the solution provided unfortunately nothing positive happened.
Appreciate your input before engaging premier support.
Thank you

Hi，
NO_SMS_ON_DRIVE.SMS
This file is used to prevent Configuration Manager from installing binaries to a volume. By default, when you install System Center 2012 Configuration Manager on a remote Site System, the SMS Site Component Manager Service installs the binaries (files and
folders) for the Site System on the NTFS-formatted volume that contains the most free space. You may want to use an NTFS volume other than the default volume for your remote Site Systems by preventing ConfigMgr from enumerating certain NTFS volumes.
In order to prevent CM from enumerating an NTFS volume, on the remote server you can create a text file that is named NO_SMS_ON_DRIVE.SMS and put the this file on the root folder of all NTFS volumes where you do not want to install the binaries (SMS folder)
for the ConfigMgr components.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.

One of my replication job failed with below error, which means job failed because of permission issue on the folder. To resolve that, I have granted the permission and it started working fine. Now the question is as my job was running fine since long time
without any issue then how suddenly the permission of the folder got omitted automatically? I am sure that no one deleted the permission from the folder and as the server is part of SQL cluster no failover occurs.
Error:-The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.
Rahul

Hi Rahul,
Error code 5 indicates that the error is "access is denied." Please make sure that the COM folder is excluded from any antivirus scan that occurs on the system.
If the issue still persists, I recommend you use
Process Monitor to find out a bit more about the accounts and access requests involved. Then grant write permission to the exact COM folder for the account that is running the SQL Server Agent service. For more details, please review the following similar
thread.
http://www.sqlservercentral.com/Forums/Topic1364832-1550-1.aspx
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

"Enable distribution-point sharing for this source site" did not showing SCCM 2007 DPs as SCCM 2012 content shares for CM12 clients

Hi
We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
source site" but data gathering process is completing successfully.
Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
Thanks in Advance
srkr

Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
site" but data gathering process is completing successfully.
Earlier all the shared DPs are showing under Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

WSUS SP2; SCCM 2012 SP1; Sync failed: WSUS update source not found

Hi,
I have installed the Fresh SCCM 2012 SP1 and WSUS 3.0 SP2 + KB2720211 + KB2734608. However, still the Sync is getting failed. This is what I am getting in the wsyncmgr and WCM logs:
wsyncmgr:
Sync failed: WSUS update source not found on site PR1. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=3668 GMTDATE=Fri Jan 09 18:00:00.537 2015 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found
on site PR1. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 1/9/2015 12:00:00 PM
3668 (0x0E54)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
1/9/2015 12:00:00 PM 3668 (0x0E54)
WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER
1/9/2015 11:19:03 AM 4176 (0x1050)
STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.489 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
Remote configuration failed on WSUS Server.
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=ABC.XYZ.net SITE=PR1 PID=2724 TID=4176 GMTDATE=Fri Jan 09 17:19:03.515 2015 ISTR0="DEF.XYZ.net" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_CONFIGURATION_MANAGER 1/9/2015 11:19:03 AM
4176 (0x1050)
I have used the default port numbers 80 and 443 still the sync is failing. Please provide your advise to fix this issue.
Regards,
Malwinder

WCM:
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
It's not only a matter of installing the console, but also those hotfixes on a remote server ...
Torsten Meringer | http://www.mssccmfaq.de

Operations Manager failed to run a WMI query -Access Denied

v hosts to 2012 r2, and now we're seeing a lot of "Operations Manager failed to run a WMI Query", With "Object enumeration failed".
Query: 'SELECT Name, State FROM MSCLUSTER_NetworkInterface where Name="our host name
- Management"' HRESULT: 0x80070005 Details: Access is denied.
Our Cluster run-as account is local admin on the hosts beeing monitored.
We've tried rebuilding the WMI database following this procedure:
1. Disable and stop the WMI service.
     sc config winmgmt start= disabled
     net stop winmgmt
2. Run the following commands.
     Winmgmt /salvagerepository %windir%\System32\wbem      (I noticed that you have run this command, but I would suggest
that you try it again)
    Winmgmt /resetrepository %windir%\System32\wbem
4. Re-enable the WMI service and then reboot the server to see how it goes.
     sc config winmgmt start= auto
If the problem remains, then try the following steps to rebuild the repository:
1. Disable and stop the WMI service.
     sc config winmgmt start= disabled     (note that there is a blank between '=' and 'disabled')
     net stop winmgmt
2. Rename the repository folder (located at %windir%\System32\wbem\repository) to repository.old.
3. Re-enable the WMI service.
     sc config winmgmt start= auto
4. Reboot the server to see if the problem remains.
but we've had no Luck so far. Any help would be
appreciated!
Regards,
Torbjørn

Have you checked if DCOM is enabled, WMI will not be able to connect if its disabled.
Use the steps below to configure DCOM.
Run dcomcnfg.exe
Double-click Component Services
Double-click Computers
Right-click My Computer
Select Properties
Select Default Properties tab
Ensure the "Enable Distributed COM on this computer" checkbox is checked
Default Authentication Level: Connect
Default Impersonation Level: Identify
Next:
Click on COM Security tab
Click Edit Limits under "Launch and Acitvate Permissions"
Make sure Remote Launch and Activation permissions are enabled for the Administrators group
Hope this helps
-Adrian

Trying to install iTunes 10.7 fails - "The installer has insufficient privileges to access this directory: C:\Program Files (x86)\common\files\apple\MobileDeviceSupport\Sync Services\....\Windows

I am trying to install iTunes 10.7 and keep getting this error message (I am running Win 7 Ultimate 64 bit):
"The installer has insufficient privileges to access this directory: C:\Program Files (x86)\common\files\apple\MobileDeviceSupport\Sync Services\....\Windows"
There seem to be other threads that deal with other permission errors, those fixes did not work for this.
Thanks

That one's consistent with disk/file damage. The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
XP instructions in the following document: How to perform disk error checking in Windows XP
Vista instructions in the following document: Check your hard disk for errors
Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

SCCM Distribution Manager Failed to access source directory...

Similar Messages

Maybe you are looking for