Great. Like I said, a support case will be the fastest route to getting 
assistance.
If you could also file a bug on Connect with the logs, that will help us get 
moving on investigation for a future release to at least be able to better 
detect this sort of thing in the future. If/when you do, please share the 
feedback ID with me.

Can you also check the task scheduler service, make sure it’s running and 
healthy?

From: [email protected] [mailto:[email protected]] On 
Behalf Of Kevin Johnston
Sent: Wednesday, February 3, 2016 12:38 PM
To: '[email protected]' <[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

Thanks Aaron,

As my luck would have it we signed a new SA with Microsoft so we are having 
issues able to call in at the moment, or place a ticket.

I have moved the server into an OU that has no GPOs, also modified the 
permissions and still it fails.

To be quite honest, I don’t know what the permissions are supposed to be. In 
the log it does say the following:

[12:29:00] Port settings have not changed.
[12:29:00] SSL port settings have not changed.
[12:29:00] IIS7 is installed. Removing application 'ConfigMgr Management Point'.
[12:29:00] Successfully removed application 'ConfigMgr Management Point' with 
IIS7.
[12:29:00] Creating IIS Virtual Directory 'CCM_CLIENT'
[12:29:00] Method 'DeleteExtensionFileRecord' failed with 80020009
[12:29:00] Automation Exception invoking method "DeleteExtensionFileRecord"
[12:29:00] Automation Exception Source is "<null>"
[12:29:00] Automation Exception Description is "<null>"
[12:29:00] Automation Exception wCode is 0
[12:29:00] Automation Exception sCode is 0x800CC801
[12:29:00] IGNORE: Failed to delete extension 'c:\sms_ccm\ccmclientisapi.dll'. 
Return Code = 0x80020009 (The extension might not be registered)
[12:29:00] Successfully added extension 'c:\sms_ccm\ccmclientisapi.dll' to 
group 'CcmClientRedistDir'
[12:29:01] Successfully created virtual directory application
[12:29:01] IIS7 is installed. Removing module CGI-exe
[12:29:01] Created IIS virtual directory 'CCM_CLIENT'
[12:29:01] Creating IIS Virtual Directory 'CCM_Incoming'
[12:29:02] Successfully created virtual directory application
[12:29:02] Enabling BITS
[12:29:06] @@ERR:25006
MSI (s) (84!90) [12:29:06:046]: Product: ConfigMgr Management Point -- Error 
25006. Setup was unable to create the Internet virtual directory CCM_Incoming
The error code is 80070005
Error 25006. Setup was unable to create the Internet virtual directory 
CCM_Incoming
The error code is 80070005
CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603 
(note this may not be 100% accurate if translation happened inside sandbox)

KEVIN JOHNSTON

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Aaron Czechowski
Sent: Wednesday, February 03, 2016 10:07 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

Hi Kevin –
I checked with folks in engineering on this and wanted to share some thoughts:

•         This is the incoming virtual folder that is setup with IIS BITS 
server extensions for state/inventory uploads. This MSI setup code has not 
changed for several releases.

•         There are some similar instances of this from SCCM 2007 days, see 
http://myitforum.com/myitforumwp/2011/10/05/mpsetup-log-setup-was-unable-to-create-ccm_incoming/<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fmyitforum.com%2fmyitforumwp%2f2011%2f10%2f05%2fmpsetup-log-setup-was-unable-to-create-ccm_incoming%2f&data=01%7c01%7caaron.czechowski%40microsoft.com%7c82fe66acd888497d359e08d32cc10483%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=sH53dnySzXLDyB0vOgsvPj2NEKul7Rv4qwAbIZv10wc%3d>

•         Could there have been something external that monkeyed with 
permissions over time? GPO, another admin, etc.?

•         You could use Process Monitor to identify where the specific access 
denial is happening.

It might warrant a call to support to get help troubleshooting. Not something 
that we’ve seen, but perhaps support has seen other instances? You could file 
an item on Connect with the MP setup logs (especially MP MSI log) for us to 
investigate, but it won’t be immediate. If we were able to repro it would be 
something we would look at for a future release. Support would provide more 
immediate relief and/or be able to escalate for hotfix consideration if 
necessary.

Hope that helps

Aaron


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Kevin Johnston
Sent: Tuesday, February 2, 2016 2:38 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

No I do not have a no_sms_ file on C:

Something I am noticing is that on the CCM folder I only have SYSTEM, 
Administrators, and our SCCM Admin account with permissions.
When I go into the Incoming properties I have IUSR, SYSTEM,LOCAL SERVICE, 
Administrators, SCCMAdmin account

[cid:[email protected]]

KEVIN JOHNSTON
Intermediate Systems Administrator, Corp IT

HALOGEN SOFTWARE
Strategic Talent Management Made Easy
T +1 613-270-1011 Ext. 4450   F +1 613-270-8311
C +1 613-301-1597

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Andrew Craig
Sent: Tuesday, February 02, 2016 2:31 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

As it is installing to the root of C: I would check the ntfs permissions and uac
Try manually creating the folder structure and see if you get a uac prompt.
If they already exist on C: then it might throw access denied, again because of 
C:
Also, you don’t have a no_sms_on_drive file on c:? silly question I know

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Damien Solodow
Sent: 02 February 2016 20:24
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

IIS Manager on the Site Server would be my first stop. ☺

DAMIEN SOLODOW
Senior Systems Engineer
317.447.6033 (office)
317.447.6014 (fax)
HARRISON COLLEGE

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Kevin Johnston
Sent: Tuesday, February 2, 2016 2:21 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

Well this is an upgrade from 2012 R2 SP1 so the assumption is yes. I did not 
change anything.

Where would I go to confirm this?

KEVIN JOHNSTON
Intermediate Systems Administrator, Corp IT

HALOGEN SOFTWARE
Strategic Talent Management Made Easy
T +1 613-270-1011 Ext. 4450   F +1 613-270-8311
C +1 613-301-1597

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Damien Solodow
Sent: Tuesday, February 02, 2016 2:16 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

80070005 is access denied.
Does those virtual directories already exist?

DAMIEN SOLODOW
Senior Systems Engineer
317.447.6033 (office)
317.447.6014 (fax)
HARRISON COLLEGE

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Kevin Johnston
Sent: Tuesday, February 2, 2016 2:13 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

This is what it says:

MSI (s) (74!FC) [13:27:24:334]: Product: ConfigMgr Management Point -- Error 
25006. Setup was unable to create the Internet virtual directory CCM_Incoming
The error code is 80070005
Error 25006. Setup was unable to create the Internet virtual directory 
CCM_Incoming
The error code is 80070005
CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603 
(note this may not be 100% accurate if translation happened inside sandbox)



KEVIN JOHNSTON

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Qadri, Syed
Sent: Tuesday, February 02, 2016 2:09 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

Since this is a fetal error (1603).
Open the mpmsi.log and then search for the keyword “return value 3”. The line 
above this will tell you exactly why it is failing.

Syed.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Kevin Johnston
Sent: Wednesday, February 03, 2016 12:36 AM
To: '[email protected]'
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

No it is on my Primary SCCM server. I only have one MP.

Before I started digging, I was trying to upgrade a client, and the errors 
where saying that it couldn’t connect to the MP.
I then went to Monitoring – Site Status and noticed it said Critical.

I then found where it was giving me errors, which then after some googling lead 
me to the MP logs.

It currently still says Critical

The error :

MP Control Manager detected MPsetup has failed to create the CCM_Incoming 
Virtual Directory.

Then it gives some suggestions which everyone says to do the things I have 
done.. Now I also have issues with my SUP and Application Catalog web service 
point

Going from bad to worse..

KEVIN JOHNSTON
Intermediate Systems Administrator, Corp IT

HALOGEN SOFTWARE
Strategic Talent Management Made Easy
T +1 613-270-1011 Ext. 4450   F +1 613-270-8311
C +1 613-301-1597

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Andrew Craig
Sent: Tuesday, February 02, 2016 1:58 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Epic fail on upgrading to v1511 from 2012 R2 SP1

This MP is on a remote site server? How is the MP on the site server looking?

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Kevin Johnston
Sent: 02 February 2016 19:47
To: '[email protected]' 
<[email protected]<mailto:[email protected]>>
Subject: [mssms] Epic fail on upgrading to v1511 from 2012 R2 SP1

So I had everything in place and it looked like my upgrade was great until I 
say some errors then I started to dig a bit deeper…

So currently my biggest issues is the MP will not install. I mean it was 
already there, but I guess during the upgrade that failed.

So I went on a mad hunt to figure out the issue, and I read things from WMI to 
BITS to IIS.

So I removed the agent (did a PS script to remove from WMI)
I uninstalled BITS
Uninstalled IIS

Reinstalled IIS (web Services and BITS) and I still get the same issue in the 
mpmsi.log and MPSetup.log

MPMSI.log:
MSI (s) (A0:C4) [12:09:12:936]: Product: ConfigMgr Management Point -- 
Installation operation failed.
MSI (s) (A0:C4) [12:09:12:937]: Windows Installer installed the product. 
Product Name: ConfigMgr Management Point. Product Version: 5.00.8325.1000. 
Product Language: 1033. Manufacturer: Microsoft Corporation. Installation 
success or error status: 1603.

MPSetup.log:
<02/02/16 11:04:12> No versions of SMSMP are installed.  Installing new SMSMP.
<02/02/16 11:04:12> Enabling MSI logging.  mp.msi will log to 
C:\ConfigManager\logs\mpMSI.log
<02/02/16 11:04:12> Installing C:\ConfigManager\bin\x64\mp.msi 
CCMINSTALLDIR="C:\SMS_CCM" CCMSERVERDATAROOT="C:\ConfigManager" 
USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE 
SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 
CCMLOGMAXHISTORY=1
<02/02/16 11:04:46> mp.msi exited with return code: 1603
<02/02/16 11:04:46> Backing up C:\ConfigManager\logs\mpMSI.log to 
C:\ConfigManager\logs\mpMSI.log.LastError
<02/02/16 11:04:46> Fatal MSI Error - mp.msi could not be installed.
<02/02/16 11:04:46> ~RoleSetup().

I have no idea why this is not installing.


If I run the mp.msi I get the following error:

Internet information Services Web support is either not installed or is not 
configured correctly.

I know that seems like it tells me, but I can’t figure out which of it is not 
configured. This also was the case BEFORE I did any uninstalling and fixing.


KEVIN JOHNSTON




This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient, you are not authorized 
to read, print, retain, copy, disseminate, distribute, or use this message or 
any part thereof. If you receive this message in error, please notify the 
sender immediately and delete all copies of this message.










Reply via email to