CI Build broke after nugit update

For various reasons i wont go into it is pretty clear to me that the people who originally set up the search server had never restarted it.. ever. I am having some trouble getting search to function correctly, or even start back up normally after i restarted the search server.

What oringally forced me to restart the server was during my morning browsing of the error logs on my servers, i noticed that the search server (MOSS) had no hard drive space left on it's c:\ drive. So after clearing out some *.log files and freeing up alot of space, i tried restarting the server.

The error messages i get are as follow:

1. Under Shared Services Administration> Search> Search settings
   The search service is currently offline. Visit the services on Server page in SharePoint Central Administration to verify whether the service is enabled. This might also be because an indexer move is in progress.
   
2. On the search server (Moss) event log:
   The database connection string is not available.
   Event Type: Error
   Event Source: Office Server Search
   Event Category: Gatherer
   Event ID: 10046
   Date: 12/9/2008
   Time: 2:04:15 PM
   User: N/A
   Computer: MOSS
   Description:
   The database connection string is not available.
   ---------------------------------------------------------------
   Event Type: Error
   Event Source: Office Server Search
   Event Category: Gatherer
   Event ID: 10032
   Date: 12/9/2008
   Time: 2:06:15 PM
   User: N/A
   Computer: MOSS
   Description:
   Could not create a database session.
   
   Context: Application 'b41221b0-0663-4c48-b9d6-1d09c213d21b'
   
   Details:
   The database connection string is not available. (0xc0041228)
   
   The service then stops, and starts it's self again.
3. On the web front end machine's error log:
   Event Type: Warning
   Event Source: Office Server Search
   Event Category: Search service
   Event ID: 10039
   Date: 12/9/2008
   Time: 2:00:58 PM
   User: N/A
   Computer: INTRA
   Description:
   Retry of query machine 'MOSS' has failed with error: The system cannot find the file specified. 0x80070002.

The solution, i also posted it on technet:

After toying around with settings for over a day, i found a solution to my problem, here are the steps i took, first few steps are most likely not needed, but it is exactly what i did:

1. Removed search and indexing from the search and indexing server
   (Central Administration > Operations > Servers in Farm > Click on the server's name)
   
2. Set their roles to be search/index again but did not rebind them to my old SSP
   (Central Administration > Operations > Servers in Farm > Click on the server's name)
   
3. Created a new web application for my (to be new soon) SSP
   (Central Administration > Application Management > Create or Extend Web Application > Create New Web Application)
   
4. Created a new SSP using the above as my web application"
   (Central Administration > Application Management > Manage this Farm's Shared Service > New SSP)
   
5. Moved all of my sites over to my new SSP
   (Central Administration > Application Management > Manage this Farm's Shared Services > Change Association between Web Applications and SSPs)

Now if you have the same problem i had creating a new SSP, you may need to set up the username or correct any deleted usernames for your central administration site:

Found that solution on this blog here: http://blog.rafelo.com/2008/04/shared-services-provider-creation.html

1. Go to SharePoint Central Administration --> Application Management.
2. Click "Site Collection Administrators" under the "SharePoint Site Management" group.
3. Make sure you select the Central Administration Site Collection.
4. Update the Primary (and secondary of necessary) Site Collection Administrator accounts.
5. Execute the following stsadm command:
   stsadm -o execadmsvcjobs

Also if you have a problem with moving your main web application because you made it your shared service provider administration site, you will need to move your SSP admin site:

1. Create a new web application for the SSP to site on.
   (Central Administration > Application Management > Create or Extend Web Application > Create New Web Application)

2. Define a new managed path for the web application to be "ssp/admin"
   (Central Administration > Application Management > Define Managed Paths)
   And make it explicit inclusion.
3. Create a new site collection using a ssp administration site template through stsadm:
   stsadm -o createsute http://[the new web application from 1]:[Port]/ssp/admin -ownerlogin [login] -owneremail [email] -sitetemplate OSRV#0 -title "Shared Services Administration SharedServices1"
   replace the SharedServices1 at the end with your sharedservices administration site and fill in all of the [] feilds
4. Edit your SSP to point to the new ssp administration site you just made
   stsadm -o editssp -title "[your ssp name]" -sspadminsite "[the url to the new ssp site you just made, dont forget :port/ssp/admin]"

Simple right? right? Have a good one.