Dell OMCI Mof - Issue adding to SMS_def.mof

Hi All, 
I am trying to add the Dell OMCI version 8.0.1 mof to my clients current SMS_Def.mof.  I have done this at previous clients without issues.  


When I append SMS_Def.mof I get the following error in in dataldr.log
 
MofCompiler failed:
error occurred while storing the data  
(80041002); ObjectNum=119, FirstLine=5776, LastLine=5785 BAD MOF backed up to C:\Program Files\Microsoft Configuration Manager\data\hinvarchive\sms_def.mof.bad.bak
MOF restored from C:\Program Files\Microsoft Configuration Manager\data\hinvarchive\sms_def.mof.bak
STATMSG: ID=2721 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_INVENTORY_DATA_LOADER" SYS=AU-BNE-SVR-CM01 SITE=S01 PID=2556 TID=3532 GMTDATE=Wed Feb 15 00:05:07.466 2012 ISTR0="C:\Program Files\Microsoft Configuration Manager\inboxes\clifiles.src\hinv\sms_def.mof" ISTR1="C:\Program Files\Microsoft Configuration Manager\data\hinvarchive\sms_def.mof.bad.bak" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
End of cimv2\sms-to-policy conversion; returning 0x80004005
Failed to convert MOF class/properties to policy; a retry will be attempted later...
 
[font="%value"]This is the lines of the MOF that are mentioned in the error message  
[font="%value"]

//===================================================================// Define Dell classes for inventory reporting//===================================================================

[ SMS_Report(FALSE), SMS_Group_Name("Dell Indication Conf"), SMS_Class_ID("DELL|INDICATIONCONFIGURATION|1.0"), SMS_Namespace(FALSE), Namespace("\\\\\\\\.\\\\root\\\\DellOMCI") ]class Dell_IndicationConfiguration : SMS_Class_Template
{
[SMS_Report (FALSE)] string Caption;
[SMS_Report (FALSE)] string Description;
[SMS_Report (FALSE)] boolean LocalOnly;
[SMS_Report (FALSE), Key] string Name;
[SMS_Report (FALSE)] boolean PollEnabled;
[SMS_Report (FALSE)] uint32 PollingInterval;
[SMS_Report (FALSE)] uint32 StartDelay;
};
 
I have searched this as much as I can and will continue to work on it, but if anyone could offer any assistance it would be much appreciated. 

havent got a answer but intrested to see any answers as im just upgrading from OMCI 7.6 to 8.0.1 & will have to update the SMS_DEF.mof.
 
have you posted this same question on the dell System managment forum?. The dell guys there maywell be able to assist.

this part:  [ SMS_Report(FALSE), SMS_Group_Name("Dell Indication Conf"), SMS_Class_ID("DELL|INDICATIONCONFIGURATION|1.0"), SMS_Namespace(FALSE), Namespace("\\\\\\\\.\\\\root\\\\DellOMCI") ]class Dell_IndicationConfiguration : SMS_Class_Template
 
Is it really formatted like that? with no line break between that closing ] and class Dell_...?
 
try this:
 
[ SMS_Report(FALSE),
  SMS_Group_Name("Dell Indication Conf"),
  SMS_Class_ID("DELL|INDICATIONCONFIGURATION|1.0"),
  SMS_Namespace(FALSE),
  Namespace("\\\\\\\\.\\\\root\\\\DellOMCI") ]

class Dell_IndicationConfiguration : SMS_Class_Template

{
[SMS_Report (FALSE)] string Caption;
[SMS_Report (FALSE)] string Description;
[SMS_Report (FALSE)] boolean LocalOnly;
[SMS_Report (FALSE), Key] string Name;
[SMS_Report (FALSE)] boolean PollEnabled;
[SMS_Report (FALSE)] uint32 PollingInterval;
[SMS_Report (FALSE)] uint32 StartDelay;
};

I have a feeling the issue the class being on the wrong line, was my fault. I was trying to make it easier to read in the post. 
I tried your example anyway and still get an error for line 5781 which is 
 
class Dell_IndicationConfiguration : SMS_Class_Template 
 
When I compile the mof on my machine it compiles without issue, that said it does already has the OMCI package installed so the WMI classes "root\DELLOMCI" are already there.   Not sure if this has anything to do with it, but thought I would try and provide as information as I can.
 
Thanks
Marty
 

all I can think of to ask is... in  your existing sms_def.mof, do you already have a dell_indicationconfiguration somewhere in there?

