[SQLSTATE 01000] via Agent Job, but not Query Analyzer

I run a sproc through query analyzer, and all is fine, when I run the job via the SQL Agent, [SQLSTATE 01000] appears after every line in the "log" file, any ideas ?
This happens with the sp_help_revlogin procedure.
both are being run with sa.Known issue with the PRINT command in SQL Server.

[SQL Server 2000] How to programmatically read Merge Agent properties

Dear all,
I would like to read from SQL Server information that is presented in
Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
Agents (particularly the columns "Subscription" and "Action Time").
Which tables should I read? I checked the tables in msdb and master database
but couldn't find anything suitable. BOL and Google were of no help either.
Thank you in advance for your help.
Best regards,
AndrewTry a profiler trace and examine the source of the executed procs.
Hope this helps.
Dan Guzman
SQL Server MVP
"Andrew Drake" <andrewdrake@.hotmail.com> wrote in message
news:uBPvoxZAHHA.4024@.TK2MSFTNGP04.phx.gbl...
> Dear all,
> I would like to read from SQL Server information that is presented in
> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
> Agents (particularly the columns "Subscription" and "Action Time").
> Which tables should I read? I checked the tables in msdb and master
> database
> but couldn't find anything suitable. BOL and Google were of no help
> either.
> Thank you in advance for your help.
> Best regards,
> Andrew
>
>|||"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:12D028F8-1237-454D-8387-4A30B283851F@.microsoft.com...[vbcol=seagreen]
> Try a profiler trace and examine the source of the executed procs.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>
Ok, I've checked, but unfortunately that is an undocumented procedure:
sp_MSenum_replication_agents @.type = 4
(type = 4 stands for merge replication agent)
Thank you for your help.
Best regards,
Andrew|||I took cursory look at the text of that proc and the called proc and it
looks to me like the source of the data is the MSmerge_history table. It's
documented in the Books Online.
Hope this helps.
Dan Guzman
SQL Server MVP
"Andrew Drake" <andrewdrake@.hotmail.com> wrote in message
news:uizTrebAHHA.4328@.TK2MSFTNGP03.phx.gbl...
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:12D028F8-1237-454D-8387-4A30B283851F@.microsoft.com...
> Ok, I've checked, but unfortunately that is an undocumented procedure:
> sp_MSenum_replication_agents @.type = 4
> (type = 4 stands for merge replication agent)
> Thank you for your help.
> Best regards,
> Andrew
>|||"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:CF65CD9F-E7BA-4FAB-AC81-326BD56C2FB7@.microsoft.com...
>I took cursory look at the text of that proc and the called proc and it
>looks to me like the source of the data is the MSmerge_history table. It's
>documented in the Books Online.
[...][vbcol=seagreen]
> Dan Guzman
> SQL Server MVP
>
Dan,
Thank you for your help!
Best regards,
Andrew

[SQL Server 2000] How to programmatically read Merge Agent properties

