[Paraview] Problems loading saved states

[Christoph Meyer]

Please find a little sample attached. The message I get when trying to open
it is this here:


	ERROR: In ..\..\..\..\src\VTK\IO\vtkXMLParser.cxx, line 483
	vtkPVXMLParser (000000000C09BE60): Error parsing XML in stream at
line 3771, column 35, byte index 186690: not well-formed (invalid token)
	Root does not exist. Either state file could not be opened or it
does not contain valid xml


Looking at the pvsm file in the appropriate line, I don't understand all of
it, but can't see anything  suspicious either.



-----Ursprüngliche Nachricht-----
Von: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com] 
Gesendet: Montag, 14. Mai 2012 16:02
An: Christoph Meyer
Cc: paraview at paraview.org
Betreff: Re: [Paraview] Problems loading saved states

You can try to look at your pvsm file and see if you find something
suspicious. Otherwise, if you can share the state file without the data, you
can send it to us so we can try to track the problem down.

Seb

On Mon, May 14, 2012 at 9:30 AM, Christoph Meyer <meyer at ib-bauklimatik.de>
wrote:
> No, not that I am aware of. We do have those weird special chars in 
> German (ä, ö, ü, ß), which I've learned long ago better to avoid in 
> technical software. And I did, as far as I can see.
> But, since you mention it, I did at one point have the feeling, that 
> ParaView doesn't treat the german standard notation for decimal 
> numbers (decimal comma, separator point) consistently. My system is 
> set to that format, but (most, possibly not all) numbers in ParaView's 
> menus appear in anglo-saxon notation (decimal point). Unfortunately, I 
> can't find an example for exceptions right now.
> Could that be something?
>
>
> -----Ursprüngliche Nachricht-----
> Von: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
> Gesendet: Montag, 14. Mai 2012 15:17
> An: Christoph Meyer
> Cc: paraview at paraview.org
> Betreff: Re: [Paraview] Problems loading saved states
>
> Is it possible that you have some non-ascii chars in your state file 
> that could come from your field data ?
>
> On Mon, May 14, 2012 at 4:51 AM, Christoph Meyer 
> <meyer at ib-bauklimatik.de>
> wrote:
>> Hello everyone around.
>>
>>
>>
>> as a newbie to this list – and a relative beginner with ParaView – 
>> I’m glad to have found you, and very relieved by the prospect of 
>> possibly getting some help for my present problems with ParaView. 
>> Apologies in advance, in case my beginner-questions should turn out to be
quite basic.
>>
>>
>>
>> Most pressing problem is, that my installation (ParaView 3.14.1 64 
>> bit, running on WIN7) is extremely unreliable, when it comes to 
>> loading saved states. In fact, that works very rarely. Most of the 
>> times, I get error messages similar to this one
>>
>>
>>
>> ERROR: In ..\..\..\..\src\VTK\IO\vtkXMLParser.cxx, line 483
>>
>> vtkPVXMLParser (000000000C1412F0): Error parsing XML in stream at 
>> line 2149, column 35, byte index 109506: not well-formed (invalid 
>> token)
>>
>> Root does not exist. Either state file could not be opened or it does 
>> not contain valid xml
>>
>>
>>
>> There is no indication of any problems while working with ParaView or 
>> when saving a state. I don’t think I’m using any exotic filters 
>> (ENSIGHT-reader, calculator, slices etc.). The crash occurs before 
>> I’m asked which data file to read, right after picking a *.pvsm file to
load.
>>
>>
>>
>> I will now try to work around the problem by tracing my work, but 
>> would very much prefer a proper start from a saved state. Any hint on 
>> possible solution will be very much appreciated.
>>
>>
>>
>> Regards
>>
>> Chris
>>
>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the ParaView Wiki at:
>> http://paraview.org/Wiki/ParaView
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.paraview.org/mailman/listinfo/paraview
>>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SavedState.pvsm
Type: application/octet-stream
Size: 230205 bytes
Desc: not available
URL: <http://www.paraview.org/pipermail/paraview/attachments/20120514/9d5a782e/attachment-0001.obj>