D
Derek Bolan
As a Project Server admin, I regularly modify the groups that
individual users belong to (from Web Access, select Admin -> Manage
users and groups -> Users ->(select user) -> Modify User). I make the
modifications, click Save Changes and receive "The user could not be
created. Check the spelling of the user name, verify that a valid
domain name was included, and check that a duplicate domain was not
used." This error occurs when modifying any account except my own.
Note that the user had previouly been successfully created and that in
our implementation of Project Server, we force Windows Authentication
for all accounts.
I have verified the spelling of the user and domain names, and
examined the MSP_WEB_RESOURCES table to ensure that there are no
duplicate accounts. Note also that the user is up and running,
receiving assignments and otherwise apparently happy!
I have discovered a work-around whereby instead of adding the group to
the user, I add the user to the group (from Web Access, select Admin
-> Manage users and groups -> Groups -> (select group) -> Modify Group
-> add user to group). While this works nicely, I'm waiting for
whatever the problem is to come bite me in another way.
PS. This function worked a few weeks ago - I'm convinced that
something changed on the network side, but the network folks claim
that nothing has changed.
Anyone have any ideas on what I should be looking at in order to track
this down?
individual users belong to (from Web Access, select Admin -> Manage
users and groups -> Users ->(select user) -> Modify User). I make the
modifications, click Save Changes and receive "The user could not be
created. Check the spelling of the user name, verify that a valid
domain name was included, and check that a duplicate domain was not
used." This error occurs when modifying any account except my own.
Note that the user had previouly been successfully created and that in
our implementation of Project Server, we force Windows Authentication
for all accounts.
I have verified the spelling of the user and domain names, and
examined the MSP_WEB_RESOURCES table to ensure that there are no
duplicate accounts. Note also that the user is up and running,
receiving assignments and otherwise apparently happy!
I have discovered a work-around whereby instead of adding the group to
the user, I add the user to the group (from Web Access, select Admin
-> Manage users and groups -> Groups -> (select group) -> Modify Group
-> add user to group). While this works nicely, I'm waiting for
whatever the problem is to come bite me in another way.
PS. This function worked a few weeks ago - I'm convinced that
something changed on the network side, but the network folks claim
that nothing has changed.
Anyone have any ideas on what I should be looking at in order to track
this down?