Lookup tables - BUG

[mike.mahoney]

All

I have a moderately configured PS 2007 system which includes a lot of
project and task lookup tables. At some point in defining custom
fields Project Professional does a wobbler and mixes up data from
different lookup tables. This problem has been confirmed by other
users.

I am desperate for a strategy to retrieve / prevent this situation as
Project, in terms of maintaining custom data, becomes unusable, and
credibility of the system is shot.

Pick lists displayed in PWA seems to be ok and I can devise a process
to update project level codes in this interface, but I also have a
bunch of task level codes which I can only update in Project.

I have back-tracked and deleted some tables and the problem has gone
away but I have no confidence that it will not reappear.

Does anyone have any suggestions to avoid or fix this situation? Does
Microsoft understand the significance of this problem? When will a
patch be available - it can't wait for a service pack.

in hope

Mike

 

[Dale Howard [MVP]]

Mike --

I have seen this problem as well and have reported the bug to Microsoft.
The best I can figure is that the mixup is a "display only" situation. I
believe the data in the background is correct, although it displays
incorrectly in Microsoft Project Professional. I know of no workaround at
this point. I think a hotfix or Service Pack is the only cure. Hope this
helps.

 

[Dale Howard [MVP]]

Marc --

PSS?

Dale,

I'm surprised to hear that. For us it worked everytime, I'm sorry... This
is also the workaround that PSS recommended to us.

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

Marc --

I tried this workaround and it does not work. I suspect the problem is
internal to the software rather than external through the Cache.

Mike,

This is a known bug of the Project Server 2007 release. I expect this
bug to be addressed in SP1, although it has not yet been announced when
the first service pack will become available. All I heard is that the SP
for Project Server 2007 will be released together with SP1 for all 2007
Office products. No idea on the timeline though...

However, there is a workaround for this issue which is obviously caused
by the Active Cache in Project Pro. Open Windows Explorer and navigate
to C:\Documents and Settings\<user name>\Application Data\Microsoft\MS
Project\Cache\<cacheGUID>. Delete the "global[n].mpc" files or even the
entire <cacheGUID> subfolders in \Cache. Make sure the application is
not running while you're doing this.

Hope this helps...

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

All

I have a moderately configured PS 2007 system which includes a lot of
project and task lookup tables. At some point in defining custom
fields Project Professional does a wobbler and mixes up data from
different lookup tables. This problem has been confirmed by other
users.

I am desperate for a strategy to retrieve / prevent this situation as
Project, in terms of maintaining custom data, becomes unusable, and
credibility of the system is shot.

Pick lists displayed in PWA seems to be ok and I can devise a process
to update project level codes in this interface, but I also have a
bunch of task level codes which I can only update in Project.

I have back-tracked and deleted some tables and the problem has gone
away but I have no confidence that it will not reappear.

Does anyone have any suggestions to avoid or fix this situation? Does
Microsoft understand the significance of this problem? When will a
patch be available - it can't wait for a service pack.

in hope

Mike

 

[Marc Schoeni]

Mike,

This is a known bug of the Project Server 2007 release. I expect this bug to
be addressed in SP1, although it has not yet been announced when the first
service pack will become available. All I heard is that the SP for Project
Server 2007 will be released together with SP1 for all 2007 Office products.
No idea on the timeline though...

However, there is a workaround for this issue which is obviously caused by
the Active Cache in Project Pro. Open Windows Explorer and navigate to
C:\Documents and Settings\<user name>\Application Data\Microsoft\MS
Project\Cache\<cacheGUID>. Delete the "global[n].mpc" files or even the
entire <cacheGUID> subfolders in \Cache. Make sure the application is not
running while you're doing this.

Hope this helps...

 

[mike.mahoney]

Mike,

This is a known bug of the Project Server 2007 release. I expect this bug to
be addressed in SP1, although it has not yet been announced when the first
service pack will become available. All I heard is that the SP for Project
Server 2007 will be released together with SP1 for all 2007 Office products.
No idea on the timeline though...