I really wish I could say yes.  However the answer is no.
The WMI on the SCCM server shows a class of DCIM which from what I understand is the version 8 class. 
If I add this to the configuration.mof will I be able to report on it? i.e see information in resource explorer.

That's a reporting class, for sms_def.mof.  not for configuration.mof.  configuration.mof won't take it.

That's what I thought. 
It is strange as other places I have worked at which had Dell hardware, it was just a matter of appending the MOF provided by Dell to the end of the SMS_def.mof file and everything was grand. 
The lastest addition that I made to this MOF file was for the MDT Tattoo settings. This compiled without issue but that was registry and not WMI. This makes me wonder if WMI corruption on the ConfigMgr server might be causing the issue.
 
I will start to looking into this as I am rapidly running out of any other idea's.
 
Any other idea/thoughts/suggestions would be very much appreicated
 

After running WMIdiag on the ConfigMgr server, I get the following errors.
 
extract from the WMIdiag log 
77175 12:57:45 (0) **          i.e. 'WMIDiag ShowMOFErrors'
77176 12:57:45 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
77177 12:57:45 (0) **          ALL fixes previously mentioned.77178 12:57:45 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
77179 12:57:45 (0) ** 77180 12:57:45 (0) ** 
77181 12:57:45 (0) ** 1 error(s) 0x80041011 - (WBEM_E_PROVIDER_NOT_FOUND) Provider referenced in the schema does not have a corresponding registration
77182 12:57:45 (0) ** => This error is typically due to the following major reasons:
77183 12:57:45 (0) **    - The application queried by the WMI provider is not installed, not available or not running77184 12:57:45 (0) **      at the time of the request was made. This error can also be generated because 
77185 12:57:45 (0) **      the application supporting the providers has been uninstalled.
77186 12:57:45 (0) **    - Some WMI providers (i.e. RSOP Planning Mode, Exchange 2003) are implemented as a WMI service.
77187 12:57:45 (0) **      Make sure the required services are successfully started.
77188 12:57:45 (0) **    - The WMI provider binary files are not accessible (i.e. access denied ACL).
77189 12:57:45 (0) **    - A WMI provider registration problem at the CIM level (MOFCOMP.EXE) or at the COM level (REGSVR32.EXE)
.77190 12:57:45 (0) **      You must re-register the WMI provider by recompiling its associated MOF file with MOFCOMP.EXE
77191 12:57:45 (0) **    Note: - If the WMI provider DLL CIM and COM registrations are correct, this error can77192 12:57:45 (0) **            be returned because the provider has a dependency on another DLL that cannot be77193 12:57:45 (0) **            loaded (missing or bad DLL)
 
So my next problem is how to fix it.  I am not sure what effect rebuilding the WMI repository would have on Config Mgr. 
Does anyone know what effect running winmgmt.exe /salvagerepository would have?

<wince> running anything wmi-fix-related on a Server is scary.  and very scary on a ConfigMgr site server, since so many things regarding CM are related to wmi.
If I were you, I'd start by going over to the Dell forums, and see if they are aware of anything specific to the omci edits.
Otherwise, I'd open up a call to Microsoft.

Thankyou, your wince made me feel a lot better.  At least I know I am not alone in thinking this isn't going to end nice. 
 
I will see what Dell and M'S have to say fingers crossed.  
 
You don't happen to be doing a topic on rebuilding WMI on your Config Mgr Server at MMS this year? 
 
 

"You don't happen to be doing a topic on rebuilding WMI on your Config Mgr Server at MMS this year?"
 
I could, but it would be a very short session.  "Don't"
end of presentation, any questions?
lol

Oh well,
I will track you down anyway to say hello.

Just thought I would post an update of what the outcome of this issue was.
 
The last addition to SMS_Def.mof that I added was the MDT 2010 tattoo entries to be able to record build information.   These entries added without issues, and have been working fine. 

However for whatever reason, (I presume that only Dr Who, or a Jedi knight might know) they didn't seem to work with the Dell OMCI mof or to more specific they don't like being before the OMCI entries in SMS_def.Mof.  I have had these working together in the past, I can only presume that I added the MDT entries after OMCI

So I removed the MDT tattoo information, add the OMCI entries, watched the dataldr.log and waited to see the magical 0x0 which had been alluding me for some time. Thankfully I wasn't disappointed. 
I then added the MDT Tattoo information back into the SMS_def.mof and then also got 0x0.
 
I hope this helps someone in the future.
 
 
 
 

Wow, that's nutty.  Never heard of that before.  If you don't mind, would you send your mof files to mofmaster a t myitforum.com  ?  Now I'm curious.