The operating system reported error
Question
I’m trying to add a Distribution Point on a new site server but I’m getting the error: 2147942405: Access is denied. in the component manager.
I have the site server’s computer account in the administrators group on the remote DP and I have restarted the server since doing so.
The problem is definitely not network / firewall related because if I choose to use my own crednetials to install the role it goes through OK (although this then causes other errors!)
Any ideas why I am getting access denied error?
Answers
Yes, I know this is an old post, but I’m trying to clean them up.
The error states “Recoverable error: This network connection does not exist” this would suggest that there is a network issue, when this log was created.
- Proposed as answer by Garth Jones MVP Wednesday, January 14, 2015 2:36 AM
- Marked as answer by Garth Jones MVP Saturday, January 24, 2015 3:41 PM
All replies
SMS Site Component Manager is configuring site system «\\CRWNBDP1» to receive SMS server components.
SMS Site Component Manager could not access site system «\\CRWNBDP1». The operating system reported error 2147942405: Access is denied.
Possible cause: The site system is turned off, not connected to the network, or not functioning properly.
Solution: Verify that the site system is turned on, connected to the network, and functioning properly.
Possible cause: SMS Site Component Manager does not have sufficient access rights to connect to the site system.
Solution: Verify that the Site Server’s computer$ account has administrator rights on the remote site system.
Possible cause: Network problems are preventing SMS Site Component Manager from connecting to the site system.
Solution: Investigate and correct any problems on your network.
Possible cause: You took the site system out of service and do not intend on using it as a site system any more.
Solution: Remove this site system from the list of site systems for this site. The list appears in the Site Systems node of the Administrator console.
SMS Site Component Manager failed to configure site system «\\CRWNBDP1» to receive SMS server components.
Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager cannot install any SMS server components on this site system until the site system is configured successfully. SMS Site Component Manager will automatically retry this operation in 60 minutes. To force SMS Site Component Manager to immediately retry this operation, stop and restart SMS Site Component Manager using the SMS Service Manager.
Could not read registry key «HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\MCS» on computer CRWNBDP1. The operating system reported error 5: Access is denied.
Could not read registry key «HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS» on computer CRWNBDP1. The operating system reported error 1: Incorrect function.
Could not read registry key «Software\Microsoft\SMS\Security» on computer CRWNBDP1. The operating system reported error 5: Access is denied.
The operating system reported error
HI. I have what it looked like a fairly simple requirement.
1> Create a folder during OSD TS execution
2> Copy some contents to that folder
For this purpose I have created a standard package without any programs.
For Step 1> I have tried following combination
%windir%\system32\cmd.exe /c md C:\Windows\SoftwareDistribution\SomeFolder <> Tried with quotes, with only cmd.exe /c etc
Start In — C:\windows\system32 <> tried keeping this field blank
For Step 2> %windir%\system32xcopy.exe «.\*.*» «C:\Windows\SoftwareDistribution\SomeFolder» /D /E /C /I /Q /H /R /Y /S
this has the folder selected that has contents.
Below is the error reported:
The task sequence execution engine failed executing the action (Create SomeFolder Folder) in the group (SomeFolder Installation) with the error code 2147942667
Action output: . ackageID = »
BaseVar = », ContinueOnError=»
ProgramName = ‘C:\WINDOWS\system32\cmd.exe /c md C:\Windows\SoftwareDistribution\SomeFolder’
SwdAction = ‘0001’
Command line for extension .exe is «%1» %*
Set command line: Run command line
Working dir ‘X:\WINDOWS’
Executing command line: Run command line
CreateProcess( NULL, (LPWSTR)m_sCommandLine.c_str(), NULL, NULL, TRUE, bNT ? CREATE_UNICODE_ENVIRONMENT : 0, m_pEnvironmentBlock, pszWorkingDir, &si, &pi ), HRESULT=8007010b (..\CommandLine.cpp,1010)clCommandLine.Execute( uOptions, pszWorkingDir, lpDesktop ), HRESULT=8007010b (runcommandline.cpp,565)
cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=8007010b (main.cpp,378)
CreateProcess failed. Code(0x8007010B)
Command line executionfailed (8007010B)
Failed to execute command line ‘C:\WINDOWS\system32\cmd.exe /c md C:\Windows\SoftwareDistribution\SomeFolder’ .
The directory name is invalid. (Error: 8007010B; Source: Windows)
Install Software failed to run command line, hr=0x8007010b. The operating system reported error 2147942667: The directory name is invalid.
I thought it is trying to execute in X:\windows there fore changed to environment variable %windir% to launch cmd.exe. Also I tried to restart the machine is Windows OS before these two steps. Also the Disable 64 bit redirection is checked.
I am running SCCM CB1802 with WinpE from ADK 10 and Windows 7 X64.
Please let me know what could be causing this seemingly simple step to fail.
The operating system reported error
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Asked by:
Question
we have a problem with our OSD.
Every TS with a «Apply Driver Package» step fails with following Error.
The task sequence execution engine failed executing the action (Setup Windows and Configuration Manager) in the group (Installation) with the error code 2147500037
Action output: . ed configuration information to C:\_SMSTaskSequence\unattend.xml
Successfully initialized driver information
Command line for extension .EXE is «%1» %*
Set command line: «C:\_SMSTaskSequence\Packages\KIZ0000E\SOURCES\SETUP.EXE» «/unattend:C:\_SMSTaskSequence\unattend.xml» /noreboot
Executing command line: «C:\_SMSTaskSequence\Packages\KIZ0000E\SOURCES\SETUP.EXE» «/unattend:C:\_SMSTaskSequence\unattend.xml» /noreboot
Process completed with exit code 31
Windows Setup completed with exit code 31
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\KIZ0000E
reference count 1 for the source C:\_SMSTaskSequence\Packages\KIZ0000E before releasing
Released the resolved source C:\_SMSTaskSequence\Packages\KIZ0000E
exitCode == 0, HRESULT=80004005(e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)
setup.run(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1668)
Exiting with code 0x80004005
Windows setup failed, code 31. The operating system reported error 2147500037: Unspecified error
I tried it with an empty «Driver Package» and a «Driver Package» which contains the right drivers.
But the error is the same.
The only solution is to remove the «Apply Driver Package» step. Then the TS runs without an error.
Does anyone have an idea where the problem is?
All replies
are you sure ? it looks like it’s failing at the Setup Windows and configmgr step from what you are posting above.
Windows setup failed, code 31. The operating system reported error 2147500037: Unspecified error
check your ccmsetup.log and client.msi.log, do you see any authenticode errors ? if so apply the authenticode hotfix to your configmgr server and try the deployment again
Step by Step Configuration Manager Guides > 2012 Guides | 2007 Guides | I’m on Twitter > ncbrady
The error appears before the client download part of the « Setup Windows and Configuration Manager» step begins.
The last thing what the TS does is finsihing the «Windows Setup»
After this i only see the _SMS. Folder and a old.windows folder at the c:\ drive.
Now i tried it with the Windows 8 x64 as OS install sources. And that works without an error.
Windows 7 x64 and Windows Vista x86 = error
Windows 8 x64 = no error
Maybe the problem are the new boot images?
I have the exactly same issue with my SCCM 2012 SP1 with MDT 2012 Update 1.
Everything was working perfectly before upgrading to SP1. Now I’m regretting that upgrade.
My Windows 7 x86 and x64 both fails at Setup Windows and ConfigMgr.
Successfully initialized driver information OSDSetupWindows 11.02.2013 13:20:18 1100 (0x044C)
Command line for extension .EXE is «%1» %* OSDSetupWindows 11.02.2013 13:20:18 1100 (0x044C)
Set command line: «C:\_SMSTaskSequence\Packages\GVA00034\SOURCES\SETUP.EXE» «/unattend:C:\_SMSTaskSequence\unattend.xml» /noreboot OSDSetupWindows 11.02.2013 13:20:18 1100 (0x044C)
Executing command line: «C:\_SMSTaskSequence\Packages\GVA00034\SOURCES\SETUP.EXE» «/unattend:C:\_SMSTaskSequence\unattend.xml» /noreboot OSDSetupWindows 11.02.2013 13:20:18 1100 (0x044C)
Process completed with exit code 31 OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
Windows Setup completed with exit code 31 OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\GVA00034 OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
reference count 1 for the source C:\_SMSTaskSequence\Packages\GVA00034 before releasing OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
Released the resolved source C:\_SMSTaskSequence\Packages\GVA00034 OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
exitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,440) OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
Windows setup failed, code 31 OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
setup.run(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1668) OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
Exiting with code 0x80004005 OSDSetupWindows 11.02.2013 13:25:06 1100 (0x044C)
Process completed with exit code 2147500037 TSManager 11.02.2013 13:25:06 360 (0x0168)
!———————————————————————————————! TSManager 11.02.2013 13:25:06 360 (0x0168)
Failed to run the action: Setup Windows and ConfigMgr.
Unspecified error (Error: 80004005; Source: Windows) TSManager 11.02.2013 13:25:06 360 (0x0168)
If I see the setupact.log, I have a critical driver error:
2013-02-11 13:24:47, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [C:\_SMSTaskSequence\drivers\11\bcbthid32.inf] into driver store. Error code is [0x80070032]
2013-02-11 13:24:47, Error [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [C:\_SMSTaskSequence\drivers\11\bcbthid32.inf]. Driver package is [Critical]. Error code is [0x32][gle=0x00000032]
2013-02-11 13:24:47, Error [0x0602ab] IBS CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x32][gle=0x00000032]
2013-02-11 13:24:47, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows installation cannot continue because a required driver could not be installed.]
2013-02-11 13:24:48, Info [SETUP.EXE] Called script [X:\windows\Setup\Scripts\ErrorHandler.cmd] to handle fatal error
It says that Bluetooth driver (bcbthid32.inf) installation is failing. I don’t understand how a bluetooth driver could be boot critical.
I was thinking as you that the new WinPE 4.0 boot image is the cause oh my issue. I’m really confused.
I just wanted to add that my SCCM 2012 SP1 sources were from after 25 January 2013.
I tested Windows 8 x64 deployment and it worked like a charm.
Windows 7 x86 and x64 are failing at «Setup Windows and Configmgr» at drivers install.
Now i tried it with the Windows 8 x64 as OS install sources. And that works without an error.
Windows 7 x64 and Windows Vista x86 = error
Windows 8 x64 = no error
Maybe the problem are the new boot images?
I would advice you to check ccmsetup.log and make sure, is the confmgr client healthy or not, but because your W8 image deployment works, I don´t think that´s it.
The best way to limit driver package related issue, is to deploy image on a clean virtual machine, set auto apply drivers to be enabled, but limit drivers with categories so it won´t get any drivers. If you could deploy the image this way, you could limit your problem to a driver packages only, and starting consentrate on a drivers themselves.
In my case, the TS doesn’t go to SCCM client installation, it fails before that. It’s not related to client installation (I’m using SCCM 2012 SP1 sources which includes KB2801987).
I understand your recommendation on deploying on clean VM and drivers but what I’m trying to understand is how SP1 application can impact drivers installation during OSD while it was working perfectly before SP1.
I understand your recommendation on deploying on clean VM and drivers but what I’m trying to understand is how SP1 application can impact drivers installation during OSD while it was working perfectly before SP1.
I know that WinPE 4.0 is Win8 based but how that change could impact drivers installation failing? Drivers on SCCM 2012 are for Windows 7 and I don’t thing I will need Win8 drivers just because I’m installing those drivers from a WinPE 4.0.
I’m gonna try to use a category to limit number of drivers.
ok i tested it with your way to deploy drivers. I created a new category with no drivers and used it in my TS.
And the TS run without an error!
Its not about the Step. Its about the driver’s / driver.
But i need some driver in my OS :\ I tested it with different drivers and it doesnt worked with any kind of driver!?
here is the end of the smsts.log
here a part of my setupact.log
2013-02-12 13:40:22, Warning [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ansmw60.inf]. Driver package is [Non Critical]. Error code is [0x32]
2013-02-12 13:40:22, Info [0x0602a4] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package path is [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ANSP2KXP.INF]
2013-02-12 13:40:22, Info [0x0602b2] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package is [NOT critical]
2013-02-12 13:40:22, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ANSP2KXP.INF]
2013-02-12 13:40:22, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x0]
2013-02-12 13:40:22, Info IBS AddDriverPackageIntoDriverStore:System root is [C:\Windows]
2013-02-12 13:40:22, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\]
2013-02-12 13:40:42, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ANSP2KXP.INF] into driver store. Error code is [0x80070032]
2013-02-12 13:40:42, Warning [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ANSP2KXP.INF]. Driver package is [Non Critical]. Error code is [0x32]
2013-02-12 13:40:42, Info [0x0602a4] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package path is [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\anspw60.inf]
2013-02-12 13:40:42, Info [0x0602b2] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package is [NOT critical]
2013-02-12 13:40:42, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\anspw60.inf]
2013-02-12 13:40:42, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x0]
2013-02-12 13:40:42, Info IBS AddDriverPackageIntoDriverStore:System root is [C:\Windows]
2013-02-12 13:40:42, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\]
2013-02-12 13:41:03, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\anspw60.inf] into driver store. Error code is [0x80070032]
2013-02-12 13:41:03, Warning [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\anspw60.inf]. Driver package is [Non Critical]. Error code is [0x32]
2013-02-12 13:41:03, Info [0x0602a4] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package path is [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ifcoemp.inf]
2013-02-12 13:41:03, Info [0x0602b2] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package is [critical]
2013-02-12 13:41:03, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ifcoemp.inf]
2013-02-12 13:41:03, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x0]
2013-02-12 13:41:03, Info IBS AddDriverPackageIntoDriverStore:System root is [C:\Windows]
2013-02-12 13:41:03, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\]
2013-02-12 13:41:23, Warning [0x0602b1] IBS AddDriverPackageIntoDriverStore:Failed to add the driver package [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ifcoemp.inf] into driver store. Error code is [0x80070032]
2013-02-12 13:41:23, Error [0x0602a9] IBS CallBack_AddDriverPackageIntoDriverStore:Failed to install the driver package [C:\_SMSTaskSequence\drivers\1\Install\DRIVERS\ifcoemp.inf]. Driver package is [Critical]. Error code is [0x32][gle=0x00000032]
2013-02-12 13:41:23, Error [0x0602ab] IBS CallBack_AddDriverPackageIntoDriverStore:An error occurred while installing the driver package [] offline GLE is [0x32][gle=0x00000032]
2013-02-12 13:41:23, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Die Windows-Installation kann nicht fortgesetzt werden, da ein erforderlicher Treiber nicht installiert werden konnte.]
2013-02-12 13:41:24, Info [SETUP.EXE] Called script [X:\WINDOWS\Setup\Scripts\ErrorHandler.cmd] to handle fatal error
2013-02-12 13:41:24, Info IBS Callback_Rollback_ExecuteOnlineRollback: Executing [C:\_SMSTaskSequence\Packages\KIZ000EE\SOURCES\rollback.exe /CleanInstallFromWinPE /noui /BTFolder:C:\$WINDOWS.
The same errors like Hammoudi.
What about dism.log?
Have you been pushing and updating the same driver package to DP? You probably should create a single driver package for this model and query its model with WMI.
I created a specific driver package for my model and applied it in my TS but still failed at driver installation. it’s driving me crazy.