However, there is a workaround for this issue which is obviously caused by
the Active Cache in Project Pro. Open Windows Explorer and navigate to
C:\Documents and Settings\<user name>\Application Data\Microsoft\MS
Project\Cache\<cacheGUID>. Delete the "global[n].mpc" files or even the
entire <cacheGUID> subfolders in \Cache. Make sure the application is not
running while you're doing this.

Hope this helps...

--
Marc
MCP for EPMwww.diventis.chwww.msepm.blogspot.com

All

I have a moderately configured PS 2007 system which includes a lot of
project and task lookup tables. At some point in defining custom
fields Project Professional does a wobbler and mixes up data from
different lookup tables. This problem has been confirmed by other
users.

I am desperate for a strategy to retrieve / prevent this situation as
Project, in terms of maintaining custom data, becomes unusable, and
credibility of the system is shot.

Pick lists displayed in PWA seems to be ok and I can devise a process
to update project level codes in this interface, but I also have a
bunch of task level codes which I can only update in Project.

I have back-tracked and deleted some tables and the problem has gone
away but I have no confidence that it will not reappear.

Does anyone have any suggestions to avoid or fix this situation? Does
Microsoft understand the significance of this problem? When will a
patch be available - it can't wait for a service pack.

in hope

Mike- Hide quoted text -

- Show quoted text -

Marc

Thanks this gives me away forward

regards

Mike

 

[Marc Schoeni]

Mike,

Also see my blog for more detail on the workaround for this bug:
www.msepm.blogspot.com

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

Mike,

This is a known bug of the Project Server 2007 release. I expect this bug
to
be addressed in SP1, although it has not yet been announced when the
first
service pack will become available. All I heard is that the SP for
Project
Server 2007 will be released together with SP1 for all 2007 Office
products.
No idea on the timeline though...

However, there is a workaround for this issue which is obviously caused
by
the Active Cache in Project Pro. Open Windows Explorer and navigate to
C:\Documents and Settings\<user name>\Application Data\Microsoft\MS
Project\Cache\<cacheGUID>. Delete the "global[n].mpc" files or even the
entire <cacheGUID> subfolders in \Cache. Make sure the application is not
running while you're doing this.

Hope this helps...

--
Marc
MCP for EPMwww.diventis.chwww.msepm.blogspot.com

All

I have a moderately configured PS 2007 system which includes a lot of
project and task lookup tables. At some point in defining custom
fields Project Professional does a wobbler and mixes up data from
different lookup tables. This problem has been confirmed by other
users.

I am desperate for a strategy to retrieve / prevent this situation as
Project, in terms of maintaining custom data, becomes unusable, and
credibility of the system is shot.

Pick lists displayed in PWA seems to be ok and I can devise a process
to update project level codes in this interface, but I also have a
bunch of task level codes which I can only update in Project.

I have back-tracked and deleted some tables and the problem has gone
away but I have no confidence that it will not reappear.

Does anyone have any suggestions to avoid or fix this situation? Does
Microsoft understand the significance of this problem? When will a
patch be available - it can't wait for a service pack.

in hope

Mike- Hide quoted text -

- Show quoted text -

Marc

Thanks this gives me away forward

regards

Mike

 

[Dale Howard [MVP]]

Marc --

I tried this workaround and it does not work. I suspect the problem is
internal to the software rather than external through the Cache.

Mike,

This is a known bug of the Project Server 2007 release. I expect this bug
to be addressed in SP1, although it has not yet been announced when the
first service pack will become available. All I heard is that the SP for
Project Server 2007 will be released together with SP1 for all 2007 Office
products. No idea on the timeline though...

