Setup cannot compile mof

This hotfix only provides a partial fix for this MOF compilation issue. To completely resolve this issue, you must also apply hotfix For more information, click the following article number to view the article in the Microsoft Knowledge Base:. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:.

Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. We recommend that you consider applying the most recent fix release that contains this hotfix.

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server R2, click the following article number to view the article in the Microsoft Knowledge Base:. Was reinstalling a client on a distribution point that broke during an in-place upgrade from Server to , Config Manager version Encountered this same problem and this solution is what worked.

Like Like. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. This didn't work though. Do you want to continue? Setup failed to install SMS Provider. I spent 2 days trying to locate the answer.

It finally dawned on me. These are the symptoms of the problem that I had: 1. SMS Provider Failed installation failed 2. Similar to the above issue during the fourth step of SCCM setup you may see the following pop up error message:. Additionally, after you quit setup you are unable to manually mofcomp smsprov. The following error occurs:. The solution is to use Depends. Once placing the file there we were able to manually register SMSProv.

An alternate solution and better explanation for this behavior is as follows:. Configuration Manager does not support 8. In this instance, however, it was off by the time the setup was run and it does NOT check the logged on user for how their profile was created. Cannot insert duplicate key in object 'dbo. However in this customers case it was noted that the report itself had been somewhat modified. To resolve this issue we deleted this report after which, we were able to compile the smsrprt.

An alternate resolution may have been to simply modify the customized query in this report back to the SCCM SP1 defaults. It is not known why the report was not able to be upgraded as that troubleshooting path was not pursued.