The set volume utility indirectly made these errors come up. Unity isn't going to crash or anything, but it is of concern. The CPU usage increasing after the utility is normal. That process is running at a lower priority than other Unity processes, so if it needs to give up some CPU time, it will.
Basically what's happening here is the SetVolume utility makes changes on the local Unity server and then starts off what we call a "SQL Sync". The SQL Sync pushes information out of the local SQL database into the directory.
What's going on is that there's a Unity property that's trying to be set in the directory that's not kosher. Attributes in the directory have an expected data type. For instance "name" would be of type "string". On the other hand, "useDefaults" would be of type "bool". Here Unity is trying to set an attribute with an incorrect data type (trying to set the value as a string when the directory is expecting a bool).
The problem is that from the error message, we can't tell exaclty what is trying to be set (in 4.0, you would). We'll need to set traces to figure out what's up.
Is the Unity server connected to E55 or E2K?
