Importing MS Proj Files Into P5 Read Only Error
In the Open Standard
Douglas BylesMember for 19 years 7 months
- Created
- 3
- 4
0
Hi,
I was wondering if anyone has run across this issue before. When I try to import a Microsoft Project File into P5, the process runs correctly, but when it opens the MSP file it says it is read only and a copy needs to be made.
Irrespective of whether I allow a copy of cancel the dialog box, the process completes running, but fails to create the new Project in P5.
I get the "Process completed with errors. See log file for details." message and my log contains this.
INFORMATION: Creating temporary working file...
*** ERROR ***: Unable to open file T:\DougB\V634-307 MMPM.mpp. - An unexpected error occurred with the method
INFORMATION: Importing Global Data...
But it gave me the option to save it as something else, then proceeded with the rest of the import as normal.
Regards,
Doug
(Software Jockey striving to be a better Planner)
I was wondering if anyone has run across this issue before. When I try to import a Microsoft Project File into P5, the process runs correctly, but when it opens the MSP file it says it is read only and a copy needs to be made.
Irrespective of whether I allow a copy of cancel the dialog box, the process completes running, but fails to create the new Project in P5.
I get the "Process completed with errors. See log file for details." message and my log contains this.
INFORMATION: Creating temporary working file...
*** ERROR ***: Unable to open file T:\DougB\V634-307 MMPM.mpp. - An unexpected error occurred with the method
INFORMATION: Importing Global Data...
But it gave me the option to save it as something else, then proceeded with the rest of the import as normal.
Regards,
Doug
(Software Jockey striving to be a better Planner)
3 replies
Oldest first- 0Dieter Wambach ·Douglas
I assume that you don’t have write access to drive T:. Especially to arrange (code-)tables, temporary files have to be built. As far as I remember, the location is indicated during the installation process.
In former times lack of space would be another reason.
Regards
Dieter
- 0Douglas Byles ·Hi all,
The answer turned out to be something completely unexpected.
(For us at least).
By nature of the way, the other dept creates their Microsoft Projects, the Project Summary Task is hidden. This Summary task contains a very long detailed set of notes, which causes a Microsoft Project Warning to occur.
This warning caused the import to fail. By removing the long notes, the warning no longer occurred and the imports were successful.
thank you for your feedback, we have also fed that into our "Things to remember".
Regards
Doug
Log in or join to reply
ProjectControls.com is free to join. Members can post questions, reply, vote and follow discussions.
Existing members: your original username and password still work. Forgot password?