Hi all,

While using poser 6 I was injecting a face pose to V3 when I got this error message:
"XML ERROR
Parse Error: junk after document element at line 2"

What the blazes is that? Has anyone else seen such an error? After I hit ok to clear the error warning off Poser seemed to be working fine. Anyone got a clue?

Thanks!

I got it too...  about an hour ago...  could not find anything wrong

Very strange. By chance tom271 are you running poser on a dual-core machine? I don't know if it has anything to do with it or not. When I had my old box I never got any errors at all. This has just started yesterday.

No I'm not running a dual core....   I suspect that it had to do with the sites webpage trying to re-load into Poser's Content room....

i had this today as well

This is indeed strange.

See if wither of these threads helps
http://www.renderosity.com/mod/forumpro/showthread.php?message_id=2767204&ebot_calc_page#top
http://www.renderosity.com/mod/forumpro/showthread.php?message_id=2665017&ebot_calc_page#top

You know what, I got the same thing today too!  Makes me wonder if e frontier did a "stealthy license check" or some crap and botched it, that is a pretty odd series of coincidences so close to Poser 7 release.

Quote - See if wither of these threads helps
http://www.renderosity.com/mod/forumpro/showthread.php?message_id=2767204&ebot_calc_page#top
http://www.renderosity.com/mod/forumpro/showthread.php?message_id=2665017&ebot_calc_page#top

Ahhh that cured all pains! Thanks!!

Oh yeah wanted to add that I found the problem. It seems to have been a freebie prop I downloaded.

poser worked fine after i pressed ok....and after rebootin i dint get the msg again

Quote - poser worked fine after i pressed ok....and after rebootin i dint get the msg again

That';s because it creates a fresh LibraryPrefs.xml that doesn't refer to any external Runtimes or have any default folders set.
If you don't fix the problem folder, you'll get the same trouble each time you exit with it selected.

okie kokie :D...i'll know what to do when it happens again then :)

XML- Extensible Markup Language..sort of an outgrowth/upgrade/etc of HTML. Web code, but used in other programs as well, such as Poser.

