Hi,
when loading the domidx task I receive the following error message:
Domain Indexer Aborting: File does not exist
Domain Indexer process shutdown: File does not exist
Which file is missing (catalog.nsf exists)? Someone an idea?
Bernd
Subject: As I recall…
Hi
It has been a long since I have “mingled” with domain search, but it should not be nessesary to call the domain indexer from the console
Make shure you have a correct server document.
-
domain catalog : yes
-
domain index schedule :enabled
regards
Jesper Kiaer
Subject: SOLUTION: Error message when loading domidx
See this technote:
Subject: Error message when loading domidx
Hi there, I am just getting the same exact problem. We are using 6.03 on Linux RedHat 8.
Catalog exists and everything seems fine.
This is quite a strange problem.
If anyone has any serious suggestions please let us know!
Thank in advanced
Martin
Subject: RE: Error message when loading domidx
I am having the same problem and cannot find an answer in another post… so I’ve created a new post…
Subject: Error message when loading domidx
I got around this error by uninstalling then reinstalling the Notes server. Copy your data directory and Notes.ini to another location before doing this, then copy them back after the install.
I found it happens if you try and kill the domidx task when it is indexing the File System, or when domidx task says that it is updating (type “sh ta” at the console) but nothing seems to be happening.
I was hoping that Domain Search would be more stable in R6, but I am finding it is no better than in R5. It is a fine art trying to get it working, and when it does, dont touch it!
Subject: Don’t run as service!
After more research I found that reinstalling wasn’t the fix - it was to do with the way the Domino server was loaded. If it was started as a service, I would get the “File not found” error. If run as a program, Domain Indexer would run fine - it actually seems to be more stable when run as a program.
Subject: RE: Don’t run as service!
After much pain I too have discovered that Domain Indexing of file systems does not work if Domino is running as a Windows service.
I have tried the following things to try and get around this, none of which have worked:
Set the domino service to run as a user that is a member of the windows domain. I have agents that access file systems using UNC paths (eg. \server\share\file), and the agents have no problems accessing these files that are on another server within the windows domain
Setup the Domain Index to search a mounted network drive (instead of an UNC path)
Created a scheduled task, running as the same user as the domino server to remap the drive
Created an agent to remap the drive
If anyone has any other ideas, or has file system domain indexing working accross network drives, please let me know.
Thanks
Adam
Subject: RE: Don’t run as service! A solution
I submitted this problem to IBM, and this is the solution provided which works a treat!
Domino indexing and UNC path problem
File-system and share implementation are supported — but due to a
Microsoft Windows imitation, user can not specify only the “server” & the
“share” directly. For example, if the share is “\servername\fileshare”
---- then this is not allowed.
One subdirectory beneath the actual share must be designated. Just as the
GUI user example states: “\Fileserver\share\folder.…”. In this case
“folder” is specified under “share”.
Work around(s): The user can specify
'\servername\fileshare\domain-files" — i.e. one level beneath the
share.
Related Topic - Directory Links with UNC-Path to a Subdirectory Fail
http://www-1.ibm.com/support/docview.wss?uid=swg21088330