Error 1923 while installing SQL 2005 Express

This is from the event log

Product: Microsoft SQL Server 2005 Express Edition -- Error 1923. Service 'SQL Server ()' () could not be installed. Verify that you have sufficient privileges to install system services.

I've tried uninstalling through control panel and various cleanup tools and tried reinstalling with no luck.

I'm logged on with a user that has full admin rights.

1923 is an RPC error that translates to "The specified profile entry could not be added." You'll need to search through the SQL Server Setup log files for more detail on what went wrong. Start by looking here and in the subdirectory:

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Paul

|||I am having the same problem. Did you figure out a work around?

|||I have found NO answer to this question anywhere online. I got mine working last night here is what I did:
I was trying to install it on a VPS I only have licensing for one terminal server session and I noticed that earlier in the day my RDP connection had timed out and I was still logged in so I kicked the old connection uninstalled all instances of SQL and tried again. Guess what? it didn't work...lol So I uninstalled everything again and restarted the VPS and then it installed. I have no idea exactly what was wrong but that is how I solved it. Hope it helps someone else out.
sql

Error 1923 while installing SQL 2005 Express

This is from the event log

Product: Microsoft SQL Server 2005 Express Edition -- Error 1923. Service 'SQL Server ()' () could not be installed. Verify that you have sufficient privileges to install system services.

I've tried uninstalling through control panel and various cleanup tools and tried reinstalling with no luck.

I'm logged on with a user that has full admin rights.

1923 is an RPC error that translates to "The specified profile entry could not be added." You'll need to search through the SQL Server Setup log files for more detail on what went wrong. Start by looking here and in the subdirectory:

C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

Paul

|||I am having the same problem. Did you figure out a work around?

|||I have found NO answer to this question anywhere online. I got mine working last night here is what I did:
I was trying to install it on a VPS I only have licensing for one terminal server session and I noticed that earlier in the day my RDP connection had timed out and I was still logged in so I kicked the old connection uninstalled all instances of SQL and tried again. Guess what? it didn't work...lol So I uninstalled everything again and restarted the VPS and then it installed. I have no idea exactly what was wrong but that is how I solved it. Hope it helps someone else out.

ERROR 18456 not being logged in event viewer

Hi.
I made an alert that will email me whenever someone causes error 18456 to be
raised... My thinking behind this is that if anyones trying to access my
server and FAILS, then they are probably up to no good.
So anyway... This alert was created... I verified that SQL Server Agent
Mail is running, as is SQL Mail... so thats not the point of failure.
I just attempted to log in with sa and a fake password. It predictably did
not give me access to the databases, but the event was NOT logged to the
application log. I checked in enterprise manager, and the checkbox that
says "Always write to Windows eventlog" is checked.
I also verified that the SQL Server Agent is running under a local and
domain admin, and this is the case.
Does anybody have any ideas?
Thanks in advance,
-- Jason
I assume that this error number is failed login. If so, you handle this in a special way. EM, right-click your
server, security.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jeigh" <folkens.jason@.acd.net> wrote in message news:CoydnaIo9LfTcVndRVn-gw@.giganews.com...
> Hi.
> I made an alert that will email me whenever someone causes error 18456 to be
> raised... My thinking behind this is that if anyones trying to access my
> server and FAILS, then they are probably up to no good.
> So anyway... This alert was created... I verified that SQL Server Agent
> Mail is running, as is SQL Mail... so thats not the point of failure.
> I just attempted to log in with sa and a fake password. It predictably did
> not give me access to the databases, but the event was NOT logged to the
> application log. I checked in enterprise manager, and the checkbox that
> says "Always write to Windows eventlog" is checked.
> I also verified that the SQL Server Agent is running under a local and
> domain admin, and this is the case.
> Does anybody have any ideas?
> Thanks in advance,
> -- Jason
>
|||Are you referring to the "Audit Level" raido buttons?
Changing it from "None" to "Failure" didnt seem to make that much of a
difference. Am I looking at the right thing?
Thanks,
-- Jason
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:O6NBB4STEHA.2416@.TK2MSFTNGP09.phx.gbl...
> I assume that this error number is failed login. If so, you handle this in
a special way. EM, right-click your
> server, security.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Jeigh" <folkens.jason@.acd.net> wrote in message
news:CoydnaIo9LfTcVndRVn-gw@.giganews.com...[vbcol=seagreen]
to be[vbcol=seagreen]
my[vbcol=seagreen]
Agent[vbcol=seagreen]
did
>
|||Yep, that's the one I was referring to. So you don't see the events logged to eventlog, after checking the
checkbox. Strange, I know it work for me. Perhaps time to open a case with MS?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jeigh" <folkens.jason@.acd.net> wrote in message news:p7GdnZI30-avWFjd4p2dnA@.giganews.com...
> Are you referring to the "Audit Level" raido buttons?
> Changing it from "None" to "Failure" didnt seem to make that much of a
> difference. Am I looking at the right thing?
> Thanks,
> -- Jason
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:O6NBB4STEHA.2416@.TK2MSFTNGP09.phx.gbl...
> a special way. EM, right-click your
> news:CoydnaIo9LfTcVndRVn-gw@.giganews.com...
> to be
> my
> Agent
> did
>

Error 17883