However, there is a workaround for this issue which is obviously caused by
the Active Cache in Project Pro. Open Windows Explorer and navigate to
C:\Documents and Settings\<user name>\Application Data\Microsoft\MS
Project\Cache\<cacheGUID>. Delete the "global[n].mpc" files or even the
entire <cacheGUID> subfolders in \Cache. Make sure the application is not
running while you're doing this.

Hope this helps...

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

All

I have a moderately configured PS 2007 system which includes a lot of
project and task lookup tables. At some point in defining custom
fields Project Professional does a wobbler and mixes up data from
different lookup tables. This problem has been confirmed by other
users.

I am desperate for a strategy to retrieve / prevent this situation as
Project, in terms of maintaining custom data, becomes unusable, and
credibility of the system is shot.

Pick lists displayed in PWA seems to be ok and I can devise a process
to update project level codes in this interface, but I also have a
bunch of task level codes which I can only update in Project.

I have back-tracked and deleted some tables and the problem has gone
away but I have no confidence that it will not reappear.

Does anyone have any suggestions to avoid or fix this situation? Does
Microsoft understand the significance of this problem? When will a
patch be available - it can't wait for a service pack.

in hope

Mike

 

[Marc Schoeni]

Dale,

I'm surprised to hear that. For us it worked everytime, I'm sorry... This is
also the workaround that PSS recommended to us.

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

Marc --

I tried this workaround and it does not work. I suspect the problem is
internal to the software rather than external through the Cache.

Mike,

This is a known bug of the Project Server 2007 release. I expect this bug
to be addressed in SP1, although it has not yet been announced when the
first service pack will become available. All I heard is that the SP for
Project Server 2007 will be released together with SP1 for all 2007
Office products. No idea on the timeline though...

However, there is a workaround for this issue which is obviously caused
by the Active Cache in Project Pro. Open Windows Explorer and navigate to
C:\Documents and Settings\<user name>\Application Data\Microsoft\MS
Project\Cache\<cacheGUID>. Delete the "global[n].mpc" files or even the
entire <cacheGUID> subfolders in \Cache. Make sure the application is not
running while you're doing this.

Hope this helps...

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

All

I have a moderately configured PS 2007 system which includes a lot of
project and task lookup tables. At some point in defining custom
fields Project Professional does a wobbler and mixes up data from
different lookup tables. This problem has been confirmed by other
users.

I am desperate for a strategy to retrieve / prevent this situation as
Project, in terms of maintaining custom data, becomes unusable, and
credibility of the system is shot.

Pick lists displayed in PWA seems to be ok and I can devise a process
to update project level codes in this interface, but I also have a
bunch of task level codes which I can only update in Project.

I have back-tracked and deleted some tables and the problem has gone
away but I have no confidence that it will not reappear.

Does anyone have any suggestions to avoid or fix this situation? Does
Microsoft understand the significance of this problem? When will a
patch be available - it can't wait for a service pack.

in hope

Mike

 

[Jay Carter]

We tried the same fix, and it generally corrected the problem. Unfortunately,
we have one project (there might be more?) that still shows bad data in the
lookup dropdowns. Also, when you show a gantt chart (right side of slider
bar), that side of the window flickers and the cursor goes to hourglass and
back to pointer constantly. The only way I can see to turn it off is to turn
off automatic calculations.

The active cache doesn't solve the problem. We can open the project on a
different computer that has never opened the project, and the same flickering
behavior occurs.

--
Oakwood Systems Group: http://www.oakwoodsys.com

Dale,

I'm surprised to hear that. For us it worked everytime, I'm sorry... This is
also the workaround that PSS recommended to us.

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

Marc --

I tried this workaround and it does not work. I suspect the problem is
internal to the software rather than external through the Cache.

Mike,

This is a known bug of the Project Server 2007 release. I expect this bug
to be addressed in SP1, although it has not yet been announced when the
first service pack will become available. All I heard is that the SP for
Project Server 2007 will be released together with SP1 for all 2007
Office products. No idea on the timeline though...

