I created an article of clothing for M3 using LW and after conforming my newly created object in Poser 7, I get an error which reads:

XML Error Parse

Error: mismatched tag at line 30

The figure still conforms nicely, however I wanted to know what this error meant and how I could fix it?

Thanks,

-J

Two possible causes :-

1. You have checking for updates on.
   If you just installed an SR, it may have reset that preference to on.
   Solution: turn update checking off.

2. You have used either an XML reserved character or something else in the name of a directory that is causing Poser to fail to parse LibraryPrefs.xml.
   Solution: check all linked Runtimes for bad characters in directory names and rename.

If you can't find the problem in case 2), either remove each Runtime until you find the problem one, or post a few lines either side of the one mentioned and I'll see if I can spot the problem.

I did recently re-install the SR1 for M3.  When you are referring to "updates on" do you mean in Posers "General Preferences" section under the "Misc" tab? ("Check for updates on launch"  this check box was checked).  If so, I need to uncheck this?

Interestingly to mention though was this, I was tinkering about with conforming my figure by doing it one of two ways, using 3D Dimension Tool Collection "ConCloth" routine and then later manually using Posers Setup Room.  During that time that error only came up when I tried loading the CR2 created with "ConCloth", not with the CR2 created with Posers Setup Room.

Also, I happened to install M4 base and it added an icon on my desktop which reads "Update Michael 4 base".  Not sure if that has any bearing on it. 

Quote - When you are referring to "updates on" do you mean in Posers "General Preferences" section under the "Misc" tab? ("Check for updates on launch"  this check box was checked).  If so, I need to uncheck this?

That's the setting I was referring to, and it should be unchecked.

I suspect that the cause of the problem is 2) as the line number in the error message is, IIRC, 2 for cause 1)

The other possibility is some of the Face room data installers can mess up another XML file.
This applies only to CL/EF/SM figures.
Other content will only cause problems if there are bad characters in directory names.

Did you try to see if one particular Runtime is responsible ?
Once we know which file Poser is having trouble with, we can attempt to work out why the problem is occuring.

Actually, I unchecked that box, shut down Poser, took my newly created OBJ file and re-conformed it using ConCloth.  I then opened Poser and attempted to conform my OBJ to M3.  It did so without an error messages (so far as once the error message popped up a few minutes after I conformed my OBJ to M3 on my other computer.  don't know if it did so because that computer is notoriously slow). 

It's been a few minutes since I did so and no error messages.  I think your first suggestion was the source of the problem particularly since I haven't added any new Runtimes in over a year and this problem just happened yesterday, coincidentally when I installed the M3 SR1 update and M4.

Thanks so much for your help nruddock, it's greatly appreciated.  :)

-J

A question came to mind from a vendor's perspective. Even though we seemed to have found the source of the problem, wouldn't this error message popping up cause this product I'm creating to fail during the 'Rosity testing stage since some people are apt to have that "update" function turned on and will more than likely receive that error message even though the conform works properly? 

If it's the update function that caused the problem then this won't happen to people testing your product. The update function connects to a server and then tries to parse the XML response of the server. The problem is that Poser didn't get a proper XML response from the server and it doesn't handle that case too well.
So other people may get the same error, but it's not related to your product. They may not even have any content beside the default Poser content installed and will get the error :-)

Thanks for the explanation Dizzi, I appreciate it. :)