Hi ~
I realize that this has been posted on, but I am confused. We are
getting an error in our event logs at odd times (not at backup times or
anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
Scheduler 3, or a variant there of.. and so far, the only solution
that I can see for this problem on a Win2K server running SQL 2000 SP4
is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
option though, as this would open the server to known security flaws,
etc... correct? Are there any other options?
Hi
17883 errors have been around since SP3 (the error was introduced to show
issues that were there, but were not detectable by users).
More and more have been fixed in the various hotfixes since then. It is best
for you to open a case with Microsoft Support so that they can sort the
problem out for you.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"shandain@.gmail.com" wrote:

> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>
|||I had this error after MS05-027 applied. Removing MS05-027 fixed the
problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
drivers were up-to-date. Engineers from MS admitted it was a rare bug
reported only by 2 customers. Since it affected only 2 customers MS didn't
want to think of a fix and asked us to seal the port 454.
<shandain@.gmail.com> wrote in message
news:1125535239.274678.73180@.o13g2000cwo.googlegro ups.com...
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>
|||I met this error on SP3a after moving to SAN. Now we are trying to install
SP4 to fix this issue. You can find my post on Sept 1. Are you running on
SAN?
Bill
"shandain@.gmail.com" wrote:

> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>
|||How do i remove MS05-027 as it is not showing up in the add remove programs.
(I'm not sure if i have removed it but i am still getting the 17883 errors
when trying to backup databases)
"ME" wrote:

> I had this error after MS05-027 applied. Removing MS05-027 fixed the
> problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
> drivers were up-to-date. Engineers from MS admitted it was a rare bug
> reported only by 2 customers. Since it affected only 2 customers MS didn't
> want to think of a fix and asked us to seal the port 454.
>
> <shandain@.gmail.com> wrote in message
> news:1125535239.274678.73180@.o13g2000cwo.googlegro ups.com...
>
>

Error 17883

Hi ~
I realize that this has been posted on, but I am confused. We are
getting an error in our event logs at odd times (not at backup times or
anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
Scheduler 3, or a variant there of.. and so far, the only solution
that I can see for this problem on a Win2K server running SQL 2000 SP4
is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
option though, as this would open the server to known security flaws,
etc... correct? Are there any other options?Hi
17883 errors have been around since SP3 (the error was introduced to show
issues that were there, but were not detectable by users).
More and more have been fixed in the various hotfixes since then. It is best
for you to open a case with Microsoft Support so that they can sort the
problem out for you.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"shandain@.gmail.com" wrote:

> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||I had this error after MS05-027 applied. Removing MS05-027 fixed the
problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
drivers were up-to-date. Engineers from MS admitted it was a rare bug
reported only by 2 customers. Since it affected only 2 customers MS didn't
want to think of a fix and asked us to seal the port 454.
<shandain@.gmail.com> wrote in message
news:1125535239.274678.73180@.o13g2000cwo.googlegroups.com...
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||I met this error on SP3a after moving to SAN. Now we are trying to install
SP4 to fix this issue. You can find my post on Sept 1. Are you running on
SAN?
Bill
"shandain@.gmail.com" wrote:

> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||How do i remove MS05-027 as it is not showing up in the add remove programs.
(I'm not sure if i have removed it but i am still getting the 17883 errors
when trying to backup databases)
"ME" wrote:

> I had this error after MS05-027 applied. Removing MS05-027 fixed the
> problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. Al
l
> drivers were up-to-date. Engineers from MS admitted it was a rare bug
> reported only by 2 customers. Since it affected only 2 customers MS didn'
t
> want to think of a fix and asked us to seal the port 454.
>
> <shandain@.gmail.com> wrote in message
> news:1125535239.274678.73180@.o13g2000cwo.googlegroups.com...
>
>

Error 17883

Hi ~
I realize that this has been posted on, but I am confused. We are
getting an error in our event logs at odd times (not at backup times or
anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
Scheduler 3, or a variant there of.. and so far, the only solution
that I can see for this problem on a Win2K server running SQL 2000 SP4
is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
option though, as this would open the server to known security flaws,
etc... correct? Are there any other options?Hi
17883 errors have been around since SP3 (the error was introduced to show
issues that were there, but were not detectable by users).
More and more have been fixed in the various hotfixes since then. It is best
for you to open a case with Microsoft Support so that they can sort the
problem out for you.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"shandain@.gmail.com" wrote:
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||I had this error after MS05-027 applied. Removing MS05-027 fixed the
problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
drivers were up-to-date. Engineers from MS admitted it was a rare bug
reported only by 2 customers. Since it affected only 2 customers MS didn't
want to think of a fix and asked us to seal the port 454. :)
<shandain@.gmail.com> wrote in message
news:1125535239.274678.73180@.o13g2000cwo.googlegroups.com...
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||I met this error on SP3a after moving to SAN. Now we are trying to install
SP4 to fix this issue. You can find my post on Sept 1. Are you running on
SAN?
Bill
"shandain@.gmail.com" wrote:
> Hi ~
> I realize that this has been posted on, but I am confused. We are
> getting an error in our event logs at odd times (not at backup times or
> anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> Scheduler 3, or a variant there of.. and so far, the only solution
> that I can see for this problem on a Win2K server running SQL 2000 SP4
> is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> option though, as this would open the server to known security flaws,
> etc... correct? Are there any other options?
>|||How do i remove MS05-027 as it is not showing up in the add remove programs.
(I'm not sure if i have removed it but i am still getting the 17883 errors
when trying to backup databases)
"ME" wrote:
> I had this error after MS05-027 applied. Removing MS05-027 fixed the
> problem. It happened on 2 DL380 G2 Compaq servers with exac same h/w. All
> drivers were up-to-date. Engineers from MS admitted it was a rare bug
> reported only by 2 customers. Since it affected only 2 customers MS didn't
> want to think of a fix and asked us to seal the port 454. :)
>
> <shandain@.gmail.com> wrote in message
> news:1125535239.274678.73180@.o13g2000cwo.googlegroups.com...
> > Hi ~
> >
> > I realize that this has been posted on, but I am confused. We are
> > getting an error in our event logs at odd times (not at backup times or
> > anything) with the infamous Error: 17883, Severity: 1, State: 0 Process
> > 0:0 (e54) UMS Context 0x121CA9A0 appears to be non-yielding on
> > Scheduler 3, or a variant there of.. and so far, the only solution
> > that I can see for this problem on a Win2K server running SQL 2000 SP4
> > is to downgrade to SQL 2000 sp3a... I can't really see this as a valid
> > option though, as this would open the server to known security flaws,
> > etc... correct? Are there any other options?
> >
>
>

Error 17055

Getting the following in the event log after starting the
sql services.
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17055
Date: 1/22/2004
Time: 2:37:21 PM
User: N/A
Computer: SMSPRIMARY
Description:
18456 :
Login failed for user 'smslab\smsadmin'.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 0b 00 00 00 53 00 4d 00 ...S.M.
0010: 53 00 50 00 52 00 49 00 S.P.R.I.
0018: 4d 00 41 00 52 00 59 00 M.A.R.Y.
0020: 00 00 07 00 00 00 6d 00 .....m.
0028: 61 00 73 00 74 00 65 00 a.s.t.e.
0030: 72 00 00 00 r...
This is a SMS 2003 server.
Any info would be helpful. Thanks.Piedmont,
This is actually error 18456. It appears that smslab\smsadmin does not have
rights to login. From the BOL:
Error 18456
Severity Level 14
Message Text
Login failed for user '%ls'.
Explanation
You do not have permission to log in to the server.
Action
Contact a member of the sysadmin fixed server role to request login
permission.
Russell Fields
"Piedmont" <anonymous@.discussions.microsoft.com> wrote in message
news:26c401c3e11d$7e06ec70$a001280a@.phx.gbl...

quote:

---

> Getting the following in the event log after starting the
> sql services.
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (4)
> Event ID: 17055
> Date: 1/22/2004
> Time: 2:37:21 PM
> User: N/A
> Computer: SMSPRIMARY
> Description:
> 18456 :
> Login failed for user 'smslab\smsadmin'.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 18 48 00 00 0e 00 00 00 .H.....
> 0008: 0b 00 00 00 53 00 4d 00 ...S.M.
> 0010: 53 00 50 00 52 00 49 00 S.P.R.I.
> 0018: 4d 00 41 00 52 00 59 00 M.A.R.Y.
> 0020: 00 00 07 00 00 00 6d 00 .....m.
> 0028: 61 00 73 00 74 00 65 00 a.s.t.e.
> 0030: 72 00 00 00 r...
>
> This is a SMS 2003 server.
> Any info would be helpful. Thanks.

---

|||In enterprise manager under logins the user is listed and
has the right to login to the database.

quote:

---

>--Original Message--
>Piedmont,
>This is actually error 18456. It appears that

---

smslab\smsadmin does not have

quote:

---

>rights to login. From the BOL:
>Error 18456
>Severity Level 14
>Message Text
>Login failed for user '%ls'.
>Explanation
>You do not have permission to log in to the server.
>Action
>Contact a member of the sysadmin fixed server role to

---

request login

quote:

---

>permission.
>
>Russell Fields
>"Piedmont" <anonymous@.discussions.microsoft.com> wrote in

---

message

quote:

---

>news:26c401c3e11d$7e06ec70$a001280a@.phx.gbl...
the[QUOTE]
>
>.
>

---

|||Then I have no help for you, I am afraid. My only suggestions are clerical:
-- Double check the spelling of the login that you see in SEM just in case.
-- Doube check the server you are investigating, the domain of the login is
smslab, do you have an smsprd?
Sorry,
Russell Fields
"Piedmont" <anonymous@.discussions.microsoft.com> wrote in message
news:2bd501c3e126$2c249e30$a601280a@.phx.gbl...[QUOTE]
> In enterprise manager under logins the user is listed and
> has the right to login to the database.
>
> smslab\smsadmin does not have
> request login
> message
> the|||Perhaps the SMSAdmin password was changed. Make sure you can stop n start
this account from Control panel services. Also verify that it is a member
of the Builtin admin group via the local administrators group on the
machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sql

Error 17052

I've got the following event in the event viewer of my server that runs
SQL Server 2000, and it's getting stopped every 5 minutes, I don't know
if this event and the crash have relation, if anyone know, please help
me...
17052:
This SQL Server has been optimized for 8 concurrent queries. This limit
has been exceedec by 5 queries and performance may be adversely
affected.
Diego Modolo Ribeiro
Harsmaken
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message389771.htmlWhat version of SQL do you have and how many CPUs do U have configured for S
QL
if more than 4 what is your MAXDOP(sp_configure 'Degree') run_value?|||You are running either MSDE or Personal Edition, and these 2 versions are
optimised for a maximum of 8 concurrent queries. When you have more, the
performance of your server will drop, and you might get time outs etc. You
will have to upgrade to SQL Server Standard Edition if you want to have more
concurrent queries.
Jacco Schalkwijk
SQL Server MVP
"Harsmaken" <Harsmaken.11kjeo@.mail.mcse.ms> wrote in message
news:Harsmaken.11kjeo@.mail.mcse.ms...
> I've got the following event in the event viewer of my server that runs
> SQL Server 2000, and it's getting stopped every 5 minutes, I don't know
> if this event and the crash have relation, if anyone know, please help
> me...
> 17052:
> This SQL Server has been optimized for 8 concurrent queries. This limit
> has been exceedec by 5 queries and performance may be adversely
> affected.
>
> Diego Modolo Ribeiro
>
> Harsmaken
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message389771.html
>|||Thanks for clearing this up Jacco..never encountered this before|||On Wed, 19 Nov 2003 08:21:35 -0800, "eric"
<anonymous@.discussions.microsoft.com> wrote:

>Error: 644, Severity: 21, State: 3
>Could not find the index entry for
>RID '36100101406d0610730740650720' in index page (1:257),
>index ID 0, database 'master'.
hi Eric,
we encountered the same issue on a freshly install of an
active/passive cluster Windows 2000 AS SP4 with SQLServer 2000 SP3.
the issue comes out when we try to move related cluster services from
node A to node B.
apart of fixing the master table, I'd be interested on knowing the
cause of such index curruption.
have you got any ideas?
thank you.
Francesco "Matro" Martire
available at www.realpopup.it:
RealPopup, the freeware winpopup replacer
RealAccount, freeware plugin for MS Outlook XP
MaTreo, freeware frontscreen for your Treo and PalmOS devices

Error 17052

I've got the following event in the event viewer of my server that run
SQL Server 2000, and it's getting stopped every 5 minutes, I don't kno
if this event and the crash have relation, if anyone know, please hel
me...
17052:
This SQL Server has been optimized for 8 concurrent queries. This limi
has been exceedec by 5 queries and performance may be adversel
affected.
Diego Modolo Ribeir
Harsmake
----
Posted via http://www.mcse.m
----
View this thread: http://www.mcse.ms/message389771.htmWhat version of SQL do you have and how many CPUs do U have configured for SQL
if more than 4 what is your MAXDOP(sp_configure 'Degree') run_value?|||You are running either MSDE or Personal Edition, and these 2 versions are
optimised for a maximum of 8 concurrent queries. When you have more, the
performance of your server will drop, and you might get time outs etc. You
will have to upgrade to SQL Server Standard Edition if you want to have more
concurrent queries.
--
Jacco Schalkwijk
SQL Server MVP
"Harsmaken" <Harsmaken.11kjeo@.mail.mcse.ms> wrote in message
news:Harsmaken.11kjeo@.mail.mcse.ms...
> I've got the following event in the event viewer of my server that runs
> SQL Server 2000, and it's getting stopped every 5 minutes, I don't know
> if this event and the crash have relation, if anyone know, please help
> me...
> 17052:
> This SQL Server has been optimized for 8 concurrent queries. This limit
> has been exceedec by 5 queries and performance may be adversely
> affected.
>
> Diego Modolo Ribeiro
>
> Harsmaken
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message389771.html
>|||Thanks for clearing this up Jacco..never encountered this before

Error 1355 from SQL Server 2000

I found a warning from Event Viewer application log. It
is from SQL Server 2000,
Category: (B),
Event ID: 19011,
Description:
SuperSocket Info: (SpnRegister): Error 1355
What is about? Where should I look into?
Thanks,
TianwenHave you seen this: http://support.microsoft.com/?kbid=303411
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"tianwen" <anonymous@.discussions.microsoft.com> wrote in message
news:0d3801c3d934$40dd2f30$a601280a@.phx.gbl...
I found a warning from Event Viewer application log. It
is from SQL Server 2000,
Category: (B),
Event ID: 19011,
Description:
SuperSocket Info: (SpnRegister): Error 1355
What is about? Where should I look into?
Thanks,
Tianwen

Error 1355 from SQL Server 2000

I found a warning from Event Viewer application log. It
is from SQL Server 2000,
Category: (B),
Event ID: 19011,
Description:
SuperSocket Info: (SpnRegister): Error 1355
What is about? Where should I look into?
Thanks,
TianwenHave you seen this: http://support.microsoft.com/?kbid=303411
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"tianwen" <anonymous@.discussions.microsoft.com> wrote in message
news:0d3801c3d934$40dd2f30$a601280a@.phx.gbl...
I found a warning from Event Viewer application log. It
is from SQL Server 2000,
Category: (B),
Event ID: 19011,
Description:
SuperSocket Info: (SpnRegister): Error 1355
What is about? Where should I look into?
Thanks,
Tianwen

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I ca
n
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have th
e
same problem? Or maybe deleting the existing maintenance plan and creating i
t
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:

> We have a maintainance plan for full/diff/log backups of selected database
s
> running at regular intervals through SQLAgent. The backups are working; I
can
> restore the databases. But starting a few weeks ago we've been getting err
or
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backup
s
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage
)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Serve
r
> "ERRORLOG" text file also contains no error messages in connection with th
e
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestion
s
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have
the
> same problem? Or maybe deleting the existing maintenance plan and creating
it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried runnin
g
> the package manually from SSIS (like using the Execute Package Utility) an
d
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
>|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:

> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>
>
>

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom JuergensHi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:
> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
> > We have a maintainance plan for full/diff/log backups of selected databases
> > running at regular intervals through SQLAgent. The backups are working; I can
> > restore the databases. But starting a few weeks ago we've been getting error
> > messages in the system event log.
> >
> > First, there's an entry confirming the successful completion of the backups
> > with ID 18265 (source MSSQL$...)
> > Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> > followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> > Error ..." (source SQLAgent$...)
> >
> > As I said, the backups themselves seem to be successful, and the SQL Server
> > "ERRORLOG" text file also contains no error messages in connection with the
> > plans.
> >
> > This is still worrying us a bit, because we fear there might be a good
> > reason for these error messages, and obviously we want to be quite certain
> > that our backups are working properly and will be available if and when we
> > need them.
> >
> > Does anyone have any insight/advice on Error 12291?
> >
> > Thanks
> > Tom Juergens|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
======================================================When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:
> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ======================================================> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================>
>
>

Error 12291 in Event Log

We have a maintainance plan for full/diff/log backups of selected databases
running at regular intervals through SQLAgent. The backups are working; I can
restore the databases. But starting a few weeks ago we've been getting error
messages in the system event log.
First, there's an entry confirming the successful completion of the backups
with ID 18265 (source MSSQL$...)
Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
Error ..." (source SQLAgent$...)
As I said, the backups themselves seem to be successful, and the SQL Server
"ERRORLOG" text file also contains no error messages in connection with the
plans.
This is still worrying us a bit, because we fear there might be a good
reason for these error messages, and obviously we want to be quite certain
that our backups are working properly and will be available if and when we
need them.
Does anyone have any insight/advice on Error 12291?
Thanks
Tom Juergens
Hi Tom,
Since some maintenance plans are very easy to create, have you tried
creating a new or very similar maintenance plan and see if you still have the
same problem? Or maybe deleting the existing maintenance plan and creating it
again?
Also, since the maintenance plan is an SSIS package, have you tried running
the package manually from SSIS (like using the Execute Package Utility) and
check for errors or warnings? Have you tried Logging on this SSIS package?
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Tom Juergens" wrote:

> We have a maintainance plan for full/diff/log backups of selected databases
> running at regular intervals through SQLAgent. The backups are working; I can
> restore the databases. But starting a few weeks ago we've been getting error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL Server
> "ERRORLOG" text file also contains no error messages in connection with the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens
|||You would need to post the whole log to get a full analysis. The plan should
be generating a log file, not the error log, which may help. If not,
configure it to generate a detailed log.
Also check the package has no reference to mapped drives as the mappings may
not be available to SQL Agent.
Nigel Ainscoe
"Tom Juergens" <antaeus@.newsgroup.nospam> wrote in message
news:9A9C2F9C-A3E6-4131-9BC8-16196C1E6733@.microsoft.com...
> We have a maintainance plan for full/diff/log backups of selected
> databases
> running at regular intervals through SQLAgent. The backups are working; I
> can
> restore the databases. But starting a few weeks ago we've been getting
> error
> messages in the system event log.
> First, there's an entry confirming the successful completion of the
> backups
> with ID 18265 (source MSSQL$...)
> Then comes the error: ID 12291 "Error in package ..." (source
> SQLISPackage)
> followed by a warning with ID 208 "SQL Server Scheduled Job ... - Status:
> Error ..." (source SQLAgent$...)
> As I said, the backups themselves seem to be successful, and the SQL
> Server
> "ERRORLOG" text file also contains no error messages in connection with
> the
> plans.
> This is still worrying us a bit, because we fear there might be a good
> reason for these error messages, and obviously we want to be quite certain
> that our backups are working properly and will be available if and when we
> need them.
> Does anyone have any insight/advice on Error 12291?
> Thanks
> Tom Juergens
|||Thanks to you both for the pointers and good ideas. I'll try your suggestions
and post again here if I don't find a solution.
Tom
"Ben Nevarez" wrote:
[vbcol=seagreen]
> Hi Tom,
> Since some maintenance plans are very easy to create, have you tried
> creating a new or very similar maintenance plan and see if you still have the
> same problem? Or maybe deleting the existing maintenance plan and creating it
> again?
> Also, since the maintenance plan is an SSIS package, have you tried running
> the package manually from SSIS (like using the Execute Package Utility) and
> check for errors or warnings? Have you tried Logging on this SSIS package?
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "Tom Juergens" wrote:
|||Hi Tom,
To let us better understand your issue, could you please let us know the
following questions:
1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
2. Did the maintainance plan only backup your databases?
3. Could you please post all the event error messages here for more
effective research? You may also mail me (changliw_at_microsoft_dot_com)
the event error logs.
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||My client has decided to reinstall the server, which is a good option since
there are some other things that aren't quite right as well... So we just
have to live with this behavior for another couple of weeks and I won't be
investing much more time in finding a solution. Consider this case closed.
Thanks
Tom
"Charles Wang[MSFT]" wrote:

> Hi Tom,
> To let us better understand your issue, could you please let us know the
> following questions:
> 1. What is the version of your SQL Server? (Run SELECT @.@.VERSION.)
> 2. Did the maintainance plan only backup your databases?
> 3. Could you please post all the event error messages here for more
> effective research? You may also mail me (changliw_at_microsoft_dot_com)
> the event error logs.
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
>
>

error 1053 when try to start mssqlserver service

I have a two node cluster. When I try to failover from active node which is
node2 to node1 I get the following errors in the event viewer/ system logs
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely
fashion.
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
Cluster resource 'SQL Cluster Group Server Service' in Resource Group
'006-PM2-DBASQL' failed.
SQL Server Error Logs dont show any error either execpt one which i think is
unrelated to this issue:
2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-04-05 09:51:43.86 server All rights reserved.
2006-04-05 09:51:43.86 server Server Process ID is 5508.
2006-04-05 09:51:43.86 server Logging SQL Server messages in file
'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-04-05 09:51:43.86 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-04-05 09:51:44.00 server SQL Server configured for thread mode
processing.
2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-04-05 09:51:44.10 server Attempting to initialize Distributed
Transaction Coordinator.
2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-04-05 09:51:47.21 server SQL Server is ready for client connections
2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
complete (approximately 0 more seconds)
2006-04-05 09:51:53.63 spid3 Recovery complete.
2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
created.
2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlmaint'.
2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'S:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog _200604050952.TRN'}).
2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_MSgetversion'.
2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_msver'.
2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
MSSQLServer and SQLServerAgent services are running under a system admin
user account. What possibly could be the issue here?
Thanks
You could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/224071/en-us for
some info.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>I have a two node cluster. When I try to failover from active node which is
> node2 to node1 I get the following errors in the event viewer/ system logs
>
> The MSSQLSERVER service failed to start due to the following error:
> The service did not respond to the start or control request in a timely
> fashion.
> Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
> Cluster resource 'SQL Cluster Group Server Service' in Resource Group
> '006-PM2-DBASQL' failed.
>
> SQL Server Error Logs dont show any error either execpt one which i think is
> unrelated to this issue:
> 2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2006-04-05 09:51:43.86 server All rights reserved.
> 2006-04-05 09:51:43.86 server Server Process ID is 5508.
> 2006-04-05 09:51:43.86 server Logging SQL Server messages in file
> 'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2006-04-05 09:51:43.86 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2006-04-05 09:51:44.00 server SQL Server configured for thread mode
> processing.
> 2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2006-04-05 09:51:44.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
> 2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
> 2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
> 2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
> 2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
> 2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
> 2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
> 2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2006-04-05 09:51:47.21 server SQL Server is ready for client connections
> 2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
> 2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
> 2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
> 2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
> 2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
> 2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
> 2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
> 2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
> complete (approximately 0 more seconds)
> 2006-04-05 09:51:53.63 spid3 Recovery complete.
> 2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
> created.
> 2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlmaint'.
> 2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
> creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
> 23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
> {'S:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog _200604050952.TRN'}).
> 2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'sp_MSgetversion'.
> 2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
> 2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_msver'.
> 2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
>
> MSSQLServer and SQLServerAgent services are running under a system admin
> user account. What possibly could be the issue here?
> Thanks

