Re: Unable to run SQL Query Analyzer ......

Hi Steve,

Thank you very much for the prompt reply.

I do see Microsoft SQL Server SP4 folder in C:\Programs Files. I'll apply
SP4 to both the default instance and SharePoint instance, and let you know
the results.

Regards,

Leo

"Steve Foster [SBS MVP]" wrote:

Leo wrote:

Hi there,

I have a SBS2003 Premium Edition with SQL 2000 installed. I also upgraded
SharePoint web site database from MSDE to SQL2000 SP3.

Did you really mean SP3? The rest of the SQL/MSDE instances on SBS2003 are
at SP4, so you've almost certainly broken shared bits by stopping at SP3.

I'd start by reapplying SP4 to all instances.


I got the following 3 errors regarding the Windows SharePoint Service 2.0,
MSSQL$SHAREPOINT, and Active Server Pages:

1. Windows SharePoint Services 2.0: #50070: Unable to connect to the
database STS_ADENNA-SFS-SVR_1 on ADENNA-SFS-SVR\SharePoint. Check the
database connection information and make sure that the database server is
running.

That suggests the instance is unavailable.

2. MSSQL$SHAREPOINT: 17113 : initconfig: Error 32(The process cannot
access
the file because it is being used by another process.) opening 'C:\Program
Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data\master.mdf' for
configuration information.

That strongly suggests that the Sharepoint instance isn't starting
properly, because it can't get access to the Master database (on which SQL
depends!).


3. Active Server Pages: Error: The Template Persistent Cache initialization
failed for Application Pool 'DefaultAppPool' because of the following
error:
Could not create a Disk Cache Sub-directory for the Application Pool. The
data may have additional error codes.

That's minor, and can be ignored for the time being. It's not directly
relevant to the bigger problem.


I can see the SharePoint Instance and its databases on SQL Enterprise
Magager. When I tried to run SQL Query Analyzer from Tools menu inside SQL
Enterprise Manager, it gives me the error of "The specified file was not
found"

SQL Query Analyzer runs from Start >> All Programs >> Microsoft SQL Server
Programs group, but MSSQL$SHAREPOINT instance is not listed in the Select
Server dialog box.

I tried to run Server Network Utility, it gives me the error of "The
specified module could not be found" with the title of 126.

These are additional symptoms of the mismatched service pack levels.

OSQL utility can query the instance.

Really? That seems highly unlikely.


--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

.

Relevant Pages

  • Re: Full Text Repair
    ... Emil Caruthers ... > Since your customer has already applied SP4, I'm assuming that this is a SQL ... > For SQL Server 7.0 installations, there is a registry key and value that you ...
    (microsoft.public.sqlserver.fulltext)
  • Re: SQL Server SP3 vs SP4 questions
    ... SQL with SP4 applied, SPS front-end web server with SQL client tools at SP3, ...
    (microsoft.public.sharepoint.portalserver)
  • Re: SBS 2003 Std - SQL Eval expired...will un-installing break SBS fun
    ... I agree with Claus that you're able to remove SQL 2005 instances if you did ... you can get SBS R2 which already contains SQL Server 2005 ... Workgroup Edition, and upgrade Sharepoint instance, and install other ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... Scenario 1" in SQL Server 2000 Books Online. ... Run Database Components SP4 Setup on the node you have ... DBC01 (SQL Instance 1) ...
    (microsoft.public.sqlserver.clustering)
  • Re: Full Text Repair
    ... Since your customer has already applied SP4, I'm assuming that this is a SQL ... For SQL Server 7.0 installations, there is a registry key and value that you ... It will contain your hotfix build version number such that 7.00.xxx is the ...
    (microsoft.public.sqlserver.fulltext)
Loading