Answered by:
Sometimes users can log on, sometimes they can't

Question
-
This is question two of my Project questions.
Project server 2010 is on AD, and all users are domain users. My account can consistently log on, but a co-worker with every possible permission can sometimes log on, and sometimes not. I thought this was odd, so I created a test user in AD and got the same result. First try, I could get on. After that it was hit or miss, mostly miss. The error I get is:
Error: Access Denied
Current User
You are currently signed in as: AD\sharepoint Sign in as a different user
(ad\sharepoint is my test account that also has every possible permission).
Thanks
Brent
Tuesday, August 17, 2010 7:52 PM
Answers
-
Hello BrentHaslehoff
There are a number of reasons for the user not logging into Project 2010. Not sure why it works and doesn't, but it's obvious that something in the security model is not correct. You will need to log at the ULS logs, SQL logs and windows events for clues as what is going ton.
Second, users can have all the rights and privileges in the world, but when logging into Project Server, it's the services that are running the show for access. So this means, if you are an administrator, it doesn't mean you have access.
When you set up the test account, did you put the users in the list of Project users and did what role did you assign them to. WHen you say permission, are you meaning role?
Also, check if this is true on one workstation or other workstations.
cheers!
Michael Wharton, MBA, PMP, MCT
Sincerely, Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA www.WhartonComputer.com- Proposed as answer by Christophe FiessingerMicrosoft employee Wednesday, August 18, 2010 8:09 PM
- Marked as answer by Mike Glen Sunday, October 16, 2011 8:11 PM
Wednesday, August 18, 2010 2:36 PM -
Hi,
in addition to Michael's suggestions, I had a similar issue a few weeks ago in 2007. It was somehow related with changing permissions while user had been logged in. Some minor chances happened to selected projects in one category with denies included, but that was sufficient to get this issue. I was able to solve by removing user from all groups and start an AD sync manually (during non-working hours to make sure that he is not looged in). No idea if it can be the same in your environment, since you are working on 2010. Only an additional idea.
Regards
Barbara- Marked as answer by Mike Glen Sunday, October 16, 2011 8:11 PM
Wednesday, August 18, 2010 6:55 PM
All replies
-
Hello BrentHaslehoff
There are a number of reasons for the user not logging into Project 2010. Not sure why it works and doesn't, but it's obvious that something in the security model is not correct. You will need to log at the ULS logs, SQL logs and windows events for clues as what is going ton.
Second, users can have all the rights and privileges in the world, but when logging into Project Server, it's the services that are running the show for access. So this means, if you are an administrator, it doesn't mean you have access.
When you set up the test account, did you put the users in the list of Project users and did what role did you assign them to. WHen you say permission, are you meaning role?
Also, check if this is true on one workstation or other workstations.
cheers!
Michael Wharton, MBA, PMP, MCT
Sincerely, Michael Wharton, MBA, PMP, MCT, MCSD, MCSE+I, MCDBA www.WhartonComputer.com- Proposed as answer by Christophe FiessingerMicrosoft employee Wednesday, August 18, 2010 8:09 PM
- Marked as answer by Mike Glen Sunday, October 16, 2011 8:11 PM
Wednesday, August 18, 2010 2:36 PM -
Hi,
in addition to Michael's suggestions, I had a similar issue a few weeks ago in 2007. It was somehow related with changing permissions while user had been logged in. Some minor chances happened to selected projects in one category with denies included, but that was sufficient to get this issue. I was able to solve by removing user from all groups and start an AD sync manually (during non-working hours to make sure that he is not looged in). No idea if it can be the same in your environment, since you are working on 2010. Only an additional idea.
Regards
Barbara- Marked as answer by Mike Glen Sunday, October 16, 2011 8:11 PM
Wednesday, August 18, 2010 6:55 PM -
Thanks for the suggestions. I looked a little closer at some of the logs, and it seems that a SQL problem may have been the problem. I did a fresh install using SQL 2008 instead of letting SP install SQL Express, and it's a lot better now. I'll certainly keep this information handy in case I have problems again.
Thanks
Friday, August 20, 2010 2:22 AM