Error when "My Tasks" is selected in PWA 2007

[anovak]

One of my pilot testers is getting this error. However, he is the
ONLY one on the team having this problem when reporting time in PWA
with a VMWare virtual client we had build for everyone to use (we're
using that cause we're still on Novell and the VM is Windows-
only). See below.

Any insight would be appreciated.

Thanks,
Andy Novak
UNT


Whenever I click on the "My Task" hyperlink, I get the following
Message:

Error


An unexpected error has occurred.

Web Parts Maintenance Page: If you have permission, you can use this
page to temporarily close Web Parts or remove personal settings. For
more information, contact your site administrator.
Troubleshoot issues with Windows SharePoint Services.

 

[Daniel McG]

I had this error once as well. I was messing around with my test project and
I put myself back on as a resource. It seemed to have something to do with
the way I entered myself as a resource. It would give me that same error
message, so I went back into edit the project and re-entered the resources
and then everything was fine.

 

[Jonathan Sofer]

The cause could be due to known bug in MSPS 2007 - My Tasks.
Cause:
When a second resource is being assigned to a task that has a Work %
Completed > 0.

Behaviour:
The second resource will be presented the unexpected error.

Solution:
See posting below for a workaround:
http://groups.google.com/group/micr...server/browse_thread/thread/29c8d035bb1cae3d#

Hope this helps,

Jonathan

 

[Ravi]

The cause could be due to known bug in MSPS 2007 - My Tasks.
Cause:
When a second resource is being assigned to a task that has a Work %
Completed > 0.

Behaviour:
The second resource will be presented the unexpected error.

Solution:
See posting below for a workaround:http://groups.google.com/group/microsoft.public.project.server/browse...

Hope this helps,

Jonathan










- Show quoted text -

Yes Jonathan,

Its absolutely correct and this issue has been resolved in SP1. Thank
you for the wonderful writeup of this issue!

Thanks,
Ravi

 

[Jim Erwin]

this link should help: http://ebilal.spaces.live.com/blog/cns!1EB5037F50572440!819.entry

 

[anovak]

this link should help:http://ebilal.spaces.live.com/blog/cns!1EB5037F50572440!819.entry

I would argue that it has NOT been resolved in SP1. We have been on
SP1 for quite some time now.

 

[Jonathan Sofer]

I agree. As far as I was aware, this issue has not been resolved in SP1 and
no hotfixes have been released to fix this. The workaround that was
provided is the only currently viable solution.

Jonathan

this link should
help:http://ebilal.spaces.live.com/blog/cns!1EB5037F50572440!819.entry

I would argue that it has NOT been resolved in SP1. We have been on
SP1 for quite some time now.

 

[Ravi]

I agree.  As far as I was aware, this issue has not been resolved in SP1and
no hotfixes have been released to fix this.  The workaround that was
provided is the only currently viable solution.

Jonathan




I would argue that it has NOT been resolved in SP1.   We have been on
SP1 for quite some time now.

Okay, my earlier deployment was 2007 w/o SP1. When SP1 was rolled out
this issue was given as resolved and I recall the MS engineers told
the same. If not really, them I was wrong.

 

[Barbara - Austria]

It is solved with April's hotfix. Have a look at KB 950816.