Forms authentication

[Mike]

I previously had forms authentication working successfully, but had to
reinstall project server.
I set up forms authentication as before. The pjFormsAuthUpgrade
utility works fine it adds accounts to project server, and the
accounts validate and are usable, with the exception that cannot log
on to PWA. When I enter extended web site url the sign in form
presents itself but after entering a correct account and password WSS
returns an "unexpected error" with no further details. Any
suggestions?

Thanks

Mike

 

[Mike]

I previously had forms authentication working successfully, but had to
reinstall project server.
I set up forms authentication as before. The pjFormsAuthUpgrade
utility works fine it adds accounts to project server, and the
accounts validate and are usable, with the exception that cannot log
on to PWA. When I enter extended web site url the sign in form
presents itself but after entering a correct account and password WSS
returns an "unexpected error" with no further details. Any
suggestions?

Thanks

Mike

I am not sure of the correlation but I am noticing some DCOM errors in
the system event log:

The application-specific permission settings do not grant Local
Activation permission for the
COM Server application with CLSID {61738644-
F196-11D0-9953-00C04FD919C1}
to the user CHEYNE\PS-Admin SID
(S-1-5-21-164770905-1455706766-1538882281-9075).
This security permission can be modified using the Component Services
administrative tool.

This relates to this service IISADMIN under DCOM Config and is
repeated for WSS-Admin and SSP-Admin accounts

I suspect on earlier installations these accounts were local admins

Thanks

 

[Rob]

Mike, from the server, Administrative Tools--> Component Services
Expand Component Services->Computers->My Computer->DCOM Config
RIght CLick on IIS WAMREG Admin Service, select Properties.
On the Security tab, click on the EDIT button for Launch and Activation
Permissions.
Add your WSS-Admin and SSP-Admin accounts.

Hope this helps,
-RS

 

[JYX]

Rob,
I got almost exact same problem as Mike... small farm ps 2007 deployment,
web&app tier is on one win2003 box and sql 2005 is on another win2003 box;
extended on port 81 for forms authentication. Followed all the
docs/instructions from MS tech net and got no complains during deployment, I
can see users in the aspnetdb and "manage users" view in pwa when logged in
as admin thru windows auth. But can't log in by using forms authentication,
got the "unexpected error" page. The annoying thing is it doesn't really tell
you anything.
By the way, I got similar error as Mike in the event log too, and tried your
solution it did removed those errors but still can't log in thru forms
authentication.

Any ideas?

Many thanks!
Jerold

 

[mike.mahoney]

Rob,
I got almost exact same problem as Mike... small farm ps 2007 deployment,
web&app tier is on one win2003 box and sql 2005 is on another win2003 box;
extended on port 81 for forms authentication. Followed all the
docs/instructions from MS tech net and got no complains during deployment, I
can see users in the aspnetdb and "manage users" view in pwa when logged in
as admin thru windows auth. But can't log in by using forms authentication,
got the "unexpected error" page. The annoying thing is it doesn't really tell
you anything.
By the way, I got similar error as Mike in the event log too, and tried your
solution it did removed those errors but still can't log in thru forms
authentication.

Any ideas?

Many thanks!
Jerold







- Show quoted text -

Jerold

My problem was self inflicted. To establish forms authentication you
have to set up a connection to the forms database in web.config file
(connection strings). I entered the machine name of the project
server and not the SQL instance name. I corrected this and everything
works fine. So check this.

regards

Mike

 

[JYX]

Mike,
I did setup the connection string. Actually initially I made a mistake in it
(I changed the connection name to something else) and was not even able to
load the users.xml. So it should be something else.

Hopefully someone can shed some light on this.
Jerold

 

[ahelp]

Jerold,
Did you add the Forms users to Project Server Groups?

Now a question from me: After updating the web.config file for the regular
pwa as well as the forms site, I was finally able to add users to aspnetdb.
However, I can't see any of the new forms users in Manage Users or Resource
Center. We have a 3 tier config: SQL, App, Web. Anyone have any ideas on why
Projectserver isn't talking to aspnetdb?
Thanks,
Mike

 

[ahelp]

The log file stops after "Creating user logon," but here is the error after
the command line entry:
Exception occurred: Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an
object.
at Microsoft.Office.Project.Server.FormsAuthUpgrade.UpgradeUsers(Users
users,
List`1 membershipUsersCreated, String membershipProviderName)
at Microsoft.Office.Project.Server.FormsAuthUpgrade.UpgradeUsers()
at Microsoft.Office.Project.Server.FormsAuthUpgradeApp.Main(String[] args)

Any clues would be appreciated...
Thanks,
Mike

 

[mike.mahoney]

The log file stops after "Creating user logon," but here is the error after
the command line entry:
Exception occurred: Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an
object.
at Microsoft.Office.Project.Server.FormsAuthUpgrade.UpgradeUsers(Users
users,
List`1 membershipUsersCreated, String membershipProviderName)
at Microsoft.Office.Project.Server.FormsAuthUpgrade.UpgradeUsers()
at Microsoft.Office.Project.Server.FormsAuthUpgradeApp.Main(String[] args)

Any clues would be appreciated...
Thanks,
Mike

My problem was self inflicted. To establish forms authentication you
have to set up a connection to the forms database in web.config file
(connection strings). I entered the machine name of the project
server and not the SQL instance name. I corrected this and everything
works fine. So check this.

Mike- Hide quoted text -

- Show quoted text -

Mike

With the new resources in the forms database have you tried manually
adding them to project server?

Mike

 

[ahelp]

Hi Mike,
Thanks for your input. I hadn't tried adding users manually to
Projectserver, so I did. I added one which was already in the aspnetdb, and
one which I subsequently added to aspnetdb. I used
AspNetSqlMembershipProvider:username as the fully qualified membership
provider user name. Projectserver added the users without error. When I added
the latter user using the forms update utility, it added the user to
aspnetdb, but gave the error documented elsewhere (repeated here for clarity):
Exception occurred: Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an
object.
at Microsoft.Office.Project.Server.FormsAuthUpgrade.UpgradeUsers(Users
users,
List`1 membershipUsersCreated, String membershipProviderName)
at Microsoft.Office.Project.Server.FormsAuthUpgrade.UpgradeUsers()
at Microsoft.Office.Project.Server.FormsAuthUpgradeApp.Main(String[] args)

The above error is not in the logfile, but only in the cmd prompt window. We
did not use the default db name, but prefixed it as Projectserver_aspnetdb,
but since an alternate name is a legitimate option, I wouldn't think it would
be a problem.

When either user tries to logon, they get "Unknown Error". They are in the
team members group and have a project asgnmt.

Something is evidently missing, but having walked through the instructions
in the new edition of the Deployment Guide as well as the lab from the EPMU
class, I don't see what it is.
Thanks,
Mike

The log file stops after "Creating user logon," but here is the error after
the command line entry:
Exception occurred: Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an
object.
at Microsoft.Office.Project.Server.FormsAuthUpgrade.UpgradeUsers(Users
users,
List`1 membershipUsersCreated, String membershipProviderName)
at Microsoft.Office.Project.Server.FormsAuthUpgrade.UpgradeUsers()
at Microsoft.Office.Project.Server.FormsAuthUpgradeApp.Main(String[] args)

Any clues would be appreciated...
Thanks,
Mike

Rob,
I got almost exact same problem as Mike... small farm ps 2007 deployment,
web&app tier is on one win2003 box and sql 2005 is on another win2003 box;
extended on port 81 for forms authentication. Followed all the
docs/instructions from MS tech net and got no complains during deployment, I
can see users in the aspnetdb and "manage users" view in pwa when logged in
as admin thru windows auth. But can't log in by using forms authentication,
got the "unexpected error" page. The annoying thing is it doesn't really tell
you anything.
By the way, I got similar error as Mike in the event log too, and tried your
solution it did removed those errors but still can't log in thru forms
authentication.

Any ideas?

Many thanks!
Jerold

:
Mike, from the server, Administrative Tools--> Component Services
Expand Component Services->Computers->My Computer->DCOM Config
RIght CLick on IIS WAMREG Admin Service, select Properties.
On the Security tab, click on the EDIT button for Launch and Activation
Permissions.
Add your WSS-Admin and SSP-Admin accounts.

Hope this helps,
-RS

"Mike" wrote:

I previously had forms authentication working successfully, but had to
reinstall project server.
I set up forms authentication as before. The pjFormsAuthUpgrade
utility works fine it adds accounts to project server, and the
accounts validate and are usable, with the exception that cannot log
on to PWA. When I enter extended web site url the sign in form
presents itself but after entering a correct account and password WSS
returns an "unexpected error" with no further details. Any
suggestions?


I am not sure of the correlation but I am noticing some DCOM errors in
the system event log:

The application-specific permission settings do not grant Local
Activation permission for the
COM Server application with CLSID {61738644-
F196-11D0-9953-00C04FD919C1}
to the user CHEYNE\PS-Admin SID
(S-1-5-21-164770905-1455706766-1538882281-9075).
This security permission can be modified using the Component Services
administrative tool.

This relates to this service IISADMIN under DCOM Config and is
repeated for WSS-Admin and SSP-Admin accounts

I suspect on earlier installations these accounts were local admins

Thanks- Hide quoted text -

- Show quoted text -

My problem was self inflicted. To establish forms authentication you
have to set up a connection to the forms database in web.config file
(connection strings). I entered the machine name of the project
server and not the SQL instance name. I corrected this and everything
works fine. So check this.

Mike- Hide quoted text -

- Show quoted text -

Mike

With the new resources in the forms database have you tried manually
adding them to project server?

Mike

 

[JYX]

Hi guys,
I've fixed my problem... my problem was the application pool user was not
the aspnetdb user, so after I added it in all worked out fine.
I think MS should have pointed out this, because they recommend to use
domain user accounts for deployment (for database access account, application
pool account, service account, etc) but nowhere mentioned to add to aspnetdb,
and the aspnet_regsql doesn't do it either.

Jerold

 

[ahelp]

Hi Jerold,
I just want to clarify what you needed to do... It sounds like you gave the
application pool service account rights on the aspnetdb. Is that correct? If
you broke them up, was it the SSP Application pool security account or the
Application pool process account? What level of access? We've run into a
number of places where security access was not clearly laid out & was further
complicated by using multiple accounts...
Thanks,
Mike