BADMIFS problem. Please Help

[costas]

I keep getting this error message:

Severity Type Site code Date / Time System Component Message ID Description
Error Milestone 30/12/99 6:05:06 SMS_INVENTORY_DATA_LOADER 2703 SMS
Inventory Data Loader failed to process the delta MIF file "XTTTGDIIM.MIF"
and has moved it to "E:\SMS\inboxes\dataldr.box\BADMIFS\K1TGETLE.MIF".

Possible cause: The file is corrupt or contains bad syntax. Solution:
Review the immediately preceding status messages from this component for
more details. If you ignore this problem, SMS will probably fix it and
complete this operation later. If this error occurs repeatedly, refer to
your SMS documentation or the Microsoft Knowledge Base for further
troubleshooting information.

This is classed as a critical error. I've checked the Admin guide and MS
knowledge base with no luck. Any help would be great.

Regards

Con M

[Bob]

Use Mifchek.exe
"costas" <co...@homenetwork.com.au> wrote in message
news:94650914...@atlas.corp.au.home.com...

[Shriman Gurung]

I get this problem too, and looking at the files shows that they are
clearly corrupt. I can clean them up with notepad so that MIFCHECK
thinks they are lovely, but SMS still refuses to process them. I've
been putting the cleaned up versions back in the in the dataldr.box
directory to no avail.

shriman

Shriman Gurung
System Administrator
Data Connection Ltd.
http://www.datcon.co.uk/
--speaking for myself not my employer--

[Chris]

I am also experiencing this behavior - anyone know where can I find the
mifchek.exe program mentioned earlier? BORK?

Thanks!
Chris

"Shriman Gurung" <s...@datcon.co.uk> wrote in message
news:386e0da9...@news-direct.datcon.co.uk...

[Ed Aldrich]

This is usually caused when the mif (usually a delta mif) is collected from
client "x". When the data loader attempts to add the inventory to the
database, there is not a corresponding record for client "x" current in the
database (based on the GUID of the client "x" record). Since it cannot find
out where the data update should be applied, it ends up in the badmifs
folder... having a few of these is not a big deal, but if you have a fairly
high number as a percentage of your total client base, you may have a
problem. We had a REAL mess with this due to a lot of systems with duplicate
GUIDS (caused by a cloned system that had the SMS client installed when the
Ghost master was created... this was populated on 100+ new systems when we
discovered the problem! We are STILL trying to clean up the mess... This
problem will also typically show up in the SW Inventory Processor as well...
system cannot process SW inventory any better than HW inventory.

MIFCHECK is a BORK tool...

[CTI]

I am also seeing the same errors as posted by costas. There are about 110
WIN98 computers under collections and after browsing through the files in
the BADMIFS directory, I find that the files indicate about 30 problem
computers some of which have multiple MIF files. I have verified that the
computer names in the BADMIFS files are all listed in COLLECTIONS\98
SYSTEMS. I too have searched Microsoft Support page, looked in the online
help, and the SMS 2.0 training book. Any info on how to solve this problem
would be greatly appreciated.

Ed Aldrich <eald...@home.com> wrote in message
news:Z0fc4.468$jt3....@news1.wwck1.ri.home.com...

[Chris]

I used MIFCHECK and it tells me (on each file I use it on)

Error in file <file name.mif>
syntax error on line 1, token '<smiley face>'

That's all it says. Any clues?

Chris

[Kevan O'Leary]

Did any of you modify your smsdef.mof using mofman.exe from the resource
kit? Also are you running sp1?

CTI <jdo...@acsgroupinc.com> wrote in message
news:uxbEEX#V$GA....@cppssbbsa02.microsoft.com...

> I am also seeing the same errors as posted by costas. There are about 110
> WIN98 computers under collections and after browsing through the files in
> the BADMIFS directory, I find that the files indicate about 30 problem
> computers some of which have multiple MIF files. I have verified that the
> computer names in the BADMIFS files are all listed in COLLECTIONS\98
> SYSTEMS. I too have searched Microsoft Support page, looked in the online
> help, and the SMS 2.0 training book. Any info on how to solve this
problem
> would be greatly appreciated.
>
>

[Costas M]

On Thu, 6 Jan 2000 14:41:23 -0500, "Kevan O'Leary"
<kol...@fmarathon.com> wrote:

>Did any of you modify your smsdef.mof using mofman.exe from the resource
>kit? Also are you running sp1?
>

i am running SP1 but i'm still getting the errors. the smsdef.mof file
has not been altered.

Costas

[Costas M]

Theres a couple of things i did since i last posted:

1. i installed SP1 for SMS. There's a stack of bug fixes in this SP.

2. I noticed that a number of workstations on the network had the same
unique SMS ID. The SMS ID can be seen on the client in Control Panel
->Systems Management.

This is because we have been using ghost to image desktops and the
image we were using had the SMS client & Unique SMS ID on it.
Removing the SMS client does not remove the SMS ID. There is a Support
folder on the SMS CD. This has a program which installs support tools
onto your server. There is an explanation in the tools.htm file which
gives some guidelines on how to fix this problem using the tool
SMSIDDup.exe .

The Duplicate records in the SMS database have to be cleared and the
smscfg.ini has to be deleted on the client. The only thing is, i'm not
sure how to clear the duplicate records off the sms database. Can
anyone help?

Regards

Costas

On Thu, 30 Dec 1999 10:11:59 +1100, "costas" <co...@homenetwork.com.au>
wrote: