Error when add lines in pwa2007 timesheet

[Sam]

In pwa2007 when i add a line in timesheet which comes from a project plan and
then click a save .

I get the error . "While communicating with the Project Server an error
occured. Check connectivity with your administrator to determine if further
action is necessary. "

the changes made to the timesheet are not updated.

pls reply me soon.

 

[MShayeb]

Dear Sam
Please check the queue and the event view at the server , if you find an
error on the queue please post it

 

[Andrew Stokes]

Hi Sam

I have had problems with the add lines feature of Project Server 2007 since
an update last year. This may not be the same problem but it's worth a try.

When a project (any project to which the resource is assigned) contains
tasks with a blank title Project Server fails on this Null value whenever the
'Add Lines' feature is used. The solution to this is to ensure that all
tasks in all projects have titles. I've found that it's easy to accidentally
add a resource to a blank task at the end of a project without noticing.
When Project Server queries the database for tasks for which this user has
been assigned it bombs out on the blank title.

we ran the following stored procedure:-

exec MSP_WEB_SP_QRY_GetAssnToAddToTimesheet
@resUID='12345F-50C2-4464-B0DB-C826B186E7F3'

--- against Project Server Published database (replace the GUID with the
GUID of the resource).
We found out a Project where there was a orphaned task (a task with some
data but without a task name).
We opened this project in Project Professional, deleted this task, saved and
re-published the project plan and the problem was resolved.

Andy

 

[Malik Al-Shayeb]

Hi Andrew
is this the same case where the resource recives an email with this subject
"Your queue job TimesheetUpdate failed."
and

<errinfo>
<general>
<class name="User is attempting to update an assignment they do not own">
<error id="20010" name="GeneralSecurityAccessDenied"
uid="e92bc059-4a9e-42d7-b05d-97fa262f3fd1" />.
even thou the resource are assigned to the task and all the resources witth
this problem have nothing in my task page .

and what should i see when i execute the stored procedure ?

all i got is 0 rows effected

Best Regards Malik

 

[Andrew Stokes]

Hi Malik

I'm not sure if it is the cause of the problem you describe but running this
stored procedure should display all of the tasks and projects where the
resource has been assigned (essentially the same list the resource will see
if they click 'Add Lines' in their timesheets).

Make sure that you use the GUID of the resource you're having problems with.
The resource's GUID is available from the 'System Identification Data'
section of a resource's details when you edit a resource in the resource
center. I ran the stored procedure in SQL management studio by right
clicking on it and choosing 'Execute Stored Procedure' and give it the
resource GUID surrounded by 'single quotes'.

The problem shows up as NULL values in the TASK_BASE_NAME of the resulting
data.

Andy

 

[Mark E. Read]

Hi Malik

I'm not sure if it is the cause of the problem you describe but running this
stored procedure should display all of the tasks and projects where the
resource has been assigned (essentially the same list the resource will see
if they click 'Add Lines' in their timesheets).

Make sure that you use the GUID of the resource you're having problems with.
 The resource's GUID is available from the 'System Identification Data'
section of a resource's details when you edit a resource in the resource
center.  I ran the stored procedure in SQL management studio by right
clicking on it and choosing 'Execute Stored Procedure' and give it the
resource GUID surrounded by 'single quotes'.

The problem shows up as NULL values in the TASK_BASE_NAME of the resulting
data.

Andy









- Show quoted text -

I have seen this a lot in a weak domain controller environment, and
have found if I save my timesheet, and delete the blank line and re-
add it that it appears correctly. Not sure how this is related, but
it does seem fairly widespread here.

--Mark