Prev: WSS 3: Multiple top-level web sites
Next: Cannot complete this action error on top level sites?
From: kert on 27 Feb 2007 17:12
hello,

Googled this six ways to sunday and still coming up empty handed. I
think my search service config is seriously b0rked on this server,
looks like a clean reinstall is in order, but here is just a shot in
the dark:
So i dont get any indexing on documents
Central Admin->Operations->Timer Job Status reports the job SharePoint
Services Search Refresh SERVX Succeeded 100%
However, its clear from the logs that the gatherer job actually fails
and cancels.
The telltale line says:
Couldn't retrieve server http://servx2003 policy, hr = 80042616
- File:d:\office\source\search\search\gather\protocols
\sts3\sts3util.cxx Line:544
The error code, according to google, refers to a missing workflow or
something. So what exactly could be missing here ?
I'll post a more verbose bit of the log, slightly edited for brevity
at the bottom.
I also tried Admin Tools, WSS Configuration wizard, this completes
successfully but the result after restarts and so on remains the same.
As a last try i downloaded the Sharepoint Best Practices Analyser
( google for sharepointbpa ) and this does not seem to run at all on
WMSDE based installation, has trouble connecting to the SQL server
instance as it probably tries to do it over network protocols wchich
WMSDE does not support.

If i had a fuller version of SQL running, i'd check the database for
any missing records/bits but WMSDE is basically a locked down box.

In short, i have hit the oft-visited no way out corner of MS products
again. Remove, reinstall ?

/kert

mssdmn.exe MS Search Indexing CUserCatalogCache::LogStatistics()
before delete
mssdmn.exe MS Search Indexing CUserCatalogCache::LogStatistics No of
Items 0
mssdmn.exe MS Search Indexing Create CUserCatalogCache
mssdmn.exe PHSts ***** V3 Cache statistics:
committed=47194112, UserCatalogCaches=1 - File:d:\office\source\search
\search\gather\protocols\sts3\sts3util.hxx Line:171
mssdmn.exe PHSts ***** V3 Cache statistics: servers=1,
serverhit=1731, servermiss 81 - File:d:\office\source\search\search
\gather\protocols\sts3\sts3util.hxx Line:172
mssdmn.exe PHSts ***** V3 Cache statistics: sites=0,
sitehit=1728, sitemiss 8 - File:d:\office\source\search\search\gather
\protocols\sts3\sts3util.hxx Line:173
mssdmn.exe PHSts ***** V3 Cache statistics: webs=0,
webhit 1727, webmiss 8 - File:d:\office\source\search\search\gather
\protocols\sts3\sts3util.hxx Line:174
mssdmn.exe PHSts ***** V3 Cache statistics: lists=0,
listhit 1715, listmiss 16 - File:d:\office\source\search\search\gather
\protocols\sts3\sts3util.hxx Line:175
mssdmn.exe PHSts ***************** Destructor V3
UserCatalogCache dd599f27-fb74-4275-962f-309a710c713a_1_ - File:d:
\office\source\search\search\gather\protocols\sts3\sts3util.cxx Line:
199
mssdmn.exe PHSts ***** V3 UserCatalog Cache statistics:
name dd599f27-fb74-4275-962f-309a710c713a_1_, servers=1, sites=0,
webs=0, lists=0 - File:d:\office\source\search\search\gather\protocols
\sts3\sts3util.hxx Line:307
mssdmn.exe PHSts ***** Couldn't retrieve server http://servx2003
policy, hr = 80042616 - File:d:\office\source\search\search\gather
\protocols\sts3\sts3util.cxx Line:544
mssdmn.exe PHSts ****** Server servx2003 security
initialization failed, hr = 80042616 - File:d:\office\source\search
\search\gather\protocols\sts3\sts3util.cxx Line:317
mssdmn.exe PHSts CSTS3Accessor::InitURLType: Return
error to caller, hr=80042616 - File:d:\office\source\search\search
\gather\protocols\sts3\sts3acc.cxx Line:1382
mssdmn.exe PHSts CSTS3Accessor::InitURLType fails, Url
sts3://servx2003/contentdbid={2d3668e6-8c6d-44fe-8762-44942c1a1c39},
hr=80042616 - File:d:\office\source\search\search\gather\protocols
\sts3\sts3acc.cxx Line:172
mssdmn.exe PHSts CSTS3Accessor::Init fails, Url sts3://
servx2003/contentdbid={2d3668e6-8c6d-44fe-8762-44942c1a1c39},
hr=80042616 - File:d:\office\source\search\search\gather\protocols
\sts3\sts3handler.cxx Line:238
mssdmn.exe PHSts CSTS3Handler::CreateAccessorExB:
Return error to caller, hr=80042616 - File:d:\office\source\search
\search\gather\protocols\sts3\sts3handler.cxx Line:256
mssearch.exe GatherStatus Advise status change 12, project
Search, crawl -1 - File:d:\office\source\search\search\gather\server
\gatherobj.cxx Line:4688
mssearch.exe GatherStatus Advise status change 4, project
Search, crawl 21941 - File:d:\office\source\search\search\gather\server
\gatherobj.cxx Line:4688
mssearch.exe GatherStatus Remove crawl 21941 from inprogress
queue - File:d:\office\source\search\search\gather\server
\gatherobj.cxx Line:6552
mssearch.exe GatherStatus Unlock Queue - File:d:\office\source
\search\search\gather\server\gatherobj.cxx Line:2822
mssearch.exe GatherStatus Remove change status request from
Queue 4, crawl 21940 - File:d:\office\source\search\search\gather
\server\gatherobj.cxx Line:2848
mssearch.exe GatherStatus Advise status change 4, project
Search, crawl 21940 - File:d:\office\source\search\search\gather\server
\gatherobj.cxx Line:4688
mssearch.exe GatherStatus Remove crawl 21940 from inprogress
queue - File:d:\office\source\search\search\gather\server
\gatherobj.cxx Line:6552
mssearch.exe GatherStatus Unlock Queue - File:d:\office\source
\search\search\gather\server\gatherobj.cxx Line:2822

