This is my XML right after the error:

I know nruddock mentioned something about the first line  <?xml version="1.0"?> 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 <?xml version="1.0"?> 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.

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.

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.

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.

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.

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

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)

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

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

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. 

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.

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.

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!

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.

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

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.

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.

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)

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

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

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.

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.

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.