Error Building Team from Enterprise

[Christina]

Has anyone run into the following error? If so, how did you fix it?

"An imiport error occurred.
Check row 69 column Reserved_ResumeDate
This is not a valid date, or it is ouside the range for dates, which is
January 1, 1984 through December 31, 2049
Type a date in the correct format: for example, 6/15/00 or June 15,2000."

It then allows me to continue with errors, continue with no errors or stop
importing. If I select to continue importing, I receive a second error
message that is very similar but references Reserve_StopDate.

We are on Project Server 2003, Project Pro 2003 and have installed SP2.

Thanks!
Christina

 

[Ben Howard]

Certainly somewhere a date on the resource is invalid. I would check all the
dates, including the rate tables. Can you be more specific about whether is
is in Build Team from Enterprise or if you are trying to import the resources
as part of another project.

 

[Marc-Andr?]

I just got the same problem.
Those columns seems to exist in previous version of MSProject (in Table Reserved_AssignmentPoolInfo) but I cant find it in 2003. It appear that the bug is fixed by SP1, but we have sp2a as well.

What might have cause the problem on our side is a resource has been put inactive, then someone tried to force (using adjust actual) time.

I saw that error once before, we managed to find which project was causing the error, get a local copy of the project, then delete the published version from your server. See if you have the same problem locally and verify if you get date out of scope (i.e a resource that you close its calendar or work to 0% has time assigned)

Then reload the project and push back the time in PWA. *** CAUTION *** if you entered time manually into Project Pro (not using PWA), you wont be able to push the time back (since it is using Protected Actuals), in that case get a snap shot of time entered and reenter manually....

Good luck.

BTW I still hope someone has another hint for me also!

Thanks

MA

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

 

[Christina]

The error occurs when I select Build Team from Enterprise, and it occurs both
in an existing project as well as a brand new one. So I don't even know
which resource could be causing the issue.

Pardon my ignorance but when you say to check the rate tables, where do I
need to be looking.

Thank you!
Christina

 

[Christina]

Thank you for your thoughts! I was starting to think that I was going nuts
and was the only one experiencing this issue. What's interesting is that
this error occurred the day after I had to manually fix some orphan tasks in
the database, as well as to force some tasks as showing as complete. I can't
imagine that I did anything to impact a date format anywhere but that is the
only thing I can think of. At this point it doesn't "appear" to be causing
any issues other than confusion for our other project managers. But, I'd
still like to get the issue resolved. I will let you know if we figure it
out.

Thanks!
christina

 

[Ben Howard]

Hi,
Does the issue occur if you uncheck the load summary resources checkbox in
when project starts?

To check the rate tables, I'd open all the resources in the Enterprise
resource pool, double click on a resource, select the costs tab, and check
the effective data for the rate tabs A-E.

 

[Christina]

hi Ben-

I have looked at a couple of resources and checked the Effective Date in the
Rates Tab (however, we don't currently use this functionality). If we do
not enter rates in any of these tabs, I should expect to see the Effective
Date to be blank, correct?

I receive this error even if I start with a blank project and click on
"Build Team from Enterprise". However, if I open Microsoft Project and DO
NOT select "Load Summary Resource Assignments", I do NOT receive the error
when selecting Build Team from Enterprise. So.... do you have any thoughts
on what that means?

Thanks!
Christina

 

[Ben Howard]

Hi Christina,
There was a bug with summary resource assignments, but it was fixed in a
hotfix post SP1, so I guess it's worth double-checking that your server is
patched correctly to SP2a, and the clients to SP2.

Failing that, my old suggestion would be to get hold of a SQL guy and try
and find the relevant resource summary table and check for invalid dates in
there.

Alas, I can help you no further than this. Hope I was able to help though.

 

[Christina]

Hi Ben-

Thank you for your help. We are going to look into having a consultant come
out to look at our database, as well as address some other issues we are
having.

Thanks-
Christina