Multi value parameter help needed

Hi
I have a problem my database table has my parameter value
UserId integer
I need to set up my report to accept more than one id at a time (ex.
2, 44, 5). I went through the report parameters in reporting services
and set the parameter to accept multi value. When I tried to run the
report I was allowed to put in multi values with no problem, but it is
returning an error saying that it cannot convert data type nvarchar to
int. Any ideas?
thanks for the help
twoI'm guessing that your multi-value parameter has a lable and a value.
You probably set the parameter up wrong in Report Parameters. You
have a select with (label, value) pairs (apple, 2), (orange, 44),
(peach, 5). When you select apple, orange and peach you are expecting
2, 44, and 5, but you have probably set it up to pass in apple,
orange, peach. Which leads to the conversion problem you are seeing.
Are the options coming from a datasource or did you just type them
into the report parameters section?|||On Oct 5, 9:30 am, jer...@.gmail.com wrote:
> I'm guessing that your multi-value parameter has a lable and a value.
> You probably set the parameter up wrong in Report Parameters. You
> have a select with (label, value) pairs (apple, 2), (orange, 44),
> (peach, 5). When you select apple, orange and peach you are expecting
> 2, 44, and 5, but you have probably set it up to pass in apple,
> orange, peach. Which leads to the conversion problem you are seeing.
> Are the options coming from a datasource or did you just type them
> into the report parameters section?
I am using a stored procedure that requires only one paramter which is
the id (int). The options for the parameters are not coming from a
datasource, Its pulling from my datasource that id (int) is a
parameter. So there is no label since the available values section is
set to non-queried.|||On Oct 5, 10:10 am, Twobridge <Twobri...@.gmail.com> wrote:
> On Oct 5, 9:30 am, jer...@.gmail.com wrote:
> > I'm guessing that your multi-value parameter has a lable and a value.
> > You probably set the parameter up wrong in Report Parameters. You
> > have a select with (label, value) pairs (apple, 2), (orange, 44),
> > (peach, 5). When you select apple, orange and peach you are expecting
> > 2, 44, and 5, but you have probably set it up to pass in apple,
> > orange, peach. Which leads to the conversion problem you are seeing.
> > Are the options coming from a datasource or did you just type them
> > into the report parameters section?
> I am using a stored procedure that requires only one paramter which is
> the id (int). The options for the parameters are not coming from a
> datasource, Its pulling from my datasource that id (int) is a
> parameter. So there is no label since the available values section is
> set to non-queried.
I am thinking my problem isnt the parameter setting but my stored
procedure on the sqlserver. It is set up to accept a integer as it
parameter not an array of int. And to be honest i have no idea how to
set a stored procedure up to accept an array of integers.|||I have never used multi-select as a textbox that I put values in. I always
put in the values to select from, either a manual list I put in for the
parameter or a query. To make sure multi-select is working for you put in a
list of parameter values. This will make sure the issue is not your textbox
input.
The second issue I see is that you are trying to pass an multi-select list
to a stored procedure of type int. What the multi-select does is allow you
to multi-select from an option list. If you put in 1,12,34 into a listbox
this is by definition a string, it is not integers.
OK, now on to your stored procedure. There is absolutely no way to pass
multiple integers into a singe integer parameter. You are trying to get RS
to do something impossible. A way to look at this, if you cannot do it from
SQL Management Studio where you invoke the SP yourself, then there is no way
RS can do it either.
Also, for another problem what you want cannot be done without special code
in a stored procedure. If you have a query this would work:
select * from sometable where somefield in (@.id)
In this case the data type of id can be int.
Now with your stored procedure with a parameter of type int called id, it
only accepts a single integer.
Below is a post of mine from previous that describes the issue with
multi-parameters and stored procedures. What the problem is and how to get
around it:
>>>>>
What doesn't work has nothing really to do with RS but has to do with Stored
Procedures in SQL Server. You cannot do the following in a stored procedure.
Let's say you have a Parameter called @.MyParams
Now you can map that parameter to a multi-value parameter but if in your
stored procedure you try to do this:
select * from sometable where somefield in (@.MyParams)
It won't work. Try it. Create a stored procedure and try to pass a
multi-value parameter to the stored procedure. It won't work.
What you can do is to have a string parameter that is passed as a multivalue
parameter and then change the string into a table.
This technique was told to me by SQL Server MVP, Erland Sommarskog
For example I have done this
inner join charlist_to_table(@.STO,Default)f on b.sto = f.str
So note this is NOT an issue with RS, it is strictly a stored procedure
issue.
Here is the function:
CREATE FUNCTION charlist_to_table
(@.list ntext,
@.delimiter nchar(1) = N',')
RETURNS @.tbl TABLE (listpos int IDENTITY(1, 1) NOT NULL,
str varchar(4000),
nstr nvarchar(2000)) AS
BEGIN
DECLARE @.pos int,
@.textpos int,
@.chunklen smallint,
@.tmpstr nvarchar(4000),
@.leftover nvarchar(4000),
@.tmpval nvarchar(4000)
SET @.textpos = 1
SET @.leftover = ''
WHILE @.textpos <= datalength(@.list) / 2
BEGIN
SET @.chunklen = 4000 - datalength(@.leftover) / 2
SET @.tmpstr = @.leftover + substring(@.list, @.textpos, @.chunklen)
SET @.textpos = @.textpos + @.chunklen
SET @.pos = charindex(@.delimiter, @.tmpstr)
WHILE @.pos > 0
BEGIN
SET @.tmpval = ltrim(rtrim(left(@.tmpstr, @.pos - 1)))
INSERT @.tbl (str, nstr) VALUES(@.tmpval, @.tmpval)
SET @.tmpstr = substring(@.tmpstr, @.pos + 1, len(@.tmpstr))
SET @.pos = charindex(@.delimiter, @.tmpstr)
END
SET @.leftover = @.tmpstr
END
INSERT @.tbl(str, nstr) VALUES (ltrim(rtrim(@.leftover)),
ltrim(rtrim(@.leftover)))
RETURN
END
GO
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Twobridge" <Twobridge@.gmail.com> wrote in message
news:1191597037.153027.72250@.w3g2000hsg.googlegroups.com...
> On Oct 5, 9:30 am, jer...@.gmail.com wrote:
>> I'm guessing that your multi-value parameter has a lable and a value.
>> You probably set the parameter up wrong in Report Parameters. You
>> have a select with (label, value) pairs (apple, 2), (orange, 44),
>> (peach, 5). When you select apple, orange and peach you are expecting
>> 2, 44, and 5, but you have probably set it up to pass in apple,
>> orange, peach. Which leads to the conversion problem you are seeing.
>> Are the options coming from a datasource or did you just type them
>> into the report parameters section?
> I am using a stored procedure that requires only one paramter which is
> the id (int). The options for the parameters are not coming from a
> datasource, Its pulling from my datasource that id (int) is a
> parameter. So there is no label since the available values section is
> set to non-queried.
>|||On Oct 5, 10:41 am, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> I have never used multi-select as a textbox that I put values in. I always
> put in the values to select from, either a manual list I put in for the
> parameter or a query. To make sure multi-select is working for you put in a
> list of parameter values. This will make sure the issue is not your textbox
> input.
> The second issue I see is that you are trying to pass an multi-select list
> to a stored procedure of type int. What the multi-select does is allow you
> to multi-select from an option list. If you put in 1,12,34 into a listbox
> this is by definition a string, it is not integers.
> OK, now on to your stored procedure. There is absolutely no way to pass
> multiple integers into a singe integer parameter. You are trying to get RS
> to do something impossible. A way to look at this, if you cannot do it from
> SQL Management Studio where you invoke the SP yourself, then there is no way
> RS can do it either.
> Also, for another problem what you want cannot be done without special code
> in a stored procedure. If you have a query this would work:
> select * from sometable where somefield in (@.id)
> In this case the data type of id can be int.
> Now with your stored procedure with a parameter of type int called id, it
> only accepts a single integer.
> Below is a post of mine from previous that describes the issue with
> multi-parameters and stored procedures. What the problem is and how to get
> around it:
> What doesn't work has nothing really to do with RS but has to do with Stored
> Procedures in SQL Server. You cannot do the following in a stored procedure.
> Let's say you have a Parameter called @.MyParams
> Now you can map that parameter to a multi-value parameter but if in your
> stored procedure you try to do this:
> select * from sometable where somefield in (@.MyParams)
> It won't work. Try it. Create a stored procedure and try to pass a
> multi-value parameter to the stored procedure. It won't work.
> What you can do is to have a string parameter that is passed as a multivalue
> parameter and then change the string into a table.
> This technique was told to me by SQL Server MVP, Erland Sommarskog
> For example I have done this
> inner join charlist_to_table(@.STO,Default)f on b.sto = f.str
> So note this is NOT an issue with RS, it is strictly a stored procedure
> issue.
> Here is the function:
> CREATE FUNCTION charlist_to_table
> (@.list ntext,
> @.delimiter nchar(1) = N',')
> RETURNS @.tbl TABLE (listpos int IDENTITY(1, 1) NOT NULL,
> str varchar(4000),
> nstr nvarchar(2000)) AS
> BEGIN
> DECLARE @.pos int,
> @.textpos int,
> @.chunklen smallint,
> @.tmpstr nvarchar(4000),
> @.leftover nvarchar(4000),
> @.tmpval nvarchar(4000)
> SET @.textpos = 1
> SET @.leftover = ''
> WHILE @.textpos <= datalength(@.list) / 2
> BEGIN
> SET @.chunklen = 4000 - datalength(@.leftover) / 2
> SET @.tmpstr = @.leftover + substring(@.list, @.textpos, @.chunklen)
> SET @.textpos = @.textpos + @.chunklen
> SET @.pos = charindex(@.delimiter, @.tmpstr)
> WHILE @.pos > 0
> BEGIN
> SET @.tmpval = ltrim(rtrim(left(@.tmpstr, @.pos - 1)))
> INSERT @.tbl (str, nstr) VALUES(@.tmpval, @.tmpval)
> SET @.tmpstr = substring(@.tmpstr, @.pos + 1, len(@.tmpstr))
> SET @.pos = charindex(@.delimiter, @.tmpstr)
> END
> SET @.leftover = @.tmpstr
> END
> INSERT @.tbl(str, nstr) VALUES (ltrim(rtrim(@.leftover)),
> ltrim(rtrim(@.leftover)))
> RETURN
> END
> GO
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Twobridge" <Twobri...@.gmail.com> wrote in message
> news:1191597037.153027.72250@.w3g2000hsg.googlegroups.com...
>
> > On Oct 5, 9:30 am, jer...@.gmail.com wrote:
> >> I'm guessing that your multi-value parameter has a lable and a value.
> >> You probably set the parameter up wrong in Report Parameters. You
> >> have a select with (label, value) pairs (apple, 2), (orange, 44),
> >> (peach, 5). When you select apple, orange and peach you are expecting
> >> 2, 44, and 5, but you have probably set it up to pass in apple,
> >> orange, peach. Which leads to the conversion problem you are seeing.
> >> Are the options coming from a datasource or did you just type them
> >> into the report parameters section?
> > I am using a stored procedure that requires only one paramter which is
> > the id (int). The options for the parameters are not coming from a
> > datasource, Its pulling from my datasource that id (int) is a
> > parameter. So there is no label since the available values section is
> > set to non-queried.- Hide quoted text -
> - Show quoted text -
Thanks everyone who helped me out. Bruce you were correct that it was
more to do with my stored procedure that RS. I found a really good
example of a function that basically took in my string of numbers and
was able to break up the string into my needed id's . Here is a link
if anyone needs it.
http://www.sommarskog.se/arrays-in-sql-2005.html

