Very Computer

I can't get beyond the part where it tries to access SQL Server, even though
SQL Server (2000 developer edition) is running and I give the Biztalk
install wizard the current admin-authorized account information (to logon).
I think it's because of the new way that Windows 2000 Pro (why the developer
editions) uses the BOX.USERID naming scheme for everything and the install
wizard just wants the name.

Before anyone asks: Yes, I installed Win 2000 Server in its own directory,
but that's not the main work copy (email, developer tools, etc.). Obviously
I'm missing something here.

Any suggestions?

Quote:> It's the same with BizTalk, Commerce Server and IIS developer
> editions. These all come with MSDN Universal, among other ways to get them
> (i.e., install fresh off the CDs). The only thing that installed was SQL
> Server 2000 Developer edition.

> I can't get beyond the part where it tries to access SQL Server, even
though
> SQL Server (2000 developer edition) is running and I give the Biztalk
> install wizard the current admin-authorized account information (to
logon).
> I think it's because of the new way that Windows 2000 Pro (why the
developer
> editions) uses the BOX.USERID naming scheme for everything and the install
> wizard just wants the name.

> Before anyone asks: Yes, I installed Win 2000 Server in its own directory,
> but that's not the main work copy (email, developer tools, etc.).
Obviously
> I'm missing something here.

> Any suggestions?

I had a similar problem caused by me not cleaning up the underlying SQL
files after deleting the databases from SQL Enterprise manager.

Th e BizTalk install does not give you a very useful error message.

Quote:> It's the same with BizTalk, Commerce Server and IIS developer
> editions. These all come with MSDN Universal, among other ways to get them
> (i.e., install fresh off the CDs). The only thing that installed was SQL
> Server 2000 Developer edition.

> I can't get beyond the part where it tries to access SQL Server, even
though
> SQL Server (2000 developer edition) is running and I give the Biztalk
> install wizard the current admin-authorized account information (to
logon).
> I think it's because of the new way that Windows 2000 Pro (why the
developer
> editions) uses the BOX.USERID naming scheme for everything and the install
> wizard just wants the name.

> Before anyone asks: Yes, I installed Win 2000 Server in its own directory,
> but that's not the main work copy (email, developer tools, etc.).
Obviously
> I'm missing something here.

> Any suggestions?