Re: Cannot import resource into enterprise - invalid windows account
- From: "R Segawa" <rsegawa(remove)@terra.com.br>
- Date: Wed, 22 Jun 2005 16:30:40 -0300
Hi Jeffrey,
I think some problems are cascading into others.
The right steps are:
a) Configure the project pro to connect to project server.
b) Using an account of administrator in PWA, open Project Pro and open
the Enterprise Resource Pool.
c) Enter at least, the resource name, windows account in the format
<domain>\<username> (if you will use a Windows account) and e-mail and save
and close the pool. Create a different set of users from User1, 2, etc to
avoid conflict with existing accounts.
d) Go to PWA using an administrator account and change the resources to
the right group, for instance, User1 will belong to project managers group
to allow publish a project.
e) Open Project Pro using at least a Project manager group account,
create tasks, link them and create a team using the build team from
enterprise command in the Tools menu. Choose the resources from the pool and
close the dialogue bos.
f) Assign resources to the tasks.
g) Publish the project (if you have required enterprise fields or
codes, fill them first). This will start the fun.
Below are some hints:
1. A resource created in the enterprise pool is always a user in PWA, but a
user created in PWA does not belong to resource pool necessarily. You are
right that creating a resource in the pool (using import resources our going
directly to Enterprise Resource Pool), assign a Team Member group profile.
2. After creating in Enterprise Resource Pool, go to PWA and upgrade the
resource to the groups of Project Manager, Resource Manager, etc.
3. If you entered the resource directly in PWA and you are trying to create
in Enterprise Resource Pool, it is important that the resource name and
windows account are the same. The same Windows Account, but different
Resource Name will incur in error message such as invalid resource or
invalid Windows Account. For instance, there are some wrong combinations
below:
Combination 1
PWA: username: User 1, Windows account: domain\user1.
Pool: username: User1, Windows account: domain\user1.
Combination 2;
PWA: username: User1, windows account: blank (Project Server account)
Pool: username: User1, Windows account: domain\user1.
Combination 3:
PWA: username: User1, Windows account: user1
Pool: username: User1, windows account: user1
The right combination is:
PWA: username: User1, Windows account: domain\user1
Pool: username: User1, Windows account: domain\user1
If you create e resource in enterprise resource pool there is no error. It
is straightforward.
4. If a resource that uses windows account such as User1, should fill the
Windows User Account in the format of <domain name>\<user account>. If you
leave it blank, it will create a Project Server Account.
Good luck
R.Segawa
"C.K. Au, Jeffrey" <jack208@xxxxxxxxxxxxxxxxx> wrote in message
news:hhqgb19mrq6bfmprq3ocoi51ktbsgef5aa@xxxxxxxxxx
> Hi
>
> I've created some resources in a local MPP file and are trying to
> import them into the Enterprise server.. and kept having "Invalid
> Windows Account" error... I would like to ask some questions to
> clarify user and resource creation before I proceed.
>
> 1. Resources when imported into Enterprise will also be created as
> Users but with Team Member role only, right? If this is the case,
> should we actually still create "users" in PWA itself or should we
> just let the Import Resource step do the creation?
>
> Or to put it another way, under what circumstances do we need to
> create users at the PWA level?
>
> 2. I've a "resource" project (MPP) which basically contains only 4
> resources. One of them has a matching user account in PWA, the other
> three are not related. There's actually only three users in PWA:
> Administrator, User1 and User2.
>
> User1 is set as a Win authenticated user (and is the one with matching
> resource above). User2 is a pure Project Server user.
>
> 3. User2 above was created from the "Open Enterprise Resource Pool"
> option by checking out Enterprise Resources and adding the new
> resource.
>
> 4. I am using the Import Resources to Enterprise function from Tools
> menu to import the resources from the MPP file.
>
> As I go thru the Import Wizard, I'll soon reach the page where it
> displays the list of the 4 resources but with the following data/info
> in the columns:
> - Error: "Invalid windows account" in all 4 rows
> - Resource Name: the respective name for the resources
> - Windows Account: the AD user account for the resource (these are
> valid and active AD user accts). These are all in red! Format is
> "DOMAIN\useracct"
> - Base Calendar: changd to "CG Calendar" which is an Enterprise
> calendar
>
> At this stage, I am unable to proceed further.
>
> 5. We've also looked at the MSP_Web_Resources table and found it has
> only three rows (as expected):
> - Administrator
> - User1
> - User2
>
> 6. The user acct we used to log in for MS Project Pro 2003 is User1
> who is a Portfolio Manager, Resource Manager etc. He certainly have no
> problem creating User2 via the Checked Out Enterprise option
>
> 7. We've googled on this issue but could not find anything conclusive.
>
> Whew, this is long.. appreciate you taking your time to read this (if
> you read this far!!)
>
> If you need any other info, pls ask. Hope someone can tell us where we
> didn't do right.... :P
>
> NOTE:
> There was once when one of the user was allowed to be imported. So we
> proceed... but in the end Project Pro 2003 gave me this error
>
> Project Server encountered a problem with this error code: 2026
> Please contact your server administrator.
>
>
.
- References:
- Cannot import resource into enterprise - invalid windows account
- From: C.K. Au, Jeffrey
- Cannot import resource into enterprise - invalid windows account
- Prev by Date: Re: Inconsistent prompting for Windows logon
- Next by Date: Copy Views - Two Instances
- Previous by thread: Cannot import resource into enterprise - invalid windows account
- Next by thread: Inconsistent prompting for Windows logon
- Index(es):
Relevant Pages
|
