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!

My Facebook Page

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.

My Facebook Page

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.

My Facebook Page

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.

My Freebies

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!!

My Facebook Page

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

My Facebook Page

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.

I wish I'd said that.. The Staircase Wit

anahl nathrak uth vas betude doth yel dyenvey..;)

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!

My Facebook Page

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..;)

I wish I'd said that.. The Staircase Wit

anahl nathrak uth vas betude doth yel dyenvey..;)

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.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.

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 -

...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.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.

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.

My Facebook Page

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

My Facebook Page

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.

Silke

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??????

"You don't know what we can see
Why don't you tell your dreams to me
Fantasy will set you free." - Steppenwolf

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.

Silke

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

"You don't know what we can see
Why don't you tell your dreams to me
Fantasy will set you free." - Steppenwolf

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.

My Facebook Page

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...

"You don't know what we can see
Why don't you tell your dreams to me
Fantasy will set you free." - Steppenwolf

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.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.

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.

This is my XML right after the error:

I know nruddock mentioned something about the first line and it looks like to me that there is an extra space between the 1.0" and the ?>. But when I bring it into word pad the looks normal. How do I fix this as this could be the problem? It's puzzling why now we are all getting this error all of a sudden just this week.

My Facebook Page

I don't post very much, so hi all. I got the same thing too, before I installed V4. Since we all started getting this at the same time, I figured it has to be external. On a hunch I went into General Preferences - Misc, where the check for updates at launch is, and hit the check for updates now button - viola I got the same XML error. Not sure if this is everbodys issue, but it seems likely.

Quote - I know nruddock mentioned something about the first line ...

The extra space your seeing is due to the way IE formats XML files.
Seeing the extra space in your first screenshot did jog my memory about what causes the trouble.

Opening the file in either WordPad or NotePad would be better as I'm not sure whether IE is doing something else to the contents.

Yes, I got that too when I hit the check for updates now button. Well, I'm unchecking it and leaving it that way. With this forum and the ef newsletter I get I'll know when there are new updates out.

My Facebook Page

This sounds like a good candidate, so another straw poll, who has check for updates checked ?

I have "check for updates" checked.

But I didn't get the problem on launch. I got it while rendering.

Seems to have gone away now, though.

i got the error again after several days...as far as i know...update is UNchecked

Quote - I have "check for updates" checked.

But I didn't get the problem on launch. I got it while rendering.

Seems to have gone away now, though.

I've only seen the error once, which was yesterday after I installed V4, but it was on closing and the only runtimes linked are the 2 P6 runtimes. I routinely remove all of my external runtimes when closing Poser so that it doesn't take a long time to open. And it's not that I don't use Poser a lot, I use it everyday.

FYI - I got the Pro bundle.

Hugz from Phoenix, USA

Victoria

Remember, sometimes the dragon wins. Correction: MOST times.

Same...

I started receiving the message after V4 was installed. Very odd.

I got this message too and for sure before V4 came out. I also think it has to do with the update function. If I go into the General Preferences --> Misc and click the 'Check now' button I get that error message each time. I didn't see any problems resulting from this though.

But I have a really bad problem now with my saved V4 scenes I did so far. It's impossible to load them again. Got exactly the same problem as Neyjour described above. :(
I found out that when I do a 'File' --> 'Close' or start Poser 6 new and don't try to load a V4 scene I can at least load my old files not containing V4.

Yes I did have the check for updates on start up checked. I've unchecked it.

I've had the check for updates box unchecked for over and hour and a half (used to be checked all the time) and been doing render after render for that hour and a half and no error has come up. It was coming up at least 3 -4 times in the past as I was using poser so far nothing. Keeps fingers crossed

Well see what happens after I turn my machine off for the night and start it up tomorrow.

My Facebook Page

Same here - "Check for updates on launch" was enabled. If I click on Check Now, I get the error immediately. No other apparent side-affects aside from that dialog, but I don't tend to save scenes much, so I may not be seeing those yet.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.