error 1053 when try to start mssqlserver service

I have a two node cluster. When I try to failover from active node which is
node2 to node1 I get the following errors in the event viewer/ system logs
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely
fashion.
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
Cluster resource 'SQL Cluster Group Server Service' in Resource Group
'006-PM2-DBASQL' failed.
SQL Server Error Logs dont show any error either execpt one which i think is
unrelated to this issue:
2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-04-05 09:51:43.86 server All rights reserved.
2006-04-05 09:51:43.86 server Server Process ID is 5508.
2006-04-05 09:51:43.86 server Logging SQL Server messages in file
'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-04-05 09:51:43.86 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-04-05 09:51:44.00 server SQL Server configured for thread mode
processing.
2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2006-04-05 09:51:44.10 server Attempting to initialize Distributed
Transaction Coordinator.
2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433
.
2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-04-05 09:51:47.21 server SQL Server is ready for client connections
2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
complete (approximately 0 more seconds)
2006-04-05 09:51:53.63 spid3 Recovery complete.
2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
created.
2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlmaint'.
2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'S:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\TransactionLogs\Nort
hwind_tlog_200604050952.TRN'}).
2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_MSgetversion'.
2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_msver'.
2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
MSSQLServer and SQLServerAgent services are running under a system admin
user account. What possibly could be the issue here?
ThanksYou could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/
224071/en-us for
some info.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>I have a two node cluster. When I try to failover from active node which is
> node2 to node1 I get the following errors in the event viewer/ system logs
>
> The MSSQLSERVER service failed to start due to the following error:
> The service did not respond to the start or control request in a timely
> fashion.
> Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connec
t.
> Cluster resource 'SQL Cluster Group Server Service' in Resource Group
> '006-PM2-DBASQL' failed.
>
> SQL Server Error Logs dont show any error either execpt one which i think
is
> unrelated to this issue:
> 2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2006-04-05 09:51:43.86 server All rights reserved.
> 2006-04-05 09:51:43.86 server Server Process ID is 5508.
> 2006-04-05 09:51:43.86 server Logging SQL Server messages in file
> 'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2006-04-05 09:51:43.86 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2006-04-05 09:51:44.00 server SQL Server configured for thread mode
> processing.
> 2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500]
Lock
> Blocks, [5000] Lock Owner Blocks.
> 2006-04-05 09:51:44.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
> 2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 14
33.
> 2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
> 2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
> 2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
> 2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
> 2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
> 2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memor
y,
> Named Pipes.
> 2006-04-05 09:51:47.21 server SQL Server is ready for client connection
s
> 2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
> 2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
> 2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
> 2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
> 2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
> 2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
> 2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
> 2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
> complete (approximately 0 more seconds)
> 2006-04-05 09:51:53.63 spid3 Recovery complete.
> 2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
> created.
> 2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.203
9'
> to execute extended stored procedure 'xp_qv'.
> 2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlmaint'.
> 2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
> creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
> 23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DIS
K:
> {'S:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\TransactionLogs\Nort
hwind_tlog_200604050952.TRN'}).
> 2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'sp_MSgetversion'.
> 2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
> 2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039
'
> to execute extended stored procedure 'xp_msver'.
> 2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
>
> MSSQLServer and SQLServerAgent services are running under a system admin
> user account. What possibly could be the issue here?
> Thanks

error 1053 when try to start mssqlserver service

I have a two node cluster. When I try to failover from active node which is
node2 to node1 I get the following errors in the event viewer/ system logs
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely
fashion.
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
Cluster resource 'SQL Cluster Group Server Service' in Resource Group
'006-PM2-DBASQL' failed.
SQL Server Error Logs dont show any error either execpt one which i think is
unrelated to this issue:
2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-04-05 09:51:43.86 server All rights reserved.
2006-04-05 09:51:43.86 server Server Process ID is 5508.
2006-04-05 09:51:43.86 server Logging SQL Server messages in file
'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-04-05 09:51:43.86 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-04-05 09:51:44.00 server SQL Server configured for thread mode
processing.
2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-04-05 09:51:44.10 server Attempting to initialize Distributed
Transaction Coordinator.
2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-04-05 09:51:47.21 server SQL Server is ready for client connections
2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
complete (approximately 0 more seconds)
2006-04-05 09:51:53.63 spid3 Recovery complete.
2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
created.
2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlmaint'.
2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
{'S:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog_200604050952.TRN'}).
2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_MSgetversion'.
2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_msver'.
2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
options' changed from 1 to 1. Run the RECONFIGURE statement to install..
MSSQLServer and SQLServerAgent services are running under a system admin
user account. What possibly could be the issue here?
ThanksYou could try either trace flag 3607 or 3608. See http://support.microsoft.com/kb/224071/en-us for
some info.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"shahab" <shahab@.discussions.microsoft.com> wrote in message
news:329CA91B-6855-4F1F-B69F-B972163804C2@.microsoft.com...
>I have a two node cluster. When I try to failover from active node which is
> node2 to node1 I get the following errors in the event viewer/ system logs
>
> The MSSQLSERVER service failed to start due to the following error:
> The service did not respond to the start or control request in a timely
> fashion.
> Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
> Cluster resource 'SQL Cluster Group Server Service' in Resource Group
> '006-PM2-DBASQL' failed.
>
> SQL Server Error Logs dont show any error either execpt one which i think is
> unrelated to this issue:
> 2006-04-05 09:51:43.86 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
> 2006-04-05 09:51:43.86 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2006-04-05 09:51:43.86 server All rights reserved.
> 2006-04-05 09:51:43.86 server Server Process ID is 5508.
> 2006-04-05 09:51:43.86 server Logging SQL Server messages in file
> 'S:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2006-04-05 09:51:43.86 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2006-04-05 09:51:44.00 server SQL Server configured for thread mode
> processing.
> 2006-04-05 09:51:44.08 server Using dynamic lock allocation. [2500] Lock
> Blocks, [5000] Lock Owner Blocks.
> 2006-04-05 09:51:44.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2006-04-05 09:51:46.97 spid3 Starting up database 'master'.
> 2006-04-05 09:51:47.11 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2006-04-05 09:51:47.14 server SQL server listening on 10.14.200.155: 1433.
> 2006-04-05 09:51:47.16 spid5 Starting up database 'model'.
> 2006-04-05 09:51:47.16 spid3 Server name is '006-PM2-DBASQL'.
> 2006-04-05 09:51:47.18 spid8 Starting up database 'msdb'.
> 2006-04-05 09:51:47.21 spid9 Starting up database 'pubs'.
> 2006-04-05 09:51:47.21 spid10 Starting up database 'Northwind'.
> 2006-04-05 09:51:47.21 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2006-04-05 09:51:47.21 server SQL Server is ready for client connections
> 2006-04-05 09:51:47.21 spid11 Starting up database 'Workflow'.
> 2006-04-05 09:51:47.29 spid5 Clearing tempdb database.
> 2006-04-05 09:51:47.30 spid9 Starting up database 'Cube'.
> 2006-04-05 09:51:47.35 spid10 Starting up database 'SABADev2'.
> 2006-04-05 09:51:47.36 spid8 Starting up database 'WorkflowTest'.
> 2006-04-05 09:51:47.55 spid10 Starting up database 'WSS-Config'.
> 2006-04-05 09:51:47.79 spid5 Starting up database 'tempdb'.
> 2006-04-05 09:51:53.47 spid9 Analysis of database 'Cube' (8) is 100%
> complete (approximately 0 more seconds)
> 2006-04-05 09:51:53.63 spid3 Recovery complete.
> 2006-04-05 09:51:53.64 spid3 SQL global counter collection task is
> created.
> 2006-04-05 09:51:53.99 spid52 Using 'xpsqlbot.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2006-04-05 09:52:00.29 spid53 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlmaint'.
> 2006-04-05 09:52:01.25 backup Log backed up: Database: Northwind,
> creation date(time): 2000/08/06(01:41:00), first LSN: 23:419:1, last LSN:
> 23:421:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK:
> {'S:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\TransactionLogs\Northwind_tlog_200604050952.TRN'}).
> 2006-04-05 09:52:01.49 spid54 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'sp_MSgetversion'.
> 2006-04-05 09:52:08.63 spid55 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:52:08.63 spid55 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
> 2006-04-05 09:52:08.74 spid55 Using 'xplog70.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_msver'.
> 2006-04-05 09:53:34.49 spid54 Error: 15457, Severity: 0, State: 1
> 2006-04-05 09:53:34.49 spid54 Configuration option 'show advanced
> options' changed from 1 to 1. Run the RECONFIGURE statement to install..
>
> MSSQLServer and SQLServerAgent services are running under a system admin
> user account. What possibly could be the issue here?
> Thanks

