Error 2702 SMS_INVENTORY_DATA_LOADER warning message problem?

Help, My Sms Server is Getting a SMS_inventory_data_loader error and is
displayed as critical. The Message ID is 2702. Does anyone have any idea on
how to get rid of these messages.
My SMS Site Status under components is showing critical with a Red
Circle with a White X in the middle. On the otherhand My Server's "Site
System Status" check out completely 100%. It seems to be a problem with a
component of Sms
I Extracted this message out of the SMS Status Message View so everyone
can have a good look at the suspected problem. Oh furturemore, I have
multiple instances of the same message ID but each message is showing for
exampe a different "X13a232m1.MIF" file the file names are slitly different
but the extensions are always the same .
Secondly when I try to connect to the smsreporting website it says
"Access Denied but with no 400 client or 500 server Http errors. My webmaster
says its a SMS problem? But I am new to SMS this is a little over my head.
Its not a problem with IIS i checked it out completely. Permission, Logon
authentication accounts, permissions local security settings the works. So
the most I can figure one of my SMS components is causing a problem with the
smsreporting webinterface. So are these problems related? Thanks for any help
you can offer. Any assitance is and would be greatly appreciated.

Rob


-------------------------------------------------------------------------------------------
SMS Inventory Data Loader failed to process the delta MIF file
"Xnfwuk8by.MIF" because the file does not have a corresponding discovery
record. SMS Inventory Data Loader has moved this file to the Orphans
directory as file "D:\SMS\inboxes\auth\dataldr.box\ORPHANS\ni7kcgav. MIF" and
will retry processing it within 10 minutes.

Possible cause: The delta MIF file came from an SMS 1.2 site, and these
sites do not have discovery agents.
Solution: Verify that the delta MIF file is from a 1.2 site. If so, do
nothing.

Possible cause: Discovery Data Manager is not running.
Solution: Stop and restart Discovery Data Manager. You can use SMS Service
Manager, which is invoked from the SMS Administrator console, to stop and
start components.
-------------------------------------------------------------------------------

Since you are new to SMS, may I offer a great resource?
http://www.myitforum.com/forums/forumid_130/tt.htm

That is specifically the SMS2003 forum. There are articles/blogs, etc. on
myitforum as well. But I learned SMS from people on the myitforum web site.

The two issues you mention: reporting not working and mif files error in
status messages are unrelated.

Regarding SMS reporting, my first guess (just a guess right now) is that you
need to look at the members of the local group on your SMS server called "SMS
Reporting". Try adding "Domain Users" to that group. If that isn't enough
to fix the issue, check in your console, there is a +Security node. In there
is where you identify who can read, delete, modify reports. If it doesn't
exist, the easiest thing is to add <your domain name>\Domain Users with Read
to reporting. Last, (and actually, I think this is probably going to be the
fix), with certain Operating System Service Packs, and even some hotfixes,
Dcom Permissions to the SMS Reporting Point are changed. You, the
administrator, need to go into the server and run dcomcnfg to change them
back to a permission level which allows reporting to work. Check out this
tech faq location, the bottom area under Server 2003 Sp1 tips (don't worry if
you're on SP2 now, it's the same dcomcnfg fix):
http://technet.microsoft.com/en-us/l.../cc998654.aspx

2) the bad MIFs errors you are getting. This is one of those "it depends"
answers. (Don't you just hate those!) Every site will get some bad
inventory MIFs. The file can get corrupt occasionally and be "malformed", so
the server just rejects it. What usually happens is the server sends a
"resync" request to that client, and the client just redoes their inventory,
and they go on their merry way. But if it's the same client over and over
again, you might need to research that individual client (you'd have to open
up the MIF and somehow keep track of that. Personally, don't do that. Use a
"GPO Computer Startup Script" instead. More about that later. If *every*
client in your SMS site is sending up a bad mif, then we'll need to look
deeper too, but at the server stuff, not client stuff.

GPO Computer Startup Script: check myitforum.com. Basically, it's a gpo
script (which you edit for your environment) to encourage your clients to get
(and remain) healthy SMS clients.

"Robert Orr" wrote:

> Help, My Sms Server is Getting a SMS_inventory_data_loader error and is
> displayed as critical. The Message ID is 2702. Does anyone have any idea on
> how to get rid of these messages.
> My SMS Site Status under components is showing critical with a Red
> Circle with a White X in the middle. On the otherhand My Server's "Site
> System Status" check out completely 100%. It seems to be a problem with a
> component of Sms
> I Extracted this message out of the SMS Status Message View so everyone
> can have a good look at the suspected problem. Oh furturemore, I have
> multiple instances of the same message ID but each message is showing for
> exampe a different "X13a232m1.MIF" file the file names are slitly different
> but the extensions are always the same .
> Secondly when I try to connect to the smsreporting website it says
> "Access Denied but with no 400 client or 500 server Http errors. My webmaster
> says its a SMS problem? But I am new to SMS this is a little over my head.
> Its not a problem with IIS i checked it out completely. Permission, Logon
> authentication accounts, permissions local security settings the works. So
> the most I can figure one of my SMS components is causing a problem with the
> smsreporting webinterface. So are these problems related? Thanks for any help
> you can offer. Any assitance is and would be greatly appreciated.
>
> Rob
>
>
> -------------------------------------------------------------------------------------------
> SMS Inventory Data Loader failed to process the delta MIF file
> "Xnfwuk8by.MIF" because the file does not have a corresponding discovery
> record. SMS Inventory Data Loader has moved this file to the Orphans
> directory as file "D:\SMS\inboxes\auth\dataldr.box\ORPHANS\ni7kcgav. MIF" and
> will retry processing it within 10 minutes.
>
> Possible cause: The delta MIF file came from an SMS 1.2 site, and these
> sites do not have discovery agents.
> Solution: Verify that the delta MIF file is from a 1.2 site. If so, do
> nothing.
>
> Possible cause: Discovery Data Manager is not running.
> Solution: Stop and restart Discovery Data Manager. You can use SMS Service
> Manager, which is invoked from the SMS Administrator console, to stop and
> start components.
> -------------------------------------------------------------------------------