Verity and Collections on different servers

[sundeviltennis]

I have CFMX7 on server 1 and Collection folders on server 2. I am confused on
what to enter in the following <cfindex tag> attributes: Key and Type. I tried
type="path" and key="Shared drive on server 2" and the application works fine
if the user is mapped to that shared folder. The application failed from a
workstation that wasn't mapped to that folder on server 2. I tried
key="\\servername\collections" and no "type" entry in <cfindex>, but the index
didn't build. Any suggestions?

[MikerRoo]

By default, CF, Java/Jrun, and Verity run under "LocalSystem" on windows and
thus can't see or use all of the needed resources on another machine.

You need to create a user account just for Coldfusion. Ideally this is a
Domain or Active directory account -- but it can be local to the machines.
The username and password must be the same on all machines.

For security, do not make this account an administrator. Our systems run as
an ordinary user without any problems.
Also, use this account for nothing else.

Using the services control panel, set all of the CF, Java/Jrun, and Verity
services to run under this account on all machines.

Next create share(s) on the verity machine that the CF user has full control
on. It's best to share the full drive. (You can restrict access once
everything's working.)

You may also have to persistently map the network drive for the CF user.

[sundeviltennis]

Thanks for the tip. I am still not able to re-build my collections. My
collections folder is on my development server and Verity is on my web server.
My cfindex tag reads as follow:
<cfindex collection="Collection Name"
action="refresh"
type="path"
key="M:\Folder\Collections"
extensions=".doc, .txt, .xls, .htm, .html"
recurse="yes"
The "key" is a mapped drive pointing to the development server. I am getting
the following error when running the index.cfm page.
"The KEY specified is not a directory: M:\G4_Shared\V_Collections. The path in
the KEY attribute must be a directory when the TYPE is "PATH".
The error occurred on line 18.
In the future we will need to point to collection folders across many servers.

[MikerRoo]

Did you set up the service accounts?

Is the M drive a share seeable and usable by the account?

[LL@Work]

I will elaborate on what MikerRoo suggested:
Open the Search Server service in the Services Applet of the Control Panel
(Administrative Tools).
Click "Log On"
Change "Local System Account" to "This Account..." and make (this account) a
domain user of the server your M:\ drive connects to.

[sundeviltennis]

In addition to everyones suggestons, I simplified things by putting the
collections folder (web server) on D: and the documents on the development
server on D: drive. I also used a UNC for the key and set recurse to "no" and
it worked, Yeah!!! Thanks for everyone's help.