When I found such variances, in general there was a simple reason:
MSP allows to relate group elements (WBS), which is not accepted by P6. For each WBS P6-Import creates an activity of the type "wbs summary". After import the links are still there, but they are ignore by the scheduling algorithm. Then the start of the successor will move onto the data date.
- Is there a resource assignment with a curve? Check the curve. If the project originally comes from P3, some of the P3-curves are not supported in P6.
- Whats the activitys status - started, planned.
- if not started, modify planned duration --> F10 (system must write into database) --> F5 --> F9 --> Planned duration back to the old value again --> F10 --> F5 --> F9.
- Then try the export again - xer. If this works, then to mpp
I tried what you proposed.. I exported the project in P6.1 version & re-imported the project in different EPS... Unfortunately I get the same error message after exporting to MPP.
When done, it says..Process completed with Errors..
And Log file shows following entry for each activity in schedule:
INFORMATION: Exporting Activity: [ASPD900] Completion of Concreting
*** ERROR ***: Exporting Activity [ASPD900] Completion of Concreting: The argument value is not valid
I am not sure where I m going wrong but the Export worked perfectly well few months back. Am I doing some mistake in the MPP export template parameters or is it something else ?
I am really struggling with this now. Any pointers will be great help.
Thanks
Sue
Member for
18 years 9 months
Member for18 years9 months
Submitted by Dieter Wambach on Mon, 2009-12-14 06:23
Member for
14 years 11 monthsHi Susan,Try exporting to XML
Hi Susan,
Try exporting to XML 2007 or XML 2003 format
Thanks
Amit Parmar
Member for
15 yearsCan you help me import excel
Can you help me import excel file into P6 v7? Is there somewhere I can find instruction and/or example? Thanks
Member for
18 years 9 monthsRE: HELP ! Error during MPP export
Hi Sue
When I found such variances, in general there was a simple reason:
MSP allows to relate group elements (WBS), which is not accepted by P6. For each WBS P6-Import creates an activity of the type "wbs summary". After import the links are still there, but they are ignore by the scheduling algorithm. Then the start of the successor will move onto the data date.
Regards
Dieter
Member for
22 years 8 monthsRE: HELP ! Error during MPP export
OK I figured that the problem was with the calendars. Project default calander was not right.
However after export, I find a huge variance in dates between MSP & Primavera. (excess of 400 days for some activities)
I am aware that a exact export of dates wont be possible, but is there a easy way wherein i could perhaps im[pose the Primavera date in MSP schedule ?
Sue
Member for
23 years 8 monthsRE: HELP ! Error during MPP export
Any special character/symbol is used for resource name and ID?
If have, change to normal character
Member for
22 years 8 monthsRE: HELP ! Error during MPP export
Still doesnt work
Member for
22 years 8 monthsRE: HELP ! Error during MPP export
Hello Dieter,
There are no Errorsin the log file.
:-(
Member for
18 years 9 monthsRE: HELP ! Error during MPP export
Hello Susan
This messages says: ITs ok.
Check this log file for "error".
Regards
Dieter
Member for
22 years 8 monthsRE: HELP ! Error during MPP export
Hello Dieter,
Thankyou for your suggestions !
Tried the steps you suggested. The schedule is not resource loaded so the result of Integrity test was ok with following message:
2. Check Activity Resource Assignment for: Project mis-match between Activity Resource Assignments and Activities
>>>OK
I had just pasted activity ASPD900 as an example. In fact this error message is against each of 2000 activities in schedule :-(
I am out of ideas now.
Susan
Member for
18 years 9 monthsRE: HELP ! Error during MPP export
Susan
So the reason seem to be within your project - activity ASPD900; not the export Concentrate on this activity.
- Run Tools --> Check Project Integrity --> read log file
- Is there a resource assignment with a curve? Check the curve. If the project originally comes from P3, some of the P3-curves are not supported in P6.
- Whats the activitys status - started, planned.
- if not started, modify planned duration --> F10 (system must write into database) --> F5 --> F9 --> Planned duration back to the old value again --> F10 --> F5 --> F9.
- Then try the export again - xer. If this works, then to mpp
Good luck!
Dieter
Member for
22 years 8 monthsRE: HELP ! Error during MPP export
Thanks for the quick response Dieter,
I use MSP 2000.
I tried what you proposed.. I exported the project in P6.1 version & re-imported the project in different EPS... Unfortunately I get the same error message after exporting to MPP.
When done, it says..Process completed with Errors..
And Log file shows following entry for each activity in schedule:
INFORMATION: Exporting Activity: [ASPD900] Completion of Concreting
*** ERROR ***: Exporting Activity [ASPD900] Completion of Concreting: The argument value is not valid
I am not sure where I m going wrong but the Export worked perfectly well few months back. Am I doing some mistake in the MPP export template parameters or is it something else ?
I am really struggling with this now. Any pointers will be great help.
Thanks
Sue
Member for
18 years 9 monthsRE: HELP ! Error during MPP export
Susan
I never had this message but to get a little closer to the reason:
MPP is supported only up to MSP2003 - my assumption that you use higher.
If youll export this project in P6 format and reimport into a different area of you EPS: What happens?
Good luck!
Dieter