|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
 Answer |
|
| |
Hello Engelbert,
It is different - stopping it via SP Admin removes the search index as well
as stopping the service...
Ben
> It might be different I suppose.
>
> In one case you've **maybe** just stopped Search from running in WSS
> and in the other you might have stopped Search from running on that
> machine - i.e. (if the theory is right) WSS still thinks it is
> "running"
>
> I hope you understood that "logic". It's far-fetched I know but I've
> seen other things where where you do something is important. For
> instance using the uninstall routine provided by a third-party company
> for their software often works better than Control Panel / Add and
> Remove programs.
>
> I don't suppose you feel like doing the whole thing again ? No, I
> didn't think so. Well wait a few days anyway to see if you get some
> facts here rather than speculation..
>
> Engelbert
>
> "Ariel" <Ariel@discussions.microsoft.com> wrote in message
> news:FAB59300-FD5B-438B-AB92-DEEAC38D866B@microsoft.com...
>
>> I did. But, in hind sight, I'm wondering if I did it properly. I
>> stopped the service via manage | services | Windows Sharepoint
>> Services Search > stop. As opposed to Shareppoint 3.0 Central
>> Administration | Operations | Services on server | Windows Sharepoint
>> Services Search > stop. I can't imagine they are different, but I
>> thought it might be worth clarifying that.
>>
>> "Engelbert" wrote:
>>
>>> As you are having problem with the search part, please understand
>>> the
>>> reason
>>> for asking the following question.
>>> Did you stop the Search service before removing WWF 2.2; adding .NET
>>> Framework 3.0 and installing WSS Beta2 TR?
>>>
>>> Just so we can exclude that ...
>>>
>>> Engelbert
>>>
>>> "Ariel" <Ariel@discussions.microsoft.com> wrote in message
>>> news:432EF11D-D171-4085-9E7D-44B4603CE746@microsoft.com...
>>>
>>>> Hello,
>>>>
>>>> I installed the TR and am now having some problems.
>>>>
>>>> I followed the instructions at this URL:
>>>>
>>>> http://technet2.microsoft.com/Office/en-us/library/b3e52231-16bf-4a
>>>> 46-a7e8-cb31b814627a1033.mspx?mfr=true
>>>>
>>>> This section applied to me:
>>>> How to upgrade an existing Beta 2 installation to Beta 2 Technical
>>>> Refresh
>>>> When I try to start the Windows Sharepoint Services Search in
>>>> Services
>>>> on
>>>> Server, I get this error:
>>>> WSS_Search_xxxx on np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query
>>>> contains user-defined schema. Databases must be empty before they
>>>> can be used. Delete all of the tables, stored procedures and other
>>>> objects or use a different database.
>>>>
>>>> I'm using wmsde. How do I do the recomended actions, or is there
>>>> something
>>>> else I can do?
|
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
 Reply |
| |
 |
|
 Top |