Okay, I had "update on startup" checked, and sometimes I get the error and sometimes I don't. I also have Ethereal, which is a PC-based network analyzer, and I'm here to tell you that this isn't caused by loading V4, or fiddling about with your runtimes, or some mysterious XML virus, or Jupiter aligning with Mars. It's caused by e-frontier's update system being broken. When the updater actually contacts EF, it gets an error message back, and it spits up this XML error. This also appears to be making the update piece of Poser behave peculiarly, so if you have "update on startup" checked, I'd uncheck it if I were you.

I have to tell you this is not filling me with confidence about being able to download P7 on Monday . . .

I had it checked also, but just hit the button to check and got the error again.

Weird...I've been getting this at odd random moments for the past couple days. Doesn't matter which of my runtimes I'm trolling through. (and no, I have no V4...or Vanything)

Will try and remember to check the update thing tomorrow. Hasn't caused any problems with anything I've been doing. All files are fine, and my pz3s are still good.

But then I seem to have an electronic anomoly following me around where things malfunction until someone else walks into the room. Then they behave.

Damn computers are out to get me....

Crazy alien chick FTW! (yeah....right....)

Realm of Savage - Poser goodies and so much more!

~~

This is totally related to Victoria 4. It only started happening to everyone on the 7th, when she was released. And I've only had the issue attempting to open .pz3 scenes with her in them. Everything else functions as normal.

Way to go Daz, releasing a product on a Friday offering no weekend product support. Now there's a bunch of pissed off customers.

Well as some people has had the error BEFORE V4 came out, and some have the error withouth even owning V4, this is NOT "totally related to V4"

I have V4, Pro Bundle and I haven't got that error. What gives, huh? I want the error too! I've paid for it!

OTOH I haven't got Check for Updated checked and my firewall is blocking Poser from phoning home in any case. I don't allow my programs to go out and play on the big bad Internet without my consent.

Looks to me like it's an update issue.

Disregard my last post, as I thought there was only one page to this thread so far.

It is indeed HUGELY coincidental that 99.9% of us are having this problem as it relates to V4. But as I am tryin to examine all realms of possiblity, wrap your mind around this:

I ran some tests. I have two .pz3 scenes I set up today containing V4 (I only purchased her today; prior to my purchase I've never seen the .xml parser error). Here's what I've seen so far:

The first scene I saved appears to open, although the document window is pitch black, even though the scene is well-lit according to the light globe. The GUI seems to respond when attempting to open up the "content slider" from the right (I don't know what it's really called) or playing with the parameter dials. But the light globe is frozen; the lights cannot be added, deleted, etc.

The second scene I saved does not load the document window at all. All the above hold true as well for this particular scene. Remember, BOTH scenes contain the new V4.

I can stll open old .pz3 scenes without issue. Additionally, I created a new scene, added some figures, props, etc. and saved it, closed Poser completely, reopened it, and opened the saved .pz3 successfully. Then, I added V4 to the SAME scene, saved it as a new name, closed Poser, reopened it, and loaded that .pz3 scene. It opened successfully. So why just those two apparently corrupted ones? Well, I attempted to once again open one; same issues. Then, I went back to open the recently saved one containing V4. Same issue as the first! The document window was black (my default background color) and the GUI appeared to respond but nothing happened.

Let's go over the facts:

1. Most of us have been having this issue since the install of V4 (the bundle)
2. Been happening since Friday frequently enough to infer something has just recently broke
3. I believe the majority of us have preordered Poser 7 (giving clout to the other people in this thread who feel it is not related to V4)

So there's as much info as I can provide and I'll keep paying attention to this thread so we can solve it hopefully sooner than later. If I loose those .pz3s I'm gonna be really unhappy.

Ok, had "check for updates" ticked. Got error.
Unticked it - no error!

It seems to be related or I was just lucky.

However - I didn't get the error after clicking "Yes" and closing and reopening poser yesterday.
I did get it again at opening poser today after reboot.
Will report back if I get it back after reboot (but I'm doing stuff now so it'll be later :P)

Silke

Dysfunkshunal - Perhaps your issue is also related to the PMD's being On. Try to see if they're on or off. And uncheck Use Binary Morphtargets. That likely won't save your botched scenes but should prevent it from happening on subsequent saves.

I also got this error, started yesterday.
Is the solution to uncheck "check for updates"? I hade it ticked. Got error as soon as I clicked the "Check now" button, now it´s unchecked.

I did bye V4, but this seams to be a updateproblem. Have someone contacted E-frontier? I know I can´t, spells way to bad ;-)

