SQL Writer error message on bootup.

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.

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

"LibranDragon64" <LibranDragon64@discussions.microsoft.com> wrote in message
news:4308199B-8E2A-41E2-BDC3-6284D86A3DDD@microsoft.com...
> 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.

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@discussions.microsoft.com> wrote in message
> news:4308199B-8E2A-41E2-BDC3-6284D86A3DDD@microsoft.com...
> > 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.
>
>

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@discussions.microsoft.com> wrote in message
news:0E4B1FBF-B60D-4318-8956-0BFBE519DFA3@microsoft.com...
> 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@discussions.microsoft.com> wrote in
>> message
>> news:4308199B-8E2A-41E2-BDC3-6284D86A3DDD@microsoft.com...
>> > 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.
>>
>>

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@discussions.microsoft.com> wrote in message
> news:0E4B1FBF-B60D-4318-8956-0BFBE519DFA3@microsoft.com...
> > 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@discussions.microsoft.com> wrote in
> >> message
> >> news:4308199B-8E2A-41E2-BDC3-6284D86A3DDD@microsoft.com...
> >> > 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.
> >>
> >>
>
>
>

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@discussions.microsoft.com> wrote in message
news:3B338952-BED8-4CE4-B978-AEA79EA00CE6@microsoft.com...
> 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@discussions.microsoft.com> wrote in
>> message
>> news:0E4B1FBF-B60D-4318-8956-0BFBE519DFA3@microsoft.com...
>> > 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@discussions.microsoft.com> wrote in
>> >> message
>> >> news:4308199B-8E2A-41E2-BDC3-6284D86A3DDD@microsoft.com...
>> >> > 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.
>> >>
>> >>
>>
>>
>>

Hi Rod,

I noticed that this post is duplicated with the other issue which is post
by you on 6/23/2008 5:56 PM:

http://www.microsoft.com/communities...ault.aspx?&lan
g=&cr=&guid=&sloc=en-us&dg=microsoft.public.windows.server.sbs&p=1&tid=5fb8b
2ed-97d7-421b-828a-edaedd2555a5&mid=5fb8b2ed-97d7-421b-828a-edaedd2555a5

In order to prevent duplicated efforts on the same issue, we recommend that
let's focus on one thread. That way the issue can receive full attention
from the Support Professional to whom it is assigned in one thread. This
will also make the thread more clear and consistent for your reference.

Also, if you want to do it in this post, please feel free to let me know,
we will be very glad to work with you.

Thank you for your patience and understanding.

Best regards,

Gary Wang(MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities...s/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com>
| References: <4308199B-8E2A-41E2-BDC3-6284D86A3DDD@microsoft.com>
<#cXGsBD2IHA.5472@TK2MSFTNGP06.phx.gbl>
<0E4B1FBF-B60D-4318-8956-0BFBE519DFA3@microsoft.com>
<eayANkk2IHA.5088@TK2MSFTNGP05.phx.gbl>
<3B338952-BED8-4CE4-B978-AEA79EA00CE6@microsoft.com>
| Subject: Re: SQL Writer error message on bootup.
| Date: Sun, 29 Jun 2008 22:22:57 -0400
| Lines: 165
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
| X-RFC2646: Format=Flowed; Original
| Message-ID: <eZHf4gl2IHA.4772@TK2MSFTNGP03.phx.gbl>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: pool-71-97-156-126.aubnin.dsl-w.verizon.net
71.97.156.126
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:113426
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| 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@discussions.microsoft.com> wrote in
message
| news:3B338952-BED8-4CE4-B978-AEA79EA00CE6@microsoft.com...
| > 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@discussions.microsoft.com> wrote in
| >> message
| >> news:0E4B1FBF-B60D-4318-8956-0BFBE519DFA3@microsoft.com...
| >> > 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@discussions.microsoft.com> wrote in
| >> >> message
| >> >> news:4308199B-8E2A-41E2-BDC3-6284D86A3DDD@microsoft.com...
| >> >> > 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.
| >> >>
| >> >>
| >>
| >>
| >>
|
|
|