Multi Server Administration (Error Enlist MSX)

With Sql-Server 2000 i am using since a long time the jobserver (MSX) with TSX-servers.

Now I installed Sql-Server 2005 Standard Edition (the same i have tested with developer edition) on NT-2003 SP1.

I have 2 Sql-Server instances installed.

Now i tryed to configure one instance as MSX-Server and the other one as TSX-Server.

No Chance. When i do it with Management-Studio the following error ist displayed:
The enlist operation failed (reason:SqlServerAgent Error: Unable to connect to 'MSX HG-ALV-012\I1'). (Microsoft Sql Server,Error:22026).

In the Agent-log i found after every try the following error-messages:

Date 06.12.2005 17:29:42
Log SQL Agent (Current - 06.12.2005 17:29:00)

Message
[298] SQLServer Error: 805, SSL Provider: Die Zertifikatkette wurde von einer nicht vertrauenswürdigen Zertifizierungsstelle ausgestellt. [SQLSTATE 08001]

[298] SQLServer Error: 805, Client unable to establish connection [SQLSTATE 08001]

Message in Eventlog:
Date 06.12.2005 17:29:42
Log Windows NT (System)

Source Schannel
Category (0)
Event 3221262354
Computer HG-ALV-012

Message
Das vom Remoteserver erhaltene Zertifikat wurde von einer nicht vertrauenswürdigen Zertifizierungsstelle
ausgestellt. Aus diesem Grund k?nnen keine der im Zertifikat enthalten Daten verifiziert werden. Die
SSL-Verbindungsanforderung ist fehlgeschlagen. Die angeh?ngten Daten enthalten das Serverzertifikat.
I don't know what this has to do with certificates? The Configuration for the connections on the server (tcp) is definitely set to "ForceEncrypten=No".

Both Sql Server instances are running under the same Domain-Account. (Also the Agents!)

Has anyone an idea how to solve that problem?

There is a good Webcast exactly on this topic recorded at Dec 15 2005.
Theme: Upgrading SQL Server Agent to SQL Server 2000.

EventID is 1032285816

Look at http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032285816&EventCategory=5&culture=en-US&CountryCode=US

Regards

Ralph Kemperdick

Multi Server Administration (Error Enlist MSX)

With Sql-Server 2000 i am using since a long time the jobserver (MSX) with TSX-servers.

Now I installed Sql-Server 2005 Standard Edition (the same i have tested with developer edition) on NT-2003 SP1.

I have 2 Sql-Server instances installed.

Now i tryed to configure one instance as MSX-Server and the other one as TSX-Server.

No Chance. When i do it with Management-Studio the following error ist displayed:
The enlist operation failed (reason:SqlServerAgent Error: Unable to connect to 'MSX HG-ALV-012\I1'). (Microsoft Sql Server,Error:22026).

In the Agent-log i found after every try the following error-messages:

Date 06.12.2005 17:29:42
Log SQL Agent (Current - 06.12.2005 17:29:00)

Message
[298] SQLServer Error: 805, SSL Provider: Die Zertifikatkette wurde von einer nicht vertrauenswürdigen Zertifizierungsstelle ausgestellt. [SQLSTATE 08001]

[298] SQLServer Error: 805, Client unable to establish connection [SQLSTATE 08001]

Message in Eventlog:
Date 06.12.2005 17:29:42
Log Windows NT (System)

Source Schannel
Category (0)
Event 3221262354
Computer HG-ALV-012

Message
Das vom Remoteserver erhaltene Zertifikat wurde von einer nicht vertrauenswürdigen Zertifizierungsstelle
ausgestellt. Aus diesem Grund k?nnen keine der im Zertifikat enthalten Daten verifiziert werden. Die
SSL-Verbindungsanforderung ist fehlgeschlagen. Die angeh?ngten Daten enthalten das Serverzertifikat.
I don't know what this has to do with certificates? The Configuration for the connections on the server (tcp) is definitely set to "ForceEncrypten=No".

Both Sql Server instances are running under the same Domain-Account. (Also the Agents!)

Has anyone an idea how to solve that problem?

There is a good Webcast exactly on this topic recorded at Dec 15 2005.
Theme: Upgrading SQL Server Agent to SQL Server 2000.

EventID is 1032285816

Look at http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032285816&EventCategory=5&culture=en-US&CountryCode=US

Regards

Ralph Kemperdick

sql

Multi company Application

I'm developing an application that needs to handle several companies data one at a time.

I have a database called ROOT with the common tables like companies, users, etc. and all the stored procedures that I need.

Then I have a unique database per company containing all their info.

How can I apply the stored procedures that I have on database ROOT to the tables on each company's databases ?

The TSQL USE command do not accept variables.

Thanks for your help,
MOsheOoh. I'd use one database and then put a company ID on everything. Other than that, I think you would have to use dynamic SQL for everything and use full object names database.owner.object. That would get to be a real pain. It'll also wreak havoc with permissisons since the execute permissions for the stored procedure won't allow you to access those objects unless the user has permissisons on the underlying objects themselves. Unless you're bound to multiple databases, I'd change that.|||Select * From [DataBaseName].[dbo].[TableName]sql

MTD

I have created the following calculated member on my cube
Ancestor([Time].CurrentMember, [Time].[Month]), i want to link this to the
measures so that i can give me previous month versus the current months
sales figures, at the moment when i process the cube this member returns
nothing on the cube, how do i do this?
You'll have to explain a bit more fully because my understanding from that is
that you just want to compare 2 months side by side which is just a matter of
referencing those 2 months in your MDX statement e.g. {Time.January,
Time.February ON ROWS}. This is very easy to do so I'm guessing your problem
is a little more complex than that.
The subject of this thread leads me to think you are after MonthToDate or
similar.
Can you explain further?
Regards
Jamie Thomson
"MANDLA MKHWANAZI" wrote:

> I have created the following calculated member on my cube
> Ancestor([Time].CurrentMember, [Time].[Month]), i want to link this to the
> measures so that i can give me previous month versus the current months
> sales figures, at the moment when i process the cube this member returns
> nothing on the cube, how do i do this?
>
>

MTBF

Hi,
I am looking for some statistics for MSDE. In particular, I am looking for
information that would catain items such as Mean Time Between Failure.
Can anyone point me to a resource for this?
Thank you,
Paul
ooops. misspelling. I meant certain items (not catain). sorry.
"Paul" <NO_SPAM_paul@.whygle.com> wrote in message
news:Odj0RpRdEHA.2704@.tk2msftngp13.phx.gbl...
> Hi,
> I am looking for some statistics for MSDE. In particular, I am looking
for
> information that would catain items such as Mean Time Between Failure.
> Can anyone point me to a resource for this?
> Thank you,
> Paul
>

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

sql

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSXML6 install fails

I'm having a hard time installing SQLServer 2005. msxml6 keep on failing. The log looks like this.

Installing: msxml6 on target: GPA-DEMO
Error: MsiOpenDatabase failed with 87
Failed to install package
This action is only valid for products that are currently installed.

If i try to run the MSXML6.msi on the install disk directly i'm getting a permission error. Any ideas?

Copying the files to my hard drive and replacing the MXSML6.msi file resolved the problem.|||

When I try installing SQL Server 2005 MSXML6 Always fails where do I find the log file and can you explain what you did to fix the problem step by step.

|||Ohohohohhh, naughty boy - do you think it's that easy on the Microsoft Way? Just to check the log and see what happened?
Nahhh, that's not M$; it must be more difficult otherwise you wouldn't post here, to get in touch with other frustrated admins and you wouldn't be able to vent your frustration because you wouldn't be frustrated at all... that's not good, you know, in M$ world, a liad-back admin...

