Re: SQL Writer error message on bootup.

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Rod,

Here's one way to determine your SQL version...

How to identify your SQL Server version and edition
http://support.microsoft.com/kb/321185

Here's another...

SBS 2003 Version and service packs (including components)
http://reloadnuggets.com/?p=14

--
Merv Porter [SBS-MVP]
============================

"LibranDragon64" <LibranDragon64@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3B338952-BED8-4CE4-B978-AEA79EA00CE6@xxxxxxxxxxxxxxxx
Hi Merv. Thanks for your reply.

Initially i did download Sp2 to E: drive but when it failed to upgrade i
copied it to C: drive and run it again but still got the same install
error.

How can i find out which version of SQL server/update is currently
installed
on this machine? It was already installed prior to me working at this
company.

Thanks
Rod.


"Merv Porter [SBS-MVP]" wrote:

Juts a guess...

If not done already: When you upgrade to SQL Server 2003 Sp2, copy Sp2
to
the C: drive rather than another partition or some other drive (inlcuding
an
external drive). The try to run SP2.

--
Merv Porter [SBS-MVP]
============================


"LibranDragon64" <LibranDragon64@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:0E4B1FBF-B60D-4318-8956-0BFBE519DFA3@xxxxxxxxxxxxxxxx
Hi bass_player thanks for your reply.

I have tried to restart the MICROSOFT##SSEE as advised but got the
following
error:
Could not start the Windows Internal Database (MICROSOFT##SSEE) service
on
local computer. Error 1053: The service did not respond to the start or
control request in a timely fashion.

There was also an Error in the Application Log as follows: Event ID:
1000
Source: Application Error. Faulting application sqlserver.exe, version
2005.90.3042.0 faulting module kernel32.dll, version 5.2.3790.2919,
fault
address 0x0015e02.

Any further help would be appreciated.

Rod



"bass_player" wrote:

Try restating the MICROSOFT##SSEE service and see what happens

"LibranDragon64" <LibranDragon64@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:4308199B-8E2A-41E2-BDC3-6284D86A3DDD@xxxxxxxxxxxxxxxx
On booting our SBS Server 2003 Sp1 (Not R2) I receive the following
error
message on the screen.

SQLDumper library failed initialization. Your installation is either
corrupt
or has been tampered with. Please uninstall then re-run setup to
correct
this
problem.

After looking at the System logs in the event viewer the following 5
error
messages appear:

ID: 7022 Source: Service Control Manager
The Kerberos Key Distribution Center service hung on starting.

ID: 7009 Source: Service Control Manager
Timeout (30000 milliseconds) waiting for the Windows Internal
Database
(MICROSOFT##SSEE) service to connect.

ID: 7000 Source: Service Control Manager
The Windows Internal Database (MICROSOFT##SSEE) service failed to
start
due
to the following error:
The service did not respond to the start or control request in a
timely
fashion.

ID: 7022 Source: Service Control Manager
The SQL Server VSS Writer hung on starting.

ID: 7034 Source: Service Control Manager
The SQL Server VSS Writer service terminated unexpectedly.


And there is 1 error in the Application Log in the Event Viewer as
follows:

ID: 1008 Source: Perflib
The open procedure for service "PSched" in DLL
"C:\Windows\System32\pschdprf.dll" failed. Performance data for this
service
will not be available. The status code returned is the first DWORD
in
the
attached data.

It was recommended that I install SQL Server 2003 Sp2 to fix the
problem,
so
I downloaded SQL Server 2003 Sp2 from Microsoft and tried to install
with
the
following result:

During setup a message window appears saying that it detected the
following
SQL Server 2005 features: MSXML 6.0 Parser.
After clicking continue it says there are no locked files and then
it
appears to commence installation when a error message appears saying
"Hotfix.exe encountered a problem and needs to close, so i then
click
on a
view summary button but it contains no data, the program then
closes.


Any help on these issues would be appreciated.


Regards
Rod.







.

Quantcast