"John Kane" <jt-kane@comcast.net> wrote in message
news:OUeo3$wzDHA.1500@TK2MSFTNGP12.phx.gbl...
> You're welcome, Russ,
> Hmm... several possible issues here... First of all, Exchange 2003 as well
> as install it on the same machine as SQL Server 2000 and both products use
> the "Microsoft Search" (mssearch.exe) service. Additionally, installing
both
> product on a DC can be problematic too... Exchange 2003 *might* of
upgraded
> the MSSearch service and cause problems for SQL Server or the upgrade of
the
> MSSearch by Exchange might of failed for some reason. Could you provide
the
> MSSearch.exe version info?
>
> Is this a clustered environment? If so, is this a active/passive or
> active/active (multi-instance) environment? Yes, it is possible the
startup
> sequence is incorrect. Please review the "Dependencies" of the "Microsoft
> Search" service as it should depend upon NT LM Security Support provider
and
> Remote Procedure Call (RPC) services, if yours is different, please post
> what is the difference.
>
> As for your NTBackup question, "non-simple recovery mode", indicates that
> your database has the Recovery model of either "Full" (default) or
> "Bulk-Logged". This is most likely a warning by NTBackup and a
> recommendation to use SQL Server Agent to schedule your Database backup as
> well as Transaction log backups. See SQL Server Books Online (BOL) titles
> "Database Maintenance Plan Wizard" and "Handling Multiple Job Steps".
> However, if you want, you can stop the MSSQLServer service and the
MSSearch
> service (optional) via NET STOP <service_name> and use NTBackup to backup
> your database files as "file level" back, if you must have a file level
> backup vs. a database & transaction log backup.
>
> Thanks,
> John
> PS: Yes, I recognize the list of dll's from previous post I made...
>
>
>
> "Russ" <Russ@alias.com> wrote in message
> news:uzbQ1cwzDHA.3196@TK2MSFTNGP11.phx.gbl...
> >
> > John,
> > Thank you for the reply. The service is set to run under the local
> > system account and the builtin\administrators still exists under SQL.
The
> > machine is a domain controller and previously had exchange 2003
installed.
> > When exchnage was installed the system attendant service would fail
along
> > with the microsoft search service at boot up. Just like now, once logged
> in
> > you can manually start the services and all works well. Is it possible
> that
> > the startup order of services is incorrect? If that is even possible.
> These
> > are the .dlls that I reregistered. They were pulled from a previous post
> by
> > you. Also while I have your time, I get an error when trying to do a
> > ntbackup on a database that we have installed from another company to
> > support my clients dental software. When it tries to do a back-up it
> > displays this in the back-up log:
> >
> > MSDEWriter has reported a VSS error 0x800423f4.
> > NtBackup does not support backing up SQL databases which are configured
in
> > non-simple recovery mode.
> > If the database has been backed up, it is likely corrupted. Please do
not
> > restore this database.
> > The recommended way of backing up non-simple SQL database is to use the
> > backup solution that comes with SQL Server.
> >
> > I do know how to do the SQL back-up if needed to be, I was just curious
if
> > you understood why this happens?
> >
> > in ..\MSSearch\Bin
> > ==================
> > ftsqlpar.dll
> > mssadmin.dll
> > msscntrs.dll
> > mssmmcsi.dll
> > mssmsg.dll
> > mssmulpi.dll
> > mssph.dll
> > mssrch.dll
> > msstools.dll
> > nlhtml.dll
> > objcreat.dll
> > offfilt.dll
> > propdefs.dll
> > srchadm.dll
> > srchidx.dll
> > tquery.dll
> >
> > in ..\MSSearch\Common
> > =====================
> > mssitlb.dll
> >
> >
> > in ..WINNT\System32\
> > ====================
> > athprxy.dll
> >
> > Thanks again John,
> >
> > Russ Grotewold
> >
> > "John Kane" <jt-kane@comcast.net> wrote in message
> > news:uKs4EMwzDHA.2116@TK2MSFTNGP11.phx.gbl...
> > > Russ,
> > > The timeout errors *might* be a symptom that is "hiding" the real
> > > problems... Have you or anyone else recently changed the MSSQLServer
> > startup
> > > account &.or password? IF so, checkout the following KB article 317746
> > > (Q317746) PRB: SQL Server Full-Text Search Does Not Populate Catalogs
> > > [800705b4 timeout] at
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;317746 and
> 277549
> > > (Q277549) PRB: Unable to Build Full-Text Catalog After You Modify
> > > MSSQLServer Logon Account Through [NT4.0) Control Panel [or Win2K
> > Component
> > > Services] at
> > http://support.microsoft.com/default.aspx?scid=KB;EN-US;277549
> > >
> > > Does the SQL Server login BUILTIN\Administrators exist? If so, does it
> > have
> > > master as the default database and sysadmin privileges? If not, then
> > either
> > > add this login back or use the following code:
> > >
> > > exec sp_grantlogin N'NT Authority\System'
> > > exec sp_defaultdb N'NT Authority\System', N'master'
> > > exec sp_defaultlanguage N'NT Authority\System','us_english'
> > > exec sp_addsrvrolemember N'NT Authority\System', sysadmin
> > >
> > > see also KB article: 263712 (Q263712) INF: How to Impede Windows NT
> > > Administrators from Administering a Clustered SQL Server
> > > http://support.microsoft.com/default.aspx?scid=KB;EN-US;263712
> > >
> > > What dll's did you register? Could you list them in your reply as you
> > might
> > > of missed one or two. If the above does not resolve the timeout
errors,
> > the
> > > problem *might* also exist in one or more registry keys that are
missing
> > > &/or have incorrect information. Could you post your SearchSetup.log
> > > (usually under\windows or \winnt folders) and sqlsp.log.
> > >
> > > FYI, debugging the MSSearch service is a non-trivial effort and if you
> > want
> > > to do this, then I'd recommend that you open a support case with
> Microsoft
> > > PSS SQL Server support...
> > >
> > > Regards,
> > > John
> > >
> > >
> > >
> > > "Russ" <Russ@alias.com> wrote in message