Log is producedf, of course - you just cannot read it.
Isn't it great fun? Apparently due to some retarded thing or person - they are unrivaled in this field, Microsoft - by the time the path to the log is displayed the log already been deleted by the installer.
Sounds like tons of fun, right?
What? You think it's powerful stupid?
Oh noooo, you are wrong - you just need more Kool-Aid and you will realize it's THE FUN FACTOR. Yeah, this is what makes every M$ installation an unmatched challenge, it's a great fun every time...

MySQL is sooo boring - it just works, without any of these idiotic extra hops. Boring - I hate boring things, even if they work, you don't want to go there...

Now I am sorry but I have to go back and have more fun with SQL2k5 SP2 bec ause I'm having the same problem with all my selected components... good times, indeed!

|||I copied the content of the install CD to my had drive, replace the MSXML6.xmi with one i downloaded from the web and then ran the install from the hard disk. I have installed SQLServer mahy times and this was the first time it did not install.|||

I sorted my problem out by using the Windows Intall Clean Up tool. It seems that my machine had 2 versions of MSXML6 running on my machine using add remove programs was useless. If you use Windows Intall Clean Up tool to remove all traces of MSXML6 then reintall SQL SERVER it should work.

I think this is the link i used to download the tool.

http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml

|||

I have also faced the same problem the Windows Intall Clean Up tool helped.

Thanks a lot for the help

MSSQLServer services

I'm running SQL 7.0 SP4 on NT 4.0. Each time i restart server, the sql
services just showing starting status for 2 minutes & gives error message "1
or more services failed to start". I have start the services manually. I've
tried to reinstall sql server but still the same. Kindly advice wht could be
the possible causes for this problem.
ThanksHi
What does the NT event log say? Any startup errors are logged there.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"chittana" <chittana@.discussions.microsoft.com> wrote in message
news:638D188B-8D35-4667-BFE3-0225BA31CB4B@.microsoft.com...
> I'm running SQL 7.0 SP4 on NT 4.0. Each time i restart server, the sql
> services just showing starting status for 2 minutes & gives error message
"1
> or more services failed to start". I have start the services manually.
I've
> tried to reinstall sql server but still the same. Kindly advice wht could
be
> the possible causes for this problem.
> Thanks|||Nope Mike. No startup error been logged in NT event log.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does the NT event log say? Any startup errors are logged there.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "chittana" <chittana@.discussions.microsoft.com> wrote in message
> news:638D188B-8D35-4667-BFE3-0225BA31CB4B@.microsoft.com...
> > I'm running SQL 7.0 SP4 on NT 4.0. Each time i restart server, the sql
> > services just showing starting status for 2 minutes & gives error message
> "1
> > or more services failed to start". I have start the services manually.
> I've
> > tried to reinstall sql server but still the same. Kindly advice wht could
> be
> > the possible causes for this problem.
> >
> > Thanks
>
>

MSSQLServer services

I'm running SQL 7.0 SP4 on NT 4.0. Each time i restart server, the sql
services just showing starting status for 2 minutes & gives error message "1
or more services failed to start". I have start the services manually. I've
tried to reinstall sql server but still the same. Kindly advice wht could be
the possible causes for this problem.
Thanks
Hi
What does the NT event log say? Any startup errors are logged there.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"chittana" <chittana@.discussions.microsoft.com> wrote in message
news:638D188B-8D35-4667-BFE3-0225BA31CB4B@.microsoft.com...
> I'm running SQL 7.0 SP4 on NT 4.0. Each time i restart server, the sql
> services just showing starting status for 2 minutes & gives error message
"1
> or more services failed to start". I have start the services manually.
I've
> tried to reinstall sql server but still the same. Kindly advice wht could
be
> the possible causes for this problem.
> Thanks
|||Nope Mike. No startup error been logged in NT event log.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What does the NT event log say? Any startup errors are logged there.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "chittana" <chittana@.discussions.microsoft.com> wrote in message
> news:638D188B-8D35-4667-BFE3-0225BA31CB4B@.microsoft.com...
> "1
> I've
> be
>
>

MSSQLServer services

I'm running SQL 7.0 SP4 on NT 4.0. Each time i restart server, the sql
services just showing starting status for 2 minutes & gives error message "1
or more services failed to start". I have start the services manually. I've
tried to reinstall sql server but still the same. Kindly advice wht could be
the possible causes for this problem.
ThanksHi
What does the NT event log say? Any startup errors are logged there.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"chittana" <chittana@.discussions.microsoft.com> wrote in message
news:638D188B-8D35-4667-BFE3-0225BA31CB4B@.microsoft.com...
> I'm running SQL 7.0 SP4 on NT 4.0. Each time i restart server, the sql
> services just showing starting status for 2 minutes & gives error message
"1
> or more services failed to start". I have start the services manually.
I've
> tried to reinstall sql server but still the same. Kindly advice wht could
be
> the possible causes for this problem.
> Thanks|||Nope Mike. No startup error been logged in NT event log.
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What does the NT event log say? Any startup errors are logged there.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "chittana" <chittana@.discussions.microsoft.com> wrote in message
> news:638D188B-8D35-4667-BFE3-0225BA31CB4B@.microsoft.com...
> "1
> I've
> be
>
>