|
|
|
|
|
|
|
|
|
| |
Thanks Ben. Do I have any recourse?
"Ben Robb [cScape]" wrote:
> Hello Engelbert,
>
> It is different - stopping it via SP Admin removes the search index as well
> as stopping the service...
>
> Ben
>
> > It might be different I suppose.
> >
> > In one case you've **maybe** just stopped Search from running in WSS
> > and in the other you might have stopped Search from running on that
> > machine - i.e. (if the theory is right) WSS still thinks it is
> > "running"
> >
> > I hope you understood that "logic". It's far-fetched I know but I've
> > seen other things where where you do something is important. For
> > instance using the uninstall routine provided by a third-party company
> > for their software often works better than Control Panel / Add and
> > Remove programs.
> >
> > I don't suppose you feel like doing the whole thing again ? No, I
> > didn't think so. Well wait a few days anyway to see if you get some
> > facts here rather than speculation..
> >
> > Engelbert
> >
> > "Ariel" <Ariel@discussions.microsoft.com> wrote in message
> > news:FAB59300-FD5B-438B-AB92-DEEAC38D866B@microsoft.com...
> >
> >> I did. But, in hind sight, I'm wondering if I did it properly. I
> >> stopped the service via manage | services | Windows Sharepoint
> >> Services Search > stop. As opposed to Shareppoint 3.0 Central
> >> Administration | Operations | Services on server | Windows Sharepoint
> >> Services Search > stop. I can't imagine they are different, but I
> >> thought it might be worth clarifying that.
> >>
> >> "Engelbert" wrote:
> >>
> >>> As you are having problem with the search part, please understand
> >>> the
> >>> reason
> >>> for asking the following question.
> >>> Did you stop the Search service before removing WWF 2.2; adding .NET
> >>> Framework 3.0 and installing WSS Beta2 TR?
> >>>
> >>> Just so we can exclude that ...
> >>>
> >>> Engelbert
> >>>
> >>> "Ariel" <Ariel@discussions.microsoft.com> wrote in message
> >>> news:432EF11D-D171-4085-9E7D-44B4603CE746@microsoft.com...
> >>>
> >>>> Hello,
> >>>>
> >>>> I installed the TR and am now having some problems.
> >>>>
> >>>> I followed the instructions at this URL:
> >>>>
> >>>> http://technet2.microsoft.com/Office/en-us/library/b3e52231-16bf-4a
> >>>> 46-a7e8-cb31b814627a1033.mspx?mfr=true
> >>>>
> >>>> This section applied to me:
> >>>> How to upgrade an existing Beta 2 installation to Beta 2 Technical
> >>>> Refresh
> >>>> When I try to start the Windows Sharepoint Services Search in
> >>>> Services
> >>>> on
> >>>> Server, I get this error:
> >>>> WSS_Search_xxxx on np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query
> >>>> contains user-defined schema. Databases must be empty before they
> >>>> can be used. Delete all of the tables, stored procedures and other
> >>>> objects or use a different database.
> >>>>
> >>>> I'm using wmsde. How do I do the recomended actions, or is there
> >>>> something
> >>>> else I can do?
>
>
> |
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
|
|
|
|
| |
Thanks Ben,
and with the search index still there when it ought not to be ....
Engelbert
"Ben Robb [cScape]" <ben@microsoftdiscussions.com> wrote in message
news:4407d23b74f538c8a701f35bb54c@msnews.microsoft.com...
> Hello Engelbert,
>
> It is different - stopping it via SP Admin removes the search index as
> well as stopping the service...
>
> Ben
>
>> It might be different I suppose.
>>
>> In one case you've **maybe** just stopped Search from running in WSS
>> and in the other you might have stopped Search from running on that
>> machine - i.e. (if the theory is right) WSS still thinks it is
>> "running"
>>
>> I hope you understood that "logic". It's far-fetched I know but I've
>> seen other things where where you do something is important. For
>> instance using the uninstall routine provided by a third-party company
>> for their software often works better than Control Panel / Add and
>> Remove programs.
>>
>> I don't suppose you feel like doing the whole thing again ? No, I
>> didn't think so. Well wait a few days anyway to see if you get some
>> facts here rather than speculation..
>>
>> Engelbert
>>
>> "Ariel" <Ariel@discussions.microsoft.com> wrote in message
>> news:FAB59300-FD5B-438B-AB92-DEEAC38D866B@microsoft.com...
>>
>>> I did. But, in hind sight, I'm wondering if I did it properly. I
>>> stopped the service via manage | services | Windows Sharepoint
>>> Services Search > stop. As opposed to Shareppoint 3.0 Central
>>> Administration | Operations | Services on server | Windows Sharepoint
>>> Services Search > stop. I can't imagine they are different, but I
>>> thought it might be worth clarifying that.
>>>
>>> "Engelbert" wrote:
>>>
>>>> As you are having problem with the search part, please understand
>>>> the
>>>> reason
>>>> for asking the following question.
>>>> Did you stop the Search service before removing WWF 2.2; adding .NET
>>>> Framework 3.0 and installing WSS Beta2 TR?
>>>>
>>>> Just so we can exclude that ...
>>>>
>>>> Engelbert
>>>>
>>>> "Ariel" <Ariel@discussions.microsoft.com> wrote in message
>>>> news:432EF11D-D171-4085-9E7D-44B4603CE746@microsoft.com...
>>>>
>>>>> Hello,
>>>>>
>>>>> I installed the TR and am now having some problems.
>>>>>
>>>>> I followed the instructions at this URL:
>>>>>
>>>>> http://technet2.microsoft.com/Office/en-us/library/b3e52231-16bf-4a
>>>>> 46-a7e8-cb31b814627a1033.mspx?mfr=true
>>>>>
>>>>> This section applied to me:
>>>>> How to upgrade an existing Beta 2 installation to Beta 2 Technical
>>>>> Refresh
>>>>> When I try to start the Windows Sharepoint Services Search in
>>>>> Services
>>>>> on
>>>>> Server, I get this error:
>>>>> WSS_Search_xxxx on np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query
>>>>> contains user-defined schema. Databases must be empty before they
>>>>> can be used. Delete all of the tables, stored procedures and other
>>>>> objects or use a different database.
>>>>>
>>>>> I'm using wmsde. How do I do the recomended actions, or is there
>>>>> something
>>>>> else I can do?
>
>
|
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
|
|
|
|
| |
I think I'm all set. I ran step 13 again in the section I previously refered
to and all is good. Perhaps I had a syntax error before....this is what I
ran:
13.
Start the Windows SharePoint Services Search service from the Services on
Server page or by using stsadm -o spsearch -action start -databaseserver <DB
server\instance> -databasename <new name>
Thanks for all who commented. I really appreciate it!
"Engelbert" wrote:
> Thanks Ben,
>
> and with the search index still there when it ought not to be ....
>
> Engelbert
>
> "Ben Robb [cScape]" <ben@microsoftdiscussions.com> wrote in message
> news:4407d23b74f538c8a701f35bb54c@msnews.microsoft.com...
> > Hello Engelbert,
> >
> > It is different - stopping it via SP Admin removes the search index as
> > well as stopping the service...
> >
> > Ben
> >
> >> It might be different I suppose.
> >>
> >> In one case you've **maybe** just stopped Search from running in WSS
> >> and in the other you might have stopped Search from running on that
> >> machine - i.e. (if the theory is right) WSS still thinks it is
> >> "running"
> >>
> >> I hope you understood that "logic". It's far-fetched I know but I've
> >> seen other things where where you do something is important. For
> >> instance using the uninstall routine provided by a third-party company
> >> for their software often works better than Control Panel / Add and
> >> Remove programs.
> >>
> >> I don't suppose you feel like doing the whole thing again ? No, I
> >> didn't think so. Well wait a few days anyway to see if you get some
> >> facts here rather than speculation..
> >>
> >> Engelbert
> >>
> >> "Ariel" <Ariel@discussions.microsoft.com> wrote in message
> >> news:FAB59300-FD5B-438B-AB92-DEEAC38D866B@microsoft.com...
> >>
> >>> I did. But, in hind sight, I'm wondering if I did it properly. I
> >>> stopped the service via manage | services | Windows Sharepoint
> >>> Services Search > stop. As opposed to Shareppoint 3.0 Central
> >>> Administration | Operations | Services on server | Windows Sharepoint
> >>> Services Search > stop. I can't imagine they are different, but I
> >>> thought it might be worth clarifying that.
> >>>
> >>> "Engelbert" wrote:
> >>>
> >>>> As you are having problem with the search part, please understand
> >>>> the
> >>>> reason
> >>>> for asking the following question.
> >>>> Did you stop the Search service before removing WWF 2.2; adding .NET
> >>>> Framework 3.0 and installing WSS Beta2 TR?
> >>>>
> >>>> Just so we can exclude that ...
> >>>>
> >>>> Engelbert
> >>>>
> >>>> "Ariel" <Ariel@discussions.microsoft.com> wrote in message
> >>>> news:432EF11D-D171-4085-9E7D-44B4603CE746@microsoft.com...
> >>>>
> >>>>> Hello,
> >>>>>
> >>>>> I installed the TR and am now having some problems.
> >>>>>
> >>>>> I followed the instructions at this URL:
> >>>>>
> >>>>> http://technet2.microsoft.com/Office/en-us/library/b3e52231-16bf-4a
> >>>>> 46-a7e8-cb31b814627a1033.mspx?mfr=true
> >>>>>
> >>>>> This section applied to me:
> >>>>> How to upgrade an existing Beta 2 installation to Beta 2 Technical
> >>>>> Refresh
> >>>>> When I try to start the Windows Sharepoint Services Search in
> >>>>> Services
> >>>>> on
> >>>>> Server, I get this error:
> >>>>> WSS_Search_xxxx on np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query
> >>>>> contains user-defined schema. Databases must be empty before they
> >>>>> can be used. Delete all of the tables, stored procedures and other
> >>>>> objects or use a different database.
> >>>>>
> >>>>> I'm using wmsde. How do I do the recomended actions, or is there
> >>>>> something
> >>>>> else I can do?
> >
> >
>
>
> |
| |
|
| |
Was this post helpful to you? |
|
|
|
|
|
|
|
Reply |
| |
|
|
Top |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Question
Notify me of replies