Dear all,
I would like to read from SQL Server information that is presented in
Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
Agents (particularly the columns "Subscription" and "Action Time").
Which tables should I read? I checked the tables in msdb and master database
but couldn't find anything suitable. BOL and Google were of no help either.
Thank you in advance for your help.
Best regards,
AndrewTry a profiler trace and examine the source of the executed procs.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Andrew Drake" <andrewdrake@.hotmail.com> wrote in message
news:uBPvoxZAHHA.4024@.TK2MSFTNGP04.phx.gbl...
> Dear all,
> I would like to read from SQL Server information that is presented in
> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
> Agents (particularly the columns "Subscription" and "Action Time").
> Which tables should I read? I checked the tables in msdb and master
> database
> but couldn't find anything suitable. BOL and Google were of no help
> either.
> Thank you in advance for your help.
> Best regards,
> Andrew
>
>|||"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:12D028F8-1237-454D-8387-4A30B283851F@.microsoft.com...
> Try a profiler trace and examine the source of the executed procs.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
>> Dear all,
>> I would like to read from SQL Server information that is presented in
>> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \ Merge
>> Agents (particularly the columns "Subscription" and "Action Time").
>> Which tables should I read? I checked the tables in msdb and master
>> database
>> but couldn't find anything suitable. BOL and Google were of no help
>> either.
>> Thank you in advance for your help.
>> Best regards,
>> Andrew
Ok, I've checked, but unfortunately that is an undocumented procedure:
sp_MSenum_replication_agents @.type = 4
(type = 4 stands for merge replication agent)
Thank you for your help.
Best regards,
Andrew|||I took cursory look at the text of that proc and the called proc and it
looks to me like the source of the data is the MSmerge_history table. It's
documented in the Books Online.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Andrew Drake" <andrewdrake@.hotmail.com> wrote in message
news:uizTrebAHHA.4328@.TK2MSFTNGP03.phx.gbl...
> "Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
> news:12D028F8-1237-454D-8387-4A30B283851F@.microsoft.com...
>> Try a profiler trace and examine the source of the executed procs.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> Dear all,
>> I would like to read from SQL Server information that is presented in
>> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \
>> Merge
>> Agents (particularly the columns "Subscription" and "Action Time").
>> Which tables should I read? I checked the tables in msdb and master
>> database
>> but couldn't find anything suitable. BOL and Google were of no help
>> either.
>> Thank you in advance for your help.
>> Best regards,
>> Andrew
> Ok, I've checked, but unfortunately that is an undocumented procedure:
> sp_MSenum_replication_agents @.type = 4
> (type = 4 stands for merge replication agent)
> Thank you for your help.
> Best regards,
> Andrew
>|||"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:CF65CD9F-E7BA-4FAB-AC81-326BD56C2FB7@.microsoft.com...
>I took cursory look at the text of that proc and the called proc and it
>looks to me like the source of the data is the MSmerge_history table. It's
>documented in the Books Online.
[...]
> Dan Guzman
> SQL Server MVP
>> Dear all,
>> I would like to read from SQL Server information that is presented in
>> Enterprise Manager \ <server_name> \ Replication Monitor \ Agents \
>> Merge
>> Agents (particularly the columns "Subscription" and "Action Time").
>> Which tables should I read? I checked the tables in msdb and master
>> database
>> but couldn't find anything suitable. BOL and Google were of no help
>> either.
>> Ok, I've checked, but unfortunately that is an undocumented procedure:
>> sp_MSenum_replication_agents @.type = 4
>> (type = 4 stands for merge replication agent)
Dan,
Thank you for your help!
Best regards,
Andrew

[Performance Discussion] To schedule a time for mssql command, which way would be faster a

1. Use mssql server agent service to take the schedule
2. Use a .NET windows service with timers to call SqlClientConnection

above, which way would be faster and get a better performance?I don't think you'll see any performance difference.

but go with agent.|||ok, but will have a difference when busy

[Fail] Could not add ASPNET user to SQL Server.

Ok here's my setup

1. Installed msde 2000 with sp3.
2. started the SQL Server and SQL Server Agent.
3. Ran IBuySpy Store Installation, when I ran the configuration I get error on bottum.

10:51:55 PM Tuesday, September 23, 2003: [Checking system requirements]
10:51:55 PM Tuesday, September 23, 2003: [Pass] Detected a local instance of SQL Server.
10:51:55 PM Tuesday, September 23, 2003: [Pass] Determined SQL Server version (8.00.194).
10:51:55 PM Tuesday, September 23, 2003: [Pass] Detected .NET Framework.
10:51:55 PM Tuesday, September 23, 2003: [Pass] Detected Internet Information Server (IIS).
10:52:03 PM Tuesday, September 23, 2003: [Begin Sample Configuration]
10:52:05 PM Tuesday, September 23, 2003: [Pass] Created IIS virtual directory.: StoreVBVS
10:52:05 PM Tuesday, September 23, 2003: [Pass] Determined SQL Server version (8.00.194).
10:52:22 PM Tuesday, September 23, 2003: [Fail] Could not add ASPNET user to SQL Server.
SQL Server does not exist or access denied.
10:52:22 PM Tuesday, September 23, 2003: [Done]

Can someone please tell me step by step on what I need to do and where to do it to get this working, thanks !!!did you add it via users in your db? when you xpand our db in sql server xplorer, you can add users using "users"...

HTH

'[380] Unable to start JobManager thread for job' appears in SQLAgent log.