error 1053 when I try to start SQLagent

sqlagent.out => startup erroe: The event log service has
not been started.
>--Original Message--
>I also get and error of unable to complete the operation
>on "system Log" The interface is unknown.
>.
>
Here is how I got around the problem, trying to put a program to run as a Service
in Windows:
How to setup the Morning Negotiation Tool(MNTOOL), so it will
Run as a Service in Windows 2003 Server.
1.) You must have the following programs, which you can find
in the Microsoft NT/2000 resource kit:
a.) srvany.exe.
b.) instsrv.exe.
2. Put the MNTOOL execution file in the directory D:\smt_tool as pass.exe.
3. Copy INSTSRV.EXE and SRVANY.EXE, on Windows 2003 Server, under
the directory C:\windows\.
4. Run "C:\Windows\INSTSRV MNTOOL C:\Windows\srvany.exe"
5. Using REGEDT32 find the following key:-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MNTOOL
6. Create a new key called "Parameters" , under MNTOOL.
7. Create a new REG_SZ value, under Parameters, called "Application" and give it
the value d:\smt_tool\pass.exe.
8. Run Control Panel, Services, find the MNTOOL service and change the Startup
settings for this service to log on account smt, which should have Administrator
permissions.
9. Start the MNTOOL service, from the Service menu, and it should remain
running. Do a Cntrl/Alt/Delete to get the TASK Manager ICON and make
sure it says that PASS.exe is running.
Note:
To delete the MNTOOL, from running as a service, you can use the following
DOS command, which is only available in Windows XP PRO and Windows
2003 Service software: “sc delete MNTOOL”
? NJC 4/08/2004

