Search the Community

Hello all. I am running into multicast issues and looking for some help. Current system: SCCM 2012 R2 Cumulative Update 3 (5.0.7958.1401) with 1 site server, 1 db server, and 1 distribution point. I have a task sequence to push out an image via multicast but on the client computer I keep getting error number 80070002. The DP is set to enable multicast, all the contact within the task sequence is located on the DP and all packages are set to "allow this package to be transferred via multicast." I read a few places that turning off multicast support on the DP for an hour then turning it back on would correct the issue. This is a copy of the log file after doing so. Notice the Error finding namespace entry in the log. Any help and suggestions would be greatly appreciated. Thank you. Josh Multicast error file: Setting WDS IpAddressSource McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:51 PM 5088 (0x13E0) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:52 PM 5088 (0x13E0) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Succesfully Configured WDS McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Error finding namespace McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Checking MCS Certificate McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) MCSEncryptionCert Created. Length 980. McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:38:53 PM 5088 (0x13E0) Setting WDS IpAddressSource McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:55 PM 2468 (0x09A4) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:56 PM 2468 (0x09A4) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:38:57 PM 2468 (0x09A4) Succesfully Configured WDS McsExec 11/21/2014 1:38:57 PM 2468 (0x09A4) Setting WDS IpAddressSource McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Running: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:36 PM 4924 (0x133C) Run completed for: WDSUTIL.exe /Set-TransportServer /ObtainIPv4From:Range /Start:239.0.0.1 /End:239.0.0.254 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Running: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Waiting for completion of: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:37 PM 4924 (0x133C) Run completed for: WDSUTIL.exe /Set-TransportServer /StartPort:64001 /EndPort:65000 McsExec 11/21/2014 1:43:38 PM 4924 (0x133C) Succesfully Configured WDS McsExec 11/21/2014 1:43:38 PM 4924 (0x133C) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:43:53 PM 4244 (0x1094) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:43:53 PM 4244 (0x1094) Error finding namespace McsExec 11/21/2014 1:48:53 PM 3328 (0x0D00) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:48:53 PM 312 (0x0138) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:48:53 PM 312 (0x0138) ========== HashAndSignBuffer McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession McsExec 11/21/2014 1:52:19 PM 312 (0x0138) Error finding namespace McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession -- exit code: 0xc1100113 McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== HashAndSignBuffer McsExec 11/21/2014 1:52:19 PM 312 (0x0138) ========== OpenSession McsExec 11/21/2014 1:52:20 PM 312 (0x0138) Error finding namespace McsExec 11/21/2014 1:52:20 PM 312 (0x0138) ========== OpenSession -- exit code: 0xc1100113 McsExec 11/21/2014 1:52:20 PM 312 (0x0138) ========== HealthCheck ffffffff-ffff-ffff-ffff-ffffffffffff McsExec 11/21/2014 1:53:53 PM 312 (0x0138) Error finding namespace: 0xc1100113 McsExec 11/21/2014 1:53:53 PM 312 (0x0138)

Anyone got any ideas here? WAIK and ADK is reinstalled. And also - why does it look like it's trying to fetch image properties from a drive that doesn't exist? I've googled my ass off for two days in a row now, I'm about to give up and start all over again Error: Boot image to update: • Microsoft Windows PE (x64) Error: Actions to perform: • Add ConfigMgr binaries • Add custom background • Set scratch space • Enable Windows PE command line support Optional components: • Scripting (WinPE-Scripting) • Startup (WinPE-SecureStartup) • Network (WinPE-WDS-Tools) • Scripting (WinPE-WMI) Error: The wizard detected the following problems when updating the boot image. • The SMS Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { • Description = "Failed to insert OSD binaries into the WIM file"; • ErrorCode = 2152205056; • File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; • Line = 4630; • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; • Operation = "ExecMethod"; • ParameterInfo = "SMS_BootImagePackage.PackageID=\"A0100013\""; • ProviderName = "WinMgmt"; • StatusCode = 2147749889; }; And! When I'm trying to create a new MDT Boot Image, I get this error: Started processing. Creating boot image. Copying WIM file. Mounting WIM file. WIM file mounted. Setting Windows PE system root. Set Windows PE system root. Set Windows PE scratch space. Adding standard components. Adding component: winpe-mdac Adding extra content from: C:\Users\STIMYH~1\AppData\Local\Temp\2\0f51stur.hkc Unmounting WIM. Copying WIM to the package source directory. Creating boot image package. Error while importing Microsoft Deployment Toolkit Task Sequence. Failed to read image property from the source WIM file due to error 80070002 Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.Put(PutOptions options) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) --- End of inner exception stack trace --- at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put() SMSPROV.LOG: *~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3634) : Failed to read image property from the source WIM file due to error 80070002~*~* SMS Provider 03.12.2013 17:01:07 4112 (0x1010) *~*~Failed to read image property from the source WIM file due to error 80070002 ~*~* SMS Provider 03.12.2013 17:01:07 4112 (0x1010)

First and foremost thanks for the great site. Honestly couldn't have gotten started with SCCM without the site. With that said, I was able to get everything up and working fine for SCCM 2012 using the articles and forums. I decided to upgrade to SP1 to check out some of the new features and I have regretted it since. Basically I can't deploy via PXE since the upgrade. I always get the 80070002 error. I'm pretty sure it is a permissions issue but I'm baffled that an upgrade to SP1 would so drastically change permissions. I've looked far and wide for a solution and have gone as far as to set my domain admin account as the Network Access Account to see if that solved the issue. I'm able to do an install from media but it has to be a full media install. It would be great if this were something simple that I have overlooked. I have attached the latest smsts.log file. Any help or insight into what the problem is would be great. smsts.log