Multi value in Report Parameter using MSVS Report Designer.

Hi All,

I have a question, How to user the Multi value in Visual Studio Report Designer.

My dataset contains the following

Select empno,empname,basicpay,deptcd from employee where deptcd in (substring(@.gdept,1,4))

Here variable gdept is the report parameter. I am passing the value.
it works fine with single value.

( the source of gdept is a another dataset to list the deparment code+name,

Example

DEP1 - COMPUTER

DEP2 - ADMIN

DEP3 - FINANCE

)

when I preview, i have a combo box to select the department.

If I choose one deparment, it works fine.

If I choose more than one department or select all I have error message

"substring function requires 3 aruguments."

what is wrong is the query

Please advise.

Cheers,

Saleem

Thats nor possible within a single query. By choosing more than one Value it will evaluate to SUBSTR('A','B',1,4) which is not valid, because the signature of SUBSTRING Only allows 3 parameters. You will have to do that with splitting the values. I once wrote a function for that which will make those values Accessible for you as a table and which can be joined easily afterwards.

See more details on: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=320221&SiteID=1

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Multi Threading in Stored Procedures?

hi,
I want to execute two user created stored procedures in a multithreaded manner in ms-sql server . Can some tell me how i can do that.
Thanks in advance.
Regards,
ManpreetOriginally posted by chugh_manpreet
hi,

I want to execute two users


Ya know....I've ALWAYS wanted to do that...

but then who would use the system?

Well, I guess if you limit to just 2....

To answer though...every exec od a sproc is threaded...it's not serial...

Are you talking about withIN the sproc itself?|||By its design the SQL engine is single-process multi-threaded. A series of asynchronous calls always result in multi-threaded processing on the server. I guess I have the same question as Brett, - are you talking about multi-threading within a stored procedure? And why do you need that?|||No chuckles?

Anyway...To thread in a sproc, create jobs and start'em...

They'll be aysyncronus and thread...