error 1053 when I try to start SQLagent

sqlagent.out => startup erroe: The event log service has
not been started.
>--Original Message--
>I also get and error of unable to complete the operation
>on "system Log" The interface is unknown.
>.
>Here is how I got around the problem, trying to put a program to run as a Se
rvice
in Windows:
How to setup the Morning Negotiation Tool(MNTOOL), so it will
Run as a Service in Windows 2003 Server.
1.) You must have the following programs, which you can find
in the Microsoft NT/2000 resource kit:
a.) srvany.exe.
b.) instsrv.exe.
2. Put the MNTOOL execution file in the directory D:\smt_tool as pass.exe.
3. Copy INSTSRV.EXE and SRVANY.EXE, on Windows 2003 Server, under
the directory C:\windows\.
4. Run "C:\Windows\INSTSRV MNTOOL C:\Windows\srvany.exe"
5. Using REGEDT32 find the following key:-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\MNTOOL
6. Create a new key called "Parameters" , under MNTOOL.
7. Create a new REG_SZ value, under Parameters, called "Application" and giv
e it
the value d:\smt_tool\pass.exe.
8. Run Control Panel, Services, find the MNTOOL service and change the Start
up
settings for this service to log on account smt, which should have Administr
ator
permissions.
9. Start the MNTOOL service, from the Service menu, and it should remain
running. Do a Cntrl/Alt/Delete to get the TASK Manager ICON and make
sure it says that PASS.exe is running.
Note:
To delete the MNTOOL, from running as a service, you can use the following
DOS command, which is only available in Windows XP PRO and Windows
2003 Service software: “sc delete MNTOOL”
? NJC 4/08/2004