My store at DAZ
My Renderosity store

I also got this error, started yesterday.
Is the solution to uncheck "check for updates"? I hade it ticked. Got error as soon as I clicked the "Check now" button, now it´s unchecked.

I did bye V4, but this seams to be a updateproblem. Have someone contacted E-frontier? I know I can´t, spells way to bad ;-)

My store at DAZ
My Renderosity store

Well my check for updates on start is checked, and always has been. As I said before I got the message before V4, Im also thinking it has to do with E Frontier somehow.

So...if there was an update, why not tell us? :rolleyes: That way, those of us who've been effected (yes, me, too) can choose NOT to update.
Call me paranoid or snooty, but I'd like the choice as to whether or not to update a software package of mine.

Sitemail | Freestuff | Craftythings | Youtube|

Knowledge is knowing a tomato is a fruit. Wisdom is not putting it into a fruit salad.

I'm beginning to believe it was something to do with ef and the up coming release of P7. I know a few of you have not pre-ordered P7 but I think the majority of us has and maybe this was not an update from ef but a check of valid serial numbers of those of us who have ordered P7. I know I did and I chose the electronic delivery. As I said I noticed this problem just about the same time ef announced the release and ship date of P7 which was before the release of V4.

This make me wonder if ef sent this verification of serial numbers as an update which really messed up this function in P6. I don't know it's just a theory and my 2 cents. I know now that I have unchecked the "check for updates" I'm not getting the error now.

I did the same for Windows too. I don't take the auto updates I do them myself for this very reason.

My Facebook Page

I almost hope that was it, but if I can't use my P6 without difficulties, I'm gonna get cranky :lol: I get this error at least once per hour while working.

Sitemail | Freestuff | Craftythings | Youtube|

Knowledge is knowing a tomato is a fruit. Wisdom is not putting it into a fruit salad.

Quote - I almost hope that was it, but if I can't use my P6 without difficulties, I'm gonna get cranky :lol: I get this error at least once per hour while working.

I was too Jen but last night I unchecked the box for check for updates and for almost two hours, until I hit the rack, I worked in P6 making render after render and for about 2 hours never got the error message again.

I'm working on P6 right now and have yet to see the nasty little error. Now I feel I've jinx myself...LOL!

My Facebook Page

Quote - I'm beginning to believe it was something to do with ef and the up coming release of P7.

Well there is definitely a problem with EF update check.
They did have server trouble beginning last weekend, and during this week, so this would account why it popped up when it did.

I doubt it's related to the P7 release, other than it's broken and they haven't fixed it yet, either because they don't know, or it's seen as low priority.

@Mihoshi - love the name! ^_~

I almost don't dare to post it, because I don't want to tempt fate, but after turning off the automatic search for updates, and not having my .pmd's saved extra anymore, I saved 6 different pz3 with V4 and different textures and content, and was able to open them again.

knocks on wood

It may just be as a few people have pointed out; it's something with e-Frontier's update service. I had the XML error on maybe Wednesday or Thursday but Poser started up alright so I just ignored it and didn't give it much thought after that because I just though that it was "one of those things" you might get every now and then. I didn't own V4 then (just got her yesterday) and hadn't put in my preorder for Poser 7 until Friday. Haven't had much problem saving or opening files that I'm aware of but I've been working in Vue 6 since then but think I'll turn off auto updates just to be on the safe side. crosses fingers.