However, there is a workaround for this issue which is obviously caused
by the Active Cache in Project Pro. Open Windows Explorer and navigate to
C:\Documents and Settings\<user name>\Application Data\Microsoft\MS
Project\Cache\<cacheGUID>. Delete the "global[n].mpc" files or even the
entire <cacheGUID> subfolders in \Cache. Make sure the application is not
running while you're doing this.

Hope this helps...

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

All

I have a moderately configured PS 2007 system which includes a lot of
project and task lookup tables. At some point in defining custom
fields Project Professional does a wobbler and mixes up data from
different lookup tables. This problem has been confirmed by other
users.

I am desperate for a strategy to retrieve / prevent this situation as
Project, in terms of maintaining custom data, becomes unusable, and
credibility of the system is shot.

Pick lists displayed in PWA seems to be ok and I can devise a process
to update project level codes in this interface, but I also have a
bunch of task level codes which I can only update in Project.

I have back-tracked and deleted some tables and the problem has gone
away but I have no confidence that it will not reappear.

Does anyone have any suggestions to avoid or fix this situation? Does
Microsoft understand the significance of this problem? When will a
patch be available - it can't wait for a service pack.

in hope

Mike

 

[Dale Howard [MVP]]

Jay --

Thanks for sharing that the Cache does not solve all the problems. I think
this is an issue that Microsoft needs to address in a Service Pack. Hope
this helps.

We tried the same fix, and it generally corrected the problem.
Unfortunately,
we have one project (there might be more?) that still shows bad data in
the
lookup dropdowns. Also, when you show a gantt chart (right side of slider
bar), that side of the window flickers and the cursor goes to hourglass
and
back to pointer constantly. The only way I can see to turn it off is to
turn
off automatic calculations.

The active cache doesn't solve the problem. We can open the project on a
different computer that has never opened the project, and the same
flickering
behavior occurs.

--
Oakwood Systems Group: http://www.oakwoodsys.com

Dale,

I'm surprised to hear that. For us it worked everytime, I'm sorry... This
is
also the workaround that PSS recommended to us.

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

"Dale Howard [MVP]" <dale(dot)howard(at)msprojectexperts(dot)com> wrote
in
message news:[email protected]...

Marc --

I tried this workaround and it does not work. I suspect the problem is
internal to the software rather than external through the Cache.





Mike,

This is a known bug of the Project Server 2007 release. I expect this
bug
to be addressed in SP1, although it has not yet been announced when
the
first service pack will become available. All I heard is that the SP
for
Project Server 2007 will be released together with SP1 for all 2007
Office products. No idea on the timeline though...

However, there is a workaround for this issue which is obviously
caused
by the Active Cache in Project Pro. Open Windows Explorer and navigate
to
C:\Documents and Settings\<user name>\Application Data\Microsoft\MS
Project\Cache\<cacheGUID>. Delete the "global[n].mpc" files or even
the
entire <cacheGUID> subfolders in \Cache. Make sure the application is
not
running while you're doing this.

Hope this helps...

--
Marc
MCP for EPM
www.diventis.ch
www.msepm.blogspot.com

All

I have a moderately configured PS 2007 system which includes a lot of
project and task lookup tables. At some point in defining custom
fields Project Professional does a wobbler and mixes up data from
different lookup tables. This problem has been confirmed by other
users.

I am desperate for a strategy to retrieve / prevent this situation as
Project, in terms of maintaining custom data, becomes unusable, and
credibility of the system is shot.

Pick lists displayed in PWA seems to be ok and I can devise a process
to update project level codes in this interface, but I also have a
bunch of task level codes which I can only update in Project.

I have back-tracked and deleted some tables and the problem has gone
away but I have no confidence that it will not reappear.

Does anyone have any suggestions to avoid or fix this situation? Does
Microsoft understand the significance of this problem? When will a
patch be available - it can't wait for a service pack.

in hope

Mike