Error ?

Hi,
any ideas on this error '?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 23-10-2003
Time: 21:45:44
User: N/A
Computer: LX1SQL004
Description:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS Context 0x03843DE8 Data:
0000: db 45 00 00 01 00 00 00 =DBE.....
0008: 0a 00 00 00 4c 00 58 00 ...L.X.
0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
0018: 30 00 30 00 34 00 00 00 0.0.4...
0020: 00 00 00 00 ...
Thanks in advance
Miguel CorreiaHave a look at this KB article
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B810885
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Miguel" <cmlcorreia@.netcabo.pt> wrote in message
news:084c01c39a1c$c9a680c0$a501280a@.phx.gbl...
Hi,
any ideas on this error '?
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 23-10-2003
Time: 21:45:44
User: N/A
Computer: LX1SQL004
Description:
Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS
Context 0x03843DE8
Data:
0000: db 45 00 00 01 00 00 00 ÛE.....
0008: 0a 00 00 00 4c 00 58 00 ...L.X.
0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
0018: 30 00 30 00 34 00 00 00 0.0.4...
0020: 00 00 00 00 ...
Thanks in advance
Miguel Correia|||Thanks a lot :)
>--Original Message--
>Have a look at this KB article
>http://support.microsoft.com/default.aspx?scid=3Dkb%3Ben-us%
3B810885
>-- >
>Allan Mitchell (Microsoft SQL Server MVP)
>MCSE,MCDBA
>www.SQLDTS.com
>I support PASS - the definitive, global community
>for SQL Server professionals - http://www.sqlpass.org
>
>
>"Miguel" <cmlcorreia@.netcabo.pt> wrote in message
>news:084c01c39a1c$c9a680c0$a501280a@.phx.gbl...
>Hi,
>any ideas on this error '?
>Event Type: Information
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17052
>Date: 23-10-2003
>Time: 21:45:44
>User: N/A
>Computer: LX1SQL004
>Description:
>Error: 17883, Severity: 1, State: 0
>The Scheduler 0 appears to be hung. SPID 68, ECID 0, UMS
>Context 0x03843DE8
>Data:
>0000: db 45 00 00 01 00 00 00 =DBE.....
>0008: 0a 00 00 00 4c 00 58 00 ...L.X.
>0010: 31 00 53 00 51 00 4c 00 1.S.Q.L.
>0018: 30 00 30 00 34 00 00 00 0.0.4...
>0020: 00 00 00 00 ...
>
>Thanks in advance
>Miguel Correia
>
>.
>