Setup was unable to create unknown machines - R2 installation
I have successfully backed up an SCCM 2007 SP2 configuration, set up a Windows 2008 x64 R2 server, restored the SCCM 2007 SP2 configuration on that server in the C:\Program Files\Microsoft Configuration Manager directory, which was required. I am now attempting to install the R2 feature pack, which fails with the message:Setup was unable to create unknown machines. 0x80070003I am not finding anything helpful in my searches. Anyone seen this before?SnoBoy
February 1st, 2010 5:42pm
I would guess this has something to do with security. Does the computeraccount of the new server have the neccessary rights on the sql server?Btw, did you run a site reset after the restore?
February 1st, 2010 6:11pm
0x80070003 = The specified path couldn't be found. There's a logfile for the R2 installation (in %windir%\temp or %temp% IIRC. I can't remember its name). It might contain more information.
February 1st, 2010 6:25pm
I worked with a MS tech support to get everything setup. I doubt it is a security issue, but may be proven wrong. The Computer account for the SQL server is a local admin on the SCCM server and the Computer account for the SCCM server is also a local Admin for the SQL server. All of the collections, including special ones I created are there. The MS tech verified proper operation last Friday, but did not do a site reset.SnoBoy
February 1st, 2010 6:34pm
I am wondering if it is trying to find the SCCM installation in Program FIles (x86) rather than the Program Files directory, which it had to be installed in to restore from the old x86 server it was backed up on. There wasn't an opportunity to specify the path to install to. Is there a way around this to force the installion to where it is really installed?SnoBoy
February 1st, 2010 6:37pm
0x80070003 = The specified path couldn't be found. There's a logfile for the R2 installation (in %windir%\temp or %temp% IIRC. I can't remember its name). It might contain more information. What about the logfile I mentioned earlier? The path were ConfigMgr was installed to before has to be exactly the same in a recovery scenario.
February 1st, 2010 6:45pm
There were no log files in the two directories for R2. I just found it in the Users directory for the account I am logged in as:C:\Users\username\AppData\Local\Temp\2\ConfigMgr2007R2.log (perhaps this will help someone find it in the future!)This leads me to believe it is trying to create them in the x86 program files instead of where it is really installed (emphasis mine):MSI (s) (38:C8) [08:25:33:953]: Executing op: ActionStart(Name=CreateUnknownMachinesCA,Description=Creating unknown machines...,)Action 8:25:33: CreateUnknownMachinesCA. Creating unknown machines...MSI (s) (38:C8) [08:25:33:955]: Executing op: CustomActionSchedule(Action=CreateUnknownMachinesCA,ActionType=3073,Source=BinaryData,Target=CreateUnknownMachinesCA,CustomActionData=SITECODE=SC1;TARGETDIR=C:\Program Files (x86)\Microsoft Configuration Manager\;UNKNOWNMACHINEX64=x64 Unknown Computer;UNKNOWNMACHINEX86=x86 Unknown Computer;)MSI (s) (38:48) [08:25:33:958]: Invoking remote custom action. DLL: C:\Windows\Installer\MSID8F9.tmp, Entrypoint: CreateUnknownMachinesCA[8:25:33] Entered CreateUnknownMachinesCA...[8:25:33] Entered SendDDRToSMS()[8:25:33] ERROR: Error code 25021 reported, hr = 0x80070003Error 25021. Setup was unable to create unknown machines. 0x80070003MSI (s) (38:FC) [08:30:18:488]: Running as a service.MSI (s) (38!88) [08:38:49:855]: Product: Microsoft System Center Configuration Manager 2007 R2 -- Error 25021. Setup was unable to create unknown machines. 0x80070003MSI (s) (38!88) [08:38:49:857]: Closing MSIHANDLE (40) of type 790531 for thread 3976CustomAction CreateUnknownMachinesCA returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)MSI (s) (38:48) [08:38:49:860]: Closing MSIHANDLE (36) of type 790536 for thread 968Since the MSI file allows no redirection of the installation path, this appears to be a bug to me. There needs to be a way to specify where it is to be installed! SnoBoy
February 1st, 2010 6:59pm
I got this from an MVP who contacted a MS contact:There is indeed a problem with installing R2 after doing the x86 to x64 upgrade. I just went through this process myself on my demo system. The ConfigMgr support organization gave me this workaround: 1) Manually create this folder structure:Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box(give folder same ACL's as is on existing installed directory) 2) Run R2 setup again. When install completes, copy the two DDR's from the C:\Program Files (x86)\Microsoft Configuration Manager\inboxes\auth\ddm.box and place them it into the “C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box” (where SCCM is actually installed): 3) Once the DDR's processed the R2 installation should succeed. SnoBoy
February 1st, 2010 11:34pm
@Bluess, it would be D:\SCCM\inboxes\auth\ddm.box\ Make sure it is a folder not a file, and double check to make sure it inherits the parent's permission.
July 14th, 2010 7:40pm
Thanks a lot.
February 23rd, 2011 1:01am
Hi, Having the same problem installing R3 (moving from old hardware to new hardware and os), so performed step 1 listed above and now i get a different but similar message: Setup was unable to create unknown machines. 0x8007010B for grins i tried installing R2 and had the same message. Any suggestions? Thanks, Matt
May 3rd, 2011 12:08pm