although I swear (and can't confirm) that using xp_cmdshell does...even though everywhere I read it's synchronous...(I couldn;t explain some blocking awhile back...still don't know why)|||I can! In pre-SP3 era when everybody and their mother was firing it while trying to be cute, and coming back with OSQL through it. There was a hell of a blocking going on. It is actually due to the nature of OSQL, rather than xp_cmdshell, but those who were using it didn't even bother to check into the possibility of it to occur, and we were stuck to debug, and what's most frustrating, - explain, how it happened. Now they are all squealing, because they can't do any more damage :)|||Yeah, but in a sproc if you do...

DELETE FROM myTable99

master xp_cmdshell 'bcp command...for myTable99'

Wouldn't you expect the DELETE to be completed before the bcp?

It actually launches 2 spids (of course) but spid 1 (the execution of the sproc and the delete) blocks spid 2, the execution of xp_cmdshell

huh?

Is this a fundamental thing I'm totally missing?|||hi,

thanks for your reply. Actually i have written two stored procedures which call a dll(non-sql) funtion. Now i want these two stored procedures simultaneously in a multi threaded manner.

I tried executing it like this

exec sp_Procedure1
exec sp_Procedure2

but the second stored procedures is not getting executed untill first gets executed. I want both the stored procedures execute simultaneously in a multi threaded manner.

Any inputs in this regard are welcome

Regards,
Manpreet

Originally posted by Brett Kaiser
No chuckles?

Anyway...To thread in a sproc, create jobs and start'em...

They'll be aysyncronus and thread...

although I swear (and can't confirm) that using xp_cmdshell does...even though everywhere I read it's synchronous...(I couldn;t explain some blocking awhile back...still don't know why)|||hi,

thanks for your reply. Actually i have written two stored procedures which call a dll(non-sql) funtion. Now i want these two stored procedures simultaneously in a multi threaded manner.

I tried executing it like this

exec sp_Procedure1
exec sp_Procedure2

but the second stored procedures is not getting executed untill first gets executed. I want both the stored procedures execute simultaneously in a multi threaded manner.

Any inputs in this regard are welcome

Regards,
Manpreet
Sorry for bumping an old post, but I am looking to do the same thing, pseudocode below for those that want to know why.

---------------
CREATE PROC COMPANY_ISP
@.company_id INT
AS

INSERT COMPANY(COMPANY_ID)
SELECT @.company_id

EXEC COMPANY_REBUILD_INDEX @.company_id

RETURN
---------------

The proc is actaully a little longer then the above but you get the idea, COMPANY_REBUILD_INDEX takes about 10 seconds to run and waiting for it to process is not critical to the web page calling this proc, but rather a hindrance since the application needs to wait for this process to finish.

I suppose the application could call this proc separately behind the scenes somehow, I can talk with the .Net developer to see what he thinks, but thought it would be nice to have a solution that would work in SQL. xp_cmdshell? I thought that was only for DOS commands, does not seem like it is the solution I am looking for.

Thanks,
-John|||Applicaton design issues should be handled by the application designers.

If I want an application to run two stored procedures simultaneously, then I expect the application to thread the executions. If the applicaton wants serial execution, then serialize them.

You should consider not only the near term results, but also the long term maintainability. Cute solutions usually compromise the latter for the former.

For your solution, it seems you are expecting an inherently single threaded application (browser) to handle asynchronous communications.

The reindex should probably be done via a job that detects the request (writes a flag somewhere), and then you can write a control that polls a progress table for completion. This way, a user can refresh their browser w/o losing (needing to maintain) the state of the ReIndex.|||first thing that bothers me here is the fact that you are reindexing after every insert. why not just reindex the table overnight in a job.

I wonder what effect of (and I would never try this exepcially with a 10 second execution) is of putting your reindex into an insert trigger (which I use sparingly) on the table. Would the ASP page go about it's merry business before the trigger completed or would you still get held up on your page waiting on the trigger to execute.

By the way if your trying to insert and reindex at the same time on the same table I do imagine there would be some blocking even if you used multi-threading as implimented in JAVA.|||first thing that bothers me here is the fact that you are reindexing after every insert. why not just reindex the table overnight in a job.

I wonder what effect of (and I would never try this exepcially with a 10 second execution) is of putting your reindex into an insert trigger (which I use sparingly) on the table. Would the ASP page go about it's merry business before the trigger completed or would you still get held up on your page waiting on the trigger to execute.

By the way if your trying to insert and reindex at the same time on the same table I do imagine there would be some blocking even if you used multi-threading as implimented in JAVA.

I was curious myself about the trigger, if I created a trigger would the calling proc wait for the trigger to finish before returning to the application?

The reason I need to incrementally rebuild the index (I currently have an overnight job btw) is that when a user adds a new company they need a way to be able to search for it later, our search page does a phonetic search for companies (in case they misspelled it), if the job only runs nightly then the user would have to wait until the next day to see the company in the search results. This is an intranet application for about 50 users and adding companies is not going to be a very frequent process so I am not concerned with the strain on the server.

For anyone interested in implementing a phonetic search here is the pseudocode:

1. Split the company name into words
2. Translate each word into its phonetic representation (soundex is one option albeit bad - I implemented a double metaphone translation)
3. Remove duplicate phonetic words per company
4. Aggregate the occurrences of each phonetic
5. Give a score based on (in)frequency of each phonetic to aid in improved search results.
6. Increase the score for exact word matches
7. Increase the score for exact phrase matches
8. Return the results by score descending

There are about 40k unique phonetic words that are created as a result of this (out of a pool of close to a million companies).|||I was curious myself about the trigger, if I created a trigger would the calling proc wait for the trigger to finish before returning to the application?

Try it and let me know.|||Maybe I'm missing something really fundamental, but what on earth are you trying to accomplish? Reindexing is a performance issue, it can improve the internal structure of an index after massive inserts or deletes. Reindexing had better not have any effect at all on what rows are visible in the table!

Did I miss a meeting, or is this entire discussion moot?

-PatP|||Pat,

from what it sounds like his sp (COMPANY_REBUILD_INDEX) is a misnomer. It sounds like he is really doing all of his processing for his phonetic thingy majiggy and not a DBCC DBREINDEX. (which sounds like a lot of trouble to go through to tame some bad data entry).|||It's a nessary evil, we have over 100k council members that enter their own data, the search is used to help normalize the company name that they enter into their job history profile (each member can enter multiple job profiles based on their work history). The search had to be as flexible as possible and had to search on a per word basis and handle spelling mistakes, I think in the next version they want us to use a thesaurus to be able to match firm to company but in my mind THAT is going way overboard.|||did you try the trigger thing. i assumed you were't really doing a reindex as in dbcc. how did it go?

Multi Server Jobs

I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leil|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>> I am running two instances of SQL Server 2005 Developer Edition (SP1)
>> on the same machine. Both SQL Server and Agent services use a local
>> user account which is member of Windows Administrators. The wizard for
>> Enlisting TSX fails with the following report:
>> Enlist TSX Progress
>> - Create MSXOperator (Success)
>> Checking for an existing MSXOperator.
>> Updating existing MSXOperator.
>> Successfully updated MSXOperator.
>> - Make sure the Agent service for 'NIMA\sql2005_1' is running
>> (Success)
>> The service 'SQLAgent$SQL2005_1' is running.
>> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
>> Enlisting target server 'NIMA\sql2005_2' with master server
>> 'NIMA\sql2005_1'.
>> Using new enlistment method.
>> Messages
>> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
>> (Microsoft.SqlServer.Smo)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
>> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
>> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
>> 6
>> --
>> ADDITIONAL INFORMATION:
>> An exception occurred while executing a Transact-SQL statement or
>> batch. (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The enlist operation failed (reason: SQLServerAgent Error: Unable to
>> connect to server. .) (Microsoft SQL Server, Error: 22026)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
>> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
>> Any help would be greatly appreciated,
>> leila
>

Multi Server Jobs

I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons

> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leila|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews
.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>sql

Multi Server Jobs

I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=MSX+enlist+JobServer&LinkId=20476[/url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476[ /url]
Any help would be greatly appreciated,
leila
Hello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons

> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management. Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+J obServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20 476
> Any help would be greatly appreciated,
> leila
|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft .com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>

Multi Select Parameters?

In SQL Reporting Services, Is there anyway to create a parameter in
which a user can be prompted to choose multiple values from a list?
Ultimately, the multi-selected values would be passed to the Dataset
query as an "IN" qualification.
Example:
SELECT first_name, last_name
FROM employees
LEFT OUTER JOIN department ON
employees.dept_id = department.dept_id
WHERE dept_name IN ('Accounting', 'Sales', Support')
Crystal Reports has this functionality but I can not figure out how to
do this in MSRS.
If you know how to do this and would like to help a guy out, could you
include step by step answer or a link to a step by step tutorial?
Thanks!Here are a couple of options:
Option #1: Use a query expression as follows: ="select top 10 name, type
from sysobjects where type in (" & Parameters!Report_Parameter_0.Value &
")".
Option #2: Check
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=0a3800c4-4180-419c-a117-bfa21b2de099.
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"The Whistler" <sharris@.SLeasynews.com> wrote in message
news:ltnrg01f5qf251e89c5vsrmcdn7fu01k4i@.4ax.com...
> In SQL Reporting Services, Is there anyway to create a parameter in
> which a user can be prompted to choose multiple values from a list?
> Ultimately, the multi-selected values would be passed to the Dataset
> query as an "IN" qualification.
> Example:
> SELECT first_name, last_name
> FROM employees
> LEFT OUTER JOIN department ON
> employees.dept_id = department.dept_id
> WHERE dept_name IN ('Accounting', 'Sales', Support')
> Crystal Reports has this functionality but I can not figure out how to
> do this in MSRS.
> If you know how to do this and would like to help a guy out, could you
> include step by step answer or a link to a step by step tutorial?
> Thanks!sql

Multi Language Report Function

I have written a function which translates text based upon the language the
user chooses to see the report in (it can also be passed in as a data driven
parm for static runs) Anyway ... my question is this ... since I am new to RS
and new to Vb .Net I was wondering if someone out there can look at what I am
trying to do and suggest a better way ... since I dont want to have to code a
function like this for 25+ fields to be translated and in 4+ languages. I
think when you see the function I wrote you will get the idea and perhaps be
able to suggest an efficient way to translate all fields at once or perhaps
"generic" function (which I tried to code too with nested CASE statements but
abandoned). Anyway ... here is the newbie's (my) solution - dont laugh :-)
This is what I code in the text box for the expression ===>
=Code.TranslateTitle(Parameters!pm_language_code.value)
HERE IS THE FUNCTION
Function TranslateTitle ( ByVal Language_Code As String ) As String
Select Language_Code
Case "EN"
Return "Detailed Report : "
Case "FR"
Return "Rapport Détaillé : "
Case "DE"
Return "Ausführlicher Report : "
Case "NL"
Return "Gedetailleerd Rapport : "
Case Else
Return "Detailed Report : "
End Select
End Function
This works just fine ... but I have 25+ fields with translations !!!
Thanks in advanceHi,
You can use resource files just as in ASP.NET applications.
You can reference these resource dll files within a function written as a
custom code.
Eralper
http://www.kodyaz.com
"MJ Taft" wrote:
> I have written a function which translates text based upon the language the
> user chooses to see the report in (it can also be passed in as a data driven
> parm for static runs) Anyway ... my question is this ... since I am new to RS
> and new to Vb .Net I was wondering if someone out there can look at what I am
> trying to do and suggest a better way ... since I dont want to have to code a
> function like this for 25+ fields to be translated and in 4+ languages. I
> think when you see the function I wrote you will get the idea and perhaps be
> able to suggest an efficient way to translate all fields at once or perhaps
> "generic" function (which I tried to code too with nested CASE statements but
> abandoned). Anyway ... here is the newbie's (my) solution - dont laugh :-)
> This is what I code in the text box for the expression ===>
> =Code.TranslateTitle(Parameters!pm_language_code.value)
> HERE IS THE FUNCTION
> Function TranslateTitle ( ByVal Language_Code As String ) As String
> Select Language_Code
> Case "EN"
> Return "Detailed Report : "
> Case "FR"
> Return "Rapport Détaillé : "
> Case "DE"
> Return "Ausführlicher Report : "
> Case "NL"
> Return "Gedetailleerd Rapport : "
> Case Else
> Return "Detailed Report : "
> End Select
> End Function
> This works just fine ... but I have 25+ fields with translations !!!
> Thanks in advance|||Thanks for your response however I dont know asp .net - in fact ... just got
a book to learn it. So I dont know how to do what you are suggesting here.
Could you be more specific? Point to a simple example maybe?
"eralper" wrote:
> Hi,
> You can use resource files just as in ASP.NET applications.
> You can reference these resource dll files within a function written as a
> custom code.
> Eralper
> http://www.kodyaz.com
> "MJ Taft" wrote:
> > I have written a function which translates text based upon the language the
> > user chooses to see the report in (it can also be passed in as a data driven
> > parm for static runs) Anyway ... my question is this ... since I am new to RS
> > and new to Vb .Net I was wondering if someone out there can look at what I am
> > trying to do and suggest a better way ... since I dont want to have to code a
> > function like this for 25+ fields to be translated and in 4+ languages. I
> > think when you see the function I wrote you will get the idea and perhaps be
> > able to suggest an efficient way to translate all fields at once or perhaps
> > "generic" function (which I tried to code too with nested CASE statements but
> > abandoned). Anyway ... here is the newbie's (my) solution - dont laugh :-)
> >
> > This is what I code in the text box for the expression ===>
> >
> > =Code.TranslateTitle(Parameters!pm_language_code.value)
> >
> > HERE IS THE FUNCTION
> >
> > Function TranslateTitle ( ByVal Language_Code As String ) As String
> > Select Language_Code
> > Case "EN"
> > Return "Detailed Report : "
> > Case "FR"
> > Return "Rapport Détaillé : "
> > Case "DE"
> > Return "Ausführlicher Report : "
> > Case "NL"
> > Return "Gedetailleerd Rapport : "
> > Case Else
> > Return "Detailed Report : "
> > End Select
> > End Function
> >
> > This works just fine ... but I have 25+ fields with translations !!!
> >
> > Thanks in advance

Multi connection problem

Hi all,
In my accounting application if one user tries to execute a long report that
my take several minutes, the other users who are entering invoices almost
hang, and the process of enter products into the invoices or the saving the
invoices slow down significantly.
I'm using VC++ 2003, ODBC, SQL 2000 Ent.
Any body know how to overcome this problem.
Thanks in advance.You could try running the report query inside a transaction with READ
UNCOMMITTED isolation level.
The next time the report runs, take a look at the locks in the database. If
there are a lot of locks, running the report under READ UNCOMMITTED should
help.
"ATS967" wrote:

> Hi all,
> In my accounting application if one user tries to execute a long report th
at
> my take several minutes, the other users who are entering invoices almost
> hang, and the process of enter products into the invoices or the saving th
e
> invoices slow down significantly.
> I'm using VC++ 2003, ODBC, SQL 2000 Ent.
> Any body know how to overcome this problem.
> Thanks in advance.|||A seperate reporting database would solve this. A simple solution is to
restore a backup of the production db with a different name on a nightly
basis. Data is a day old but that's usually OK for reporting. If you mark th
e
reporting db read-only it will speed up those reports too.
"ATS967" wrote:

> Hi all,
> In my accounting application if one user tries to execute a long report th
at
> my take several minutes, the other users who are entering invoices almost
> hang, and the process of enter products into the invoices or the saving th
e
> invoices slow down significantly.
> I'm using VC++ 2003, ODBC, SQL 2000 Ent.
> Any body know how to overcome this problem.
> Thanks in advance.

multi choice dropdownlist

Hi,

I want to display States for selected country in a dropdown list and allow user to choose multiple states before clicking view report . Is this feature possible in SRS ?

Pl help

Bhat

Bhat,

In the report parameters dialog screen, click on the parameter and check the box that says multiple values.

This will place a checkbox on each item in the dropdown list, and allow them to check all that apply.|||

I want to implement this feature in 2000 reporting service . I am aware it is in 2005 .

Mullti-report navigation through hyperlinking in Crystal Reports XI

Hi everybody.
I have 4 fields(columns) in report A, 3 fields in report B and 3 fields in report C. What I want is, when a user clicks on the values in the first field in report A, say EmpId, it should jump to report B with only the data for the EmpId on which the user clicked. Again, when the user clicks on the 3rd field in report B(the opened/generated from A), it should open the report C with corresponding values of report B. In short, it should jump from A->B->C.
A part of it can be achieved by using subreports, but it cannot jump from B->C.
Can anyone suggest anything.
Thanks in advance.
Waiting eagerly for reply.

Thanks.U can use on demand subreports, but a main report can have many subrepports but a subreport cannot have another subreport.

MSSQLService (MSDE) Not Re-Configured correctly

Hi all,

I have a question regarding restarting MS SQL Service under a different user, in other words, re-starting MSSQLService as a "Log on as" user instead of "Local System" account. By default MSSQLService starts as a local system account.

Now my problem is, that I install MSDE 2000 for my application. And I install it as a seperate instance with name "MyInstance". So after Install my service is called MSSQL$MyInstance.

so my process basically creates an NT user on the machine with administartors rights, stops the service, change the service configuration to my NT user account credentials and then starts it using scm. The whole process works fine on my machine running Win XP Pro v.2002 SP1. But it fails to work on Win XP Pro v2002 SP2.

on SP2 machine, service gets reconfigured because I can see the Log on as account being changed from Local System to MyNTUser. But when I try to start it every time error is "Log on failure". But when I go to service properties and change the Password to my NT users password service starts properly.

So i'm not sure what exactly is going on, because if reconfiguration process works for my machine, typically it should work on SP2 machine as well, as the notes on ChangeServiceConfig winapi method(requires Advapi32.dll) suggests that it will work for XP, NT and win 2002.

Does anyone has any idea why is that.

Code Snippets:

Create User:

DirectoryEntry AD = new DirectoryEntry("WinNT://" + machineName + ", computer");
DirectoryEntry newUser;
try {
newUser = AD.Children.Find(userName, "user");
DeleteNTUserAccount(userName);
newUser = AD.Children.Add(userName, "user");
}

catch (Exception) {
newUser = AD.Children.Add(userName, "user");
}
newUser.Invoke("Put", new object[] {"Description", userDescription});
newUser.Invoke("SetPassword", new object[] {userPWD});
newUser.CommitChanges();
DirectoryEntry group;
group = AD.Children.Find("Administrators", "group");
if (group != null)
group.Invoke("Add", new object[] {newUser.Path.ToString()});
group.Close();
newUser.Close();
AD.Close();

Code to Stop Service:

ServiceController sc;
TimeSpan timeout = new TimeSpan(0, 0, 60);
OperatingSystem os;
os = Environment.OSVersion;
if (os.Platform != PlatformID.Win32NT) {
txtInstallInfo.Text += "\r\n\tApplication is built only for NT, 2000, XP or Later";
this.Refresh();
retVal = false;
}
os = null;
sc = new ServiceController(serviceName);
if (sc.Status == ServiceControllerStatus.Running) {
if (sc.CanStop) {
txtInstallInfo.Text += "\r\n\tRestarting the " + serviceName + " service";
this.Refresh();
sc.Stop();
try {
sc.WaitForStatus(ServiceControllerStatus.Stopped, timeout);
txtInstallInfo.Text += "\r\n\t" + serviceName + " service stopped successfully";
this.Refresh();
}

catch(TimeoutException) {
txtInstallInfo.Text += "\r\n\t" + serviceName + " service did not respond to the stop command in a timely fashion. Please Restart Installer at later time.";
this.Refresh();
retVal = false;
}
}
else {
txtInstallInfo.Text += "\r\n\t" + serviceName + " service cannot be stopped. Please Wait make sure no application is running.";
this.Refresh();
retVal = false;
}
}
else {
txtInstallInfo.Text += "\r\n\t" + serviceName + " service was not running.";
this.Refresh();
}
sc.Close();
sc = null;

Code to Re-Configure Service:

string UserName = "MyNTUser";
string UserPwd = "abc123";

int HandleToScm = OpenSCManager( null, null, ServiceControlAccessRights.AllAccess );

int HandleToSvc = OpenService( HandleToScm, ServiceName, ServiceSpecificAccessType.ChangeConfig );

if ( ChangeServiceConfig(
HandleToSvc,
ServiceControlType.OwnProcess,
ServiceStartType.AutoStart,
ServiceNoChange,
null,
null,
IntPtr.Zero,
null,
@.".\" + UserName,
UserPwd,
ServiceName ) ) {
CloseServiceHandle( HandleToSvc );
CloseServiceHandle( HandleToScm );
}

Code to Start Service:

scm -Action 1 -Service MSSQL$MyInstance -Silent 1 -SvcAccount .\MYNTUserAccount -SvcPwd MYNTAccountPassword

I've never seen this post before, yet it is dated May 2005. Bumping message...sql

mssqlserver service user profile

greetings, I am trying to get MSSQLserver service to get
started under LocalSystem account. Where can I get info.
regarding this? I am currently starting the MSSQLserver
service under a network user that also has SQL2k profile
with admin role. What user is LocalSystem using. Thanks
for any info. you can send my way.
Sincerely,FredPerusing several on-line book topics, the following comprises some of the
information surrounding the Local System account:
The local system account does not require a password, does not have network
access rights in Windows 2000, Windows XP, and Windows Server 2003, and
restricts your SQL Server installation from interacting with other servers.
==Run SQL Server services with the lowest possible privileges. Associate SQL
Server services with Windows accounts.
==In Windows NT/2000, the Local System account is generally understood to mean
the operating system itself. Selecting the Local System account always
works. However, this account has no network access rights. Therefore, if
you want to integrate more than one SQL Server on your network or integrate
SQL Server with other BackOffice services such as Microsoft Exchange Server,
you should run the SQL Server services under a user account.
--
Keith Wilson
This posting is provided "AS IS" without express or implied warranty,
guarantee, or rights.
"fred ghaffari" <fred_ghaffari@.yahoo.com> wrote in message
news:014301c34c8b$1418ca80$a401280a@.phx.gbl...
> greetings, I am trying to get MSSQLserver service to get
> started under LocalSystem account. Where can I get info.
> regarding this? I am currently starting the MSSQLserver
> service under a network user that also has SQL2k profile
> with admin role. What user is LocalSystem using. Thanks
> for any info. you can send my way.
> Sincerely,Fred

MSSQLSERVER not showing in Services

Hello,
We just installed SQL Server 2K on a user machine. For some reason,
MSSQLSERVER and SQLSERVERAGENT is not showing in Services. We use Services
to update the logon password when we change our NT password. First, what do
we need to do to get MSSQLSERVER to show in Services and is there another
way to update the logon password?
Thanks in advance,
sck10
Perhaps you installed it as a Named instance instead of a default instance. In that case, the
service name is MSSQL$InstanceName.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sck10" <sck10@.online.nospam> wrote in message news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl...
> Hello,
> We just installed SQL Server 2K on a user machine. For some reason,
> MSSQLSERVER and SQLSERVERAGENT is not showing in Services. We use Services
> to update the logon password when we change our NT password. First, what do
> we need to do to get MSSQLSERVER to show in Services and is there another
> way to update the logon password?
> --
> Thanks in advance,
> sck10
>
|||Hi Tibor,
There isn't anything starting with MSSQL.
Thanks in advance,
sck10
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23uMNzfihFHA.3544@.TK2MSFTNGP15.phx.gbl...
> Perhaps you installed it as a Named instance instead of a default
instance. In that case, the
> service name is MSSQL$InstanceName.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sck10" <sck10@.online.nospam> wrote in message
news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
Services[vbcol=seagreen]
what do[vbcol=seagreen]
another
>
|||Perhaps you only installed the client components?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sck10" <sck10@.online.nospam> wrote in message news:OhdxPCjhFHA.1248@.TK2MSFTNGP12.phx.gbl...
> Hi Tibor,
> There isn't anything starting with MSSQL.
> --
> Thanks in advance,
> sck10
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23uMNzfihFHA.3544@.TK2MSFTNGP15.phx.gbl...
> instance. In that case, the
> news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl...
> Services
> what do
> another
>
|||"sck10" <sck10@.online.nospam> wrote in message
news:OhdxPCjhFHA.1248@.TK2MSFTNGP12.phx.gbl...
> Hi Tibor,
> There isn't anything starting with MSSQL.
> --
> Thanks in advance,
> sck10
If you open a command prompt and type
net start mssqlserver
what happens?

MSSQLSERVER not showing in Services

Hello,
We just installed SQL Server 2K on a user machine. For some reason,
MSSQLSERVER and SQLSERVERAGENT is not showing in Services. We use Services
to update the logon password when we change our NT password. First, what do
we need to do to get MSSQLSERVER to show in Services and is there another
way to update the logon password?
--
Thanks in advance,
sck10Perhaps you installed it as a Named instance instead of a default instance. In that case, the
service name is MSSQL$InstanceName.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sck10" <sck10@.online.nospam> wrote in message news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl...
> Hello,
> We just installed SQL Server 2K on a user machine. For some reason,
> MSSQLSERVER and SQLSERVERAGENT is not showing in Services. We use Services
> to update the logon password when we change our NT password. First, what do
> we need to do to get MSSQLSERVER to show in Services and is there another
> way to update the logon password?
> --
> Thanks in advance,
> sck10
>|||Hi Tibor,
There isn't anything starting with MSSQL.
--
Thanks in advance,
sck10
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23uMNzfihFHA.3544@.TK2MSFTNGP15.phx.gbl...
> Perhaps you installed it as a Named instance instead of a default
instance. In that case, the
> service name is MSSQL$InstanceName.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sck10" <sck10@.online.nospam> wrote in message
news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl...
> > Hello,
> >
> > We just installed SQL Server 2K on a user machine. For some reason,
> > MSSQLSERVER and SQLSERVERAGENT is not showing in Services. We use
Services
> > to update the logon password when we change our NT password. First,
what do
> > we need to do to get MSSQLSERVER to show in Services and is there
another
> > way to update the logon password?
> >
> > --
> > Thanks in advance,
> >
> > sck10
> >
> >
>|||Perhaps you only installed the client components?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sck10" <sck10@.online.nospam> wrote in message news:OhdxPCjhFHA.1248@.TK2MSFTNGP12.phx.gbl...
> Hi Tibor,
> There isn't anything starting with MSSQL.
> --
> Thanks in advance,
> sck10
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
> message news:%23uMNzfihFHA.3544@.TK2MSFTNGP15.phx.gbl...
>> Perhaps you installed it as a Named instance instead of a default
> instance. In that case, the
>> service name is MSSQL$InstanceName.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "sck10" <sck10@.online.nospam> wrote in message
> news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl...
>> > Hello,
>> >
>> > We just installed SQL Server 2K on a user machine. For some reason,
>> > MSSQLSERVER and SQLSERVERAGENT is not showing in Services. We use
> Services
>> > to update the logon password when we change our NT password. First,
> what do
>> > we need to do to get MSSQLSERVER to show in Services and is there
> another
>> > way to update the logon password?
>> >
>> > --
>> > Thanks in advance,
>> >
>> > sck10
>> >
>> >
>|||"sck10" <sck10@.online.nospam> wrote in message
news:OhdxPCjhFHA.1248@.TK2MSFTNGP12.phx.gbl...
> Hi Tibor,
> There isn't anything starting with MSSQL.
> --
> Thanks in advance,
> sck10
If you open a command prompt and type
net start mssqlserver
what happens?

MSSQLSERVER not showing in Services

Hello,
We just installed SQL Server 2K on a user machine. For some reason,
MSSQLSERVER and SQLSERVERAGENT is not showing in Services. We use Services
to update the logon password when we change our NT password. First, what do
we need to do to get MSSQLSERVER to show in Services and is there another
way to update the logon password?
Thanks in advance,
sck10Perhaps you installed it as a Named instance instead of a default instance.
In that case, the
service name is MSSQL$InstanceName.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sck10" <sck10@.online.nospam> wrote in message news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl..
.
> Hello,
> We just installed SQL Server 2K on a user machine. For some reason,
> MSSQLSERVER and SQLSERVERAGENT is not showing in Services. We use Service
s
> to update the logon password when we change our NT password. First, what
do
> we need to do to get MSSQLSERVER to show in Services and is there another
> way to update the logon password?
> --
> Thanks in advance,
> sck10
>|||Hi Tibor,
There isn't anything starting with MSSQL.
Thanks in advance,
sck10
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23uMNzfihFHA.3544@.TK2MSFTNGP15.phx.gbl...
> Perhaps you installed it as a Named instance instead of a default
instance. In that case, the
> service name is MSSQL$InstanceName.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "sck10" <sck10@.online.nospam> wrote in message
news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl...
Services[vbcol=seagreen]
what do[vbcol=seagreen]
another[vbcol=seagreen]
>|||Perhaps you only installed the client components?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"sck10" <sck10@.online.nospam> wrote in message news:OhdxPCjhFHA.1248@.TK2MSFTNGP12.phx.gbl...

> Hi Tibor,
> There isn't anything starting with MSSQL.
> --
> Thanks in advance,
> sck10
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n
> message news:%23uMNzfihFHA.3544@.TK2MSFTNGP15.phx.gbl...
> instance. In that case, the
> news:%23c5Uv5hhFHA.720@.TK2MSFTNGP14.phx.gbl...
> Services
> what do
> another
>|||"sck10" <sck10@.online.nospam> wrote in message
news:OhdxPCjhFHA.1248@.TK2MSFTNGP12.phx.gbl...
> Hi Tibor,
> There isn't anything starting with MSSQL.
> --
> Thanks in advance,
> sck10
If you open a command prompt and type
net start mssqlserver
what happens?

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)
>> >> >> >
>> >> >> >