FIXME: IOUnserialize has detected a string that is not valid UTF-8, "�SMB012".

Something that REALLY annoys me is when users post the same message across multiple forums but here I am doing just that. Why? Because I can't find anyone anywhere that can offer any advice.

I've been getting the system.log message below, every 30 seconds for over two months!

configd[14]: FIXME: IOUnserialize has detected a string that is not valid UTF-8, "�SMB012".
Surely there must be someone out there who knows what this message means! The only thing I know is it's network related. I'm very careful what I install on my Mac and I'm not one for messing with the settings, so I don't understand how this problem occurred.

Are there any tools that I can use to monitor processes and data files that will me workout where this error steams from?

Many thanks,
M.

(p.s. Obviously any advice offered on AppleInsider I'll share with other forums)

If you open each of those in textedit, check to see if the string SMB012 is in the file. You won't be able to edit it if it is, but you can drag the file out, modify it and drag it back in and authenticate.

The plist files contain no reference to the SMB012 string and I've also tried restoring the files from Time Machine. I also used EasyFind to search for SMB012 across the entire disk but nothing was found.

I messed with the network settings and managed to get the message to change slightly when I removed the AirPort interface (...not valid UTF-8, "".) but the original message returned only I setup AirPort again.

I also used EasyFind to search for SMB012 across the entire disk but nothing was found.

EasyFind will only search file name. You'd need to use something like fgrep to search file contents e.g in the terminal type:

fgrep -iR "SMB012" /Library/Preferences

Quote:

Originally Posted by Mateus109

I messed with the network settings and managed to get the message to change slightly when I removed the AirPort interface (...not valid UTF-8, "".) but the original message returned only I setup AirPort again.

You can debug configd by running another copy. You type in the terminal:

sudo /usr/libexec/configd -dv

It will ask for you password. This should give you debugging info about each bundle as it loads and dump any messages that normally go into the syslog to the terminal window. You can load each bundle one at a time too e.g:

UPDATE:
I don't believe it... it's the battery! Just rebooted without the battery in and there are no messages at all. The battery must be faulty, sending bad signals to the Mac?

It might be the case that the power management bundle isn't loaded when the battery isn't in. Try running it without the battery and then load in the power management bundle manually into the terminal. If the messages still appear, it's likely to be the bundle itself or a settings file it uses.

It might be the case that the power management bundle isn't loaded when the battery isn't in. Try running it without the battery and then load in the power management bundle manually into the terminal. If the messages still appear, it's likely to be the bundle itself or a settings file it uses.

Presumably running the sudo /usr/libexec/configd -dv -t /System/Library/SystemConfiguration/PowerManagement.bundle would say if it didn't load when typed into the Terminal? So bundle seems to load and no messages appear in System.log

Presumably running the sudo /usr/libexec/configd -dv -t /System/Library/SystemConfiguration/PowerManagement.bundle would say if it didn't load when typed into the Terminal? So bundle seems to load and no messages appear in System.log

M.

Yeah, that would load the bundle in and run it although some code probably won't execute until a battery is present. Do you have the latest battery updates installed?

The powermanagement.bundle seems to determine a few power settings, where your hibernate file goes and some warnings if you are using a UPS. What is the exact size in bytes of the bundle in Get Info? Mine is 359,456 bytes on 10.6.3 and has version 160.0.0.

If you took it into an Apple Store, they might let you try a replacement battery in it or if you knew someone else who had the same model MBP. The only other option would be to disable the bundle but I'm not sure what side-effects that would have.