<p>We've been having some issues with a SharePoint instance in a test
environment. Thankfully this is not production ;) The problems started
when the disk with the SQL Server databases and search index ran out
of space. Following this, the search service would not run and search
settings in the SSP were not accessible. Reclaiming the disk space did
not resolve the issue. So rather than restoring the VM, we decided to
try to fix the issue.</p>

<p>We created a new SSP and changed the association of all services to
the new SSP. The old SSP and it's databases were then deleted. Search
results for PDF files are no longer appearing, but the search works
fine otherwise. MySites also works OK.</p>

<p>Following the implementation of this change, these problems occur:</p>

<blockquote>
  <p>1) An audit failure message started appearing in the application event log, for 'DOMAIN\SPMOSSSvc' which is the MOSS farm account.</p>
</blockquote>

<pre><code>Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18456
Date: 8/5/2008
Time: 3:55:19 PM
User: DOMAIN\SPMOSSSvc
Computer: dastest01
Description:
Login failed for user 'DOMAIN\SPMOSSSvc'. [CLIENT: &lt;local machine&gt;]
</code></pre>

<blockquote>
  <p>2) SQL Server profiler is showing queries from SharePoint that reference the old
  (deleted) SSP database.</p>
</blockquote>

<p>So...</p>

<ul>
<li>Where would these references to DOMAIN\SPMOSSSvc and the old SSP
database exist?</li>
<li>Is there a way to 'completely' remove the SSP from the server, and
re-create? The option to delete was not available (greyed out) when a
single SSP is in place.</li>
</ul>

[{'answer_id': 5475, 'author': 'Daniel O', 'author_id': 697, 'author_profile': 'https://Stackoverflow.com/users/697', 'pm_score': 1, 'selected': False, 'text': '<p>Have you tried removing the SSP using the command line? I found this worked once when we had a broken an SSP and just wanted to get rid of it.</p>\n\n<p>The command is:</p>\n\n<pre><code>stsadm.exe -o deletessp -title &lt;sspname&gt; [-deletedatabases]\n</code></pre>\n\n<p>The <code>deletedatbases</code> switch is optional.</p>\n\n<hr>\n\n<p>Also, check in Central Administration under Job Definitions and Job Schedules to ensure no SSP related jobs are still running</p>\n'}, {'answer_id': 7109, 'author': 'Daniel McPherson', 'author_id': 897, 'author_profile': 'https://Stackoverflow.com/users/897', 'pm_score': 2, 'selected': False, 'text': '<p>I suspect these are related to the SQL Server Agent trying to login to a database that no longer exists. </p>\n\n<p>To clear it up you need to:\n 1. Go to SQL Server Management Studio\n 2. Disable the job called <code>&lt;database name&gt;_job_deleteExpiredSessions</code></p>\n\n<p>If that works, then you should be all clear to delete it.</p>\n'}, {'answer_id': 97256, 'author': 'Aidenn', 'author_id': 15346, 'author_profile': 'https://Stackoverflow.com/users/15346', 'pm_score': 4, 'selected': True, 'text': '<p>As Daniel McPherson said, this is caused when SSPs are deleted but the associated \njob are not and attempt to communicate with the deleted database.<br><br>If the SSP \ndatabase has been deleted or a problem occurred when deleting an SSP, the job may \nnot be deleted. When the job attempts to run, it will fail since the database no \nlonger exists.</p>\n\n<p>Follow the steps Daniel mentioned:<br>\n1. Go to SQL Server Management Studio <br>\n2. Disable the job called SSPNAME_JobDeleteExpiredSessions, right click and choose Disable Job.</p>\n'}]
['https://Stackoverflow.com/questions/4752', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/636/']