Re: Remote Indexing Server - authentication problems
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Wed, 17 May 2006 19:13:37 -0400
try this one.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex
This should be on your remote Index Services server.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"vler" <VladaEric@xxxxxxxxx> wrote in message
news:1147853883.818222.291260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hilary, thanks for reply.
I tried (searched my registry for contentindexcommon and set READ
permissions to Everyone) but still no success.
What I further noticed is that the Windows authentication from the
Query Analyzer on the DB server (using a domain account) works fine.
The same user, but on application machine, the same error.
Maybe another hint, in SQL Profiler, the error looks somewhat diferent:
"Non-interface error: OLE DB provider MSIDXS returned
DBPROP_STRUCTUREDSTORAGE without DBPROPVAL_OO_BLOB being supported"
I feel it has something to do with security account delegation, but I
really cannot find the correct settings. I tried various mappings for
the linked server.
Do all 3 servers need to reside in the same domain? What user should I
set to run SQL Server service?
Did anybody have the same experience?
Thanks!
.
- Follow-Ups:
- References:
- Remote Indexing Server - authentication problems
- From: vler
- Re: Remote Indexing Server - authentication problems
- From: Hilary Cotter
- Re: Remote Indexing Server - authentication problems
- From: vler
- Remote Indexing Server - authentication problems
- Prev by Date: Re: full-text : first request is very slow
- Next by Date: Re: ItemCount in staging differs from production
- Previous by thread: Re: Remote Indexing Server - authentication problems
- Next by thread: Re: Remote Indexing Server - authentication problems
- Index(es):
Relevant Pages
|
