Hi,


I created a catalog on my local machine and could successfully index a
folder of documents located on a d/f server. But when I try to create a
catalog on one server and index a folder of documents located on the same
server which is used in the previous scenario, it shows that the directory
is
indexed but the number of documents indexed is "0" and are not included in
the search. This is weird. Do I need to check for some permissions? What
what are they?
My local machine has Windows 2000 professional whereas the server on which
the documents are indexed for search has window 2000 server. Is that the
problem? Please help.

Thanks,
Vasantha

[ Post a follow-up to this message ]

It possibly is a security issue. Exactly what is a d/f server?  If it is a
network share, can your crawl account access it?

--
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
"vasantha peddireddy via droptable.com" <forum@nospam.droptable.com>
wrote in message  news:6973c4a508e04ddcaa82faf97d251a73@Wi
nServerKB.com...
> Hi,
>
>
> I created a catalog on my local machine and could successfully index a
> folder of documents located on a d/f server. But when I try to create a
> catalog on one server and index a folder of documents located on the same
> server which is used in the previous scenario, it shows that the directory
> is
> indexed but the number of documents indexed is "0" and are not included in
> the search. This is weird. Do I need to check for some permissions? What
> what are they?
> My local machine has Windows 2000 professional whereas the server on which
> the documents are indexed for search has window 2000 server. Is that the
> problem? Please help.
>
> Thanks,
> Vasantha

[ Post a follow-up to this message ]

Thanks for replying. Yes, it is a network share and I guess I have logon
interactively rights on to that remote server. I am using the same account
which I use for netmeeting to that remote server. It says that it included
the directory in the catalog and the Total Docs is 1 whereas there are 8
docs. I am stuck at this point. In the event viewer I see an application log
"cidaemon failed to logon user because of error 1326". I feel that the
account I am using has no problem. What steps do I need to follow to make
sure if my crawl account has access to the server? Please let me know.

Thanks,
Vasantha


"Hilary Cotter" wrote:

> It possibly is a security issue. Exactly what is a d/f server?  If it is a
> network share, can your crawl account access it?
>
> --
> 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
> "vasantha peddireddy via droptable.com" <forum@nospam.droptable.com>
> wrote in message  news:6973c4a508e04ddcaa82faf97d251a73@Wi
nServerKB.com... 
>
>
>

[ Post a follow-up to this message ]

"Vasantha peddireddy" <Vasanthapeddireddy@discussions.microsoft.com> wrote
in message news:D1208926-B7C2-436D-B550-41F42005EBD2@microsoft.com...
> Thanks for replying. Yes, it is a network share and I guess I have logon
> interactively rights on to that remote server. I am using the same account
> which I use for netmeeting to that remote server. It says that it included
> the directory in the catalog and the Total Docs is 1 whereas there are 8
> docs. I am stuck at this point. In the event viewer I see an application
log
> "cidaemon failed to logon user because of error 1326". I feel that the
> account I am using has no problem. What steps do I need to follow to make
> sure if my crawl account has access to the server? Please let me know.

By default, the indexing service (cidaemon) runs under the System account.
The remote share that you're trying to index is not accessible to the System
account hence the login error 1326 (ERROR_LOGON_FAILURE). You have two
options: 1) make the remote index accessible to the System account, or 2)
when adding the remote directory in the Indexing Service MMC, you can
specify a username and password. Set it to a usename that has reading rights
for the remote share.
Note that once the remote documents are indexed, access rights to the
document contents in the index catalog is not restricted to the original
access rights anymore.

Ton

[ Post a follow-up to this message ]

On Thu, 9 Jun 2005 10:34:07 +0200, "Ton Plooy" <tonp@crunchtech.com>
wrote:

>
>"Vasantha peddireddy" <Vasanthapeddireddy@discussions.microsoft.com> wrote
>in message news:D1208926-B7C2-436D-B550-41F42005EBD2@microsoft.com... 
>log 
>
>By default, the indexing service (cidaemon) runs under the System account.
>The remote share that you're trying to index is not accessible to the Syste
m
>account hence the login error 1326 (ERROR_LOGON_FAILURE). You have two
>options: 1) make the remote index accessible to the System account, or 2)
>when adding the remote directory in the Indexing Service MMC, you can
>specify a username and password. Set it to a usename that has reading right
s
>for the remote share.
>Note that once the remote documents are indexed, access rights to the
>document contents in the index catalog is not restricted to the original
>access rights anymore.

