![]() The most common issue we see with SP2 upgrades is a failed to compile. Section 3 List of Known Issues and Solutions It may be worth noting that 0x80041001 = generic failure, so this is not helpful other than to let you know that you have not resolved your issue as of yet since you are not able to manually compile this file. All rights reserved.Īn error occurred while processing item X defined on lines X - X in file smsrprt.mof: Microsoft (R) 32-bit MOF Compiler Version. If you try to manually compile the SMSrprt.mof and it fails you usually get the following error: it is likely that you will not be able to complete setup successfully until you can compile smsrprt.mof (or whatever mof file is failing to compile) manually successfully ![]() Run a Filemon.Īs stated above, the files to compile during setup should be able to compile outside of setup. tmp files to various locations during compile. Verify permissions on the extnprov.dll file.Check Security Rights in the SMS Admin console for the user that is executing the mofcomp command against smsrprt.mof.Take a SQL Profiler (yes, because we are going through the Provider we do look in SQL.Verify that DCOM and Windows Management Instrumentation (WMI) is enabled.Relevant log files: C:\ConfigMgrSetup.log, %ConfigMgrInstallDir%\Logs\Smsprov.log and SMSProv.lo_, %Windir%\System32\Wbem\Mofcomp.log.Things to look at (not necessarily in this order): mof file that setup was failing on, it may be safe to assume that SCCM SP2 setup can again be run and may pass this stage. Once you have implemented a solution and can manually compile the. In most (not all) cases you will getĪn error doing this as well. First off you should not have to keep going through SP2 setup after testing solutions. There are several things to consider in the scenario of. This document primarily focuses on issues of this type. It takes setup about 10-15 minutes to get to this step. Most problems we have seen thus far have been after file copy, around step 4 registering the SMS provider, and compiling. How to Test the Site Database Upgrade Process: Testdbupgrade can help you insure you are ok to upgrade however you cannot upgrade a database after you have run testdbupgrade against it. On a copy(!) of the site database command to insure your database can be upgraded without error. Always utilize the testdbupgrade setup switch SCCM RTM, SP1, SMS 2003, etc, to begin troubleshooting.Īlways insure you have a complete current and full SMS or Configuration Manager backup (performed when SMS services are disabled, all directories, SQL DB, registry settings, etc.) before upgrading your product. In some case setup may rollback successfully and in others you *may* be able to reinitiate upgrade over the top of a failed installation however in others you may have to fully restore to your previous state The bin\I386 directory of your SCCM installation. Admin Console will not launch and connect) this is because the upgraded files have already been copied to It is important to note that some of the problems outlined below can leave your Configuration Manager or SMS installation in an unusable state (i.e. ![]() Site System does not have rights to remote SQL System or Clustered SQL Nodes Checking for pre-existing duplicate reports that are new to SCCM SP2 Searching for a "bad" custom or customized reportį. Deleting Temp Files, setting Temp variables.Į. Section 3 List of Known Issues and Solutions:ī: Time Skew between remote SQL and Site ServerĬ: Re-Registering relevant files / errors attempting to re-register needed files.ĭ. mof file compilations, SQL SPNS, provider DLLs, etc. Pack or Configuration Manager versions that rely on. This document is not entirely specific to Service Pack 2 and can apply to Service Pack 1 installs, upgrades from SMS 2003 to SCCM, and future service This document was created to help in troubleshooting Configuration Manager Service Pack 2 (SP2) install failures. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |