locked
Event 7888 (An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service) RRS feed

  • Question

  •  Hi, I'm running a new installation of MOSS 2007 with a single WFE and single 2005 SQL backend.  When accessing my SSP certain links (i.e. User Profiles and Properties) display the following error message "An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator." at the same time an Event is logged 7888 "A runtime exception was detected. Details follow. Message: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665 -4620-92A3-478F47389230} failed due to the following error: 8007042d."  I have searched the net and the solution for most has been to add Network Services to the OSearch DCOM Component Service with Local Activation and Local Launch rights, however this hasn't resolved my problem I then proceeded to add every sharepoint account to the OSearch with the same rights with no success.  I am still on the early stages of configuring the User Profile/Search components of SharePoint.  I have also not sure if its related but I noticed that the Service 'Windows SharePoint Services Search' is not started, when I attempt to start the service I get an error message "Could not start the Windows SharePoint Services Search service on Local Computer. Error 6 The handle is invalid." The Log on for this service is my (Windows SharePoint Services Search service account/Windows SharePoint Services Search content access account) which is a different account from my (Office SharePoint Server Search Service account/Default content access account).  Any Help would be appreciated.
    Wednesday, January 14, 2009 12:21 PM

All replies

  • Moving to the Search forum
    Wednesday, January 14, 2009 12:55 PM
  • Hi, Apologies for the late reply to this post.  Unfortunately that post didn't help me.  The 7888 Message is not related to a message: "Access Denied! Only a site~~~" etc.  I'm not preforming a import or any other function, I get the error as soon as I enter the User Profile and Properties section.  Can't seem to find an answer to this problem.
    Thursday, February 12, 2009 5:00 PM
  • I have seen this error more than once. Hard to troubleshoot, but I found that the Indexing status was stuck in Computing Ranks. I reset all my search content and VOILA! No more problem. There were a couple of other things wrong though. My Search Database was not set. Basically I did a restore of the ssp and it didn't finish successfully. Most pieces did, though and everything seemed to be working fine except for the profiles.
    Wednesday, March 4, 2009 4:23 PM
  • Hi, Apologies for the late reply to this post.  Unfortunately that post didn't help me.  The 7888 Message is not related to a message: "Access Denied! Only a site~~~" etc.  I'm not preforming a import or any other function, I get the error as soon as I enter the User Profile and Properties section.  Can't seem to find an answer to this problem.

    Hi, we are having the exact issue, did you find out how to correct this problem? This is the first time I have seen this error, I have installed SharePoint on a number of servers. 
    Monday, May 11, 2009 10:59 AM
  • Hi,

    Is your environment MOSS 2007 Standard or MOSS 2007 Enterprise?

    Sincerely,
    Karl R.

    Wednesday, May 13, 2009 2:35 AM
  • Hi,
    We're having the same problem. We're running MOSS Standard. I have checked the services and all are running with the same service account which has admin rights to each server and to the databases. I have tried sroping and starting the search service and reseting IIS. Anyone find an answer for this?
    Thank you,
    Francis,

     

     

    Exact message:

    Under 'User Profiles and Properties:

    An error has occurred while accessing the SQL Server database or the Office SharePoint Server Search service. If this is the first time you have seen this message, try again later. If this problem persists, contact your administrator.



    In addition, when I goto the Search Settings, it says:

    An indexer is not assigned to the Shared Services Provider 'SSP Name'

    But I do have one assigned to it.
    Monday, June 1, 2009 12:08 PM
  • Hi,

    Have you tried the following:

    1. Open Central Administration
    2. Go to the Application Management tab
    3. Select “Create or Configure this farm’s shared services”
    4. Use drop-down list for the SSP, select Edit Properties
    5. Assign an indexer server

    Hopefully that helps.

    Sincerely,
    Karl
    • Edited by Par4theChords Saturday, June 6, 2009 3:10 PM Correcting "application" to application management tab
    Saturday, June 6, 2009 2:59 PM
  • Hi, after lot of digging around here is how I resolved it

    http://epmimplementations.blogspot.com/2009/08/error-has-occurred-while-accessing-sql.html

    feel free to email me if you have any questions

    -Rohit
    rrajdev@gmail.com
    Wednesday, August 5, 2009 6:47 PM
  • I ran into the same issues here is how I resolved it..

    http://epmimplementations.blogspot.com/2009/08/error-has-occurred-while-accessing-sql.html

    -Rohit
    Wednesday, August 5, 2009 6:48 PM
  • Hi, I got the same problem in our SharePoint 2007 Farm. In my case the reason for the error message was a missing profile import shared service timer job.

     

    You can list the current shared service timer jobs with the following stsadm command:

     

    stsadm –o enumssptimerjobs –title "nameofssp"

     

    If everything is ok the output should contain 4 timer jobs where the DisplayName contains "User Profile...".

    If not then you (or somebody else) deleted a timer job with the stsadm command

     

    stsadm -o deletessptimerjob

     

    The problem is that if you deleted one of this timer jobs the only supported way to recreate them is to recreate the whole shared service provider. In our case that was not an option so we called Microsoft Product Support and they provided us a way to recreate the timer jobs without deleting the shared service provider.

     

    1. Excute the following stsadm command and save the output somewhere:

     

    stsadm –o enumssptimerjobs –title "nameofssp"

     

    We need the GUIDs later

     

     

    2. Stop the SharePoint SPTimer Service (the Windows Service found under Computermanagement -> Services) on all SharePoint servers in the farm.

     

     

    3. Delete all xml files in the path "C:\ProgramData\Microsoft\SharePoint\Config\Some GUID" on every SharePoint Server in the farm. Don't delete the cache.ini file.

     

     

    4. Open the cache.ini file in the path "C:\ProgramData\Microsoft\SharePoint\Config\Some GUID" on every SharePoint Server in the farm and set the numer in the file to 1. Save the file

     

     

    5. Execute this query on the Shared Services DB (not the Shared Services Search DB) on the SQL Server:

     

    select LongXml , Cast([xml] as xml) from MIPOBJECTS where ObjectId=N'84F4E554-5D34-4C29-9E7E-9D4075971819'

     

    The XML output should contain fields named "profileChangeJobId", "profileChangeCleanupJobId", "profileFullImportJobId", "profileIncrementalImportJobId", "DLImportJobId" and "audienceCompilationJobId"

     

     

     

    6.

    Replace the GUIDs of the fields "profileChangeJobId", "profileChangeCleanupJobId", "profileFullImportJobId", "profileIncrementalImportJobId", "DLImportJobId" and "audienceCompilationJobId" in the XML output from the step before with zeros so that the result looks like this:

     

     

     

    <object>

    <field name="canonicalMySitePortalUrl" type="string">http://mysites.customer.com/</field>

    <field name="canonicalSearchCenterUrl" type="string">http://moss.customer.com/SearchCenter/Pages</field>

     

    <field name="profileChangeJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="profileChangeCleanupJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="profileFullImportJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="profileIncrementalImportJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="DLImportJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="audienceCompilationJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

     

    <field name="publishedLinksListId" type="guid">a6f420ad-c55a-4b3e-9bc8-fec98b8cfcd1</field>

    <field name="personalSiteLinksListId" type="guid">f6a4cb08-5a2e-4cd4-816f-7be4f96f4f00</field>

    <field name="profileGradualUpgradeJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="contentWebId" type="guid">06da499f-3a49-4123-b4ac-9bbbc7df1c8b</field>

    <field name="mySiteHostSiteId" type="guid">53543ec2-c802-43bb-bfce-55fd778e4e50</field>

    <field name="personalizationLinksListId" type="guid">3c605fa6-929f-4202-8375-5d3efe918eb5</field>

    <field name="profileStoreLanguage" type="int">1033</field>

    <field name="profileStoreLanguagePacksApplied" type="string">[1040][1031][1036][1033][1043][1053][1060][1029][1051]</field>

    <field name="profileStoreCollationId" type="int">25</field>

    <field name="profileCacheVersion" type="int">40</field>

    <field name="enablePersonalFeaturesForMultipleDeployments" type="boolean">false</field>

    <field name="assumeDomainNotFoundIfDCUnreachable" type="boolean">false</field>

    <field name="daysWorthOfEventsToKeep" type="int">7</field>

    <field name="ignoreIsActiveFlag" type="boolean">false</field>

    <field name="isUserManagementPagesUsingPersonalSiteLanguage" type="boolean">false</field>

    <field name="lastImportType" type="int">1</field>

    <field name="m_NeedsRestore" type="boolean">false</field>

    </object>

     

    Please note, your xml output can differ from that one shown above. This is the output from my SharePoint environment.

     

     

    7. Insert the modified XML string back into the SharedServices Database

    with the following SQL command:

     

    Update MIPObjects set [LongXML] ='<object>

    <field name="canonicalMySitePortalUrl" type="string">http://mysites.customer.com/</field>

    <field name="canonicalSearchCenterUrl" type="string">http://moss.customer.com/SearchCenter/Pages</field>

    <field name="profileChangeJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="profileChangeCleanupJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="profileFullImportJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="profileIncrementalImportJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="DLImportJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="audienceCompilationJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="publishedLinksListId" type="guid">a6f420ad-c55a-4b3e-9bc8-fec98b8cfcd1</field>

    <field name="personalSiteLinksListId" type="guid">f6a4cb08-5a2e-4cd4-816f-7be4f96f4f00</field>

    <field name="profileGradualUpgradeJobId" type="guid">00000000-0000-0000-0000-000000000000</field>

    <field name="contentWebId" type="guid">06da499f-3a49-4123-b4ac-9bbbc7df1c8b</field>

    <field name="mySiteHostSiteId" type="guid">53543ec2-c802-43bb-bfce-55fd778e4e50</field>

    <field name="personalizationLinksListId" type="guid">3c605fa6-929f-4202-8375-5d3efe918eb5</field>

    <field name="profileStoreLanguage" type="int">1033</field>

    <field name="profileStoreLanguagePacksApplied" type="string">[1040][1031][1036][1033][1043][1053][1060][1029][1051]</field>

    <field name="profileStoreCollationId" type="int">25</field>

    <field name="profileCacheVersion" type="int">40</field>

    <field name="enablePersonalFeaturesForMultipleDeployments" type="boolean">false</field>

    <field name="assumeDomainNotFoundIfDCUnreachable" type="boolean">false</field>

    <field name="daysWorthOfEventsToKeep" type="int">7</field>

    <field name="ignoreIsActiveFlag" type="boolean">false</field>

    <field name="isUserManagementPagesUsingPersonalSiteLanguage" type="boolean">false</field>

    <field name="lastImportType" type="int">1</field>

    <field name="m_NeedsRestore" type="boolean">false</field>

    </object>' where

    ObjectId=N'84F4E554-5D34-4C29-9E7E-9D4075971819'

     

     

    8. Start the SharePoint SPTimer Service (the Windows Service found under Computermanagement -> Services) on all SharePoint servers in the farm.

     

     

    9. Wait a couple of minutes and then execute the following stsadm command:

     

    stsadm –o enumssptimerjobs –title "nameofssp"

     

    The missing timer job(s) should be there now. It is likeley that some of the timer jobs exists more then one time now. So use the GUIDs of the original timer jobs from step 1 and delete the this jobs with the following stsadm command:

     

    stsadm -o deletessptimerjob -title "Timer Job Title" -jobid "Timer Job GUID"

     

     

    Good luck!

    Thursday, October 27, 2011 3:01 PM