Fault message trying to import a project from x5v13 to v14
Autor: David S.
Visitado 1682,
Seguidores 1,
Compartilhado 0
On trying to import a project from V12 or V13 into V14 I get the error message as on the attached screenshot.
Publicado em
David, can the V12 project be imported into V12, and the same with the V13 project? (this will not overwrite existing project).
Are the project names excessivily long? Are the original projects stored in the default directory (documents) and are the objects linked to in the projects local or cloud based?
Autor
let me check those questions and get back to you.
Autor
Hi Esahc
I have worked through the questions you asked. The project with the short title of MinsterGothic(1)test did import succesfully from V12 to V13 from the default directory (C:\Users\smith\Documents\Incomedia\WebSite X5 v12 - Professional\)
I saved the project in V13 again in the default directory (C:\Users\smith\Documents\Incomedia\WebSite X5 v13 - Professional\)
I have then tried to import the project into V14 with exactly the same fault message appearing.
the files are stored on my PC C drive, but are backed up to the cloud (MS). However the import is from the C Drive.
David - I was hoping for different answers and am now out of ideas. I have asked Incomedia if they can assist.
I will dwell on the issue in the interim :-)
You may wish to advise what version of windows you are using, roughly how many pages in the project / size and is it graphic intensive (lots of large pictures) in case this has any bearing on the problem.
Hi David,
Perhaps a workaround? What I always do when I upgrade to a newer version of WebsiteX5 is, to export to a folder, directly in the root of my harddrive (for example C:\WX5 Projects). I have done this from version 7 to 8, 8 to 9, all the way up to to 14 and I never experienced a problem with a filename which was too long.
Perhaps you can give it a try?
Good luck,
Robert
David
I neglected to ask, are you importing from an iwzip rather than attempting to open an existing project?
A project must be exported (create an iwzip file (step5)) in order to cleanly upgrade by import to V14
Autor
Hi Esahc and Rbbrt, firstly thank you both for your efforts to help.
I am using Windows 10 and yes I was trying to import from an iwzip file.
I really don't know exactly how many pages or size/number of images there are. I'm far from being an expert user. (which is why I chose WX5!) the site is www.minster-gothic.com if you would like to take a look.
I tried Rbbrt's idea of exporting to C\WX5 and importing from there. But same error message.
However, the story gets stranger!
I had the brainwave of installing WX5-14 on my laptop. After doing so I copied the project iwzip file from my desktop onto a usb drive. I then went to import the projectt on my laptop version of WX5-14 and YES IT WORKED. I made a few minor alterations and saved the project (obviously now a WX5-14 project).
I went back to my desktop and tried to import the file from the laptop C drive via the network. Same error message!
I formatted the usb drive, and copied the new project file back onto it from the laptop C drive. (for some reason WX5 would not export it to the usb drive) I put the usb drive into the desktop and tried to import it into the desktop version of WX5-14. YIPPEE IT WORKED!
there are a few niggles to sort out (fonts, header banner missing etc. But I'll be able to work through those I'm sure.
It was a long drawn out, trial and error process, and I've no idea what the original fault was. But all's well that ends well (for now anyway)
thanks again for your help guys, and maybe this info could help someone else.
I'm sure I'll be back for more help in the future, sooner rather than later.
Regards. Dave.
David, I am pleased you have successfully imported to V14. It sounds like previously you were importing across the network and then ultimately from a USB drive? I have seen other instances where this failed and for this reason only work from local hard drives.
Autor
Hi Esahc, no, the original failed attempts were from the local hard drive. The eventual succesful one was from a usb drive. But anyway, as long as I got something working in the end! Regards.
David, as a pre-emptive measure I'd be checking the hard drive (chkdsk c: /r from an admin DOS prompt :-)
Congrats again on your success. . . . .