Environmet:SCCM Site Server: 2k3 R2 SP2 on 2003 R2 SP2 x64Remote SQL 2005 DB on a cluster.DMZ Distribution Point (also a Management Point): 2k3 R2 SP2 x32 in DMZ. The DMZ DP is in a seperate Domain with no trust relationship with the intranet domain. for the time being the firewall between the DMZ DP and SQL and DMZ DP and Site server is wide open. Once everything is working OK, I intend on tightening it up. TCP 443 only port open to internet.The Management Point is working great, no errors, accepting connections from Internet Clients and passing data. I also have several remote intranet Distribution Points that are working fine.I have been performing pre-production testing with small program deployments and everything was going well. The problem started when I attempted to add Office 07 to the deployment point. In a Nutshell, the files are copied to the DMZ DP and a few seconds later the following events are logged in SMS_DSTRIBUTION_MANAGER:SMS Distribution Manager is starting to distribute package "Office Test" to distribution point "["Display=\\DMZ_DP\"]MSWNET:["SMS_SITE=DWN"]\\DMZ_DP\".SMS Distribution Manager copied package "DWN00018" from "Intranet_DFS" to "MSWNET:["SMS_SITE=DWN"]\\DMZ_DP\SMSPKGE$\DWN00018\".SMS Distribution Manager failed to save package status for package "DWN00018" to the SMS site database.SMS Distribution Manager failed to process package "Office Test" (package ID = DWN00018).Then the process starts all over again with the package copy process starting all over again (over 6000 events in the SMS_DSTRIBUTION_MANAGER log yesterday). I have uninstalled and reinstalled the DP role. Moved the source files to a Non-DFS share and onto the Site server. There is about 29gb free on the drive where the packages are being placed. All successful deployments are also on the intranet DFS. It appears that packages up to a couple hundred MB work OK, anything beyond that generates these errors. I have a hard time believing that it is an actual SQL problem as smaller packages are deployed to the server without error. I also created a new package pointing to the same (or different) source files, same result, small packages are OK, over a few hundred MB, same errors over and over.distmgr.log:~Copying \\Intranet_DFS\Office12-Full\Word.en-us\WordMUI.xml to \\DMZ_DP\SMSPKGE$\DWN00003\Word.en-us\WordMUI.xml, OK $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:51.417 2010 Eastern Standard Time><thread=1020 (0x3FC)>~RDC:Successfully copied package signature file E:\SMSPKGSIG\DWN00003.9.tar to \\DMZ_DP\SMSSIG$\\DWN00003.9.tar $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:52.870 2010 Eastern Standard Time><thread=1020 (0x3FC)>~RDC:Successfully set access security on \\JXN140SCCM01\SMSSIG$\\DWN00003.9.tar for package DWN00003 signature file $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:52.995 2010 Eastern Standard Time><thread=1020 (0x3FC)>~Successfully copied package DWN00003 from \\Intranet_DFS\Office12-Full\ to MSWNET:["SMS_SITE=DWN"]\\DMZ_DP\SMSPKGE$\DWN00003\ $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:52.995 2010 Eastern Standard Time><thread=1020 (0x3FC)>STATMSG: ID=2329 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Site_Server SITE=DWN PID=1768 TID=1020 GMTDATE=Fri Jan 08 04:37:52.995 2010 ISTR0="DWN00003" ISTR1="\\Intranet_DFS\Office12-Full\" ISTR2="MSWNET:["SMS_SITE=DWN"]\\DMZ_DP\SMSPKGE$\DWN00003\" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="DWN00003" AID1=404 AVAL1="["Display=\\DMZ_DP\"]MSWNET:["SMS_SITE=DWN"]\\DMZ_DP\" $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:52.995 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** [28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.010 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** [28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.010 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** Failed to connect to the SQL Server. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.010 2010 Eastern Standard Time><thread=1020 (0x3FC)>~Cannot save the package status to the data source after successfully copying the package. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.010 2010 Eastern Standard Time><thread=1020 (0x3FC)>STATMSG: ID=2326 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=JXN140SCCM00 SITE=DWN PID=1768 TID=1020 GMTDATE=Fri Jan 08 04:37:53.010 2010 ISTR0="DWN00003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="DWN00003" AID1=404 AVAL1="["Display=\\DMZ_DP\"]MSWNET:["SMS_SITE=DWN"]\\JXN140SCCM01\" $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.010 2010 Eastern Standard Time><thread=1020 (0x3FC)>Error occurred. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.010 2010 Eastern Standard Time><thread=1020 (0x3FC)>Performing error cleanup prior to returning. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.010 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** [28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.042 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** [28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.042 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** Failed to connect to the SQL Server. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.042 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** [28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.042 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** [28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.042 2010 Eastern Standard Time><thread=1020 (0x3FC)>*** Failed to connect to the SQL Server. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.057 2010 Eastern Standard Time><thread=1020 (0x3FC)>STATMSG: ID=2326 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=JXN140SCCM00 SITE=DWN PID=1768 TID=1020 GMTDATE=Fri Jan 08 04:37:53.057 2010 ISTR0="DWN00003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="DWN00003" AID1=404 AVAL1="["Display=\\DMZ_DP\"]MSWNET:["SMS_SITE=DWN"]\\DMZ_DP\" $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.057 2010 Eastern Standard Time><thread=1020 (0x3FC)>DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.057 2010 Eastern Standard Time><thread=4360 (0x1108)>DP thread with thread handle 4632 and thread ID 1020 ended. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.057 2010 Eastern Standard Time><thread=4360 (0x1108)>Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><Thu Jan 07 23:37:53.057 2010 Eastern Standard Time><thread=4360 (0x1108)>I know there are SQL errors in the log but why would the size of the package have any bering on whether the staus can be updated? SQL Cluster is in windows/SQL Auth mode. All servers have the appropriate roles. The DMZ Domain ID is in the DP's administrators group. grr, please help

I have discovered an additional oddity. If I add or remove a small package to or from the Distribution Point with a large one is in failure mode, the large one will finally succeed! Office 07 failed for about 8 hrs, I added a 300k pakage and almost immidiately the Office 07 package succeeded. Further testing has born this out 3 more times during the day today with 3 packages over 300MB.

Did you ever find a fix for this? We are having the same exact issue. We have case open with Microsoft but they don't know what's causing it or have any ideas on fixing it.

No, I did not. It is still an occational problem that I have not been able to track down. The other details I would add are: the source files are on a DFS. The DMZ Dist Point is on a different Domain than the Site server The DMZ Dist point is also the internet Management point, NO errors associated with this role THE Site database is on a different System. We ARE going to be moving the SQL DB over to the site server in an effort to improve Console performance and conserve VM resources. Once in a while I spend a bit of time trying to figure this one out. The latest is that we were getting Access denied errors with everything we tried to push out to the DMZ. I took a look at the logs on ther DFS Servers and noticed that it was trying to acces the source files with the ID used in the DMZ domain to install roles. It would 1st try it with a "generic" ID (SCCM_SYSTEM), then it would try it with the fully qualified ID (web\SCCM_SYSTEM). Both would fail. I created an ID on both the DFS Servers for that namespace that matches logon info & password with the web domain ID and the access errors went away. Also pointing the source to a specific server, and not just the namespace) seemed to help. I will post here if there are any changes. Please let me know if MS Figures anything out...

Thanks, your fix also worked for me. MS never figured it out they just kept telling me I needed to create a trust which I wasn't going to do. I spent weeks and many hours with multiple engineers and it seemed like they didn't have a clue as to what the real problem even was.