Hi all,

I have been trying to search for this issue, but have not found anything similar to this.

My problem is that there is a single Package that is not being transferred to the Branch DP.

Oher packages haev transferred ok, but there is one that does not. I have deleted and republished the package several times with no luck.

All packages have been created to copy the source files from a local directory on the site server.

The only differences that I can see between the packages are that the one not transferring:

 - is larger - about 80MB (The others aless than 20MB each)

 - contains a folder with files in it. The packages that were copied only contain one or two files each, with no folder.

Would there be any reason that would stop one package being copied but not the others?

Oh, this is with SCCM 2007 R3

Hi,

I would suggest you to go through sender.log on the Primary site and distmgr.log on the Secondary site and post the results. You will most likely find the reason in one of these logs :)

Have you configured BITS on your site server for BDP - http://technet.microsoft.com/en-us/library/bb633140.aspx

Hi rcpaqapit,

Check this link: http://technet.microsoft.com/en-us/library/bb680853.aspx that says the below:

We can set preferences to reserve a specific amount of disk space for the operating system or workstation files. Refer the below links for  steps:
http://technet.microsoft.com/en-us/library/bb632651.aspx
http://technet.microsoft.com/en-us/library/bb680754.aspx

Thanks for the responses.

I have tried to look at the Sender.log and distmgr.log files.

The Sender.log file did not seem to have anything in there at all ... even for the packages that worked?

The log file just has this every hour:

~We have 0 active connections  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.103 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
Checking for sending capacity.  Used 0 out of 5.~  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.104 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
Connecting to E:\SCCM\SCCM\inboxes\schedule.box\outboxes\LAN.~  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.104 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
Retrieved the snapshot for priority 0, there are 0 files in the snapshot.  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.105 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
Retrieved the snapshot for priority 1, there are 0 files in the snapshot.  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.105 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
Retrieved the snapshot for priority 2, there are 0 files in the snapshot.  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.105 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
Retrieved the snapshot for priority 3, there are 0 files in the snapshot.  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.106 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
Retrieved the snapshot for priority 4, there are 0 files in the snapshot.  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.106 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
No (more) send requests found to process.~  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.107 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
~Waiting for new/rescheduled send requests, Maximum Sleep Time = 60 minutes  $$<SMS_LAN_SENDER><Wed Apr 24 09:02:31.107 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>
~We have 0 active connections  $$<SMS_LAN_SENDER><Wed Apr 24 10:03:05.494 2013 AUS Eastern Standard Time><thread=3136 (0xC40)>

I could not find the distmgr.log file on the branch DP. Which directory should it be in?

This BITS tab has been configured to throttle the tranfers between 9am and 5pm for BDPs and clients, though downloads outside of throttling window is enabled at 9999Kbps.

As of now (over 48 hours since the package was deployed), it has still not been copied to the BDP.

I have also configured the reserved space to be 500MB, though the drive has 60GB capacity.

There is still 58GB free space available.

Hi rcpaqapit,

Can you create a test package of more than 50MB and try distributing it to the BDP... just to make sure if it is the size issue or someting else.
I suggest you to check the boundary settings for the BDP. Few reference links given below:

https://social.technet.microsoft.com/forums/en-US/configmgrswdist/thread/1d25f3cf-5147-4f8f-aa77-8dd027549f13/
http://blogs.technet.com/b/wemd_ua_-_sms_writing_team/archive/2008/07/27/faqs-for-branch-distribution-points.aspx

Hi,

Sorry, I missed the fact that it was a BDP, which explains why sender.log is empty, because a BDP actually retrieves the content from the Primary, it's not sent from the primary.

Thanks for the response,

I have created two more test packages and distributed to the BDP.

Test1 > Contained a 34MB file and a folder also containing a 34MB file

Test 2 > Contained a 66MB file

Both these packages transferred to the BDP.

What I am now thinking is that the folder structure of the package that refuses to copy might be too complex.

Is there a limit on folder depth or number of characters in a directory path?

The failed package has 165 files and four folders

I will do some more testing, but if anyone has any ideas please let me know.

SCCM should allow only 254 characters ..So please make sure all subfolders file naming convention not to exceed 254 characters. In this case distmgr will show this information like \\XXXX\XXX\XXX\XXX  could not be located

Thanks Narahari B.

The characters are only around 110, so I don't think that is the issue.

I have run another test.

Package 1 - An exe installer and a html readme file

Installs on Main site server DP. Also installs on Branch DP.

Package 2 - 6 files (1x msi, 2x exe, 2x ini, 1x inf) and a folder structure full of other files (dll, chm, css, gif, config, xml, aff, dic)

Installs on Main Site Server DP. Does not install on Branch DP (Not even the package folder gets created)

Package 3 - Same as Package 2, except I deleted the folders (so just the 6 main files)

Installs on Main site server DP. Also installs on Branch DP.

Package 4 - Same as Package 2, except I deleted the files within the folders (so just the 6 files and folder structure)

Installs on Main site server DP. Also installs on Branch DP.

Will do some more tests, but it is looking like it does not like some of the files within the folders in the package.

Did you checked whether your AV client blocking this transfer, run this command  %deflogdir% (mcafee)and check the logs for any blocking on it,by default the Antivirus client will block the remote creation of .INF file since its a threat. if so stop the AV client temporarily and distribute it.

Kamala kannan.c

Hi Kamala,

We do not have McAfee. We use Sophos.

I have checked the logs but nothing I can see about anything being blocked.

Package 3 above contains inf files, and it replicated them ok.

I will try without DLLs and see if it might be the DLL files it doesn't like

Hi rcpaqapit,
Is your issue resolved now.?
If so, please post the solution/findings here, so that it will be useful for others facing this kind of issue.