I haven't had any trouble with saving scenes with V4 in them. But I've been working in P6 most of the day now and have not encountered the error after unchecking the search for updates on start up box.

My Facebook Page

Okay, so it sounds like we have two prolbmes that occured at almost the same time, but are infact unrelated.

P6 has some error related to e-frontiers updating.

V4 does not get along with External Binary Morphs.

Isn't External Binary Morphs a good thing? Isn't this part of the great functionality of P6 over P5 that allows for smaller RAM imprint? Don't I want Binary Morph targets? Is this an issue Daz will ever address, or am I going to be robbed of extra functionality? Or do I have this all wrong?

OK but now this is weird.

After my boasting of how I had V4 and haven't seen that error, I came home from work, fired up Poser... and got an XML error. Two actually, and the second one was something about a malformed something at line 1. AND Poser had dumped my Poser 4 runtime (which is the main one I use, it's the PBooosted one wher eI install everything that isn't Poser 6 specific)

Poser started fine after that, and I could add the runtime back with no problems, but... My Check for Updates was NOT checked and has never been checked.

So now I'm back at wondering if it has something to do with V4 (whom I installed yesterday) after all............

Don't know if this will help...

Yesterday (Dec 9th) I got the "xml error - junk after line 2" thingy.
I have updated nothing in the last 6 months (can't afford it) and have never had this problem before.
On loading P6 this morning I got the same error.
Both times this happened after Poser had been running for approx 1 min.

This morning I happened to glance at my firewall and realised I was still connected to the net. Usually I disconnect the cable when I'm not actively using the net. Last night I must have forgotten to do that.

I read this thread and thought "Umm...."

So I disconnected, loaded P6, loaded a character, twiddled my thumbs for a couple of minutes (well, glugged some beer, actually), and... nothing happened

So I checked my preferences and lo! and behold! - "Check for Updates" was checked. (I didn't even know it was there!)
So I unchecked it. Closed Poser, re-connected, checked back into Rosity and re-entered this thread. And started posting.
Just to double-check, I restarted Poser and did the little mini-tut pic seen above: "Don't you make my blue eyes brown?" No error mesage:-))

So I guess that the "Junk after line 2" has got to be something to do with checking for updates....
(PS - The pic is pure frippery - I just wanted something to do while waiting for the error message to show up - or not... And BTW, who was it who sang "Don't you make my brown eyes blue?")

Cheers,
Diolma

For some reason, Crystal Gale comes to mind for that song......but I'm not always the best at remembering names....and I'm too lazy to google it right now.

Crazy alien chick FTW! (yeah....right....)

Realm of Savage - Poser goodies and so much more!

~~

Quote - Don't know if this will help...

Yesterday (Dec 9th) I got the "xml error - junk after line 2" thingy.
I have updated nothing in the last 6 months (can't afford it) and have never had this problem before.
On loading P6 this morning I got the same error.
Both times this happened after Poser had been running for approx 1 min.

This morning I happened to glance at my firewall and realised I was still connected to the net. Usually I disconnect the cable when I'm not actively using the net. Last night I must have forgotten to do that.

I read this thread and thought "Umm...."

So I disconnected, loaded P6, loaded a character, twiddled my thumbs for a couple of minutes (well, glugged some beer, actually), and... nothing happened

So I checked my preferences and lo! and behold! - "Check for Updates" was checked. (I didn't even know it was there!)
So I unchecked it. Closed Poser, re-connected, checked back into Rosity and re-entered this thread. And started posting.
Just to double-check, I restarted Poser and did the little mini-tut pic seen above: "Don't you make my blue eyes brown?" No error mesage:-))