From: lurowam on 27 Feb 2007 17:30
Are you sure you could enable search if you use WSMDE?
Don't think so and hope that helps.
Patrick

On Feb 28, 9:12 am, "kert" <kaidok...(a)gmail.com> wrote:
> hello,
>
> Googled this six ways to sunday and still coming up empty handed. I
> think my search service config is seriously b0rked on this server,
> looks like a clean reinstall is in order, but here is just a shot in
> the dark:
> So i dont get any indexing on documents
> Central Admin->Operations->Timer Job Status reports the job SharePoint
> Services Search Refresh SERVX Succeeded 100%
> However, its clear from the logs that the gatherer job actually fails
> and cancels.
> The telltale line says:
> Couldn't retrieve serverhttp://servx2003policy, hr = 80042616
> - File:d:\office\source\search\search\gather\protocols
> \sts3\sts3util.cxx Line:544
> The error code, according to google, refers to a missing workflow or
> something. So what exactly could be missing here ?
> I'll post a more verbose bit of the log, slightly edited for brevity
> at the bottom.
> I also tried Admin Tools, WSS Configuration wizard, this completes
> successfully but the result after restarts and so on remains the same.
> As a last try i downloaded the Sharepoint Best Practices Analyser
> ( google for sharepointbpa ) and this does not seem to run at all on
> WMSDE based installation, has trouble connecting to the SQL server
> instance as it probably tries to do it over network protocols wchich
> WMSDE does not support.
>
> If i had a fuller version of SQL running, i'd check the database for
> any missing records/bits but WMSDE is basically a locked down box.
>
> In short, i have hit the oft-visited no way out corner of MS products
> again. Remove, reinstall ?
>
> /kert
>
> mssdmn.exe MS Search Indexing CUserCatalogCache::LogStatistics()
> before delete
> mssdmn.exe MS Search Indexing CUserCatalogCache::LogStatistics No of
> Items 0
> mssdmn.exe MS Search Indexing Create CUserCatalogCache
> mssdmn.exe PHSts ***** V3 Cache statistics:
> committed=47194112, UserCatalogCaches=1 - File:d:\office\source\search
> \search\gather\protocols\sts3\sts3util.hxx Line:171
> mssdmn.exe PHSts ***** V3 Cache statistics: servers=1,
> serverhit=1731, servermiss 81 - File:d:\office\source\search\search
> \gather\protocols\sts3\sts3util.hxx Line:172
> mssdmn.exe PHSts ***** V3 Cache statistics: sites=0,
> sitehit=1728, sitemiss 8 - File:d:\office\source\search\search\gather
> \protocols\sts3\sts3util.hxx Line:173
> mssdmn.exe PHSts ***** V3 Cache statistics: webs=0,
> webhit 1727, webmiss 8 - File:d:\office\source\search\search\gather
> \protocols\sts3\sts3util.hxx Line:174
> mssdmn.exe PHSts ***** V3 Cache statistics: lists=0,
> listhit 1715, listmiss 16 - File:d:\office\source\search\search\gather
> \protocols\sts3\sts3util.hxx Line:175
> mssdmn.exe PHSts ***************** Destructor V3
> UserCatalogCache dd599f27-fb74-4275-962f-309a710c713a_1_ - File:d:
> \office\source\search\search\gather\protocols\sts3\sts3util.cxx Line:
> 199
> mssdmn.exe PHSts ***** V3 UserCatalog Cache statistics:
> name dd599f27-fb74-4275-962f-309a710c713a_1_, servers=1, sites=0,
> webs=0, lists=0 - File:d:\office\source\search\search\gather\protocols
> \sts3\sts3util.hxx Line:307
> mssdmn.exe PHSts ***** Couldn't retrieve serverhttp://servx2003
> policy, hr = 80042616 - File:d:\office\source\search\search\gather
> \protocols\sts3\sts3util.cxx Line:544
> mssdmn.exe PHSts ****** Server servx2003 security
> initialization failed, hr = 80042616 - File:d:\office\source\search
> \search\gather\protocols\sts3\sts3util.cxx Line:317
> mssdmn.exe PHSts CSTS3Accessor::InitURLType: Return
> error to caller, hr=80042616 - File:d:\office\source\search\search
> \gather\protocols\sts3\sts3acc.cxx Line:1382
> mssdmn.exe PHSts CSTS3Accessor::InitURLType fails, Url
> sts3://servx2003/contentdbid={2d3668e6-8c6d-44fe-8762-44942c1a1c39},
> hr=80042616 - File:d:\office\source\search\search\gather\protocols
> \sts3\sts3acc.cxx Line:172
> mssdmn.exe PHSts CSTS3Accessor::Init fails, Url sts3://
> servx2003/contentdbid={2d3668e6-8c6d-44fe-8762-44942c1a1c39},
> hr=80042616 - File:d:\office\source\search\search\gather\protocols
> \sts3\sts3handler.cxx Line:238
> mssdmn.exe PHSts CSTS3Handler::CreateAccessorExB:
> Return error to caller, hr=80042616 - File:d:\office\source\search
> \search\gather\protocols\sts3\sts3handler.cxx Line:256
> mssearch.exe GatherStatus Advise status change 12, project
> Search, crawl -1 - File:d:\office\source\search\search\gather\server
> \gatherobj.cxx Line:4688
> mssearch.exe GatherStatus Advise status change 4, project
> Search, crawl 21941 - File:d:\office\source\search\search\gather\server
> \gatherobj.cxx Line:4688
> mssearch.exe GatherStatus Remove crawl 21941 from inprogress
> queue - File:d:\office\source\search\search\gather\server
> \gatherobj.cxx Line:6552
> mssearch.exe GatherStatus Unlock Queue - File:d:\office\source
> \search\search\gather\server\gatherobj.cxx Line:2822
> mssearch.exe GatherStatus Remove change status request from
> Queue 4, crawl 21940 - File:d:\office\source\search\search\gather
> \server\gatherobj.cxx Line:2848
> mssearch.exe GatherStatus Advise status change 4, project
> Search, crawl 21940 - File:d:\office\source\search\search\gather\server
> \gatherobj.cxx Line:4688
> mssearch.exe GatherStatus Remove crawl 21940 from inprogress
> queue - File:d:\office\source\search\search\gather\server
> \gatherobj.cxx Line:6552
> mssearch.exe GatherStatus Unlock Queue - File:d:\office\source
> \search\search\gather\server\gatherobj.cxx Line:2822


