Cannot create WSS_Search database

Here are the steps I took:
Installed Windows 2003 R2
Upgraded to SP2
Used the Manage my Server wizard to install a typical first server
configuration (AD, DNS, DHCP)
Used the wizard to make it an Application Server and installed ASP .Net
Installed .Net 3.0 framework
Installed SQL Server 2005 Workgroup edition and applied SP2 using the Local
System account.
Installed Windows Sharepoint Services 3.0 in advanced mode.
There were no errors in installation and the Central Admin site came up.
I used the Manage my Server wizard to install a mail server.
I configured the incoming and outgoing mail services.
I created a new Web App and site collection.
Now everything is running except WSS Search Services. I created a user
SPSearcher as a member of Domain Users then used the SQL Server Management
Studio to add SPSearcher to the Logins with dbcreator and securityadmin
rights. I then Used the Central Administration wizard to Configure
Sharepoint Services Search Service using the SPSearcher account and Windows
authentication.
The wizard appears to run successfully and sends me back to the Services on
Server page but the service still says stopped and the WSS_Search database
was not created.
I have done everything I have read but I'm stumped.

Mike
Fri Jun 29 12:20:44 CDT 2007

This is presumably a single server installation so please say which of
the options you chose when you did this

"Installed Windows Sharepoint Services 3.0 in advanced mode."


Mike Walsh
WSS FAQ http://www.wssfaq.com
no questions by e-mail please



RogerBRB wrote:
> Here are the steps I took:
> Installed Windows 2003 R2
> Upgraded to SP2
> Used the Manage my Server wizard to install a typical first server
> configuration (AD, DNS, DHCP)
> Used the wizard to make it an Application Server and installed ASP .Net
> Installed .Net 3.0 framework
> Installed SQL Server 2005 Workgroup edition and applied SP2 using the Local
> System account.
> Installed Windows Sharepoint Services 3.0 in advanced mode.
> There were no errors in installation and the Central Admin site came up.
> I used the Manage my Server wizard to install a mail server.
> I configured the incoming and outgoing mail services.
> I created a new Web App and site collection.
> Now everything is running except WSS Search Services. I created a user
> SPSearcher as a member of Domain Users then used the SQL Server Management
> Studio to add SPSearcher to the Logins with dbcreator and securityadmin
> rights. I then Used the Central Administration wizard to Configure
> Sharepoint Services Search Service using the SPSearcher account and Windows
> authentication.
> The wizard appears to run successfully and sends me back to the Services on
> Server page but the service still says stopped and the WSS_Search database
> was not created.
> I have done everything I have read but I'm stumped.

Mike
Fri Jun 29 12:21:57 CDT 2007

