WebSite X5Help Center

 
Nigel W.
Nigel W.
User

Fatal Error before closing/opening project  en

Author: Nigel W.
Visited 527, Followers 1, Shared 0  

Not the first time this has happened with WebsiteX5...

An error occurred while loading the Project.

[There isan error in XML document (2115429.18).]

Luckily I have FOUR backups.

Solution, please!

Posted on the
5 ANSWERS
Incomedia
Claudio D.
Incomedia

Hello Nigel,

It depends on what happend to the project before.

Have you add a new object? Did you have problems saving the project?

Many thanks!

Read more
Posted on the from Claudio D.
Nigel W.
Nigel W.
User
Author

Yes...the project said it had not saved properly.

I frequently add/renew pictures, especially in the vintage albums and then delete the old ones i.e I sometimes find better pictures of higher dpi of the same picture.

(This shouldn't happen, should it?)

Nigel

Read more
Posted on the from Nigel W.
Incomedia
Claudio D.
Incomedia

Hello Nigel,

It can be that the size of the new image is to high and it takes longer to elaborate. In any case if you need to replace and image, try to remove the object and then add it again to see if the same happens again. If it still occurs check that the simultaneous processes are set to 1 and then try again. In this way we can understand better what is the cause of the saving issue.

Please keep me updated.

Read more
Posted on the from Claudio D.
Nigel W.
Nigel W.
User
Author

Hi Claudio...

The problem is that this fault only happens very occasionally...

It will be difficult to perform your test, therefore.

It MIGHT be a "memory" problem...but I am wondering if your programmers could look at the phenomenon and write something in the script that might counteract this?

Of course, I am out on a limb as I am one of the few with a large cumbersome project and I suppose unthought of problems will occur from time to time, as a result.

Keep this thread open and I'll add if it happens again.

Nigel

Read more
Posted on the from Nigel W.
Incomedia
Claudio D.
Incomedia

Hello Nigel,

From the behaviour it seems to be a memory problem. If you set the maximum simultaneous processes to 1 this should not happen but it is better to follow the issue to identify the exact source.

Please keep me updated.

Read more
Posted on the from Claudio D.