MSSQLSERVER Error 17052

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 2/20/2007
Time: 4:38:39 AM
User: N/A
Computer: LEESQL
Description:
SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: a8 01 00 00 0a 00 00 00 ¨......
0008: 0e 00 00 00 4c 00 45 00 ...L.E.
0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
0018: 00 00 0e 00 00 00 6d 00 .....m.
0020: 61 00 73 00 74 00 65 00 a.s.t.e.
0028: 72 00 00 00 r...
Everytime I try to run a job in sql server agent it shuts down the agent.
None of the files in the log directory have any details about the shutdown.
This is driving me nuts. I have checked and rechecked permissions and even
created a new login for the sql server and the agent to use. Still the same
thing. Since I am getting no error logs I am totally lost as to where to look
for information. I am also not finding anything about this when I google for
it. Any help anyone could give would be appreciated.
--
Mark A. Lutz (aka Eggbert)Hi
Can open the SQL Server errorlog file in notepad to see if you have
additional information?
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 2/20/2007
> Time: 4:38:39 AM
> User: N/A
> Computer: LEESQL
> Description:
> SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: a8 01 00 00 0a 00 00 00 ¨......
> 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> 0018: 00 00 0e 00 00 00 6d 00 .....m.
> 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> 0028: 72 00 00 00 r...
> Everytime I try to run a job in sql server agent it shuts down the agent.
> None of the files in the log directory have any details about the
> shutdown.
> This is driving me nuts. I have checked and rechecked permissions and even
> created a new login for the sql server and the agent to use. Still the
> same
> thing. Since I am getting no error logs I am totally lost as to where to
> look
> for information. I am also not finding anything about this when I google
> for
> it. Any help anyone could give would be appreciated.
> --
> Mark A. Lutz (aka Eggbert)|||As I mentioned I had done that and not found anything informative but I will
paste them here:
____________
SQLAGENT.OUT
2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
(x86 unicode retail build) : Process ID
2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
(x86 unicode retail build) : Process ID 396
2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
connection limit)
2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
Local host server is
2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows NT
5.2 (3790) Service Pack 1
2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
service control
2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No mail
profile defined)
2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined -
OnIdle job schedules will have no effect
____________
SQLAGENT.1
2007-02-20 04:36:59.00 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)
2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-20 04:36:59.00 server All rights reserved.
2007-02-20 04:36:59.00 server Server Process ID is 1184.
2007-02-20 04:36:59.00 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-20 04:36:59.00 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-02-20 04:36:59.09 server SQL Server configured for thread mode
processing.
2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-02-20 04:36:59.10 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2007-02-20 04:37:00.51 server SQL Server is ready for client connections
2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
2007-02-20 04:37:55.15 spid2 Recovery complete.
2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
created.
2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
____________
ERRORLOG
2007-02-20 04:36:59.00 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)
2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-02-20 04:36:59.00 server All rights reserved.
2007-02-20 04:36:59.00 server Server Process ID is 1184.
2007-02-20 04:36:59.00 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2007-02-20 04:36:59.00 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2007-02-20 04:36:59.09 server SQL Server configured for thread mode
processing.
2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2007-02-20 04:36:59.10 server Attempting to initialize Distributed
Transaction Coordinator.
2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116: 1433.
2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2007-02-20 04:37:00.51 server SQL Server is ready for client connections
2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
2007-02-20 04:37:55.15 spid2 Recovery complete.
2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
created.
2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_qv'.
2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
--
Mark A. Lutz (aka Eggbert)
"Uri Dimant" wrote:
> Hi
> Can open the SQL Server errorlog file in notepad to see if you have
> additional information?
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> > Event Type: Error
> > Event Source: MSSQLSERVER
> > Event Category: (2)
> > Event ID: 17052
> > Date: 2/20/2007
> > Time: 4:38:39 AM
> > User: N/A
> > Computer: LEESQL
> > Description:
> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: a8 01 00 00 0a 00 00 00 ¨......
> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> > 0028: 72 00 00 00 r...
> >
> > Everytime I try to run a job in sql server agent it shuts down the agent.
> > None of the files in the log directory have any details about the
> > shutdown.
> > This is driving me nuts. I have checked and rechecked permissions and even
> > created a new login for the sql server and the agent to use. Still the
> > same
> > thing. Since I am getting no error logs I am totally lost as to where to
> > look
> > for information. I am also not finding anything about this when I google
> > for
> > it. Any help anyone could give would be appreciated.
> > --
> > Mark A. Lutz (aka Eggbert)
>
>|||Hi
1) Is it SQL Server 7.0/2000/2005?
2) Is it clustered?
http://www.tutorials-ne.com/clustering/Cannot-create-14238/
3) Have you tried to set LocalSystem account to the service?
4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
> As I mentioned I had done that and not found anything informative but I
> will
> paste them here:
>
> ____________
> SQLAGENT.OUT
> 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> (x86 unicode retail build) : Process ID
> 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> (x86 unicode retail build) : Process ID 396
> 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> connection limit)
> 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
> 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
> Local host server is
> 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
> 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows NT
> 5.2 (3790) Service Pack 1
> 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
> service control
> 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
> mail
> profile defined)
> 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined -
> OnIdle job schedules will have no effect
> ____________
> SQLAGENT.1
> 2007-02-20 04:36:59.00 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)
> 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-20 04:36:59.00 server All rights reserved.
> 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> processing.
> 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> Lock
> Blocks, [5000] Lock Owner Blocks.
> 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2007-02-20 04:37:00.51 server SQL Server is ready for client
> connections
> 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> 2007-02-20 04:37:55.15 spid2 Recovery complete.
> 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> created.
> 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlagent_monitor'.
> ____________
> ERRORLOG
> 2007-02-20 04:36:59.00 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)
> 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2007-02-20 04:36:59.00 server All rights reserved.
> 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> 'normal'(2 CPUs detected).
> 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> processing.
> 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> Lock
> Blocks, [5000] Lock Owner Blocks.
> 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> 1433.
> 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> Memory,
> Named Pipes.
> 2007-02-20 04:37:00.51 server SQL Server is ready for client
> connections
> 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> 2007-02-20 04:37:55.15 spid2 Recovery complete.
> 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> created.
> 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> '2000.80.2039'
> to execute extended stored procedure 'xp_qv'.
> 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> to execute extended stored procedure 'xp_sqlagent_monitor'.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Uri Dimant" wrote:
>> Hi
>> Can open the SQL Server errorlog file in notepad to see if you have
>> additional information?
>>
>>
>> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
>> > Event Type: Error
>> > Event Source: MSSQLSERVER
>> > Event Category: (2)
>> > Event ID: 17052
>> > Date: 2/20/2007
>> > Time: 4:38:39 AM
>> > User: N/A
>> > Computer: LEESQL
>> > Description:
>> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
>> >
>> > For more information, see Help and Support Center at
>> > http://go.microsoft.com/fwlink/events.asp.
>> > Data:
>> > 0000: a8 01 00 00 0a 00 00 00 ¨......
>> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
>> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
>> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
>> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
>> > 0028: 72 00 00 00 r...
>> >
>> > Everytime I try to run a job in sql server agent it shuts down the
>> > agent.
>> > None of the files in the log directory have any details about the
>> > shutdown.
>> > This is driving me nuts. I have checked and rechecked permissions and
>> > even
>> > created a new login for the sql server and the agent to use. Still the
>> > same
>> > thing. Since I am getting no error logs I am totally lost as to where
>> > to
>> > look
>> > for information. I am also not finding anything about this when I
>> > google
>> > for
>> > it. Any help anyone could give would be appreciated.
>> > --
>> > Mark A. Lutz (aka Eggbert)
>>|||1.
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)
2.
No it is not clustered.
3.
Yes I have tried to run both the SQL Server and Agent under the local system
account
4.
I have checked all logs and nothing is recorded when Agent goes down with
the exception of what I have already stated.
--
Mark A. Lutz (aka Eggbert)
"Uri Dimant" wrote:
> Hi
> 1) Is it SQL Server 7.0/2000/2005?
> 2) Is it clustered?
> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
> 3) Have you tried to set LocalSystem account to the service?
> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
> > As I mentioned I had done that and not found anything informative but I
> > will
> > paste them here:
> >
> >
> > ____________
> > SQLAGENT.OUT
> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> > (x86 unicode retail build) : Process ID
> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version 8.00.2039
> > (x86 unicode retail build) : Process ID 396
> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> > connection limit)
> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is DBMSSHRN.DLL;
> > Local host server is
> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows NT
> > 5.2 (3790) Service Pack 1
> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
> > service control
> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
> > mail
> > profile defined)
> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been defined -
> > OnIdle job schedules will have no effect
> >
> > ____________
> > SQLAGENT.1
> > 2007-02-20 04:36:59.00 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)
> >
> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> > Corporation.
> > 2007-02-20 04:36:59.00 server All rights reserved.
> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> > 'normal'(2 CPUs detected).
> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> > processing.
> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> > Lock
> > Blocks, [5000] Lock Owner Blocks.
> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> > 1433.
> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> > 1433.
> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> > Memory,
> > Named Pipes.
> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> > connections
> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> > created.
> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> > '2000.80.2039'
> > to execute extended stored procedure 'xp_qv'.
> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >
> > ____________
> > ERRORLOG
> >
> > 2007-02-20 04:36:59.00 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)
> >
> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> > Corporation.
> > 2007-02-20 04:36:59.00 server All rights reserved.
> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority class
> > 'normal'(2 CPUs detected).
> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> > processing.
> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> > Lock
> > Blocks, [5000] Lock Owner Blocks.
> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> > Transaction Coordinator.
> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version '8.0.2039'.
> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> > 1433.
> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> > 1433.
> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1: 1433.
> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> > Memory,
> > Named Pipes.
> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> > connections
> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> > created.
> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> > '2000.80.2039'
> > to execute extended stored procedure 'xp_qv'.
> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version '2000.80.2039'
> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >
> > --
> > Mark A. Lutz (aka Eggbert)
> >
> >
> > "Uri Dimant" wrote:
> >
> >> Hi
> >> Can open the SQL Server errorlog file in notepad to see if you have
> >> additional information?
> >>
> >>
> >>
> >>
> >>
> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> >> > Event Type: Error
> >> > Event Source: MSSQLSERVER
> >> > Event Category: (2)
> >> > Event ID: 17052
> >> > Date: 2/20/2007
> >> > Time: 4:38:39 AM
> >> > User: N/A
> >> > Computer: LEESQL
> >> > Description:
> >> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> >> >
> >> > For more information, see Help and Support Center at
> >> > http://go.microsoft.com/fwlink/events.asp.
> >> > Data:
> >> > 0000: a8 01 00 00 0a 00 00 00 ¨......
> >> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> >> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> >> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
> >> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> >> > 0028: 72 00 00 00 r...
> >> >
> >> > Everytime I try to run a job in sql server agent it shuts down the
> >> > agent.
> >> > None of the files in the log directory have any details about the
> >> > shutdown.
> >> > This is driving me nuts. I have checked and rechecked permissions and
> >> > even
> >> > created a new login for the sql server and the agent to use. Still the
> >> > same
> >> > thing. Since I am getting no error logs I am totally lost as to where
> >> > to
> >> > look
> >> > for information. I am also not finding anything about this when I
> >> > google
> >> > for
> >> > it. Any help anyone could give would be appreciated.
> >> > --
> >> > Mark A. Lutz (aka Eggbert)
> >>
> >>
> >>
>
>|||Check your system and see if you have MS07-009 applied (KB 927779). This is
a windows update security patch released ths month.
Is your system in a resource domain that is called by users in another
domain?
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
> 1.
> 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)
> 2.
> No it is not clustered.
> 3.
> Yes I have tried to run both the SQL Server and Agent under the local
> system
> account
> 4.
> I have checked all logs and nothing is recorded when Agent goes down with
> the exception of what I have already stated.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Uri Dimant" wrote:
>> Hi
>> 1) Is it SQL Server 7.0/2000/2005?
>> 2) Is it clustered?
>> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
>> 3) Have you tried to set LocalSystem account to the service?
>> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
>> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
>> > As I mentioned I had done that and not found anything informative but I
>> > will
>> > paste them here:
>> >
>> >
>> > ____________
>> > SQLAGENT.OUT
>> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> > 8.00.2039
>> > (x86 unicode retail build) : Process ID
>> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> > 8.00.2039
>> > (x86 unicode retail build) : Process ID 396
>> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
>> > connection limit)
>> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
>> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
>> > DBMSSHRN.DLL;
>> > Local host server is
>> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
>> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows
>> > NT
>> > 5.2 (3790) Service Pack 1
>> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
>> > service control
>> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
>> > mail
>> > profile defined)
>> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
>> > defined -
>> > OnIdle job schedules will have no effect
>> >
>> > ____________
>> > SQLAGENT.1
>> > 2007-02-20 04:36:59.00 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)
>> >
>> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
>> > Corporation.
>> > 2007-02-20 04:36:59.00 server All rights reserved.
>> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
>> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
>> > class
>> > 'normal'(2 CPUs detected).
>> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
>> > processing.
>> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
>> > Lock
>> > Blocks, [5000] Lock Owner Blocks.
>> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
>> > Transaction Coordinator.
>> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> > '8.0.2039'.
>> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
>> > 1433.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
>> > 1433.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
>> > 1433.
>> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
>> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
>> > Memory,
>> > Named Pipes.
>> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> > connections
>> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
>> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
>> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
>> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
>> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
>> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
>> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
>> > created.
>> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> > '2000.80.2039'
>> > to execute extended stored procedure 'xp_qv'.
>> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> > '2000.80.2039'
>> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >
>> > ____________
>> > ERRORLOG
>> >
>> > 2007-02-20 04:36:59.00 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)
>> >
>> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
>> > Corporation.
>> > 2007-02-20 04:36:59.00 server All rights reserved.
>> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
>> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
>> > class
>> > 'normal'(2 CPUs detected).
>> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
>> > processing.
>> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
>> > Lock
>> > Blocks, [5000] Lock Owner Blocks.
>> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
>> > Transaction Coordinator.
>> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> > '8.0.2039'.
>> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
>> > 1433.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
>> > 1433.
>> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
>> > 1433.
>> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
>> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
>> > Memory,
>> > Named Pipes.
>> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> > connections
>> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
>> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
>> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
>> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
>> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
>> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
>> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
>> > created.
>> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> > '2000.80.2039'
>> > to execute extended stored procedure 'xp_qv'.
>> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> > '2000.80.2039'
>> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >
>> > --
>> > Mark A. Lutz (aka Eggbert)
>> >
>> >
>> > "Uri Dimant" wrote:
>> >
>> >> Hi
>> >> Can open the SQL Server errorlog file in notepad to see if you have
>> >> additional information?
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
>> >> > Event Type: Error
>> >> > Event Source: MSSQLSERVER
>> >> > Event Category: (2)
>> >> > Event ID: 17052
>> >> > Date: 2/20/2007
>> >> > Time: 4:38:39 AM
>> >> > User: N/A
>> >> > Computer: LEESQL
>> >> > Description:
>> >> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
>> >> >
>> >> > For more information, see Help and Support Center at
>> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> > Data:
>> >> > 0000: a8 01 00 00 0a 00 00 00 ¨......
>> >> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
>> >> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
>> >> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
>> >> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
>> >> > 0028: 72 00 00 00 r...
>> >> >
>> >> > Everytime I try to run a job in sql server agent it shuts down the
>> >> > agent.
>> >> > None of the files in the log directory have any details about the
>> >> > shutdown.
>> >> > This is driving me nuts. I have checked and rechecked permissions
>> >> > and
>> >> > even
>> >> > created a new login for the sql server and the agent to use. Still
>> >> > the
>> >> > same
>> >> > thing. Since I am getting no error logs I am totally lost as to
>> >> > where
>> >> > to
>> >> > look
>> >> > for information. I am also not finding anything about this when I
>> >> > google
>> >> > for
>> >> > it. Any help anyone could give would be appreciated.
>> >> > --
>> >> > Mark A. Lutz (aka Eggbert)
>> >>
>> >>
>> >>
>>|||You may also want to turn on verbose logging for SQL Agent -
from the Properties window for Agent, select Include
Execution Trace Messages from the general section on the
properties for Agent. You don't want to keep this on - just
use it for troubleshooting. Turn it on and restart Agent and
check to see what's going on more with the job executions.
The additional details will be logged to the SQL Agent error
log.
-Sue
On Tue, 20 Feb 2007 09:31:13 -0800, Eggbert
<Eggbert@.discussions.microsoft.com> wrote:
>1.
>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)
>2.
>No it is not clustered.
>3.
>Yes I have tried to run both the SQL Server and Agent under the local system
>account
>4.
>I have checked all logs and nothing is recorded when Agent goes down with
>the exception of what I have already stated.|||In my setup we have 4 servers that are colocated with a web hosting service
so I do not have direct contact with them. The servers are not in an Active
Directory Domain Structure and each opperates independantly. The server in
question is my SQL server only. Each of my servers have two network cards.
One card is connected to the internet and the other card is connected to an
internal only router. The SQL server is setup to only respond to the internal
cart and port. The account running the SQL Server and SQL Agent is the a
local account for the SQL Server box.
The last time one of my jobs ran sucsesfully was 2/6/07. It does not appear
that MS07-009 has been applied. The way I checked was to go out to
windowsupdate.microsoft.com and used the View your Update History option.
Again this is the oddest thing I have seen and I cant find a reason for it.
As I mentioned in another post wether I try to run a job manually or let
agent run it at a specific time, as soon as the job starts Agent shuts down
and restarts. There are no the last entry in the log is that the job was
requested to run i.e.
2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been requested
to run by User LEESQL\Mark
The System Event viewer records "The SQLSERVERAGENT service terminated
unexpectedly." and that the Agent has restarted. There are no other log
entries anywhere.
--
Mark A. Lutz (aka Eggbert)
"Geoff N. Hiten" wrote:
> Check your system and see if you have MS07-009 applied (KB 927779). This is
> a windows update security patch released ths month.
> Is your system in a resource domain that is called by users in another
> domain?
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
> > 1.
> > 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)
> >
> > 2.
> > No it is not clustered.
> >
> > 3.
> > Yes I have tried to run both the SQL Server and Agent under the local
> > system
> > account
> >
> > 4.
> > I have checked all logs and nothing is recorded when Agent goes down with
> > the exception of what I have already stated.
> > --
> > Mark A. Lutz (aka Eggbert)
> >
> >
> > "Uri Dimant" wrote:
> >
> >> Hi
> >> 1) Is it SQL Server 7.0/2000/2005?
> >> 2) Is it clustered?
> >> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
> >> 3) Have you tried to set LocalSystem account to the service?
> >> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
> >>
> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
> >> > As I mentioned I had done that and not found anything informative but I
> >> > will
> >> > paste them here:
> >> >
> >> >
> >> > ____________
> >> > SQLAGENT.OUT
> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
> >> > 8.00.2039
> >> > (x86 unicode retail build) : Process ID
> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
> >> > 8.00.2039
> >> > (x86 unicode retail build) : Process ID 396
> >> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> >> > connection limit)
> >> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version 3.86.1830
> >> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
> >> > DBMSSHRN.DLL;
> >> > Local host server is
> >> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM detected
> >> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running Windows
> >> > NT
> >> > 5.2 (3790) Service Pack 1
> >> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows NT
> >> > service control
> >> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason: No
> >> > mail
> >> > profile defined)
> >> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
> >> > defined -
> >> > OnIdle job schedules will have no effect
> >> >
> >> > ____________
> >> > SQLAGENT.1
> >> > 2007-02-20 04:36:59.00 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)
> >> >
> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> >> > Corporation.
> >> > 2007-02-20 04:36:59.00 server All rights reserved.
> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
> >> > class
> >> > 'normal'(2 CPUs detected).
> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> >> > processing.
> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> >> > Lock
> >> > Blocks, [5000] Lock Owner Blocks.
> >> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> >> > Transaction Coordinator.
> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
> >> > '8.0.2039'.
> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> >> > Memory,
> >> > Named Pipes.
> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> >> > connections
> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> >> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> >> > created.
> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> >> > '2000.80.2039'
> >> > to execute extended stored procedure 'xp_qv'.
> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
> >> > '2000.80.2039'
> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >> >
> >> > ____________
> >> > ERRORLOG
> >> >
> >> > 2007-02-20 04:36:59.00 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)
> >> >
> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> >> > Corporation.
> >> > 2007-02-20 04:36:59.00 server All rights reserved.
> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
> >> > class
> >> > 'normal'(2 CPUs detected).
> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread mode
> >> > processing.
> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation. [2500]
> >> > Lock
> >> > Blocks, [5000] Lock Owner Blocks.
> >> > 2007-02-20 04:36:59.10 server Attempting to initialize Distributed
> >> > Transaction Coordinator.
> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
> >> > '8.0.2039'.
> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 192.168.1.50:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 64.27.15.116:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
> >> > 1433.
> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> >> > Memory,
> >> > Named Pipes.
> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> >> > connections
> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> >> > 2007-02-20 04:37:01.29 spid14 Starting up database 'SWFPortalDev'.
> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task is
> >> > created.
> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> >> > '2000.80.2039'
> >> > to execute extended stored procedure 'xp_qv'.
> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
> >> > '2000.80.2039'
> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >> >
> >> > --
> >> > Mark A. Lutz (aka Eggbert)
> >> >
> >> >
> >> > "Uri Dimant" wrote:
> >> >
> >> >> Hi
> >> >> Can open the SQL Server errorlog file in notepad to see if you have
> >> >> additional information?
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> >> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
> >> >> > Event Type: Error
> >> >> > Event Source: MSSQLSERVER
> >> >> > Event Category: (2)
> >> >> > Event ID: 17052
> >> >> > Date: 2/20/2007
> >> >> > Time: 4:38:39 AM
> >> >> > User: N/A
> >> >> > Computer: LEESQL
> >> >> > Description:
> >> >> > SQLServerAgent Monitor: SQLServerAgent has terminated unexpectedly.
> >> >> >
> >> >> > For more information, see Help and Support Center at
> >> >> > http://go.microsoft.com/fwlink/events.asp.
> >> >> > Data:
> >> >> > 0000: a8 01 00 00 0a 00 00 00 ¨......
> >> >> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
> >> >> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
> >> >> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
> >> >> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
> >> >> > 0028: 72 00 00 00 r...
> >> >> >
> >> >> > Everytime I try to run a job in sql server agent it shuts down the
> >> >> > agent.
> >> >> > None of the files in the log directory have any details about the
> >> >> > shutdown.
> >> >> > This is driving me nuts. I have checked and rechecked permissions
> >> >> > and
> >> >> > even
> >> >> > created a new login for the sql server and the agent to use. Still
> >> >> > the
> >> >> > same
> >> >> > thing. Since I am getting no error logs I am totally lost as to
> >> >> > where
> >> >> > to
> >> >> > look
> >> >> > for information. I am also not finding anything about this when I
> >> >> > google
> >> >> > for
> >> >> > it. Any help anyone could give would be appreciated.
> >> >> > --
> >> >> > Mark A. Lutz (aka Eggbert)
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>|||I turned this on but it did not result in any additional information. As soon
as I manually or the agent triggers a job to run the agent immediatly shuts
down with no log entries and then restarts. Again it happens if I do it by
right clicking on the job and start it or the event fires off on it's own.
--
Mark A. Lutz (aka Eggbert)
"Sue Hoegemeier" wrote:
> You may also want to turn on verbose logging for SQL Agent -
> from the Properties window for Agent, select Include
> Execution Trace Messages from the general section on the
> properties for Agent. You don't want to keep this on - just
> use it for troubleshooting. Turn it on and restart Agent and
> check to see what's going on more with the job executions.
> The additional details will be logged to the SQL Agent error
> log.
> -Sue
> On Tue, 20 Feb 2007 09:31:13 -0800, Eggbert
> <Eggbert@.discussions.microsoft.com> wrote:
> >1.
> >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)
> >
> >2.
> >No it is not clustered.
> >
> >3.
> >Yes I have tried to run both the SQL Server and Agent under the local system
> >account
> >
> >4.
> >I have checked all logs and nothing is recorded when Agent goes down with
> >the exception of what I have already stated.
>|||Thanks.
I am seeing the exact same thing at a client after a maintenance window
where updates were applied. I suspect an interaction between an update and
the SQL agent, but am having some difficulty proving it. Thanks for the
details on your configuration. I will let you know if I find anything on my
end.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:E76F1FDD-5BEC-4B98-9A19-5AEBAAEA4214@.microsoft.com...
> In my setup we have 4 servers that are colocated with a web hosting
> service
> so I do not have direct contact with them. The servers are not in an
> Active
> Directory Domain Structure and each opperates independantly. The server in
> question is my SQL server only. Each of my servers have two network cards.
> One card is connected to the internet and the other card is connected to
> an
> internal only router. The SQL server is setup to only respond to the
> internal
> cart and port. The account running the SQL Server and SQL Agent is the a
> local account for the SQL Server box.
> The last time one of my jobs ran sucsesfully was 2/6/07. It does not
> appear
> that MS07-009 has been applied. The way I checked was to go out to
> windowsupdate.microsoft.com and used the View your Update History option.
> Again this is the oddest thing I have seen and I cant find a reason for
> it.
> As I mentioned in another post wether I try to run a job manually or let
> agent run it at a specific time, as soon as the job starts Agent shuts
> down
> and restarts. There are no the last entry in the log is that the job was
> requested to run i.e.
> 2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been
> requested
> to run by User LEESQL\Mark
> The System Event viewer records "The SQLSERVERAGENT service terminated
> unexpectedly." and that the Agent has restarted. There are no other log
> entries anywhere.
> --
> Mark A. Lutz (aka Eggbert)
>
> "Geoff N. Hiten" wrote:
>> Check your system and see if you have MS07-009 applied (KB 927779). This
>> is
>> a windows update security patch released ths month.
>> Is your system in a resource domain that is called by users in another
>> domain?
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
>> > 1.
>> > 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)
>> >
>> > 2.
>> > No it is not clustered.
>> >
>> > 3.
>> > Yes I have tried to run both the SQL Server and Agent under the local
>> > system
>> > account
>> >
>> > 4.
>> > I have checked all logs and nothing is recorded when Agent goes down
>> > with
>> > the exception of what I have already stated.
>> > --
>> > Mark A. Lutz (aka Eggbert)
>> >
>> >
>> > "Uri Dimant" wrote:
>> >
>> >> Hi
>> >> 1) Is it SQL Server 7.0/2000/2005?
>> >> 2) Is it clustered?
>> >> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
>> >> 3) Have you tried to set LocalSystem account to the service?
>> >> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
>> >>
>> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
>> >> > As I mentioned I had done that and not found anything informative
>> >> > but I
>> >> > will
>> >> > paste them here:
>> >> >
>> >> >
>> >> > ____________
>> >> > SQLAGENT.OUT
>> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> >> > 8.00.2039
>> >> > (x86 unicode retail build) : Process ID
>> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> >> > 8.00.2039
>> >> > (x86 unicode retail build) : Process ID 396
>> >> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
>> >> > connection limit)
>> >> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version
>> >> > 3.86.1830
>> >> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
>> >> > DBMSSHRN.DLL;
>> >> > Local host server is
>> >> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM
>> >> > detected
>> >> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running
>> >> > Windows
>> >> > NT
>> >> > 5.2 (3790) Service Pack 1
>> >> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows
>> >> > NT
>> >> > service control
>> >> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason:
>> >> > No
>> >> > mail
>> >> > profile defined)
>> >> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
>> >> > defined -
>> >> > OnIdle job schedules will have no effect
>> >> >
>> >> > ____________
>> >> > SQLAGENT.1
>> >> > 2007-02-20 04:36:59.00 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)
>> >> >
>> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
>> >> > Corporation.
>> >> > 2007-02-20 04:36:59.00 server All rights reserved.
>> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
>> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
>> >> > class
>> >> > 'normal'(2 CPUs detected).
>> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
>> >> > mode
>> >> > processing.
>> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
>> >> > [2500]
>> >> > Lock
>> >> > Blocks, [5000] Lock Owner Blocks.
>> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
>> >> > Distributed
>> >> > Transaction Coordinator.
>> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> >> > '8.0.2039'.
>> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> > 192.168.1.50:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> > 64.27.15.116:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
>> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
>> >> > Memory,
>> >> > Named Pipes.
>> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> >> > connections
>> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
>> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
>> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
>> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
>> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
>> >> > 'SWFPortalDev'.
>> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
>> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task
>> >> > is
>> >> > created.
>> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> >> > '2000.80.2039'
>> >> > to execute extended stored procedure 'xp_qv'.
>> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> >> > '2000.80.2039'
>> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >> >
>> >> > ____________
>> >> > ERRORLOG
>> >> >
>> >> > 2007-02-20 04:36:59.00 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)
>> >> >
>> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
>> >> > Corporation.
>> >> > 2007-02-20 04:36:59.00 server All rights reserved.
>> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
>> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
>> >> > class
>> >> > 'normal'(2 CPUs detected).
>> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
>> >> > mode
>> >> > processing.
>> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
>> >> > [2500]
>> >> > Lock
>> >> > Blocks, [5000] Lock Owner Blocks.
>> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
>> >> > Distributed
>> >> > Transaction Coordinator.
>> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> >> > '8.0.2039'.
>> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> > 192.168.1.50:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> > 64.27.15.116:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
>> >> > 1433.
>> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
>> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
>> >> > Memory,
>> >> > Named Pipes.
>> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> >> > connections
>> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
>> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
>> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
>> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
>> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
>> >> > 'SWFPortalDev'.
>> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
>> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task
>> >> > is
>> >> > created.
>> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> >> > '2000.80.2039'
>> >> > to execute extended stored procedure 'xp_qv'.
>> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> >> > '2000.80.2039'
>> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >> >
>> >> > --
>> >> > Mark A. Lutz (aka Eggbert)
>> >> >
>> >> >
>> >> > "Uri Dimant" wrote:
>> >> >
>> >> >> Hi
>> >> >> Can open the SQL Server errorlog file in notepad to see if you have
>> >> >> additional information?
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> >> news:A24F0B5E-BB9A-40D3-A2E3-802B14FA5DD2@.microsoft.com...
>> >> >> > Event Type: Error
>> >> >> > Event Source: MSSQLSERVER
>> >> >> > Event Category: (2)
>> >> >> > Event ID: 17052
>> >> >> > Date: 2/20/2007
>> >> >> > Time: 4:38:39 AM
>> >> >> > User: N/A
>> >> >> > Computer: LEESQL
>> >> >> > Description:
>> >> >> > SQLServerAgent Monitor: SQLServerAgent has terminated
>> >> >> > unexpectedly.
>> >> >> >
>> >> >> > For more information, see Help and Support Center at
>> >> >> > http://go.microsoft.com/fwlink/events.asp.
>> >> >> > Data:
>> >> >> > 0000: a8 01 00 00 0a 00 00 00 ¨......
>> >> >> > 0008: 0e 00 00 00 4c 00 45 00 ...L.E.
>> >> >> > 0010: 45 00 53 00 51 00 4c 00 E.S.Q.L.
>> >> >> > 0018: 00 00 0e 00 00 00 6d 00 .....m.
>> >> >> > 0020: 61 00 73 00 74 00 65 00 a.s.t.e.
>> >> >> > 0028: 72 00 00 00 r...
>> >> >> >
>> >> >> > Everytime I try to run a job in sql server agent it shuts down
>> >> >> > the
>> >> >> > agent.
>> >> >> > None of the files in the log directory have any details about the
>> >> >> > shutdown.
>> >> >> > This is driving me nuts. I have checked and rechecked permissions
>> >> >> > and
>> >> >> > even
>> >> >> > created a new login for the sql server and the agent to use.
>> >> >> > Still
>> >> >> > the
>> >> >> > same
>> >> >> > thing. Since I am getting no error logs I am totally lost as to
>> >> >> > where
>> >> >> > to
>> >> >> > look
>> >> >> > for information. I am also not finding anything about this when I
>> >> >> > google
>> >> >> > for
>> >> >> > it. Any help anyone could give would be appreciated.
>> >> >> > --
>> >> >> > Mark A. Lutz (aka Eggbert)
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||Did you happen on an answer in your situation yet?
--
Mark A. Lutz (aka Eggbert)
"Geoff N. Hiten" wrote:
> Thanks.
> I am seeing the exact same thing at a client after a maintenance window
> where updates were applied. I suspect an interaction between an update and
> the SQL agent, but am having some difficulty proving it. Thanks for the
> details on your configuration. I will let you know if I find anything on my
> end.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> news:E76F1FDD-5BEC-4B98-9A19-5AEBAAEA4214@.microsoft.com...
> > In my setup we have 4 servers that are colocated with a web hosting
> > service
> > so I do not have direct contact with them. The servers are not in an
> > Active
> > Directory Domain Structure and each opperates independantly. The server in
> > question is my SQL server only. Each of my servers have two network cards.
> > One card is connected to the internet and the other card is connected to
> > an
> > internal only router. The SQL server is setup to only respond to the
> > internal
> > cart and port. The account running the SQL Server and SQL Agent is the a
> > local account for the SQL Server box.
> > The last time one of my jobs ran sucsesfully was 2/6/07. It does not
> > appear
> > that MS07-009 has been applied. The way I checked was to go out to
> > windowsupdate.microsoft.com and used the View your Update History option.
> >
> > Again this is the oddest thing I have seen and I cant find a reason for
> > it.
> > As I mentioned in another post wether I try to run a job manually or let
> > agent run it at a specific time, as soon as the job starts Agent shuts
> > down
> > and restarts. There are no the last entry in the log is that the job was
> > requested to run i.e.
> > 2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been
> > requested
> > to run by User LEESQL\Mark
> >
> > The System Event viewer records "The SQLSERVERAGENT service terminated
> > unexpectedly." and that the Agent has restarted. There are no other log
> > entries anywhere.
> >
> > --
> > Mark A. Lutz (aka Eggbert)
> >
> >
> > "Geoff N. Hiten" wrote:
> >
> >> Check your system and see if you have MS07-009 applied (KB 927779). This
> >> is
> >> a windows update security patch released ths month.
> >>
> >> Is your system in a resource domain that is called by users in another
> >> domain?
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior Database Administrator
> >> Microsoft SQL Server MVP
> >>
> >>
> >>
> >>
> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
> >> > 1.
> >> > 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)
> >> >
> >> > 2.
> >> > No it is not clustered.
> >> >
> >> > 3.
> >> > Yes I have tried to run both the SQL Server and Agent under the local
> >> > system
> >> > account
> >> >
> >> > 4.
> >> > I have checked all logs and nothing is recorded when Agent goes down
> >> > with
> >> > the exception of what I have already stated.
> >> > --
> >> > Mark A. Lutz (aka Eggbert)
> >> >
> >> >
> >> > "Uri Dimant" wrote:
> >> >
> >> >> Hi
> >> >> 1) Is it SQL Server 7.0/2000/2005?
> >> >> 2) Is it clustered?
> >> >> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
> >> >> 3) Have you tried to set LocalSystem account to the service?
> >> >> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
> >> >>
> >> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
> >> >> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
> >> >> > As I mentioned I had done that and not found anything informative
> >> >> > but I
> >> >> > will
> >> >> > paste them here:
> >> >> >
> >> >> >
> >> >> > ____________
> >> >> > SQLAGENT.OUT
> >> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
> >> >> > 8.00.2039
> >> >> > (x86 unicode retail build) : Process ID
> >> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
> >> >> > 8.00.2039
> >> >> > (x86 unicode retail build) : Process ID 396
> >> >> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039 (0
> >> >> > connection limit)
> >> >> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version
> >> >> > 3.86.1830
> >> >> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
> >> >> > DBMSSHRN.DLL;
> >> >> > Local host server is
> >> >> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM
> >> >> > detected
> >> >> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running
> >> >> > Windows
> >> >> > NT
> >> >> > 5.2 (3790) Service Pack 1
> >> >> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under Windows
> >> >> > NT
> >> >> > service control
> >> >> > 2007-02-20 04:38:39 - + [260] Unable to start mail session (reason:
> >> >> > No
> >> >> > mail
> >> >> > profile defined)
> >> >> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
> >> >> > defined -
> >> >> > OnIdle job schedules will have no effect
> >> >> >
> >> >> > ____________
> >> >> > SQLAGENT.1
> >> >> > 2007-02-20 04:36:59.00 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)
> >> >> >
> >> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> >> >> > Corporation.
> >> >> > 2007-02-20 04:36:59.00 server All rights reserved.
> >> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> >> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> >> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> >> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
> >> >> > class
> >> >> > 'normal'(2 CPUs detected).
> >> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
> >> >> > mode
> >> >> > processing.
> >> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
> >> >> > [2500]
> >> >> > Lock
> >> >> > Blocks, [5000] Lock Owner Blocks.
> >> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
> >> >> > Distributed
> >> >> > Transaction Coordinator.
> >> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> >> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
> >> >> > '8.0.2039'.
> >> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> >> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
> >> >> > 192.168.1.50:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
> >> >> > 64.27.15.116:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> >> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> >> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> >> >> > Memory,
> >> >> > Named Pipes.
> >> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> >> >> > connections
> >> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> >> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> >> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> >> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> >> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> >> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> >> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> >> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> >> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> >> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> >> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> >> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> >> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> >> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
> >> >> > 'SWFPortalDev'.
> >> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> >> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> >> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task
> >> >> > is
> >> >> > created.
> >> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> >> >> > '2000.80.2039'
> >> >> > to execute extended stored procedure 'xp_qv'.
> >> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
> >> >> > '2000.80.2039'
> >> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >> >> >
> >> >> > ____________
> >> >> > ERRORLOG
> >> >> >
> >> >> > 2007-02-20 04:36:59.00 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)
> >> >> >
> >> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002 Microsoft
> >> >> > Corporation.
> >> >> > 2007-02-20 04:36:59.00 server All rights reserved.
> >> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
> >> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in file
> >> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
> >> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at priority
> >> >> > class
> >> >> > 'normal'(2 CPUs detected).
> >> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
> >> >> > mode
> >> >> > processing.
> >> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
> >> >> > [2500]
> >> >> > Lock
> >> >> > Blocks, [5000] Lock Owner Blocks.
> >> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
> >> >> > Distributed
> >> >> > Transaction Coordinator.
> >> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
> >> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
> >> >> > '8.0.2039'.
> >> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
> >> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
> >> >> > 192.168.1.50:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
> >> >> > 64.27.15.116:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on 127.0.0.1:
> >> >> > 1433.
> >> >> > 2007-02-20 04:37:00.50 spid10 Starting up database 'Northwind'.
> >> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
> >> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP, Shared
> >> >> > Memory,
> >> >> > Named Pipes.
> >> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
> >> >> > connections
> >> >> > 2007-02-20 04:37:00.51 spid13 Starting up database 'SWFLinker'.
> >> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
> >> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
> >> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
> >> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
> >> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
> >> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
> >> >> > 2007-02-20 04:37:00.78 spid9 Starting up database 'DNNTransfer'.
> >> >> > 2007-02-20 04:37:00.78 spid10 Starting up database 'OpenRealty'.
> >> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
> >> >> > 2007-02-20 04:37:00.95 spid15 Starting up database 'SWFPortal'.
> >> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
> >> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
> >> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
> >> >> > 'SWFPortalDev'.
> >> >> > 2007-02-20 04:37:01.42 spid13 Starting up database 'TimeTracker'.
> >> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
> >> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection task
> >> >> > is
> >> >> > created.
> >> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
> >> >> > '2000.80.2039'
> >> >> > to execute extended stored procedure 'xp_qv'.
> >> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
> >> >> > '2000.80.2039'
> >> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
> >> >> >
> >> >> > --
> >> >> > Mark A. Lutz (aka Eggbert)
> >> >> >
> >> >> >|||Not yet. The client rebuilt the system before I could get into it and do a
good in-depth analysis.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
news:DC3A1A40-43D3-4BD5-937D-80FCCF379BFA@.microsoft.com...
> Did you happen on an answer in your situation yet?
> --
> Mark A. Lutz (aka Eggbert)
>
> "Geoff N. Hiten" wrote:
>> Thanks.
>> I am seeing the exact same thing at a client after a maintenance window
>> where updates were applied. I suspect an interaction between an update
>> and
>> the SQL agent, but am having some difficulty proving it. Thanks for the
>> details on your configuration. I will let you know if I find anything on
>> my
>> end.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>>
>>
>> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> news:E76F1FDD-5BEC-4B98-9A19-5AEBAAEA4214@.microsoft.com...
>> > In my setup we have 4 servers that are colocated with a web hosting
>> > service
>> > so I do not have direct contact with them. The servers are not in an
>> > Active
>> > Directory Domain Structure and each opperates independantly. The server
>> > in
>> > question is my SQL server only. Each of my servers have two network
>> > cards.
>> > One card is connected to the internet and the other card is connected
>> > to
>> > an
>> > internal only router. The SQL server is setup to only respond to the
>> > internal
>> > cart and port. The account running the SQL Server and SQL Agent is the
>> > a
>> > local account for the SQL Server box.
>> > The last time one of my jobs ran sucsesfully was 2/6/07. It does not
>> > appear
>> > that MS07-009 has been applied. The way I checked was to go out to
>> > windowsupdate.microsoft.com and used the View your Update History
>> > option.
>> >
>> > Again this is the oddest thing I have seen and I cant find a reason for
>> > it.
>> > As I mentioned in another post wether I try to run a job manually or
>> > let
>> > agent run it at a specific time, as soon as the job starts Agent shuts
>> > down
>> > and restarts. There are no the last entry in the log is that the job
>> > was
>> > requested to run i.e.
>> > 2007-02-21 08:57:58 - ? [177] Job SWFHomes Listings Alert has been
>> > requested
>> > to run by User LEESQL\Mark
>> >
>> > The System Event viewer records "The SQLSERVERAGENT service terminated
>> > unexpectedly." and that the Agent has restarted. There are no other log
>> > entries anywhere.
>> >
>> > --
>> > Mark A. Lutz (aka Eggbert)
>> >
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> Check your system and see if you have MS07-009 applied (KB 927779).
>> >> This
>> >> is
>> >> a windows update security patch released ths month.
>> >>
>> >> Is your system in a resource domain that is called by users in another
>> >> domain?
>> >>
>> >> --
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP
>> >>
>> >>
>> >>
>> >>
>> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> news:B96458B0-B21A-4017-A509-3F9FEF7372D3@.microsoft.com...
>> >> > 1.
>> >> > 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)
>> >> >
>> >> > 2.
>> >> > No it is not clustered.
>> >> >
>> >> > 3.
>> >> > Yes I have tried to run both the SQL Server and Agent under the
>> >> > local
>> >> > system
>> >> > account
>> >> >
>> >> > 4.
>> >> > I have checked all logs and nothing is recorded when Agent goes down
>> >> > with
>> >> > the exception of what I have already stated.
>> >> > --
>> >> > Mark A. Lutz (aka Eggbert)
>> >> >
>> >> >
>> >> > "Uri Dimant" wrote:
>> >> >
>> >> >> Hi
>> >> >> 1) Is it SQL Server 7.0/2000/2005?
>> >> >> 2) Is it clustered?
>> >> >> http://www.tutorials-ne.com/clustering/Cannot-create-14238/
>> >> >> 3) Have you tried to set LocalSystem account to the service?
>> >> >> 4) http://msdn2.microsoft.com/en-us/library/aa213827(sql.80).aspx
>> >> >>
>> >> >> "Eggbert" <Eggbert@.discussions.microsoft.com> wrote in message
>> >> >> news:B80B5723-C7A9-4269-98EB-2C9551C23734@.microsoft.com...
>> >> >> > As I mentioned I had done that and not found anything informative
>> >> >> > but I
>> >> >> > will
>> >> >> > paste them here:
>> >> >> >
>> >> >> >
>> >> >> > ____________
>> >> >> > SQLAGENT.OUT
>> >> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> >> >> > 8.00.2039
>> >> >> > (x86 unicode retail build) : Process ID
>> >> >> > 2007-02-20 04:38:39 - ? [100] Microsoft SQLServerAgent version
>> >> >> > 8.00.2039
>> >> >> > (x86 unicode retail build) : Process ID 396
>> >> >> > 2007-02-20 04:38:39 - ? [101] SQL Server LEESQL version 8.00.2039
>> >> >> > (0
>> >> >> > connection limit)
>> >> >> > 2007-02-20 04:38:39 - ? [102] SQL Server ODBC driver version
>> >> >> > 3.86.1830
>> >> >> > 2007-02-20 04:38:39 - ? [103] NetLib being used by driver is
>> >> >> > DBMSSHRN.DLL;
>> >> >> > Local host server is
>> >> >> > 2007-02-20 04:38:39 - ? [310] 2 processor(s) and 2048 MB RAM
>> >> >> > detected
>> >> >> > 2007-02-20 04:38:39 - ? [339] Local computer is LEESQL running
>> >> >> > Windows
>> >> >> > NT
>> >> >> > 5.2 (3790) Service Pack 1
>> >> >> > 2007-02-20 04:38:39 - ? [129] SQLSERVERAGENT starting under
>> >> >> > Windows
>> >> >> > NT
>> >> >> > service control
>> >> >> > 2007-02-20 04:38:39 - + [260] Unable to start mail session
>> >> >> > (reason:
>> >> >> > No
>> >> >> > mail
>> >> >> > profile defined)
>> >> >> > 2007-02-20 04:38:39 - + [396] An idle CPU condition has not been
>> >> >> > defined -
>> >> >> > OnIdle job schedules will have no effect
>> >> >> >
>> >> >> > ____________
>> >> >> > SQLAGENT.1
>> >> >> > 2007-02-20 04:36:59.00 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)
>> >> >> >
>> >> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002
>> >> >> > Microsoft
>> >> >> > Corporation.
>> >> >> > 2007-02-20 04:36:59.00 server All rights reserved.
>> >> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> >> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in
>> >> >> > file
>> >> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> >> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at
>> >> >> > priority
>> >> >> > class
>> >> >> > 'normal'(2 CPUs detected).
>> >> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
>> >> >> > mode
>> >> >> > processing.
>> >> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
>> >> >> > [2500]
>> >> >> > Lock
>> >> >> > Blocks, [5000] Lock Owner Blocks.
>> >> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
>> >> >> > Distributed
>> >> >> > Transaction Coordinator.
>> >> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> >> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> >> >> > '8.0.2039'.
>> >> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> >> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 192.168.1.50:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 64.27.15.116:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 127.0.0.1:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 spid10 Starting up database
>> >> >> > 'Northwind'.
>> >> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> >> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP,
>> >> >> > Shared
>> >> >> > Memory,
>> >> >> > Named Pipes.
>> >> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> >> >> > connections
>> >> >> > 2007-02-20 04:37:00.51 spid13 Starting up database
>> >> >> > 'SWFLinker'.
>> >> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> >> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> >> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> >> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> >> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> >> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> >> >> > 2007-02-20 04:37:00.78 spid9 Starting up database
>> >> >> > 'DNNTransfer'.
>> >> >> > 2007-02-20 04:37:00.78 spid10 Starting up database
>> >> >> > 'OpenRealty'.
>> >> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> >> >> > 2007-02-20 04:37:00.95 spid15 Starting up database
>> >> >> > 'SWFPortal'.
>> >> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> >> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> >> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
>> >> >> > 'SWFPortalDev'.
>> >> >> > 2007-02-20 04:37:01.42 spid13 Starting up database
>> >> >> > 'TimeTracker'.
>> >> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> >> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection
>> >> >> > task
>> >> >> > is
>> >> >> > created.
>> >> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> >> >> > '2000.80.2039'
>> >> >> > to execute extended stored procedure 'xp_qv'.
>> >> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> >> >> > '2000.80.2039'
>> >> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >> >> >
>> >> >> > ____________
>> >> >> > ERRORLOG
>> >> >> >
>> >> >> > 2007-02-20 04:36:59.00 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)
>> >> >> >
>> >> >> > 2007-02-20 04:36:59.00 server Copyright (C) 1988-2002
>> >> >> > Microsoft
>> >> >> > Corporation.
>> >> >> > 2007-02-20 04:36:59.00 server All rights reserved.
>> >> >> > 2007-02-20 04:36:59.00 server Server Process ID is 1184.
>> >> >> > 2007-02-20 04:36:59.00 server Logging SQL Server messages in
>> >> >> > file
>> >> >> > 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
>> >> >> > 2007-02-20 04:36:59.00 server SQL Server is starting at
>> >> >> > priority
>> >> >> > class
>> >> >> > 'normal'(2 CPUs detected).
>> >> >> > 2007-02-20 04:36:59.09 server SQL Server configured for thread
>> >> >> > mode
>> >> >> > processing.
>> >> >> > 2007-02-20 04:36:59.10 server Using dynamic lock allocation.
>> >> >> > [2500]
>> >> >> > Lock
>> >> >> > Blocks, [5000] Lock Owner Blocks.
>> >> >> > 2007-02-20 04:36:59.10 server Attempting to initialize
>> >> >> > Distributed
>> >> >> > Transaction Coordinator.
>> >> >> > 2007-02-20 04:37:00.31 spid2 Starting up database 'master'.
>> >> >> > 2007-02-20 04:37:00.45 server Using 'SSNETLIB.DLL' version
>> >> >> > '8.0.2039'.
>> >> >> > 2007-02-20 04:37:00.45 spid5 Starting up database 'model'.
>> >> >> > 2007-02-20 04:37:00.50 spid2 Server name is 'LEESQL'.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 192.168.1.50:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 64.27.15.116:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 server SQL server listening on
>> >> >> > 127.0.0.1:
>> >> >> > 1433.
>> >> >> > 2007-02-20 04:37:00.50 spid10 Starting up database
>> >> >> > 'Northwind'.
>> >> >> > 2007-02-20 04:37:00.51 spid8 Starting up database 'msdb'.
>> >> >> > 2007-02-20 04:37:00.51 server SQL server listening on TCP,
>> >> >> > Shared
>> >> >> > Memory,
>> >> >> > Named Pipes.
>> >> >> > 2007-02-20 04:37:00.51 server SQL Server is ready for client
>> >> >> > connections
>> >> >> > 2007-02-20 04:37:00.51 spid13 Starting up database
>> >> >> > 'SWFLinker'.
>> >> >> > 2007-02-20 04:37:00.51 spid14 Starting up database 'DNN4'.
>> >> >> > 2007-02-20 04:37:00.51 spid11 Starting up database 'BT'.
>> >> >> > 2007-02-20 04:37:00.51 spid15 Starting up database 'EOD'.
>> >> >> > 2007-02-20 04:37:00.51 spid12 Starting up database 'SWFHomes'.
>> >> >> > 2007-02-20 04:37:00.51 spid9 Starting up database 'pubs'.
>> >> >> > 2007-02-20 04:37:00.76 spid5 Clearing tempdb database.
>> >> >> > 2007-02-20 04:37:00.78 spid9 Starting up database
>> >> >> > 'DNNTransfer'.
>> >> >> > 2007-02-20 04:37:00.78 spid10 Starting up database
>> >> >> > 'OpenRealty'.
>> >> >> > 2007-02-20 04:37:00.89 spid8 Starting up database 'Projects'.
>> >> >> > 2007-02-20 04:37:00.95 spid15 Starting up database
>> >> >> > 'SWFPortal'.
>> >> >> > 2007-02-20 04:37:01.23 spid11 Starting up database 'DNNTest'.
>> >> >> > 2007-02-20 04:37:01.23 spid5 Starting up database 'tempdb'.
>> >> >> > 2007-02-20 04:37:01.29 spid14 Starting up database
>> >> >> > 'SWFPortalDev'.
>> >> >> > 2007-02-20 04:37:01.42 spid13 Starting up database
>> >> >> > 'TimeTracker'.
>> >> >> > 2007-02-20 04:37:55.15 spid2 Recovery complete.
>> >> >> > 2007-02-20 04:37:55.15 spid2 SQL global counter collection
>> >> >> > task
>> >> >> > is
>> >> >> > created.
>> >> >> > 2007-02-20 04:37:55.68 spid69 Using 'xpsqlbot.dll' version
>> >> >> > '2000.80.2039'
>> >> >> > to execute extended stored procedure 'xp_qv'.
>> >> >> > 2007-02-20 04:37:55.92 spid70 Using 'xpstar.dll' version
>> >> >> > '2000.80.2039'
>> >> >> > to execute extended stored procedure 'xp_sqlagent_monitor'.
>> >> >> >
>> >> >> > --
>> >> >> > Mark A. Lutz (aka Eggbert)
>> >> >> >
>> >> >> >