Enterprise Resource Windows ID/email don't "stick" - weird workaround

J

Jack Kohn

Here's a weird one.

We're running Project 2003 server. A manager got errors attempting to
publish a project. When I examined his project, an Enterprise Resource
he used had no Windows ID or email address, so MSProject could not map
the resource appropriately. (BTW - The resource happens to be a
long-term consultant - not a regular employee - but he has a Windows
domain ID.)

I figured I screwed up when adding the resource. So I went to fix it.
Every time I opened the consultant's Resource Information in MSP Pro,
both the Windows domain ID and email address fields were blank. (I
re-input the information several times both by manually typing and by
using the "Windows Account..." button.)

Further, I could see the email/Windows ID information when I browsed
the SQL table MSP_WEB_RESOURCES. When I viewed the consultant's User
info in Web Access, the ID and email were there, too.

Troubleshooting, I deleted and recreated this resource a couple times,
always with the same effect. I even created another test resource
(someone in our Windows domain but not an MS Project user) following
the same steps. The test resource worked fine; but after adding the
consultant as a resource to a project, his WinID/email fields still
weren't coming over.


Now - for the weird part. Finally, in desperation as a workaround, I
created a local Windows account on the MSProject server for the
consultant. I reset the consultant's Resource Info to use the new
local windows account. Then I added the resource to a test project and
examined his info and it showed.... his DOMAIN Windows account!

Has anyone ever seen this?? Is there a logical explanation???

Thanks in advance for any thoughts.

-jmk
 
Top