Microsoft Search Service Fails on Boot!

I have been having a problem with the microsoft sesarch service failing on
boot up. All that I get from the event logs is: Event ID: 7009-"Timeout
(30000 milliseconds) waiting for the Microsoft Search Service to connect."
and Event ID: 7000-"The Microsoft Search service failed to start due to the
following error: The service did not respond to the start or control request
in a timely fashion.". The box has SQL 2000 w/SP3a on it and is running
Small business server 2003. I have reregistered several of the .dll files
associated with the search service. If I manually start after being logged
in it starts fine with no errors. Is there any type of detailed debugging
that can be run along side this? I have already tried posting in the SBS
Newsgroup with no success. Any help would be greatly appreciated.
Thanks,
Russ GrotewoldRuss,
See my reply in the fulltext newsgroup.
Thanks,
John
"Russ" <Russ@.alias.com> wrote in message
news:#$SbbTuzDHA.2456@.TK2MSFTNGP10.phx.gbl...
> I have been having a problem with the microsoft sesarch service failing on
> boot up. All that I get from the event logs is: Event ID: 7009-"Timeout
> (30000 milliseconds) waiting for the Microsoft Search Service to connect."
> and Event ID: 7000-"The Microsoft Search service failed to start due to
the
> following error: The service did not respond to the start or control
request
> in a timely fashion.". The box has SQL 2000 w/SP3a on it and is running
> Small business server 2003. I have reregistered several of the .dll files
> associated with the search service. If I manually start after being logged
> in it starts fine with no errors. Is there any type of detailed debugging
> that can be run along side this? I have already tried posting in the SBS
> Newsgroup with no success. Any help would be greatly appreciated.
> Thanks,
> Russ Grotewold
>

Microsoft OLE DB Provider for SQL Server error '80040e31'

Hi
Till now the website was ok. But now I am getting
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
My connection in Config.inc is
<%Set MyConn=Server.CreateObject("ADODB.Connection")
MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
ID=eventsadmin;Password=adminevents;Init
ial Catalog=Events1;Data
Source=SERVER-NAME"
%>Try to connect with the ip address instead of the server name.
"Nachi" wrote:

> Hi
> Till now the website was ok. But now I am getting
> Microsoft OLE DB Provider for SQL Server error '80040e31'
> Timeout expired
>
> My connection in Config.inc is
> <%Set MyConn=Server.CreateObject("ADODB.Connection")
> MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
> ID=eventsadmin;Password=adminevents;Init
ial Catalog=Events1;Data
> Source=SERVER-NAME"
> %>
>|||Hi Nachi,
Is the problemi resloved.... if not i have few queires for this...
how are you connecting to the server,
1. Using OLEDB or using...
2. was any time out was set at the cleint side of ODBC.
Shiva Naidu Jai
"steve wojciechowski" wrote:
[vbcol=seagreen]
> Try to connect with the ip address instead of the server name.
> "Nachi" wrote:
>sql

Microsoft OLE DB Provider for SQL Server error '80040e31'

Hi
Till now the website was ok. But now I am getting
Microsoft OLE DB Provider for SQL Server error '80040e31'
Timeout expired
My connection in Config.inc is
<%Set MyConn=Server.CreateObject("ADODB.Connection")
MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
ID=eventsadmin;Password=adminevents;Initial Catalog=Events1;Data
Source=SERVER-NAME"
%>Try to connect with the ip address instead of the server name.
"Nachi" wrote:
> Hi
> Till now the website was ok. But now I am getting
> Microsoft OLE DB Provider for SQL Server error '80040e31'
> Timeout expired
>
> My connection in Config.inc is
> <%Set MyConn=Server.CreateObject("ADODB.Connection")
> MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
> ID=eventsadmin;Password=adminevents;Initial Catalog=Events1;Data
> Source=SERVER-NAME"
> %>
>|||Hi Nachi,
Is the problemi resloved.... if not i have few queires for this...
how are you connecting to the server,
1. Using OLEDB or using...
2. was any time out was set at the cleint side of ODBC.
Shiva Naidu Jai
"steve wojciechowski" wrote:
> Try to connect with the ip address instead of the server name.
> "Nachi" wrote:
> > Hi
> >
> > Till now the website was ok. But now I am getting
> > Microsoft OLE DB Provider for SQL Server error '80040e31'
> > Timeout expired
> >
> >
> >
> > My connection in Config.inc is
> > <%Set MyConn=Server.CreateObject("ADODB.Connection")
> > MyConn.Open "PROVIDER=SQLOLEDB.1;Persist Security Info=False;User
> > ID=eventsadmin;Password=adminevents;Initial Catalog=Events1;Data
> > Source=SERVER-NAME"
> > %>
> >
> >

Message sent retry timeout

Hi

here is from BOL

>When a conversation is marked delayed, Service Broker performs the matching process again after a timeout period. Notice that failure to find a matching route is not considered an error.

for example it could happen when there is no route for a service.
the question is - what is this timeout. Is it configurable? on a system wide
basis ?

It will be great if this process is described in more details.

Best regards,

Leonid.The timeout period is not configurable. If you do want to force reclassification, however, you could trigger that by running ALTER ROUTE on some pre-existing route that basically does not change any attributes. The ALTER ROUTE would then have no effect, but it would trigger metadata change which causes Service Broker to retry classifying delayed conversations.|||

But what is the timeout is ? What is the overhead when SB trying to connect to a sevice with no route. As I understood SB will try to send a message every minute. Could you please clarify.

Leonid.

|||4 seconds that exponentially backs out to about a minute. But don't quote me on this.