Project integrity report - Project/WBS mismatch
Forum Sponsor
Top Posters
Nick Johnson-Pond
3 posts
sairedz25
0 posts
Ahmed Awad
2 posts
Syed Shoeb
0 posts
Vimukthi
0 posts
bal aji
2 posts
Lee Mallek
23 posts
Viet Tran
9 posts
Ola Gbotoso
0 posts
Jaturapit Multongka
1 posts
Ellyn
Sorry for bad expression.
Try to add a new document and assign it to an activity and to a WBS --> F10 (Commit changes) --> F5 --> delete --> run integrity check.
Target of this action is to write into the table with the documents then to write again - the deletion-flag. My hope is that Oracle or MS-SQL recognizes a mismatch and corrects. Same idea as for the WBS.
(Ive some impression of a bug in P7 or in the transfer program from P6 to P7)
Good luck!
Dieter
Ellyn
Sorry, I have no experience with P7. Was there everything ok with the transfer of the database to the new version - log-file checked? Check Primavera POINT for a known error.
Recently I had that issue (WBS mismatch) as well. Since didnt like to take the risk of using SQL in a productive system, I tried inside P6:
- Checked if someone else was working with that project -->
- Opened exclusively -->
- Added WBS --> F9 --> deleted this WBS --> ran integrity check
After three - why, I have no idea - times this error disappeared. I would try anologue with a document.
Good luck!
Dieter
Maya
This error is a little dangerous. There seems to be a mismatch within the projwbs table. If you dont report progress via time sheets, create a new project and move everything of the damaged into the new project.
As far as I remember there was an issue in 5.0 but solved by a patch. Check if you installed all service packs.
Good luck
Dieter