locked
MOSS 2007 errors RRS feed

  • Question

  • Hi.

    My customer is experiencing errors on MOSS 2007.

    The first error was :

    A runtime exception was detected. Details follow. Message : Windows NT user or group 'CETUS\administrator' not found. Check the name again.

    Technical details:

    System.Data.SqlClient.SqlException: Windows NT user or group 'CETUS\administrator' not found. Check the name again.

       w System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

       w System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

       w System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

       w System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

       w System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

       w System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

       w System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

       w System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

       w System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

       w Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)

       w Microsoft.Office.Server.Data.SqlServerManager.GrantLogin(String user)

       w Microsoft.Office.Server.Administration.SharedResourceProvider.SynchronizeConfigurationDatabaseAccess(SharedComponentSecurity security)

       w Microsoft.Office.Server.Administration.SharedResourceProvider.SynchronizeAccessControl(SharedComponentSecurity sharedApplicationSecurity)

       w Microsoft.Office.Server.Administration.SharedResourceProvider.Microsoft.Office.Server.Administration.ISharedComponent.Synchronize()

    I found this: http://social.technet.microsoft.com/forums/en-US/sharepointadmin/thread/d10a0cc1-13f0-483a-8871-3d9a5ead8326/ advise to use

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

    but when I tried to do the stsadm it replied with :

    Method not found: 'Void Microsoft.SharePoint.Administration.SPCredentialDeployment.UpdateFarmCredentials(Microsoft.SharePoint.Administration.IdentityType,

     System.String, System.Security.SecureString, Boolean, Boolean

    The second thing is problem with MS Outlook connection to the MOSS list.

    When client tries to post, Outlook puts his post twice, or three times, or posts vanish.

    The farm is MOSS 2007 SP2 on Win2003 x86 SP2 with SQL Server 2005.

     

     

     

     

    Monday, December 20, 2010 2:34 PM

All replies

  • P. S. Outlook prompts the following error message: Job "Sharepoint" reported error (0x80004005): "Sharepoint list (Forum) couldn't be found.

    If the error persists please contact with Sharepoint site administrator. Http 404".

    Monday, December 20, 2010 2:37 PM
  • Did you recently change farm admin account name or password ?

    And are you running stsadm command using admin rights ?

    to update farm credentials please follow procedure mentioned in http://support.microsoft.com/kb/934838


    Regards, Pratik Vyas | SharePoint Consultant |
    Monday, December 20, 2010 2:40 PM
  • The action was performed from farm system account.

    The procedure from the KB934838 cannot be used beacause the error

    Method not found: 'Void Microsoft.SharePoint.Administration.SPCredentialDeployment.UpdateFarmCredentials(Microsoft.SharePoint.Administration.IdentityType,

    encountered when performing point 1 from the KB.

    Tuesday, December 21, 2010 7:25 AM
  • Hi,

     

    Please check if the server farm have WSS SP2 applied. Did your customer copy the wrong version of stsadm.exe across servers within the farm?

      

    Thanks & Regards.


    Lily Wu
    Wednesday, December 22, 2010 3:31 AM
  • There is only one app node in the farm. SP2 is installed.

    Wednesday, December 22, 2010 8:19 AM
  • It seems that you have the MOSS farm on SP2 version. The version shows updated to SP2 even when you have only applied the MOSS SP2 without having the WSS 3.0 SP2 installed.

    As per Best practices it is required to have the WSS 3.0 SP2 and MOSS SP2 installed.

    http://technet.microsoft.com/en-us/office/sharepointserver/bb736746

    Addition step by step references:

    http://msmvps.com/blogs/shane/archive/2009/04/29/install-guide-sp2-for-sharepoint-wss-v3-and-moss-2007.aspx

     

    Ensure that you have the correct apppool identity, Follow below steps:

    Set correct apppool identity using adsutil.vbs

    1. Change the app pool account with the following command:

    cscript.exe adsutil.vbs get "/W3SVC/AppPools/CentralAdminAppPool/WAMUserName"

    2. After changing the account, wait for next timer job to execute (approx 5 min)

    3. Add the MOSSADMIN, which is the actual admin user account, in all the databases as securityadmin, dbcreator, sysadmin

     

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

    Follow http://support.microsoft.com/kb/939308 to clear the config cache and check if the issue still occurs.

     

    Lastly check to ensure that you’re pointing to the correct DB server …if not then run STSADM renameserver and then updatefarmcredentials.

    http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/c924af8b-4b1e-4b0b-8d59-53a29f7d615a


    Regards, Savoeurn Va Microsoft Online Community Support
    • Edited by Mike Walsh FIN Monday, December 27, 2010 3:22 PM A couple of "we"s changed to "you"
    Monday, December 27, 2010 3:15 PM
  • As per Best practices it is required to have the WSS 3.0 SP2 and MOSS SP2 installed.

    I'd say it was more than just a Best Practice. That assumes there are alternative approaches.

    For MOSS 2007 it is essential that if you have MOSS 2007 and want to upgrade it to SP2 level that both the WSS 3.0 SP2 and (then) the MOSS  2007 SP2 are installed.

    As your text went on after the (misleading) reference to Best Practices, "it is required  to have the WSS 3.0 SP2 and MOSS SP2 installed."

     


    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
    Monday, December 27, 2010 3:26 PM
  • There is SP2 correctly installed in the farm - SP2 for WSS and MOSS.

    Clear config cache doesn't give anything - still stsadm -updatecredentials returns "method not found".

    Farm is pointing to the correct DBMS.

    Any help ?

    Wednesday, December 29, 2010 9:41 AM
  • Hi,

    What happens when you run psconfig -cmd upgrade -inplace b2b -force -wait?

    Have a backup of the farm before you do this.


    Regards, Savoeurn Va Microsoft Online Community Support
    Wednesday, December 29, 2010 3:46 PM