McCoyIT
asked on
SCCM 2012 Content Distribution Issue
I am running into intermittent problems sending content to distributions points, and I'm having difficulty pinpointing the issue, because it happens seemingly randomly, never consistently the same distribution points, and doesn't always happen.
The issue comes up where I send out a new package or software updates to distribution points (whether individually or distribution point groups), and the distribution point status shows "failed" for some of the points, so I then go to monitoring to look at content status, find the package / updates and look at the error tab.
The status shows "Failed to initialize NAL" status type "Error", under Asset Details it shows the description: "Distribution Manager failed to connect to the distribution point. Possible cause: Distribution Manager cannot access the distribution point machine because of access permissions issues. Solution: Make sure that the siteserver machine account or Site System Installation account has administrative permissions on the distribution point machine."
I know that's not the case, because the machine account of the Primary server is what was used to install the distribution point in the first place, and upon repeat attempts (Package properties > Content Locations > select distribution point > Redistribute) it will successfully send the package.
Windows firewall is running on the primary site server and all distribution points, configured with ports open as per the TechNet article.
This is what I see in distmgr.log:
Sometimes it will work after retrying, other times it won't, can't seem to find a pattern to it.
The issue comes up where I send out a new package or software updates to distribution points (whether individually or distribution point groups), and the distribution point status shows "failed" for some of the points, so I then go to monitoring to look at content status, find the package / updates and look at the error tab.
The status shows "Failed to initialize NAL" status type "Error", under Asset Details it shows the description: "Distribution Manager failed to connect to the distribution point. Possible cause: Distribution Manager cannot access the distribution point machine because of access permissions issues. Solution: Make sure that the siteserver machine account or Site System Installation account has administrative permissions on the distribution point machine."
I know that's not the case, because the machine account of the Primary server is what was used to install the distribution point in the first place, and upon repeat attempts (Package properties > Content Locations > select distribution point > Redistribute) it will successfully send the package.
Windows firewall is running on the primary site server and all distribution points, configured with ports open as per the TechNet article.
This is what I see in distmgr.log:
Failed to make a network connection to \\server.domain.com\ADMIN$(0x35).
Cannot establish connection to ["Display=\\server.domain.com\"]MSWN ET:["SMS_S ITE=XXX"]\ \server.do main.com\. Error = 53Error occurred.
Performing error cleanup prior to returning.
Sometimes it will work after retrying, other times it won't, can't seem to find a pattern to it.
ASKER
Both articles appear to relate to SCCM 2007, but in regards to some of the comments on the articles - yes, the primary server computer account has been added to the local admin group on the site servers.
I'm seeing two other errors as well as the Error 53:
I'm seeing two other errors as well as the Error 53:
Failed to make a network connection to \\server.domain.com\ADMIN$ (0x40).
Cannot establish connection to ["Display=\\server.domain.com\"]MSWNET:["SMS_SITE=XXX"]\\server.domain.com\. Error = 64
Yes these are for 2007, but you have to check the above settings on the 2012 also.
These errors you highlighted are related to them. thats why i give to you.
These errors you highlighted are related to them. thats why i give to you.
ASKER
The only setting I could see that was applicable was related to the computer account, which is already set.
The other error I see is in PkgXferMgr.log which is:
The other error I see is in PkgXferMgr.log which is:
There is no existing connection, Win32 error = 64ASKER
Consistently though, if I go to the package and hit re-distribute, it will send the package without issue, this only happens the first time I send out a package to all the distribution points, which is why this seems difficult to track down the cause.
I think it is a known issue. I have a video from Johan Arwidmark saying so.
ASKER
Interesting, do you happen to have a link?
This could be a different error but it is similar.
http://www.deployvista.com/Blog/JohanArwidmark/tabid/78/EntryID/62/Default.aspx
=============
Instead, most times it's the Settings Package that is failing and you only need to Update the Distribution Point for that package and then everyhing works just fine...
================
http://www.deploymentresearch.com/Research/tabid/62/EntryId/85/To-be-fixed-the-ConfigMgr-2012-SP1-feature-Access-content-directly-from-DP.aspx
If you get the below error, it just the old "hash value is not correct bug" that has been haunting ConfigMgr for years. The fix is easy, you simply need to update the distribution point(s) for operating system image package.
Failed to run the action: Apply Operating System Image
Overlapped I/O operation is in progress. (Error: 800703E5; Source: Windows)
==========================
I am giving you another link because the one i was thinking is in one of the videos I watched from him.
http://www.deployvista.com/Blog/JohanArwidmark/tabid/78/EntryID/62/Default.aspx
=============
Instead, most times it's the Settings Package that is failing and you only need to Update the Distribution Point for that package and then everyhing works just fine...
================
http://www.deploymentresearch.com/Research/tabid/62/EntryId/85/To-be-fixed-the-ConfigMgr-2012-SP1-feature-Access-content-directly-from-DP.aspx
If you get the below error, it just the old "hash value is not correct bug" that has been haunting ConfigMgr for years. The fix is easy, you simply need to update the distribution point(s) for operating system image package.
Failed to run the action: Apply Operating System Image
Overlapped I/O operation is in progress. (Error: 800703E5; Source: Windows)
==========================
I am giving you another link because the one i was thinking is in one of the videos I watched from him.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Found the answer myself through more testing.
1) http://social.technet.microsoft.com/Forums/systemcenter/en-US/e6d6c8be-9474-417d-a7a4-4394c774480c/cannot-create-nal-path-for-the-distribution-point
2) http://social.technet.microsoft.com/Forums/systemcenter/en-US/47700bf8-92ea-45b4-af62-046d35a34a5a/sms-distribution-manager-failed-to-initialize-the-network-abstraction-layer-nal