Severity 20 error messages in Error log

29 Nov 2007 11:43 AM

vijay

Hi
We have been recieving the below given message before enabling AWE
on the sql server

2007-11-07 15:39:29.44 Logon Error: 17806, Severity: 20, State: 2.

2007-11-07 15:39:29.44 Logon SSPI handshake failed with error code
0x8009030c while establishing a connection with integrated security;
the connection has been closed. [CLIENT: 100.200.100.100]

2007-11-07 15:39:29.44 Logon Error: 18452, Severity: 14, State: 1.

The above mentioned error messages didn't appear after implementing
the below steps and recycling the SQL services.

Enabled AWE.
Changed max server memory to 6.5 GB.
Added user group to 'Lock pages in memory' option in Security Policy
setting.
Changed size of tempdb to 5 GB.

The new message '2007-11-24 11:58:08.59 spid104 Error: 7886,
Severity: 20, State: 2' has been appearing in log scan at the same
frequency as that of old messages.

Anyone has faced similar kind of issue.

Thanks
VS

29 Nov 2007 11:59 AM

Uri Dimant

See if this helps you
http://www.webservertalk.com/archive137-2006-2-1407167.html

Show quote

"vijay" <vjsek***@gmail.com> wrote in message
news:38b43e24-6dea-4afd-bc0f-089d982a581d@d61g2000hsa.googlegroups.com...
> Hi
> We have been recieving the below given message before enabling AWE
> on the sql server
>
> 2007-11-07 15:39:29.44 Logon Error: 17806, Severity: 20, State: 2.
>
> 2007-11-07 15:39:29.44 Logon SSPI handshake failed with error code
> 0x8009030c while establishing a connection with integrated security;
> the connection has been closed. [CLIENT: 100.200.100.100]
>
> 2007-11-07 15:39:29.44 Logon Error: 18452, Severity: 14, State: 1.
>
> The above mentioned error messages didn't appear after implementing
> the below steps and recycling the SQL services.
>
> Enabled AWE.
> Changed max server memory to 6.5 GB.
> Added user group to 'Lock pages in memory' option in Security Policy
> setting.
> Changed size of tempdb to 5 GB.
>
> The new message '2007-11-24 11:58:08.59 spid104 Error: 7886,
> Severity: 20, State: 2' has been appearing in log scan at the same
> frequency as that of old messages.
>
> Anyone has faced similar kind of issue.
>
> Thanks
> VS

29 Nov 2007 1:15 PM

vijay

Show quote

On Nov 29, 4:59 pm, "Uri Dimant" <u***@iscar.co.il> wrote:
> See if this helps youhttp://www.webservertalk.com/archive137-2006-2-1407167.html
>
> "vijay" <vjsek***@gmail.com> wrote in message
>
> news:38b43e24-6dea-4afd-bc0f-089d982a581d@d61g2000hsa.googlegroups.com...
>
> > Hi
> > We have been recieving the below given message before enabling AWE
> > on the sql server
>
> > 2007-11-07 15:39:29.44 Logon Error: 17806, Severity: 20, State: 2.
>
> > 2007-11-07 15:39:29.44 Logon SSPI handshake failed with error code
> > 0x8009030c while establishing a connection with integrated security;
> > the connection has been closed. [CLIENT: 100.200.100.100]
>
> > 2007-11-07 15:39:29.44 Logon Error: 18452, Severity: 14, State: 1.
>
> > The above mentioned error messages didn't appear after implementing
> > the below steps and recycling the SQL services.
>
> > Enabled AWE.
> > Changed max server memory to 6.5 GB.
> > Added user group to 'Lock pages in memory' option in Security Policy
> > setting.
> > Changed size of tempdb to 5 GB.
>
> > The new message '2007-11-24 11:58:08.59 spid104 Error: 7886,
> > Severity: 20, State: 2' has been appearing in log scan at the same
> > frequency as that of old messages.
>
> > Anyone has faced similar kind of issue.
>
> > Thanks
> > VS

we get the below message along with the error message

2007-11-24 11:58:08.59 spid104 Error: 7886,> > Severity: 20, State:
2'

A read operation on a large object failed while sending data to the
client. A common cause for this is if the application is running in
READ UNCOMMITTED isolation level. This connection will be terminated.

Thanks
VS