From: Mike Walsh on 28 Feb 2007 01:16
Provided he by "stock WSS" means that he is using WSS 2.0 (which the WMSDE
seems to indicate) then you are of course right.

Kert will need a third-party tool iif he wants search without using real SQL
Server 2xxx.

But as he is only now installing WSS it seems odd that he is not installing
WSS 3.0. There search does work even with the embedded database system. That
database system isn't however WMSDE but "Windows Internal Database" or
formerly "embedded SQL Server 2005 Express (Windows)".

Mike Walsh
WSS FAQ: www.wssv3faq.com / wss.collutions.com
No private questions please (additions to FAQ welcome)

<lurowam(a)gmail.com> wrote in message
news:1172615405.645950.297410(a)k78g2000cwa.googlegroups.com...
> Are you sure you could enable search if you use WSMDE?
> Don't think so and hope that helps.
> Patrick
>
> On Feb 28, 9:12 am, "kert" <kaidok...(a)gmail.com> wrote:
>> hello,
>>
>> Googled this six ways to sunday and still coming up empty handed. I
>> think my search service config is seriously b0rked on this server,
>> looks like a clean reinstall is in order, but here is just a shot in
>> the dark:
>> So i dont get any indexing on documents
>> Central Admin->Operations->Timer Job Status reports the job SharePoint
>> Services Search Refresh SERVX Succeeded 100%
>> However, its clear from the logs that the gatherer job actually fails
>> and cancels.
>> The telltale line says:
>> Couldn't retrieve serverhttp://servx2003policy, hr = 80042616
>> - File:d:\office\source\search\search\gather\protocols
>> \sts3\sts3util.cxx Line:544
>> The error code, according to google, refers to a missing workflow or
>> something. So what exactly could be missing here ?
>> I'll post a more verbose bit of the log, slightly edited for brevity
>> at the bottom.
>> I also tried Admin Tools, WSS Configuration wizard, this completes
>> successfully but the result after restarts and so on remains the same.
>> As a last try i downloaded the Sharepoint Best Practices Analyser
>> ( google for sharepointbpa ) and this does not seem to run at all on
>> WMSDE based installation, has trouble connecting to the SQL server
>> instance as it probably tries to do it over network protocols wchich
>> WMSDE does not support.
>>
>> If i had a fuller version of SQL running, i'd check the database for
>> any missing records/bits but WMSDE is basically a locked down box.
>>
>> In short, i have hit the oft-visited no way out corner of MS products
>> again. Remove, reinstall ?
>>
>> /kert
>>
>> mssdmn.exe MS Search Indexing CUserCatalogCache::LogStatistics()
>> before delete
>> mssdmn.exe MS Search Indexing CUserCatalogCache::LogStatistics No of
>> Items 0
>> mssdmn.exe MS Search Indexing Create CUserCatalogCache
>> mssdmn.exe PHSts ***** V3 Cache statistics:
>> committed=47194112, UserCatalogCaches=1 - File:d:\office\source\search
>> \search\gather\protocols\sts3\sts3util.hxx Line:171
>> mssdmn.exe PHSts ***** V3 Cache statistics: servers=1,
>> serverhit=1731, servermiss 81 - File:d:\office\source\search\search
>> \gather\protocols\sts3\sts3util.hxx Line:172
>> mssdmn.exe PHSts ***** V3 Cache statistics: sites=0,
>> sitehit=1728, sitemiss 8 - File:d:\office\source\search\search\gather
>> \protocols\sts3\sts3util.hxx Line:173
>> mssdmn.exe PHSts ***** V3 Cache statistics: webs=0,
>> webhit 1727, webmiss 8 - File:d:\office\source\search\search\gather
>> \protocols\sts3\sts3util.hxx Line:174
>> mssdmn.exe PHSts ***** V3 Cache statistics: lists=0,
>> listhit 1715, listmiss 16 - File:d:\office\source\search\search\gather
>> \protocols\sts3\sts3util.hxx Line:175
>> mssdmn.exe PHSts ***************** Destructor V3
>> UserCatalogCache dd599f27-fb74-4275-962f-309a710c713a_1_ - File:d:
>> \office\source\search\search\gather\protocols\sts3\sts3util.cxx Line:
>> 199
>> mssdmn.exe PHSts ***** V3 UserCatalog Cache statistics:
>> name dd599f27-fb74-4275-962f-309a710c713a_1_, servers=1, sites=0,
>> webs=0, lists=0 - File:d:\office\source\search\search\gather\protocols
>> \sts3\sts3util.hxx Line:307
>> mssdmn.exe PHSts ***** Couldn't retrieve
>> serverhttp://servx2003
>> policy, hr = 80042616 - File:d:\office\source\search\search\gather
>> \protocols\sts3\sts3util.cxx Line:544
>> mssdmn.exe PHSts ****** Server servx2003 security
>> initialization failed, hr = 80042616 - File:d:\office\source\search
>> \search\gather\protocols\sts3\sts3util.cxx Line:317
>> mssdmn.exe PHSts CSTS3Accessor::InitURLType: Return
>> error to caller, hr=80042616 - File:d:\office\source\search\search
>> \gather\protocols\sts3\sts3acc.cxx Line:1382
>> mssdmn.exe PHSts CSTS3Accessor::InitURLType fails, Url
>> sts3://servx2003/contentdbid={2d3668e6-8c6d-44fe-8762-44942c1a1c39},
>> hr=80042616 - File:d:\office\source\search\search\gather\protocols
>> \sts3\sts3acc.cxx Line:172
>> mssdmn.exe PHSts CSTS3Accessor::Init fails, Url sts3://
>> servx2003/contentdbid={2d3668e6-8c6d-44fe-8762-44942c1a1c39},
>> hr=80042616 - File:d:\office\source\search\search\gather\protocols
>> \sts3\sts3handler.cxx Line:238
>> mssdmn.exe PHSts CSTS3Handler::CreateAccessorExB:
>> Return error to caller, hr=80042616 - File:d:\office\source\search
>> \search\gather\protocols\sts3\sts3handler.cxx Line:256
>> mssearch.exe GatherStatus Advise status change 12, project
>> Search, crawl -1 - File:d:\office\source\search\search\gather\server
>> \gatherobj.cxx Line:4688
>> mssearch.exe GatherStatus Advise status change 4, project
>> Search, crawl 21941 - File:d:\office\source\search\search\gather\server
>> \gatherobj.cxx Line:4688
>> mssearch.exe GatherStatus Remove crawl 21941 from inprogress
>> queue - File:d:\office\source\search\search\gather\server
>> \gatherobj.cxx Line:6552
>> mssearch.exe GatherStatus Unlock Queue - File:d:\office\source
>> \search\search\gather\server\gatherobj.cxx Line:2822
>> mssearch.exe GatherStatus Remove change status request from
>> Queue 4, crawl 21940 - File:d:\office\source\search\search\gather
>> \server\gatherobj.cxx Line:2848
>> mssearch.exe GatherStatus Advise status change 4, project
>> Search, crawl 21940 - File:d:\office\source\search\search\gather\server
>> \gatherobj.cxx Line:4688
>> mssearch.exe GatherStatus Remove crawl 21940 from inprogress
>> queue - File:d:\office\source\search\search\gather\server
>> \gatherobj.cxx Line:6552
>> mssearch.exe GatherStatus Unlock Queue - File:d:\office\source
>> \search\search\gather\server\gatherobj.cxx Line:2822
>
>


