Mpsetup.log: Setup was unable to create ccm_incoming
Recently had an issue where a brand new environment failed to successfully install the management point.
I figured this had something to do with the new Windows Server 2008 R2 x64 I was installing on.
My mpsetup.log showed the following erors, time after time, after time.
Mp.msi exited with return code: 1603
Backing up mpmsi.log to mpmsi.log.lasterror
Fatal MSI error – mp.msi could not be installed.
The Mpmsi.log had the following relevant error messages:
Product: SMS Management point – Error 25006: Setup was unable to create the internet virtual directory CCM_Incoming
The error code is 80070005.
Now, 80070005 is an access denied error, but the MP was running on the local site server, so I wasn't sure what could provoke an access is denied error.
Tried the usual fixes for the can't create ccm_incoming error, with removing the mp, removing IIS, rebooting, reinstall IIS, all to no avail.
After some searching the culprit turned out to be a GPO that modified the scheduled task folder.
The company I installed Sccm 2007 R3 at, had a gpo that modified the permissions on the tasks folder inside the Windows folder.
As a result of this policy LocalSystem no longer had administrative rights on this folder.
Now, when an MP installs it tries to create a scheduled task Called Bits_ccm_imcoming_someguid to cleanup old unhandled Bits jobs.
This is where my install failed, as without the permissions, localsystem could not create the scheduled task.
Error logging could be a bit more clear for this, but if you have the above error, make sure you don't have something in place that prevents the creation of scheduled tasks.
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
del.icio.us Tags: SCCM,ConfigMgr,Wmi Eventing
Technorati Tags: SCCM,ConfigMgr,Wmi Eventing