Error 14258: ... FIXED !

I changed 'lightweight pooling' to 0, as you suggested, and after restarting
the server (just to make sure...) everything was back to normal !
Thank you very much for your time and invaluable help.
PS: by checking ERRORLOG I found out that the server did some database
recovering after the restart which immediately finished successfully, in
contrast to previous times when I was continously getting the error "[393]
Waiting for SQL Server to recover databases...". I don't know if that has to
do with the 'lightweight pooling' option change.
"Sue Hoegemeier" wrote:

> If you tried stopping and then restarting just the Agent
> service and it won't start, reporting the same error then my
> guess would be that you are running SQL Server in
> lightweight pooling mode. Set it back to the default of
> thread mode.
> sp_configure 'allow updates', 1
> go
> reconfigure with override
> go
> sp_configure 'lightweight pooling', 0
> go
> reconfigure with override
> go
> -Sue
Yes it was from the lightweight pooling change. You rarely
would change that setting - and as you saw changing default
settings can sometimes have adverse affects. The issues you
saw were all symptoms of problems from having lightweight
pooling on.
-Sue
On Tue, 21 Feb 2006 01:12:28 -0800, "vsiat"
<vsiat@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I changed 'lightweight pooling' to 0, as you suggested, and after restarting
>the server (just to make sure...) everything was back to normal !
>Thank you very much for your time and invaluable help.
>PS: by checking ERRORLOG I found out that the server did some database
>recovering after the restart which immediately finished successfully, in
>contrast to previous times when I was continously getting the error "[393]
>Waiting for SQL Server to recover databases...". I don't know if that has to
>do with the 'lightweight pooling' option change.
>
>"Sue Hoegemeier" wrote:

Error "-2147168246 (8004d00a)" Failed to Enlist on Calling Object'

I checked what suggested with
http://support.microsoft.com/default.aspx?scid=kb;en-us;191168.
The pingtest results are OK.
Is there any other check to do in order to solve this problem?
Thanks,
LucaHi
What about the other suggestions in the 191168 or
http://support.microsoft.com/kb/193893/EN-US/
Which version of MDAC are you using?
Are you using Oracle?
John
"lalberti" <lalberti@.discussions.microsoft.com> wrote in message
news:35588228-F89A-449C-ABE2-0E5DD12073C4@.microsoft.com...
>I checked what suggested with
> http://support.microsoft.com/default.aspx?scid=kb;en-us;191168.
> The pingtest results are OK.
> Is there any other check to do in order to solve this problem?
> Thanks,
> Luca|||At the moment I'm out of office and I don't know exactly which MDAC version
I'm using on client & server side.
Anyway I'm not using ORACLE...my problem is with SQLServer...
Luca
"John Bell" wrote:
> Hi
> What about the other suggestions in the 191168 or
> http://support.microsoft.com/kb/193893/EN-US/
> Which version of MDAC are you using?
> Are you using Oracle?
> John
> "lalberti" <lalberti@.discussions.microsoft.com> wrote in message
> news:35588228-F89A-449C-ABE2-0E5DD12073C4@.microsoft.com...
> >I checked what suggested with
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;191168.
> > The pingtest results are OK.
> > Is there any other check to do in order to solve this problem?
> > Thanks,
> > Luca
>
>|||I get the exact same error, only after applying SP1 to the Windows 2003
Server running our SQL Server 2000 SP3 database server. Transactions from
our Windows 2000 Server SP4 application server give the same exact error. It
is basically a VB application trying to connect to the application database.
Ping tests work fine. DTC tests fail with same error.
"John Bell" wrote:
> Hi
> What about the other suggestions in the 191168 or
> http://support.microsoft.com/kb/193893/EN-US/
> Which version of MDAC are you using?
> Are you using Oracle?
> John
> "lalberti" <lalberti@.discussions.microsoft.com> wrote in message
> news:35588228-F89A-449C-ABE2-0E5DD12073C4@.microsoft.com...
> >I checked what suggested with
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;191168.
> > The pingtest results are OK.
> > Is there any other check to do in order to solve this problem?
> > Thanks,
> > Luca
>
>

Error "-2147168246 (8004d00a)" Failed to Enlist on Calling Object'

I checked what suggested with
http://support.microsoft.com/defaul...b;en-us;191168.
The pingtest results are OK.
Is there any other check to do in order to solve this problem?
Thanks,
LucaHi
What about the other suggestions in the 191168 or
http://support.microsoft.com/kb/193893/EN-US/
Which version of MDAC are you using?
Are you using Oracle?
John
"lalberti" <lalberti@.discussions.microsoft.com> wrote in message
news:35588228-F89A-449C-ABE2-0E5DD12073C4@.microsoft.com...
>I checked what suggested with
> http://support.microsoft.com/defaul...b;en-us;191168.
> The pingtest results are OK.
> Is there any other check to do in order to solve this problem?
> Thanks,
> Luca

Error "-2147168246 (8004d00a)" Failed to Enlist on Calling Object'

I checked what suggested with
http://support.microsoft.com/default...;en-us;191168.
The pingtest results are OK.
Is there any other check to do in order to solve this problem?
Thanks,
Luca
Hi
What about the other suggestions in the 191168 or
http://support.microsoft.com/kb/193893/EN-US/
Which version of MDAC are you using?
Are you using Oracle?
John
"lalberti" <lalberti@.discussions.microsoft.com> wrote in message
news:35588228-F89A-449C-ABE2-0E5DD12073C4@.microsoft.com...
>I checked what suggested with
> http://support.microsoft.com/default...;en-us;191168.
> The pingtest results are OK.
> Is there any other check to do in order to solve this problem?
> Thanks,
> Luca