From: kert on 28 Feb 2007 01:43
On 28 Feb, 08:16, "Mike Walsh" <englantilai...(a)hotmail.com> wrote:
> Provided he by "stock WSS" means that he is using WSS 2.0 (which the WMSDE
> seems to indicate) then you are of course right.
>
> Kert will need a third-party tool iif he wants search without using real SQL
> Server 2xxx.
>
> But as he is only now installing WSS it seems odd that he is not installing
> WSS 3.0. There search does work even with the embedded database system. That
> database system isn't however WMSDE but "Windows Internal Database" or
> formerly "embedded SQL Server 2005 Express (Windows)".
>
> Mike Walsh
> WSS FAQ:www.wssv3faq.com/ wss.collutions.com
> No private questions please (additions to FAQ welcome)

Ok, i messed up the terms again. i AM running WSS 3.0 with the
"Windows Internal Database". I can never keep up what Microsoft
decides to call its releases, and it aint obvious when you are running
them.
Anyway, my post above was about WSS 3.0 and the stock database that
comes with it. Both free products on existing 2003 server.

BTW, the only reason i need it to work is to verify that the custom
IFilter that i wrote also works under WSS 3.0 search. It does under
most other MS search products ( Indexing server, previous WSS, desktop
search and so on )
Once that is verified, the code will be posted on Sourceforge,
hopefully in a few days. Meanwhile, i have been installing a separate
instance of 2003 under virtual PC...

-kert

 | 
Pages: 1
Prev: WSS 3: Multiple top-level web sites
Next: Cannot complete this action error on top level sites?