Beantwortet Acces Denied for administrator

  • Montag, 30. Januar 2012 10:38
     
     

    Hi,

    Recently i've re-installed SharePoint 2010 and restored an old content-database.

    Logging in as servername/Administrator works, but when i want to open "Site settings" i'm getting the error message below.

    All other users cannot login to SharePoint, they are getting the same message after the login screen.

    Can someone help me with this problem?

    Best regards,

    Joost Lauwen

    • Bearbeitet Spike-NL Montag, 30. Januar 2012 10:44 update
    • Verschoben Mike Walsh FIN Montag, 30. Januar 2012 10:51 SP 2010 questions go only to SP 2010 forums (From:SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010))
    •  

Alle Antworten

  • Montag, 30. Januar 2012 10:40
     
     

    We need more than this.

    You can start by saying which SP you have and continue with when this is appearing and what rights the Administrator has - also if you are using default.aspx in the URL.


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters
  • Montag, 30. Januar 2012 10:47
     
     

    We need more than this.

    You can start by saying which SP you have and continue with when this is appearing and what rights the Administrator has - also if you are using default.aspx in the URL.


    SP 2010 "FAQ" (mainly useful links): http://wssv4faq.mindsharp.com/default.aspx
    WSS3/MOSS FAQ (FAQ and Links) http://wssv3faq.mindsharp.com/default.aspx
    Both also have links to extensive book lists and to (free) on-line chapters

    Something went wrong when placing the post ;)

    I'm using SharePoint 2010 SP1 14.0.6029.1000

    Administrator does have all rights.

  • Montag, 30. Januar 2012 13:17
     
     

    CA->Application Management->Site Collections - > Change Site Collection Administrator.

    There choose your account name as it is migrated from other server,you may not be the site administrator there.

     

     


    Murugesa Pandian,MCTS
  • Montag, 30. Januar 2012 14:32
     
     

    CA->Application Management->Site Collections - > Change Site Collection Administrator.

    There choose your account name as it is migrated from other server,you may not be the site administrator there.

     

     


    Murugesa Pandian,MCTS

    Tried it without any result. I'm getting an error message.



    Best regards, Joost Lauwen
  • Montag, 30. Januar 2012 14:36
     
     
    Please get the details for this correlation ID from ULS log. That will throw some light.
    Satheesh
    http://spsatheesh.wordpress.com
  • Montag, 30. Januar 2012 15:16
     
     
    Its seems to be a migration problem.Please leave the ULS log text to identify the exact problem.
    Murugesa Pandian,MCTS
  • Montag, 30. Januar 2012 15:54
     
      Enthält Code

    01-30-2012 15:27:13.99	w3wp.exe (0x1570)	0x1068	SharePoint Foundation	Logging Correlation Data	xmnv	Medium	Name=Request (POST:http://avia_server:48183/_admin/owners.aspx)	4ca6b275-361d-4488-8c03-0968c2b03dd8
    01-30-2012 15:27:13.99	w3wp.exe (0x1570)	0x1068	SharePoint Foundation	Logging Correlation Data	xmnv	Medium	Site=/	4ca6b275-361d-4488-8c03-0968c2b03dd8
    01-30-2012 15:27:14.00	w3wp.exe (0x1570)	0x1068	SharePoint Foundation	Monitoring	b4ly	High	Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=8.05366061519728	4ca6b275-361d-4488-8c03-0968c2b03dd8
    01-30-2012 15:27:14.04	w3wp.exe (0x1570)	0x1068	SharePoint Foundation	General	g8ga	Medium	Begin Query the AD to get the user email and display name.	4ca6b275-361d-4488-8c03-0968c2b03dd8
    01-30-2012 15:27:16.31	w3wp.exe (0x1570)	0x1068	SharePoint Foundation	General	g8gb	Medium	End Query the AD to get the user email and display name.	4ca6b275-361d-4488-8c03-0968c2b03dd8
    01-30-2012 15:27:16.53	w3wp.exe (0x1570)	0x1068	SharePoint Foundation	Runtime	tkau	Unexpected	System.NullReferenceException: Object reference not set to an instance of an object.    at Microsoft.SharePoint.SPUser.set_IsSiteAdmin(Boolean value)     at Microsoft.SharePoint.SPSite.set_SecondaryContact(SPUser value)     at Microsoft.SharePoint.Administration.SPSiteAdministration.set_SecondaryContactLoginName(String value)     at Microsoft.SharePoint.ApplicationPages.OwnersPage.BtnConfirm_Click(Object sender, EventArgs e)     at System.Web.UI.WebControls.Button.OnClick(EventArgs e)     at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)     at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)	4ca6b275-361d-4488-8c03-0968c2b03dd8
    01-30-2012 15:27:18.99	w3wp.exe (0x1570)	0x1068	SharePoint Foundation	Monitoring	b4ly	Medium	Leaving Monitored Scope (Request (POST:http://avia_server:48183/_admin/owners.aspx)). Execution Time=5031.1517167884	4ca6b275-361d-4488-8c03-0968c2b03dd8
    

    • Bearbeitet Spike-NL Montag, 30. Januar 2012 15:55
    •  
  • Montag, 30. Januar 2012 16:02
     
     

    Hi,

    Can you tell us in what approach you followed for migration?

    Just check without secondary administrator user name.


    Murugesa Pandian,MCTS
  • Montag, 30. Januar 2012 16:11
     
     

    Hi.

     

    Have you tried to replace the Administrator as Primary SIte Collection admin with a working account(joost?), then from a Powershell prompt run as admin:

    Set-SPSite -Identity "<SiteCollection>" -SecondaryOwnerAlias "<User>"

     

    Could be worth a try?

     

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blksthl.wordpress.com
  • Dienstag, 31. Januar 2012 08:22
     
     

    Hi Joost,

    access this link from Administrator account.There change the Site Administrator to your account.

    Before you changed the SiteCollection Adminstrators from CA now you need to change this in site level also.

    http://yourserver/_layouts/settings.aspx


    Please let me know if my post was helpful.
  • Dienstag, 31. Januar 2012 09:33
     
     

    Hi, Murugesa, have a look at the initial error...Access denied when accessing the site collections site settings...so we can probably assume that if nothing has changed from the attempts made, that it will still be access denied.

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blksthl.wordpress.com
  • Dienstag, 31. Januar 2012 09:57
     
     

    Hi Joost,

    access this link from Administrator account.There change the Site Administrator to your account.

    Before you changed the SiteCollection Adminstrators from CA now you need to change this in site level also.

    http://yourserver/_layouts/settings.aspx


    Please let me know if my post was helpful.


    The settings-page is displayed, but when I want to open an link on this page i'm getting the same "Access Denied" again.

     


    Best regards, Joost Lauwen
  • Dienstag, 31. Januar 2012 10:05
     
     

    Hi Joost.

    Have you tried to access the sites Site collection Administrators page directly?

    http://avia_server:26320/_layouts/mngsiteadmin.aspx

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blksthl.wordpress.com
  • Dienstag, 31. Januar 2012 10:09
     
     

    Go to sharePoint powershell command and type this command

    Set-SPSite -Identity "<SiteCollection>" -OwnerAlias "<Userwithdomain>"

    Add your name or server administrator.


    Please let me know if my post was helpful.
  • Dienstag, 31. Januar 2012 10:16
     
     

    yes that is possible. After changing the Primary Site administrator, i cannot login with any users.


    Best regards, Joost Lauwen
  • Dienstag, 31. Januar 2012 10:20
     
     

    any users means ? Just give them permission to access your site.

    But administrator rights for your account and server administrator account only.

    Add some users in Member,Visitors groups and check them to log in into the site.


    Please let me know if my post was helpful.
  • Dienstag, 31. Januar 2012 10:21
     
     

    Go to sharePoint powershell command and type this command

    Set-SPSite -Identity "<SiteCollection>" -OwnerAlias "<Userwithdomain>"

    Add your name or server administrator.


    Please let me know if my post was helpful.

    Ive added "Set-SPSite -Identity http://avia_server:26320 -OwnerAlias avia_server\Administrator" without any succes
    Best regards, Joost Lauwen
  • Dienstag, 31. Januar 2012 10:25
     
     

    Hi,

    This command throws any error ? or return just blank.

    Now open the site and still you got the error change the browser and test the same.

    You might be not fully logged out on your previous session.

     


    Please let me know if my post was helpful.
    • Als Antwort markiert Spike-NL Dienstag, 31. Januar 2012 10:30
    • Tag als Antwort aufgehoben Spike-NL Dienstag, 31. Januar 2012 10:30
    •  
  • Dienstag, 31. Januar 2012 10:31
     
     

    Hi,

    This command throws any error ? or return just blank.

    Now open the site and still you got the error change the browser and test the same.

    You might be not fully logged out on your previous session.

     


    Please let me know if my post was helpful.


    There was no error. It returned just blank.

    I've tried it with different browsers, only getting the Access Denied error. Even for the Administrator-account.


    Best regards, Joost Lauwen
  • Dienstag, 31. Januar 2012 10:39
     
     

    Hmmm..Never giveup,

    STSADM.EXE -o enumsites -url http://avia_server:26320

    this will return the site and its owner name.and check your account and server account on Owner field.

    If not Log into Management studio find your application's content database add your name as "db_owner" role.


    Please let me know if my post was helpful.
  • Dienstag, 31. Januar 2012 10:46
     
     
      <Site Url="http://avia_server:26320" Id="65d92861-c63c-404a-9bf2-8f3b09fa3b37"
     Owner="AVIA_SERVER\administrator" ContentDatabase="WSS_Content" StorageUsedMB="
    8274.2" StorageWarningMB="0" StorageMaxMB="0" />
      <Site Url="http://avia_server:26320/my" Id="af9bd012-4741-40d1-b64d-9eaf991432
    c8" Owner="AVIA_SERVER\administrator" ContentDatabase="WSS_Content" StorageUsedM
    B="1.5" StorageWarningMB="0" StorageMaxMB="0" />
    Best regards, Joost Lauwen
  • Dienstag, 31. Januar 2012 10:48
     
     

    Is the content database set to read only in SQL?

    Can you access any MySites with the Administrator account?

     

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blksthl.wordpress.com
  • Dienstag, 31. Januar 2012 10:52
     
     

    Yes You can login as "AVIA_Server\administrator" to your site.

    Still if you get "Access Denied error". Close your browser and reopen and hit the URL.

    Try with different browser.

    After you log in give the access to your users.

    I hope In CA also AVIA_Server\administrator is in Site Administrator's group.


    Please let me know if my post was helpful.
  • Dienstag, 31. Januar 2012 10:56
     
     
    The WSS_Content database is not set to read-only. I also cannot access MySites, getting an 404-error.
    Best regards, Joost Lauwen
  • Dienstag, 31. Januar 2012 11:02
     
     

    Ok.

    Go to Central aDministration - Clicl on Manage Application [Header] You will see the Manager Content database under Database subheader.

    Click on.Find your site's content db click it to open its properties. Set "Ready".

    Now check.It wil work.


    Please let me know if my post was helpful.
  • Dienstag, 31. Januar 2012 11:13
     
     

    Perhaps you should start to focus on your IIS settings....check what you have.

    This is not normal behaviour...'

     

    (The read-only seting doeas not affect access...only creation of new SiteCollections)

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blksthl.wordpress.com
  • Dienstag, 31. Januar 2012 11:17
     
     
    Yes correct not only SiteCollection,It will not allow any update/delete and ofcourse creation of any items in the site.But same time if there is any problem in IIS configuration,He won't see the "Access Denied" messages instead some yellow error page.

    Please let me know if my post was helpful.
  • Dienstag, 31. Januar 2012 11:31
     
     

    Ok.

    Go to Central aDministration - Clicl on Manage Application [Header] You will see the Manager Content database under Database subheader.

    Click on.Find your site's content db click it to open its properties. Set "Ready".

    Now check.It wil work.


    Please let me know if my post was helpful.


    Content Database is already set to "Ready"

    I think something is went completely wrong when restoring the whole database and configuration to the new installation.

    Maybe the best solution will be:

    - Completely remove SharePoint 2010 and then install a fresh installation of SharePoint?
    - Then attach the wss_content with all our files to the new installation?

    What do you think?

     


    Best regards, Joost Lauwen
  • Dienstag, 31. Januar 2012 11:43
     
     

    Hi Joost,

    For this issue,Please don't go reinstall everything.!Lets wait some experts here to answer.

    Try to open this site using SPD 2010.Let see its allowing or not.


    Please let me know if my post was helpful.
  • Mittwoch, 1. Februar 2012 11:06
     
     

    Hi Joost,

    For this issue,Please don't go reinstall everything.!Lets wait some experts here to answer.

    Try to open this site using SPD 2010.Let see its allowing or not.


    Please let me know if my post was helpful.
    I can acces the site through SPD 2010.

    Best regards, Joost Lauwen
  • Mittwoch, 1. Februar 2012 12:40
     
     

    Yes.Now its confirm,

    You would have closed your browser and logged In use different user.some time browser retains the last logged in user detail.

    I hope the problem got resolved.


    Please let me know if my post was helpful.
  • Mittwoch, 1. Februar 2012 13:16
     
     Beantwortet

    I've tried it already. Even with a computer which never opened SharePoint.

    I'm now setting up an test environment with Hyper-V to make a new Sharepoint installation with the recent WSS_Content database.


    Best regards, Joost Lauwen
    • Als Antwort markiert Spike-NL Freitag, 10. Februar 2012 08:56
    •  
  • Mittwoch, 1. Februar 2012 13:40
     
     
    Are you using claim based or Windows classics as your authentication provider? If you have changed from Windows classics to Claim based, you need to convert all of your users to Claims.
    Regards
    Henrik A. Halmstrand
    sharepointrevealed.com
    getspconfig.codeplex.com
    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.
  • Mittwoch, 1. Februar 2012 13:55
     
     

    Hi,

    This site has been backed up through Powershell using "Lock State" and it has migrated in the same state.

    So give this command in sharePoint powershell

    Set-SPSite -Identity  siteName -LockState Unlock

     


    Please let me know if my post was helpful.
  • Mittwoch, 1. Februar 2012 14:35
     
     
    Are you using claim based or Windows classics as your authentication provider? If you have changed from Windows classics to Claim based, you need to convert all of your users to Claims.
    Regards
    Henrik A. Halmstrand
    sharepointrevealed.com
    getspconfig.codeplex.com
    Please click Mark As Answer; if a post solves your problem or Vote As Helpful; if a post has been useful to you.


    I'm using Windows Classics as my authentication provider.


    Best regards, Joost Lauwen
  • Mittwoch, 1. Februar 2012 19:24
     
     

    Try to back up the site without user from source domain while migrating to other domain.

    And please look into Henrik's reply also.Its seems to be valid answer for this issue.

     


    Please let me know if my post was helpful.
  • Freitag, 10. Februar 2012 08:56
     
     
    <p>Hi guys,</p><p>I solved the problem.</p><p>I have removed en reinstalled Sharepoint and made a new site. Then attached the old database to it.</p><p>Now everyhing is working fine.</p><p>Thanks for your tips and solutions</p>

    Best regards, Joost Lauwen

  • Montag, 13. Februar 2012 16:04
     
     

    I had the same problem after moving a site collection to another server in another domain.

    I solved the problem by deleting the "incorrect" site collection administrators in the content database:

    SELECT * FROM UserInfo

    DELETE FROM UserInfo WHERE tp_ID = {ID_to_be_deleted}

    After this I added the primary and secundary site collection administrator back through STSADM

    stsadm -o setowner -url http://SP2010 -ownerlogin dev\spadmin

    stsadm -o setowner -url http://SP2010 -secondarylogin dev\spadmin2

  • Montag, 13. Februar 2012 16:42
     
     

    Hi Steven. Altering the databases directly will render the farm unsupported.

    This should never be recommended here.

    Better to find any other alternative resolution.

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blksthl.wordpress.com

  • Donnerstag, 1. März 2012 13:56
     
     

    Hello Gents,

    I think i may have a serious problem in this area. Recently I set up a new site, and by mistake deleted all permisions to this site (there was not even a single window with qestion if I am sure to delete all permissions!! (view, contribute, administration)). Now I get the message below:

     

    What should I do to delete this Site? I need to get rid of this as I need to use this address for annother Site.

  • Donnerstag, 1. März 2012 14:47
     
     

    Hi.

    As a farm admin, go to Central Admin, then add yourself to the site collection admins, primary or secondary(only two from CA)
    Then, go to the site and delete it. As a SIte Collection admin you can do anything :-)

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com

  • Freitag, 2. März 2012 12:59
     
     

    Hello,

    I have changed my privileges to farm admin, and I am still unable to open this site.

    Regards,

    Macciu

  • Freitag, 2. März 2012 13:07
     
     

    Hi.

    You missed the important part...a farm admin has no access to content, but he can give himself permissions.

    'then add yourself to the site collection admins'

    As a farm admin, add yourself as a primary or secondary site collection administrator an dthen you can access the site.

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com

  • Freitag, 2. März 2012 13:41
     
     
    I have checked my credentials and i am also site collection admin.
  • Donnerstag, 15. März 2012 16:50
     
     

    marking this thread for later.

    i have the similar issues going on.  added a user as a farm admin and a site collection admin, still gets the Access Denied message.  happens too when trying to create a site collection.

    i'm going to see about adding dbcreator,sysadmin roles for the user to that content db

  • Sonntag, 15. April 2012 07:30
     
     
    sometimes I have run into similar issue with not having rights to a new or upgraded farm. Try adding the account to the web application policy in Central Admin. this has worked for me on many occasions and then I can get into places and reset permissions for site collection admins. Hopefully it will help. Make sure to remove the account from the policy later.
  • Donnerstag, 19. Juli 2012 17:45
     
     

    Hi,

    I'm having the same problem.

    I've managed to get a pattern in this error:

    After I execute Mount-SPContentDatabase, I change the Primary Site Collection Administrator with this command:

    Set-SPSite -OwnerAlias <User> -Identity <Url> 

    (also tried Set-SPSiteAdministration, also works)

    When i log on in the newly mounted Site Collection´with this account, it gives me "AccessDenied" when trying for example "<url>/_layouts/settings.aspx". This is weird.

    However, by checking "CA > Application Management > Change Site Collection Administration", i have verified that sharepoint indeed accepted the user i provided for Site Collection Administrator. I touch nothing and click OK.

    The moment I click OK, the "Access Denied" goes away and I am able to access the "<url>/_layouts/settings.aspx".

    Weird? Something wrong with Set-SPSite / Set-SPSiteAdministration ?? Or am I missing something ?

    Regards,

    Rodrigo


    http://brainsmack.blogspot.com