Karen - thanks for the info... did you apply the fix? If so, what was the result?

File name Size

EULA.txt 2 KB

Readme.txt 1...

I have to bounce the server before it will let me run setup again. That will have to wait until tonight... I'll give you an update.

no new SQL services were installed. It looks setup removed them when the install went bad. I'll try a different instance name, but I have used this convention...

error = "specified object (proc name) does not exist"

The problem is with all the procs called by the ASP. Here is the connection string.

SERVER=SERVERNAME\SQL2000;DB=db-name;UID=userA;PWD=userA;PROVIDER=SQLOLEDB

If I change the server...

That was my first thought but the ASP's, IIS, and SQL Server are on the same machine.

thanks guys... found this BOL topic to be very hepful.

"Database Engine Features Supported by the Editions of SQL Server 2000"

big help everyone... thanks again.

I just noticed that I am now a "1 star" poster.

1 more question - we force password changes every 30 days and I'll have 8 production boxes to manage... will I need to got each box every month and manually...

yeah... I don't think my NT admin would like the domain admin approach.

Brain - I'll read your article. Thanks.

thank you.... that's what I needed to know.

I'm sure this is a common problem and hopefully there is a common fix.

We are runing a conversion and I want to maintain the id's from the source table, but...

here's a couple of white papers that seem to clarify.

Thanks again.

http://www.microsoft.com/sql/howtobuy/licensingwp.asp

http://www.microsoft.com/sql/howtobuy/sqlserverlicensing.asp

Thanks Steve... I'll do some research and post an update.

found the problem... I forgot to mention I was running the install through Terminal Server.

I ran it on the box and all is well.

Thanks for the help.

Steve - I'm new to 2000... I do not see the option for "Log on as a service"... I am looking at the logon properties for the account.

Thanks...