locked
user permission problem in moss sp 2007 sp3 RRS feed

  • Question

  • One of our test farms is throwing errors of this type each minute. There doesn't appear to be enough info in the logs to track backwards.

    The events log contains repetitions of this message.

    Event Type: Error
    Event Source: Office SharePoint Server
    Event Category: Office Server General
    Event ID: 7888
    Date:  9/19/2013
    Time:  9:29:36 AM
    User:  N/A
    Computer: NTSRV45QA
    Description:
    A runtime exception was detected. Details follow.
    Message: User does not have permission to perform this action.

    Techinal Details:
    System.Data.SqlClient.SqlException: User does not have permission to perform this action.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
       at Microsoft.Office.Server.Data.SqlServerManager.GrantLogin(String user)
       at Microsoft.Office.Server.Administration.SharedDatabase.Microsoft.Office.Server.Administration.ISharedAccessControl.SetAccessControl(SharedComponentSecurity security)
       at Microsoft.Office.Server.Administration.SharedResourceProvider.SynchronizeAccessControl(SharedComponentSecurity sharedApplicationSecurity)
       at Microsoft.Office.Server.Administration.SharedResourceProvider.Microsoft.Office.Server.Administration.ISharedComponent.Synchronize()

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    The 12 hive log is filled with messages that basically say the same thing:

    09/19/2013 09:30:36.87  OWSTIMER.EXE (0x0770)                    0x0CF8 Office Server                  Office Server General          900n Critical A runtime exception was detected. Details follow.  Message: User does not have permission to perform this action.  Techinal Details: System.Data.SqlClient.SqlException: User does not have permission to perform this action.     at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)     at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBeha... 
    09/19/2013 09:30:36.87* OWSTIMER.EXE (0x0770)                    0x0CF8 Office Server                  Office Server General          900n Critical ...vior runBehavior, String resetOptionsString)     at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)     at System.Data.SqlClien 

    When the dbas look at the sql server side of the log, their errors say basically the same thing - they tell us it does not tell us what action or what user.

    We have rebooted the machine and that didn't help.

    Thursday, September 19, 2013 1:39 PM

Answers

  • In discussing this with the admin dealing with the issue, it turns out that on Friday, he tried

    stsadm.exe -o updatefarmcredentials -userlogin <DOMAIN\name> -password <password>

    (resetting the password to the password that has been used for quite some time) and after about 20 minutes, the error went away.

    Thank you for your suggestions!

    Since SharePoint was still operational, it seems peculiar to me that this was necessary, but it solved the issue and for that we are grateful.

    Monday, September 23, 2013 2:20 PM

All replies

  • Hello,

    It looks like there is account configured for a service but that acocunt does not have rights in SQL. Can you try to give DB owner right to all DB's which are used to configured farm? (check specially search acocunt)

    You might also want to look below blogs:

    http://aurramu.blogspot.in/2013/07/user-does-not-have-permission-to.html

    http://www.linkedin.com/groups/Nasty-little-SharePoint-bug-in-134437.S.104880521

    Let us know your result


    Hemendra:Yesterday is just a memory,Tomorrow we may never see
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, September 20, 2013 10:14 AM
    Moderator
  • We can't tell what account doesn't have permission - as far as we can tell, the normal accounts we use do have the appropriate permissions.
    Friday, September 20, 2013 11:34 AM
  • >We can't tell what account doesn't have permission

    I am talking about service accounts or farm admin accounts so you can check this out from central admin-->security option.

    Did you also see the search service acocunt in CA? f not then check this account in CA and windows services. Make sure that this service account is having proper rights in SQL.


    Hemendra:Yesterday is just a memory,Tomorrow we may never see
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, September 23, 2013 5:32 AM
    Moderator
  • In discussing this with the admin dealing with the issue, it turns out that on Friday, he tried

    stsadm.exe -o updatefarmcredentials -userlogin <DOMAIN\name> -password <password>

    (resetting the password to the password that has been used for quite some time) and after about 20 minutes, the error went away.

    Thank you for your suggestions!

    Since SharePoint was still operational, it seems peculiar to me that this was necessary, but it solved the issue and for that we are grateful.

    Monday, September 23, 2013 2:20 PM