bug? when using addcatalog method of the AdminIndexServer/Microsoft.ISAdm object remotely

[Sam Wells]

There appears to be a problem using the adminindexserver object to create a
catalogue remotely.

steps to reproduce problem

1. You need a windows 2000 server with 2 physical drives e.g. C: & E: (subst
drives are no good)
2. Run the following vb script on a workstation with 1 physical drive (C:)
This should create a catalog called test in the servers c:\test folder

dim adm
dim cat
set adm = createobject("Microsoft.ISAdm")
adm.MachineName = "172.30.0.10" 'ip address of server running indexing
service
adm.stop 'stop the service so a new catalog can be created
set cat = adm.addcatalog("test","c:\test") ' create a new remote catalogue
on the server's C: drive
msgbox cat.catalogname 'confirmation message displays the catalog name as
created above

3. Now try the following script that should create a catalog called test2 on
the servers e:\test2 folder but it FAILS

dim adm
dim cat
set adm = createobject("Microsoft.ISAdm")
adm.MachineName = "172.30.0.10" 'ip address of server running indexing
service
adm.stop 'stop the service so a new catalog can be created
set cat = adm.addcatalog("test2","e:\test") ' AHHHH it fails here
msgbox cat.catalogname

The problem appears to be that the addcatalog is checking the local
machine(workstation) for a drive e: and it obviously fails.

Now add a local drive e: to the workstation

run the script and it works fine,

why?

[Hilary Cotter]

This is by design. You can only create local catalog. For example, a rogue
admin could create a catalog on your local machine and then query it for
things like salary, home phone number, maiden name, etc.
--
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

Post by Sam Wells
There appears to be a problem using the adminindexserver object to create
a catalogue remotely.
steps to reproduce problem
(subst drives are no good)
2. Run the following vb script on a workstation with 1 physical drive (C:)
This should create a catalog called test in the servers c:\test folder
dim adm
dim cat
set adm = createobject("Microsoft.ISAdm")
adm.MachineName = "172.30.0.10" 'ip address of server running indexing
service
adm.stop 'stop the service so a new catalog can be created
set cat = adm.addcatalog("test","c:\test") ' create a new remote catalogue
on the server's C: drive
msgbox cat.catalogname 'confirmation message displays the catalog name as
created above
3. Now try the following script that should create a catalog called test2
on the servers e:\test2 folder but it FAILS
dim adm
dim cat
set adm = createobject("Microsoft.ISAdm")
adm.MachineName = "172.30.0.10" 'ip address of server running indexing
service
adm.stop 'stop the service so a new catalog can be created
set cat = adm.addcatalog("test2","e:\test") ' AHHHH it fails here
msgbox cat.catalogname
The problem appears to be that the addcatalog is checking the local
machine(workstation) for a drive e: and it obviously fails.
Now add a local drive e: to the workstation
run the script and it works fine,
why?

[Sam Wells]

If this is the case then why would the script allow you to create a remote
server catalog when you have the same local drives defined as the server.
It's quite obviously a bug, i can create a catalog on the servers c-drive no
problem its only when i try to create a catalog on a servers drive that
doesn't have the equivalent drive defined on the local drive that it fails.
Also the location of the catalogue bears no relation to the directories that
are being indexed by it, its simply the location of the data files.

Post by Hilary Cotter
This is by design. You can only create local catalog. For example, a rogue
admin could create a catalog on your local machine and then query it for
things like salary, home phone number, maiden name, etc.
--
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

Post by Sam Wells
There appears to be a problem using the adminindexserver object to create
a catalogue remotely.
steps to reproduce problem
(subst drives are no good)
2. Run the following vb script on a workstation with 1 physical drive (C:)
This should create a catalog called test in the servers c:\test folder
dim adm
dim cat
set adm = createobject("Microsoft.ISAdm")
adm.MachineName = "172.30.0.10" 'ip address of server running indexing
service
adm.stop 'stop the service so a new catalog can be created
set cat = adm.addcatalog("test","c:\test") ' create a new remote
catalogue on the server's C: drive
msgbox cat.catalogname 'confirmation message displays the catalog name as
created above
3. Now try the following script that should create a catalog called test2
on the servers e:\test2 folder but it FAILS
dim adm
dim cat
set adm = createobject("Microsoft.ISAdm")
adm.MachineName = "172.30.0.10" 'ip address of server running indexing
service
adm.stop 'stop the service so a new catalog can be created
set cat = adm.addcatalog("test2","e:\test") ' AHHHH it fails here
msgbox cat.catalogname
The problem appears to be that the addcatalog is checking the local
machine(workstation) for a drive e: and it obviously fails.
Now add a local drive e: to the workstation
run the script and it works fine,
why?