This also happened to me a couple of years ago (from a DAZ vendored product). Turned out that the product installed itself to a folder that started with a "$" sign. XML treats that as a special character (for what, I don't know).

After re-naming the offending folder all worked ok.. (Worked it out by tracking down the xml file that had last been changed, since Poser5 wouldn't even start) and yes, it was LibraryPrefs.xml ..)

I did inform Daz, but I don't know if anyone took any notice.

I suspect that some vendors try to get closer to the top of the list than "!!!!!!!!-LOOK AT ME"

Cheers,
Diolma

Okay let me get this straight. I went in and deleted the LibraryPrefs.xml, restarted poser, linked all my runtimes back again and still ever so often I get the error message. I'm at a loss as to know what to do next? How do I find this offending folder? Here is a screen shot:

Thanks!

I'd need to see the contents of your LibraryPrefs.xml just after you've had an error (it's near the top so the first few lines should be sufficient).
The problem is usually caused by XML special or other odd characters in directory names.

If you can work out which directory is causing the problem you can just rename it to remove the troublesome characters.
Until you fix the root cause you'll keep get this problem.

usually a directory with a '$' is classified as 'hidden' (at least in NT 4 and XP), so it wouldn't be smart to make an item for Poser that no one knew how to find..;)  but who says everyone is smart..;)

really weird, I got this message today too when starting up poser.  Sooo what do I do? I didnt install anything new since the last time I started poser.
Thanks

Quote - really weird, I got this message today too when starting up poser.  Sooo what do I do? I didnt install anything new since the last time I started poser.

The usual culprit is a file with an "&" in the folder name.

It may be an item that you installed some time ago, what triggers it is visiting that folder, and then exiting with that folder as the last one in that library category that you looked at for the Runtime that it's in.

You can edit the file in a text editor to correct the problem, but you must also rename the directory to stop it reoccurring.
I can't help much more without seeing the file (copy, change the extension to .DOC and attach, even a screenshot might be good enough).

nruddock, your advice may be related to your personal/past experience, but you seem to be ignoring something here... all these folks (myself included) had this happen for the first time today/yesterday... this means that it's likely a common (externally influenced) cause.

I did not download/install anything (rarely ever download freebies ayway).  I tend to agree with pjz99 above - this sounds like something that happened over the network.

Quote - nruddock, your advice may be related to your personal/past experience, but you seem to be ignoring something here... all these folks (myself included) had this happen for the first time today/yesterday... this means that it's likely a common (externally influenced) cause.

I did not download/install anything (rarely ever download freebies ayway).  I tend to agree with pjz99 above - this sounds like something that happened over the network.

Agreed, but seeing the contents of the file will aid in determining what the cause might be.
If it isn't a bad character problem, then we need to attempt to determine what triggers it, be it a coding error in some file (freebie or otherwise), or something else common to the people who've suddenly starting getting this problem.

Fair enough :).  Here's my current file:

Quote -

<?xml version="1.0"?>                                                                                      

...I don't see anything odd in there, and the problem only happened once (referring to "line 2", as others noted above).  If it occurs again, I'll check this file before doing anything else.

Quote - ...I don't see anything odd in there, and the problem only happened once (referring to "line 2", as others noted above).  If it occurs again, I'll check this file before doing anything else.

No neither do I, but if you've already restarted Poser, and linked your external Runtimes back in, then I wouldn't expect to.

The trick is to goto the prefs folder before you click on the OK to clear the error, and grab a copy of the file.
Sometimes Poser creates a copy of the buggy file called "__XML_ERROR__LibraryPrefs.xml", then writes a clean LibraryPrefs.xml

The annoying thing is I know I've seen this error before while working on code that writes LibraryPref.xml files.
Also found a report of a previous occurence -> http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2500056
Not much help unfortunately.

Spanky is correct I hadn't gotten this error before yesterday. Up until then I've never had any errors or had any problems with poser. I guess we'll just have to wait until the error shows up again and then check the libraryPref.xml before clearing the error.

Okay just happened again. Here is a screen shot of my Library Pref .XML before I hit OK to clear it.

Well, here's another voice for the choir. I'm getting this message since December 7th, too and by now I can't even reopen my old saved pz3s any more. :^( I removed the LibraryPrefs, but Poser didn't care. Really weird, I had no such things before, and with Poser 7 just around the corner it is a bit suspicious... lol

Some progress, I've remembered what caused this error, and can reproduce the message by making certain changes to LibraryPrefs.xml

Still don't know why your getting though, as I only ran into it before because I was creating a LibraryPrefs.xml using a Java program, but for the record (and I realise it won't mean a great deal to anyone who does know much about XML) the cause is that if for some reason the xml declaration in the first line isn't exactly

<?xml version="1.0"?>

E.g. if there's even an extra space between the " and ? then when Poser writes out the file you end up with 

<?xml version="1.0"?><br></br><?xml version="1.0" ?>

which is why Poser reports junk in line 2.

One possible cause of this problem may be that the code is trying to add an encoding declaration, which although legal according to the xml specification, Poser doesn't cope with them.

Thank you, nruddock, that actually helped me! ^_^ The scene with V4 seems to be cooked, but at least the others open...

I think it may be related to installing V4.  I got the error too but only after installing V4.  It did not come up the first time I opened Poser because I had not added her runtime yet.  It came up the next time I ran poser AFTER adding her runtime to my list.  I just started Poser up again (because I foolishly clicked 'ok' the first time) and I didnt' get it again.  The pz3 I worked on after getting the error is fine and the one I saved prior to getting the error is fine as well.  Whew.  I better save this character as a .cr2 so I don't lose it.

I seem to recall getting an odd XML error way back when I first got V3 too.  But, I could be hallucinating that.  It was a long time ago grins

Quote - Thank you, nruddock, that actually helped me! ^_^ The scene with V4 seems to be cooked, but at least the others open...

Now we can hopefully narrow things down.
Check any Runtimes / items you used for that scene.
Is there anything unique to that scene ?

I do not even own V4 as of yet, so I can definately say its not because I installed V4. the last thing I installed into a completely seperate runtime folder was petite Fleur Hair. I too did hit ok when I saw it, and have not had it come up again (paranoid, I keep opening and closing poser) Maybe E Frontier making me paraniod since I did not put in for my upgrade to poser 7.

Quote - I think it may be related to installing V4.  I got the error too but only after installing V4.  It did not come up the first time I opened Poser because I had not added her runtime yet.  It came up the next time I ran poser AFTER adding her runtime to my list.  I just started Poser up again (because I foolishly clicked 'ok' the first time) and I didnt' get it again.

I don't think is V4 per se, as I've not run into this.
The one recent item that I don't have that's V4 related is the Immortal Dream hair, but this is probably just a coincidence.

Also can you all check to make sure you are using the latest version of Poser (6.0.3.139).

Quote - ... the last thing I installed into a completely seperate runtime folder was petite Fleur Hair.

Another item I don't have, can you look to see if any of the directory or file names have an accented letters in them.

Well, there goes that theory anyway :)

Also, I forget, are apostorphes a problem in the directory names?

Ditto, all I've added was V4 and got the error as well.

It can't be V4, it would be nice and easy, but I got that message before she was even available, let alone installed.

There's nothing special about the killed file: it has V4, Ozone outfit, Shigi hair, Helena texture and morph plus the Condamned Hope freebie scene from DAZ, all coming from my main Poser 5 runtime on my external harddrive; the older files use things from various of my other runtimes, not just this one, but this one, too and seem to be fine.