The above message appears in the SQLAgent log. The job(s) in question don't run, it can affect all or only some of the jobs under that agent. Only solution is a restart of the SQLAgent. Can find no mention of JobManager in the online books
Anyone else experienced this?| The above message appears in the SQLAgent log. The job(s) in question
don't run,
| it can affect all or only some of the jobs under that agent. Only
solution is a restart of the
| SQLAgent. Can find no mention of JobManager in the online books.
|
| Anyone else experienced this?
--
This error indicates that you are unable to allocate more threads for
SQLAgent jobs. How many jobs are concurrently running when you hit this
error? You may need to reduce this amount.
Hope this helps,
--
Eric Cárdenas
SQL Server support|||The instance of SQL has approximately 40 jobs configured. Only 3 or 4 are active at one time. The rest are adhoc or run infrequently.||||
| The instance of SQL has approximately 40 jobs configured. Only
| 3 or 4 are active at one time. The rest are adhoc or run infrequently.
--
To confirm or dismiss that this error is a thread issue, setup performance
monitor logs on threads for SQL agent and see if you have an escalation of
threads.
If all else fails, I recommend raising a case with Microsoft product
support to assist you.
Hope this helps,
--
Eric Cárdenas
SQL Server support

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
Hanky
Do you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"??" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
HankyDo you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"??" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>

[380] Unable to start JobManager thread for job ......

An error occurred on SQL Agent Error Log of my system as follows.
[380] Unable to start JobManager thread for job .....
I have two questions.
1. How can I increase the number of thread allocated to JobManager? Should I
only decrease the number of concurrent job?
2. Is the only solution to restart the SQL Agent service in this case? The
job was not executed after this error.
Thank you
HankyDo you know how many jobs are running concurrently ? It could be a thread
issue .. but thats usually another error message that clearly states that
its waiting for a thread... something like that.. It could be that your
server is busy ... You may also consider opening up a PSS case..
"Çѱ⿵" <hanky74@.daum.net> wrote in message
news:uU4JWJDgEHA.2916@.TK2MSFTNGP12.phx.gbl...
> An error occurred on SQL Agent Error Log of my system as follows.
> [380] Unable to start JobManager thread for job .....
> I have two questions.
> 1. How can I increase the number of thread allocated to JobManager? Should
I
> only decrease the number of concurrent job?
> 2. Is the only solution to restart the SQL Agent service in this case? The
> job was not executed after this error.
> Thank you
> Hanky
>

[241] Startup error: Unable to initialize error reporting system

When I try to start the SQL Server Agent I am getting this error.
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
Thsi is very frustrating and i cant put up the DB until im sure that I
can have my backups working. Anyone know the solution to this?no one?

[165]ODBC Error 0 Timeout expired[SQLSTATE HYT00]

sql server 2000 8.00.194
Microsoft Windows 2000 Service Pack 2

I looked into my sqlserver agent log and found the following

ODBC Error 0 Timeout expired[SQLSTATE HYT00]
logon to server local '( failed)' (Job manager)

I have no idea what that means but it did keep out users for a minute or more.
The threads found on this forum almost all point to reccuring situations
mine is a sporadic one time issue.
Is it Ok to conclude it is a network error as I did?

TIA
VinceVincento Harris (wumutek@.yahoo.com) writes:
> sql server 2000 8.00.194

That's an SQL Server with no service pack. I strongly encouarge you to
download and install Service Pack 3.

> I looked into my sqlserver agent log and found the following
> ODBC Error 0 Timeout expired[SQLSTATE HYT00]
> logon to server local '( failed)' (Job manager)
> I have no idea what that means but it did keep out users for a minute or
> more. The threads found on this forum almost all point to reccuring
> situations mine is a sporadic one time issue.
> Is it Ok to conclude it is a network error as I did?

This may be a correct conclusion in the end, but it is not the most likely.

The ODBC error "Timeout expired" means that a query did not start to
return rows with the timeout period, which by default is 30 seconds.
The reason for this could be that the query itself needed longer time
to execute, because of large amounts of data to search and/or poor
indexing. It could also be that the query was blocked by another query,
and that query was long-running. In fact it does not have to be a query
as such that was blocking, but a process holding locks because of
an earlier abandoned query, which was not properly handled.

All this could have been started by some abnormal event like a
network glitch. However, it is much more likely that there was
some inappropriate SQL statement somewhere.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

[097] Memory leak detected [1260 bytes]

I have received the following error my SQL Server Agent Log.

[097] Memory leak detected [1260 bytes]

When this happens jobs will fail with the following error.
[000] Unable to retrieve steps for job Backup TLog - 1stComp (Increm)

My current work around is to stop and restart the SQL Server Agent services.

Has anyone seen this before? Is it corrected in the the 2153 hotfix?

What is the service pack level on SQL & Windows?

Also the memory leak errors seems to be hardware related too, might invole the Vendor to confirm the health state of hardware.

|||It's SQL Server 2005 SP1 64Bit Enterprise Edition.
The server is a Dell poweredge 6850 with 8 Physical CPU's 64 GB of RAM
Windows server version 5.2.3790 SP1 build 3790.

I should have encluded that in my original post.