So I guess that the "Junk after line 2" has got to be something to do with checking for updates....
(PS - The pic is pure frippery - I just wanted something to do while waiting for the error message to show up - or not... And BTW, who was it who sang "Don't you make my brown eyes blue?")

Cheers,
Diolma

Yes, I found that unchecking that box stopped the error. I've been running poser all day without that error showing up. For me though, it didn't hinder posers operation. I had no problem opening poser, rendering or saving scenes. What was happening was the annoying error coming up every hour sometimes less.

Whatever is going on I think it stinks. My wife was tongue and cheek saying she thinks ef planted a bug so P6 would meltdown and they could sell more copies of P7. Remember, she was only kidding. Whatever it is whether it's ef , V4 or a combination of the two I hope that the powers that be address this. This is not the kind of thing we want happening in P7.

My Facebook Page

Quote - Okay, so it sounds like we have two prolbmes that occured at almost the same time, but are infact unrelated.

P6 has some error related to e-frontiers updating.

V4 does not get along with External Binary Morphs.

Isn't External Binary Morphs a good thing? Isn't this part of the great functionality of P6 over P5 that allows for smaller RAM imprint? Don't I want Binary Morph targets? Is this an issue Daz will ever address, or am I going to be robbed of extra functionality? Or do I have this all wrong?

I reckon you got it. I am getting the same junk line 2 error message and had my update box checked.

I did install pro bundle for V4 and the EBM issue is a seperate thing IMO.

I think ef are doing a 'verfication thang' on folk who have pre ordered Poser 7 maybe?
Automatic check on those whose copies have the update check enabled perhaps?

It seeems what we have is a timing 'coinkydinky' between V4 & P7.

Klutz :0)

********************************************************************************************************************

Life is a beta.

In faecorum semper, solum profundum variat.

I bet it doesn't like the "-" in the V4 Hi-Res material.... because it's been happening since I installed her as well... also these files don't load in Vue, etc... it's quite irritating...

mes

How many people didn't open Poser before they installed V4?

I know I've not run it a few days. Then V4 arrives, I install, and naturally run it.
BOOM. Error shows up.

I also think it's the updates. Too many people here are reporting that it stopped when they unticked it.

I have preordered P7. Who else of those who are getting the error have done that?

(And btw - I don't think it's a serial check. Simply because it is illegal to do this without permission. They'd be sniffing personal information. Regardless of whether it's their software or not. That's why with MS you have to agree to verify/authenticate.)

Silke

Maybe they are taking the checked tick box as 'permission'? :0/

********************************************************************************************************************

Life is a beta.

In faecorum semper, solum profundum variat.

The update check just sends the Poser version number, whether your using Windows or Mac, and the first few characters of the serial (upto to the first "-").
Once I turned update checking on, I got that error after a few restarts.

The V4 / PMD thing is a completely unrelated problem.

But I got an XML error (not THE one mentioned here though, mine didn't say "junk" and it referred to malformed something at line 1) but I did NOT have Check for Updates checked.

And I haven't checked for updates manually either.

The company that created the software does not need permission to ping the program to make sure it is valid. Poser itself connects to your "network" to make sure that it's the only version with its' serial number running at the time, and there are other programs that have to "phone home" a lot to make sure they work (Virtual Fashion comes to mind). While it sucks, it's not illegal.

Sitemail | Freestuff | Craftythings | Youtube|

Knowledge is knowing a tomato is a fruit. Wisdom is not putting it into a fruit salad.

I had both errors yesterday for the first time. I also put V4 in yesterday. I pre ordered Poser7on Thursday. I have unchecked the update thing and the other one, I'll see how it goes.
I've never had these errors before.

Love is Grandchildren.

I emailed e-frontier tech support about this, and they said they were aware of the problem and hoped to have it fixed by the end of the day (Monday 11 Dec). I checked again just now, and it does appear to be fixed. Let's see if the XML errors go away.

Forum: Poser - OFFICIAL

Subject: XML ERROR???? WTH is that?