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 -10535 SQL Server Connection Timed Out

We receive the following error in SQL 6.5 and I would like some help in getting it fixed.
Error -10535 SQL Server Connection Timed Out. We get this when a client dials in to run a query
All help is greatly appreciatedis this being done through a linked server?|||Originally posted by Memnoch1207
is this being done through a linked server?

No the application connects to the database through a SQL ODBC connection.|||What is the default net-library used to connect?|||Originally posted by Satya
What is the default net-library used to connect?

Sorry for the delay. It is TCP/IP

Error 0x80041010 WinMgmt when launching SQL SERVER MANAGEMENT STUD

Hi:
SQL 2005 sp2 is already release. Just like to know if this error
0x80041010 have already been fixed in SP2 of SQL 2005.
In the list of bugs fixed by SP2 the error 0x80041010 is not included,
check this site http://support.microsoft.com/kb/921896
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
I was having the same problem on my x64 box running SQL 2005 SP1 in
cluster.
What happen that somehow permissions were removed from local
administrators and DBA's group. I had to login as sa and reassign the
system admin permissions to local admin and dba's group and it start
wotking fine.
BC
*** Sent via Developersdex http://www.codecomments.com ***
|||On Apr 6, 3:37 am, Bader Cheema <bader_chee...@.hotmail.com> wrote:
> I was having the same problem on my x64 box running SQL 2005 SP1 in
> cluster.
> What happen that somehow permissions were removed from local
> administrators and DBA's group. I had to login as sa and reassign the
> system admin permissions to local admin and dba's group and it start
> wotking fine.
> BC
> *** Sent via Developersdexhttp://www.codecomments.com***
Hi,
I tried your solution but can't understand what you mean.
what do you mean by local administrators? BUILTIN\Administrators? it
already has sysadmin in server roles.
and I didn't find DBA's group in my SQL configuration.
Please elaborate your solution for me.
I didn't install SQL 2005 SP2 yet.
Does it solve this problem?
Thanks in advance.