But keep in mind that any access rules to the documents themselves do
still apply.  If the account trying to access the document doesn't
have permissions, then they aren't accessible.  This gets important
when using anonymous access, since the anonymous user in IIS is a
local account and also doesn't normally have permissions to the remote
server's resources.

Jeff

[ Post a follow-up to this message ]

Today my network administrator created a system account for me and this
account has complete rights for the remote share. But still it does not inde
x
the documents on the remote share. I have all the permissions on those
documents. What is really strange is that I could index the same documents
from my local machine. Only difference I see is that the server which has th
e
indexing service running has Windows 2000 server and the remote server has
windows NT.

Here are the steps I am following to index a directory

When adding the directory, in the path I mentioned \\Servername\ShareName
and I also entered the username and password. But still it says total
documents indexed as '1' whereas there are '8'. Please advice as I have been
trying to fix this issue for more than 4 days now.

Thanks,
Vasantha

"Jeff Cochran" wrote:

> On Thu, 9 Jun 2005 10:34:07 +0200, "Ton Plooy" <tonp@crunchtech.com>
> wrote:
> 
>
> But keep in mind that any access rules to the documents themselves do
> still apply.  If the account trying to access the document doesn't
> have permissions, then they aren't accessible.  This gets important
> when using anonymous access, since the anonymous user in IIS is a
> local account and also doesn't normally have permissions to the remote
> server's resources.
>
> Jeff
>

[ Post a follow-up to this message ]

"Vasantha peddireddy" <Vasanthapeddireddy@discussions.microsoft.com> wrote
in message news:5F6EDC1A-3F26-4BA0-9985-B1F113E47AE4@microsoft.com...
> Today my network administrator created a system account for me and this
> account has complete rights for the remote share. But still it does not
index
> the documents on the remote share. I have all the permissions on those
> documents. What is really strange is that I could index the same documents
> from my local machine. Only difference I see is that the server which has
the
> indexing service running has Windows 2000 server and the remote server has
> windows NT.
>
> Here are the steps I am following to index a directory
>
> When adding the directory, in the path I mentioned \\Servername\ShareName
> and I also entered the username and password. But still it says total
> documents indexed as '1' whereas there are '8'. Please advice as I have
been
> trying to fix this issue for more than 4 days now.

Does it still give error 1326 for the cidaemon in the event log? You have
various options to investigate this problem. First of all make sure you
understand how to set things up by reading
http://msdn.microsoft.com/library/d...
webov_4t0z.asp .
There are troubleshooting tips at
http://support.microsoft.com/defaul...kb;en-us;308202 and more info
can be found here.

A low level debugging approach is the following. Download FileMon from the
www.sysinternals.com site and install it on your local machine. Stop the
indexing service, start filemon (possibly set a filter on *cidaemon*) and
start the indexing service and wait until you see it accessing the remote
share. The FileMon output should enable you to see if and how it accesses
the remote share and if any (security) problems arise.

Ton

[ Post a follow-up to this message ]

Nothing works. We made the remote index accessible to the system account, bu
t
still it does not index the documents in a directory. The number of document
s
indexed it says is "1" versus "8". I guess "1" is the directory.

I have a question. When trying to index documents on a remote server, is it
necessary that the remote server and the server from where we are indexing
should be on the same domain name? If both the servers are not in a domain o
r
not in the same domain, will indexing service not index documents on the
remote server? Please let me know.

Thanks,
Vasantha

"Ton Plooy" wrote:

>
> "Vasantha peddireddy" <Vasanthapeddireddy@discussions.microsoft.com> wrote
> in message news:5F6EDC1A-3F26-4BA0-9985-B1F113E47AE4@microsoft.com... 
> index 
> the 
> been 
>
> Does it still give error 1326 for the cidaemon in the event log? You have
> various options to investigate this problem. First of all make sure you
> understand how to set things up by reading
> http://msdn.microsoft.com/library/d...uwebov_4t0z.asp .
> There are troubleshooting tips at
> http://support.microsoft.com/defaul...kb;en-us;308202 and more in
fo
> can be found here.
>
> A low level debugging approach is the following. Download FileMon from the
> www.sysinternals.com site and install it on your local machine. Stop the
> indexing service, start filemon (possibly set a filter on *cidaemon*) and
> start the indexing service and wait until you see it accessing the remote
> share. The FileMon output should enable you to see if and how it accesses
> the remote share and if any (security) problems arise.
>
> Ton
>
>
>

[ Post a follow-up to this message ]