aionescu Posted March 5, 2015 Report post Posted March 5, 2015 Hello Everyone. Last month I had to restore the my Primary standalone SCCM server on a new VM as part of a datacenter migration. I've used the same FQDN and it went quite easy. Configuration: SCCM 2012 R2 CU3 running on Windows 2008 R2 and SQL Server 2012 all of them running on the same machine. After the migration I didn't really created / replicated big packages, until last week. Then I've noticed all large packages were failing to distribute. I've looked and the it looks like SMS_Exec restarting every 15 minutes and this kills the transfer/ Of course I've started to check the distrmgr.log and pkgXfermgr.log. pkgXfermgr.log: Sending thread starting for Job: 7800, package: XXXXXXXX, Version: 1, Priority: 2, server: XXXXXXXX, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 2:59:51 PM 2772 (0x0AD4) STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=XXXXXXXX SITE=XXX PID=8376 TID=2772 GMTDATE=Thu Mar 05 14:59:52.005 2015 ISTR0="GG10027C" ISTR1="XXXXXXXX" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="GG10027C" AID1=410 AVAL1="1" AID2=404 AVAL2="XXXXXXXX" SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 2:59:52 PM 2772 (0x0AD4) Sending content Content_ede44cd4-fc3b-4a1e-9ff3-712c9eb3af5e.1 for package XXXXXXXX SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:00:02 PM 2772 (0x0AD4) Redistribute=1, Related= SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:00:02 PM 2772 (0x0AD4) STATMSG: ID=8204 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=EWR0UTLAP06P.gtc.gg.group SITE=GG1 PID=8376 TID=2772 GMTDATE=Thu Mar 05 15:06:04.328 2015 ISTR0="GG10027C" ISTR1="XXXXXXXX" ISTR2="5" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="XXXXXXXX" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\XXXXXXXX\]MSWNET:["SMS_SITE=GG1"]\\XXXXXXXX\" SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:06:04 PM 2772 (0x0AD4) Waiting for all sending threads to end. SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 6216 (0x1848) Shutdown in progress, cancel sending the current package SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) CSendFileAction::SendFiles failed; 0x80004004 SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) CSendFileAction::SendFiles failed; 0x80004004 SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) CSendFileAction::SendFiles failed; 0x80004004 SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) CSendFileAction::SendFiles failed; 0x80004004 SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) Sending failed. Failure count = 2, Restart time = 3/5/2015 4:09:30 PM Coordinated Universal Time SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) Sent status to the distribution manager for pkg GG10027C, version 1, status 4 and distribution point ["Display=\\XXXXXXXX\]MSWNET:["SMS_SITE=GG1"]\\zrh1srv803.emea.gg.group\ SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=XXXXXXXX SITE=XXX PID=8376 TID=2772 GMTDATE=Thu Mar 05 15:09:30.543 2015 ISTR0="GG10027C" ISTR1="1" ISTR2="XXXXXXXX" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="XXXXXXXX" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\XXXXXXXX\]MSWNET:["SMS_SITE=GG1"]\\XXXXXXXX\" SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 3/5/2015 3:09:30 PM 2772 (0x0AD4) Of course there are no pending reboots. I've looked in Windows Logs ->Application and found this: component SMS_SITE_VSS_WRITER on computer XXXXXXX reported: SMS Writer is about to stop the ConfigMgr Services as part of the preparation for the Site backup. Of course at that time there was no site backup scheduled. Just to make sure I've disabled the regular site backup task and the SQL DB backup tasks but the issue is still the same. Does anybody have any idea? Quote Share this post Link to post Share on other sites More sharing options...
aionescu Posted March 6, 2015 Report post Posted March 6, 2015 After some digging I've found this is SMSwriter.log : Attempting to call SCOM Maintenance Mode interface. SMS_SITE_VSS_WRITER 3/6/2015 1:09:48 PM 5164 (0x142C)omEnterMomMaintenanceModeSCOM - Failed to CoCreateInstance for class SCOMMaintenanceModeControl. The error is 0x80040154. SMS_SITE_VSS_WRITER 3/6/2015 1:09:48 PM 5164 (0x142C)Attempting to call MOM 2005 Maintenance Mode interface. SMS_SITE_VSS_WRITER 3/6/2015 1:09:48 PM 5164 (0x142C)omEnterMomMaintenanceModeMOM2005 - Failed to CoCreateInstance for MOMRuntimeAPI. The error is 0x80040154. SMS_SITE_VSS_WRITER 3/6/2015 1:09:48 PM 5164 (0x142C)omEnterMomMaintenanceMode - ended; parameters reason = 'ConfigMgr 4.00.7958.0000 - Starting - Backup', timeout = 3600. SMS_SITE_VSS_WRITER 3/6/2015 1:09:48 PM 5164 (0x142C)Setting the mom agent to maintenance mode failed. May be mom agent is not present on this machine. SMS_SITE_VSS_WRITER 3/6/2015 1:09:48 PM 5164 (0x142C) The only thing is that I don't have a SCOM installation. Quote Share this post Link to post Share on other sites More sharing options...