Hi folks,

First of all, I apologize for spamming this post on several newsgroup. I
didn't know which one is the most appropriate one to get the answer to
my question since there isn't one specifically for ProjectServer2007.


Background:
I'm instructed to install and administer ProjectServer2007 so that the
company can use it to share and manage Project Pro 2007 files and
resources. Everything went smoothly; everything except one that is.

We encountered no issue when manually adding user to the Project Web
Access workspace. However the scheduled synchronization always generates
an error. What's worse, this error actually checks-out resources and the
checked-out resources would be 'stuck' in checked-out status.

Getting the checked-out status resolved is not a problem as the database
record/values can be easily updated back to check-in status (i.e. NULL).
/*
update target
set target.res_checkoutby = null
from msp_resources target
where target.res_checkoutby is not null
-- and target.res_checkoutby = cast(0 as uniqueidentifier)
*/

And it all would be fine, except we are trying to schedule a daily AD
resync.

I suppose I will be fine if I have to keep manually synchronizing it
everyday or as needed. But since the scheduler /is/ there and is
supposed to work but doesn't... well what gives?

Question #1:
Am I doing anything wrong during the installations? (I followed the
instructions to the letter, then some trial and errors to make it right,
but I think all is well).

Question #2:
Has anyone experienced the same thing?

Question #3:
If yes to Q2, how did you resolve it? Hints appreciated. Workable answer
better.

Question #4:
If no to Q2, do you think this is a Microsoft bug?


Thank you all for reading this lengthy post.

Best regards,
~Js.

Re: ProjectServer2007 - Active Directory Synchronization Issue by Mike

Mike
Fri Mar 09 00:24:48 CST 2007

>since there isn't one specifically for ProjectServer2007.

There is an it's micrososft.public.project.server (for both Project Server
2003 and 2007)

Setting follow-up to that to get rid of the rest of your list. In fact to
get rid of all of your list because you don't seem to have posted to a
Project Server newsgroup at all !

Anyone replying in this thread please therefore reply to this message!

Mike Walsh
WSS FAQ http://www.wssfaq.com
No private e-mail please.

"John Smith" <.@.> wrote in message
news:45f06d14$0$24713$4c368faf@roadrunner.com...
> Hi folks,
>
> First of all, I apologize for spamming this post on several newsgroup. I
> didn't know which one is the most appropriate one to get the answer to my
> question since there isn't one specifically for ProjectServer2007.
>
>
> Background:
> I'm instructed to install and administer ProjectServer2007 so that the
> company can use it to share and manage Project Pro 2007 files and
> resources. Everything went smoothly; everything except one that is.
>
> We encountered no issue when manually adding user to the Project Web
> Access workspace. However the scheduled synchronization always generates
> an error. What's worse, this error actually checks-out resources and the
> checked-out resources would be 'stuck' in checked-out status.
>
> Getting the checked-out status resolved is not a problem as the database
> record/values can be easily updated back to check-in status (i.e. NULL).
> /*
> update target
> set target.res_checkoutby = null
> from msp_resources target
> where target.res_checkoutby is not null
> -- and target.res_checkoutby = cast(0 as uniqueidentifier)
> */
>
> And it all would be fine, except we are trying to schedule a daily AD
> resync.
>
> I suppose I will be fine if I have to keep manually synchronizing it
> everyday or as needed. But since the scheduler /is/ there and is supposed
> to work but doesn't... well what gives?
>
> Question #1:
> Am I doing anything wrong during the installations? (I followed the
> instructions to the letter, then some trial and errors to make it right,
> but I think all is well).
>
> Question #2:
> Has anyone experienced the same thing?
>
> Question #3:
> If yes to Q2, how did you resolve it? Hints appreciated. Workable answer
> better.
>
> Question #4:
> If no to Q2, do you think this is a Microsoft bug?
>
>
> Thank you all for reading this lengthy post.
>
> Best regards,
> ~Js.