The other thing is - did you allocate the search services to a content
database? (If you did, you'll know what I mean by that!)

Mike Walsh


RogerBRB wrote:
> Here are the steps I took:
> Installed Windows 2003 R2
> Upgraded to SP2
> Used the Manage my Server wizard to install a typical first server
> configuration (AD, DNS, DHCP)
> Used the wizard to make it an Application Server and installed ASP .Net
> Installed .Net 3.0 framework
> Installed SQL Server 2005 Workgroup edition and applied SP2 using the Local
> System account.
> Installed Windows Sharepoint Services 3.0 in advanced mode.
> There were no errors in installation and the Central Admin site came up.
> I used the Manage my Server wizard to install a mail server.
> I configured the incoming and outgoing mail services.
> I created a new Web App and site collection.
> Now everything is running except WSS Search Services. I created a user
> SPSearcher as a member of Domain Users then used the SQL Server Management
> Studio to add SPSearcher to the Logins with dbcreator and securityadmin
> rights. I then Used the Central Administration wizard to Configure
> Sharepoint Services Search Service using the SPSearcher account and Windows
> authentication.
> The wizard appears to run successfully and sends me back to the Services on
> Server page but the service still says stopped and the WSS_Search database
> was not created.
> I have done everything I have read but I'm stumped.

RogerBRB
Fri Jun 29 13:12:02 CDT 2007

Thanks for the reply, Mike. The solution turned out to be going to lunch.
After stepping away for awhile and returning to the screen, it dawned on me
that I wasn't entering the username in the DOMAIN\username format.

"Mike Walsh" wrote:

> The other thing is - did you allocate the search services to a content
> database? (If you did, you'll know what I mean by that!)
>
> Mike Walsh
>
>
> RogerBRB wrote:
> > Here are the steps I took:
> > Installed Windows 2003 R2
> > Upgraded to SP2
> > Used the Manage my Server wizard to install a typical first server
> > configuration (AD, DNS, DHCP)
> > Used the wizard to make it an Application Server and installed ASP .Net
> > Installed .Net 3.0 framework
> > Installed SQL Server 2005 Workgroup edition and applied SP2 using the Local
> > System account.
> > Installed Windows Sharepoint Services 3.0 in advanced mode.
> > There were no errors in installation and the Central Admin site came up.
> > I used the Manage my Server wizard to install a mail server.
> > I configured the incoming and outgoing mail services.
> > I created a new Web App and site collection.
> > Now everything is running except WSS Search Services. I created a user
> > SPSearcher as a member of Domain Users then used the SQL Server Management
> > Studio to add SPSearcher to the Logins with dbcreator and securityadmin
> > rights. I then Used the Central Administration wizard to Configure
> > Sharepoint Services Search Service using the SPSearcher account and Windows
> > authentication.
> > The wizard appears to run successfully and sends me back to the Services on
> > Server page but the service still says stopped and the WSS_Search database
> > was not created.
> > I have done everything I have read but I'm stumped.
>

Mike
Fri Jun 29 13:32:14 CDT 2007

Just to make sure that you are using the database system you think you
are using, did you select (after advanced) Single server install or
Front-end ?

Mike Walsh


RogerBRB wrote:
> Thanks for the reply, Mike. The solution turned out to be going to lunch.
> After stepping away for awhile and returning to the screen, it dawned on me
> that I wasn't entering the username in the DOMAIN\username format.
>
> "Mike Walsh" wrote:
>
>> The other thing is - did you allocate the search services to a content
>> database? (If you did, you'll know what I mean by that!)
>>
>> Mike Walsh
>>
>>
>> RogerBRB wrote:
>>> Here are the steps I took:
>>> Installed Windows 2003 R2
>>> Upgraded to SP2
>>> Used the Manage my Server wizard to install a typical first server
>>> configuration (AD, DNS, DHCP)
>>> Used the wizard to make it an Application Server and installed ASP .Net
>>> Installed .Net 3.0 framework
>>> Installed SQL Server 2005 Workgroup edition and applied SP2 using the Local
>>> System account.
>>> Installed Windows Sharepoint Services 3.0 in advanced mode.
>>> There were no errors in installation and the Central Admin site came up.
>>> I used the Manage my Server wizard to install a mail server.
>>> I configured the incoming and outgoing mail services.
>>> I created a new Web App and site collection.
>>> Now everything is running except WSS Search Services. I created a user
>>> SPSearcher as a member of Domain Users then used the SQL Server Management
>>> Studio to add SPSearcher to the Logins with dbcreator and securityadmin
>>> rights. I then Used the Central Administration wizard to Configure
>>> Sharepoint Services Search Service using the SPSearcher account and Windows
>>> authentication.
>>> The wizard appears to run successfully and sends me back to the Services on
>>> Server page but the service still says stopped and the WSS_Search database
>>> was not created.
>>> I have done everything I have read but I'm stumped.

RogerBRB
Fri Jun 29 16:20:02 CDT 2007

I selected Front-end and yes I did connect to Sql Server 2005 workgroup and
it created the search database.


"Mike Walsh" wrote:

> Just to make sure that you are using the database system you think you
> are using, did you select (after advanced) Single server install or
> Front-end ?
>
> Mike Walsh
>
>
> RogerBRB wrote:
> > Thanks for the reply, Mike. The solution turned out to be going to lunch.
> > After stepping away for awhile and returning to the screen, it dawned on me
> > that I wasn't entering the username in the DOMAIN\username format.
> >
> > "Mike Walsh" wrote:
> >
> >> The other thing is - did you allocate the search services to a content
> >> database? (If you did, you'll know what I mean by that!)
> >>
> >> Mike Walsh
> >>
> >>
> >> RogerBRB wrote:
> >>> Here are the steps I took:
> >>> Installed Windows 2003 R2
> >>> Upgraded to SP2
> >>> Used the Manage my Server wizard to install a typical first server
> >>> configuration (AD, DNS, DHCP)
> >>> Used the wizard to make it an Application Server and installed ASP .Net
> >>> Installed .Net 3.0 framework
> >>> Installed SQL Server 2005 Workgroup edition and applied SP2 using the Local
> >>> System account.
> >>> Installed Windows Sharepoint Services 3.0 in advanced mode.
> >>> There were no errors in installation and the Central Admin site came up.
> >>> I used the Manage my Server wizard to install a mail server.
> >>> I configured the incoming and outgoing mail services.
> >>> I created a new Web App and site collection.
> >>> Now everything is running except WSS Search Services. I created a user
> >>> SPSearcher as a member of Domain Users then used the SQL Server Management
> >>> Studio to add SPSearcher to the Logins with dbcreator and securityadmin
> >>> rights. I then Used the Central Administration wizard to Configure
> >>> Sharepoint Services Search Service using the SPSearcher account and Windows
> >>> authentication.
> >>> The wizard appears to run successfully and sends me back to the Services on
> >>> Server page but the service still says stopped and the WSS_Search database
> >>> was not created.
> >>> I have done everything I have read but I'm stumped.
>

Techie
Tue Jul 24 19:18:59 CDT 2007

i'm having the same problem, here's the run down

1. have a www server w2k3 standard with IIS and WSS 3.0
2. second server W2k3 standard SQL 2000

3. have a domain account used for everything that has to do with WSS 3.0

4. when trying to start WSS_search i put in domain\user
5. try to connect to DB WSS_Search_server name

there are no errors but the service will not start.

RogerBRB wrote:
> I selected Front-end and yes I did connect to Sql Server 2005 workgroup and
> it created the search database.
>
>
> "Mike Walsh" wrote:
>
>> Just to make sure that you are using the database system you think you
>> are using, did you select (after advanced) Single server install or
>> Front-end ?
>>
>> Mike Walsh
>>
>>
>> RogerBRB wrote:
>>> Thanks for the reply, Mike. The solution turned out to be going to lunch.
>>> After stepping away for awhile and returning to the screen, it dawned on me
>>> that I wasn't entering the username in the DOMAIN\username format.
>>>
>>> "Mike Walsh" wrote:
>>>
>>>> The other thing is - did you allocate the search services to a content
>>>> database? (If you did, you'll know what I mean by that!)
>>>>
>>>> Mike Walsh
>>>>
>>>>
>>>> RogerBRB wrote:
>>>>> Here are the steps I took:
>>>>> Installed Windows 2003 R2
>>>>> Upgraded to SP2
>>>>> Used the Manage my Server wizard to install a typical first server
>>>>> configuration (AD, DNS, DHCP)
>>>>> Used the wizard to make it an Application Server and installed ASP .Net
>>>>> Installed .Net 3.0 framework
>>>>> Installed SQL Server 2005 Workgroup edition and applied SP2 using the Local
>>>>> System account.
>>>>> Installed Windows Sharepoint Services 3.0 in advanced mode.
>>>>> There were no errors in installation and the Central Admin site came up.
>>>>> I used the Manage my Server wizard to install a mail server.
>>>>> I configured the incoming and outgoing mail services.
>>>>> I created a new Web App and site collection.
>>>>> Now everything is running except WSS Search Services. I created a user
>>>>> SPSearcher as a member of Domain Users then used the SQL Server Management
>>>>> Studio to add SPSearcher to the Logins with dbcreator and securityadmin
>>>>> rights. I then Used the Central Administration wizard to Configure
>>>>> Sharepoint Services Search Service using the SPSearcher account and Windows
>>>>> authentication.
>>>>> The wizard appears to run successfully and sends me back to the Services on
>>>>> Server page but the service still says stopped and the WSS_Search database
>>>>> was not created.
>>>>> I have done everything I have read but I'm stumped.