"Bryce Ingalls" <bryce@nospam.com> wrote in message
news:OQWW4NphHHA.5048@TK2MSFTNGP03.phx.gbl...
> Hello--
>
> Recently installed SQL Server 2005 Std. Ed. on Windows Server 2003 SP1.
> Server is AD domain controller. Tried installing SP2 for SQL 2005--no
> difference. Am seeing this error over and over:
>
> The connection has been dropped because the principal that opened it
> subsequently assumed a new security context, and then tried to reset the
> connection under its impersonated security context. This scenario is not
> supported. See "Impersonation Overview" in Books Online.
>
> Error: 18059, Severity: 20, State: 1.
>
>
>
> I was not able to find much online re: the issue. SQL newbie would
> appreciate any suggestions.
>
>
>
> Bryce
>
>

"Russell Fields" <russellfields@nomail.com> wrote in message
news:ezs9qiqhHHA.4296@TK2MSFTNGP05.phx.gbl...
> Bryce,
>
> Is your application using an Application Role? If so, it might be a
> problem with connection pooling, as described in this thread.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=473777&SiteID=1
>
> The original poster solved his problem by turning off connection pooling
> with an application role.
>
> RLF
> "Bryce Ingalls" <bryce@nospam.com> wrote in message
> news:OQWW4NphHHA.5048@TK2MSFTNGP03.phx.gbl...
>> Hello--
>>
>> Recently installed SQL Server 2005 Std. Ed. on Windows Server 2003 SP1.
>> Server is AD domain controller. Tried installing SP2 for SQL 2005--no
>> difference. Am seeing this error over and over:
>>
>> The connection has been dropped because the principal that opened it
>> subsequently assumed a new security context, and then tried to reset the
>> connection under its impersonated security context. This scenario is not
>> supported. See "Impersonation Overview" in Books Online.
>>
>> Error: 18059, Severity: 20, State: 1.
>>
>>
>>
>> I was not able to find much online re: the issue. SQL newbie would
>> appreciate any suggestions.
>>
>>
>>
>> Bryce
>>
>>
>
>