I think it didn't save the scene correctly because of that XML error, not because something's causing trouble in it.

Count me as one who never saw this error until I installed V4.  (Actually, the V4 pro bundle.)  Very odd.

I'm reluctant to delete the library prefs file, because I don't want to have to add all my runtimes again.  I've got a lot.

I wish Poser would let you add every runtime in a folder, like D|S does.  And that it would automatically alphabetize them. 

I'm getting the same error for the first time ever!  Installed V4, the Morphs++ pack and Domino last night.  Created a scene, hit render, and after about 5 hours (just when the render was about to finish) P6 crapped out on me and completely froze up.  I had to Ctrl-Alt-Delete out.

I had saved my scene, so I thought, okay no problem...I'll just try again with different render settings.  So today I open up Poser, try to open my scene and I get that XML error.  I've tried deleting LibraryPrefs.xml and Poser UI Prefs_1024x768.xml and that doesn't help at all.

Whenever I try to open my V4 scene, my work window and Parameter Dials disappear.  I try to open the file again or close out of Poser and I get a message to save my file...so it's like it's there but it's not.  When I try to open an older scene file the Parameter Dials disappear but the work window is there, but completely blank!  What the hell??????

Hmmm....

Could it relate to the number of Figure Libraries you have?

For instance I have V2, V3, M2, M3, D3, Aiko, SP3, Dragons, Critters, Horse, Scenes, Architecture, Props, Hair... etc etc all in one long list.
I wonder...
I installed V4 into the top level (P6) and then again into an external runtime (I've had trouble just installing it into an external one so now I add it to the main program runtime.)

It just makes me wonder because I've never had this before. Ever.

I dunno.  Right now I've got 25 folders on the top level in the Character/Figure Library. 

I put V4 under Characters > Humans > Victoria 4

The first time I got this error message was on 5 Dec which is way before V4 was even available. I also have the V4 pro bundle but I don't know if it related. After 5 Dec the error shows up once in a while it is not consistent and does not hinder me from opening poser, rendering or really effect poser at all. It's just bloody annoying.

Besides P6 runtime I have 4 other runtime folders. I never had a problem with this error prior to 5 Dec. As a matter of fact I never had any problems with P6 at all.

I've had the same thing now for a couple of weeks and haven't installed anything other than the same characters(V3,M3,A3,H3 and Freak),materials,Hair(mostly Koz's hair)and Props that I've had on Poser 5. I have altered the Poser shell to remove the content paradise room. I can get the error loading different characters or even different props,so I don't think it can be narrowed down to just one problem file.

yeah i started getting this same message after installing V4

Those of you who started getting this after installing V4, which version did you get, Base only, Complete, or Pro Bundle ?

I got the Base and Morphs++

Poser was so messed up and completely unuseable that I decided to uninstall it and do a fresh install.  I just finished reinstalling all my new V4 stuff, tried to open that scene file and...no XML error this time, but my work space and Parameter Dials disappeared again.  sigh

That file must be corrupted or something.  I'm working on a new scene now with V4 so we'll see what happens...

Yup same here after installing V4. Wonder what's up?
Marque

Come to think of it I didn't get it until after I bought and installed the domino product.
Marque

Personally, I think the 'V4' link is a red-herring.  It could be the problem, but it might just be the trigger that caused you to use Poser again (and/or in some ways you hadn't recently).  My personal belief is that this problem is related to 'something' that happened on a specific date (a few days ago, or "the next time you ran Poser" (or clicked on the Hair folder or something like that) after the event).

If you look back through this thread, it was happening to people (incuding myself) before they bought V4 but had never seen it before a few days ago.  Either the program code itself had some date-based trigger in it, or there was some interaction via the network (more likely).

We might also be having different issues... the one that seems to have been triggered a few days ago reports a problem "xxxx... on line 2".  And after clicking Ok on the dialog, I (and others) hadn't had any other problems since,  but some of you are reporting recurring problems.  If you're having a recurring problem, look back through this thread for possible solutions.  If the solution doesn't work, post your file here so we can see it (grab the file before clicking "Ok" on the dialog).

Just for the record, I had no problems after installing the "Complete" V4 pack.

omg... I got that error also... I wasnt certain what it was about but everything worked fine So I just ignored it.  Here I thought i was the only one.  Is there any negative side effects to this error? 

I have seen this error only once when I first open up my poser 6.  After I closed the error everything works ok....

I noticed it first after i had downloaded V4 complete (on the day she was released) but I had not yet installed her.  Wierd.  And it listed an error on line 2.

Weill, it can't be related to V4 because I got the same message and I don't have V4... yet.  Unless it's based on my intention to get her.