sp_ActiveDirectory_Start problem

[cerilocke@ev1.net]

I have two Windows 2003 servers that both have SQL 2000 on them with
Service Pack 4 installed. If I run the stored procedure
sp_ActiveDirect ory_Start on one, it runs with no problem. However, on
the other, if I run it, I receive the error message xpadsi.exe failed.
Cannot drop the table 'msdb.dbo.ADSIN ewDBs', because it does not exist
in the system catalog. Could anyone please tell me why I get this. The
only difference that I can see on the servers is that on the one that
runs successfully, there is an x86 folder within Program
Files\Microsoft SQL Server\MSSQL, but on the other there is not,
despite me having run the identical service pack 4 download from MSDN
on both. I would be extremely grateful to anyone who can provide me
with a possible solution to this.

[Erland Sommarskog]

Re: sp_ActiveDirect ory_Start problem

(cerilocke@ev1. net) writes:[color=blue]
> I have two Windows 2003 servers that both have SQL 2000 on them with
> Service Pack 4 installed. If I run the stored procedure
> sp_ActiveDirect ory_Start on one, it runs with no problem. However, on
> the other, if I run it, I receive the error message xpadsi.exe failed.
> Cannot drop the table 'msdb.dbo.ADSIN ewDBs', because it does not exist
> in the system catalog. Could anyone please tell me why I get this. The
> only difference that I can see on the servers is that on the one that
> runs successfully, there is an x86 folder within Program
> Files\Microsoft SQL Server\MSSQL, but on the other there is not,
> despite me having run the identical service pack 4 download from MSDN
> on both. I would be extremely grateful to anyone who can provide me
> with a possible solution to this.[/color]


I will have to start with disclaimer that I have no experience of
Active Directory, nor the stored procedures to communicate with it.

I looked a little in Books Online, and I noticed that
sp_ActiveDirect ory_Start is not documented there. This is usually an
indication that you are on dangerous grounds and doing something
unsupported.

I tried to the procedure on my machine, and I did not get the error,
despite I did not have the table. But this may have to due to that I'm
Windows XP at home, and no active directory in sight.

A wild approach would be to create the table and see what happens. I
would strongly recommend that you backup your msdb before you go on
such adventures.

I find it difficult to believe that the x86 folder has anything to do
with it.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se

Books Online for SQL Server SP3 at

http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp