[LOG] Unable to read local eventlog (reason: The parameter is incorrect) - FLOOD

[LOG] Unable to read local eventlog (reason: The parameter is incorrect)

I just had two seperate SQL Server 2005 Enterprise Edition machines suddently throw thousands of these errors within the last 24 hours. In both cases the the SQL agent and application event logs are just being flooded with a new entry every couple of seconds.

While the errors are being logged the Agent continues to run jobs (e.g. scheduled backups, etc.) without error.

A restart of the agent stops the errors and everything seems to be back to normal.

There is no commonality between the two machines, they are on different networks, domains, etc.

Both machines have been up >30 days and have not previously logged this error.

Anybody else seen this?

Thanks,

Joe

See this post Joe:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124086&SiteID=1

HTH,

[DBNETLIB][ConnectionClient(SEDC.ClientHandshake()).] SSL Server error

I am unable to connect to SQL Server, instead I get

Sql Server ErrorL 18

Handshake error as above

A connection was successfully established with the server, but then an error occurred during the pre-login handshake (provider: SSL Provider, error: 0- The token supplied to the function is invalid) (Microsoft SQL Server)

Any ideas?

Puzzling - Received Same error....Any assistance would be helpful.|||

Can you provide more detail info:

1) Were you connecting to SQL Server 2005 or SQL 2K?

2) Is it remote connection or local?

3) What OS of client side and what OS on server side?

4) Did you specify any certificate on your server side?

5) Which account did your sql service running under?

Thanks!

Ming.

|||

Mostlikely, you turn on the SSL encryption on client side by using cliconfg or in the connection string. However, the certificate used by server is not trusted by your client.

If your server is 2005, http://blogs.msdn.com/sql_protocols/archive/2005/10/04/476705.aspx

If your server is 2000,

http://support.microsoft.com/kb/276553/

[DBNETLIB][ConnectionClient(SEDC.ClientHandshake()).] SSL Server error

I am unable to connect to SQL Server, instead I get

Sql Server ErrorL 18

Handshake error as above

A connection was successfully established with the server, but then an error occurred during the pre-login handshake (provider: SSL Provider, error: 0- The token supplied to the function is invalid) (Microsoft SQL Server)

Any ideas?

Puzzling - Received Same error....Any assistance would be helpful.|||

Can you provide more detail info:

1) Were you connecting to SQL Server 2005 or SQL 2K?

2) Is it remote connection or local?

3) What OS of client side and what OS on server side?

4) Did you specify any certificate on your server side?

5) Which account did your sql service running under?

Thanks!

Ming.

|||

Mostlikely, you turn on the SSL encryption on client side by using cliconfg or in the connection string. However, the certificate used by server is not trusted by your client.

If your server is 2005, http://blogs.msdn.com/sql_protocols/archive/2005/10/04/476705.aspx

If your server is 2000,

http://support.microsoft.com/kb/276553/

[DBNETLIB][ConnectionClient(SEDC.ClientHandshake()).] SSL Server error

I am unable to connect to SQL Server, instead I get

Sql Server ErrorL 18

Handshake error as above

A connection was successfully established with the server, but then an error occurred during the pre-login handshake (provider: SSL Provider, error: 0- The token supplied to the function is invalid) (Microsoft SQL Server)

Any ideas?

Puzzling - Received Same error....Any assistance would be helpful.|||

Can you provide more detail info:

1) Were you connecting to SQL Server 2005 or SQL 2K?

2) Is it remote connection or local?

3) What OS of client side and what OS on server side?

4) Did you specify any certificate on your server side?

5) Which account did your sql service running under?

Thanks!

Ming.

|||

Mostlikely, you turn on the SSL encryption on client side by using cliconfg or in the connection string. However, the certificate used by server is not trusted by your client.

If your server is 2005, http://blogs.msdn.com/sql_protocols/archive/2005/10/04/476705.aspx

If your server is 2000,

http://support.microsoft.com/kb/276553/

'[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?