We are trialing BizTalk for use in one of our projects, as we dont
really have any spare dev servers we though we would install it on a
virtual one......as Microsoft now support BizTalk on VS

We have installed Virtual Server, SQL Server (SP4) Visual Studio, SOAP,
SQLXML, Frontpage (and activated) plus BizTalk.

BizTalk fails to configure, it cant see the local SQL Server database
or, it cant connect to other SQL server databases on real servers.

SQL Server can see itself and all of hte other SQL Server databases on
the network.

I've tried runas 'domain admin user' and it still fails.

No event log errors, on SQL or OS

Any ideas?

Does it only 'work' on VPC?

Thanks

[ Post a follow-up to this message ]

It does work on VPC. Probably you have a problem with the account not able t
o
connect to the SQL Server database. Did you install SQL Server under the sam
e
account as you are installing BizTalk Server?
Did you chose to install SQL Server with integrated security?

Danny.
http://dannybuysse.blogspot.com/

"Neil R" wrote:

> We are trialing BizTalk for use in one of our projects, as we dont
> really have any spare dev servers we though we would install it on a
> virtual one......as Microsoft now support BizTalk on VS
>
> We have installed Virtual Server, SQL Server (SP4) Visual Studio, SOAP,
> SQLXML, Frontpage (and activated) plus BizTalk.
>
> BizTalk fails to configure, it cant see the local SQL Server database
> or, it cant connect to other SQL server databases on real servers.
>
> SQL Server can see itself and all of hte other SQL Server databases on
> the network.
>
> I've tried runas 'domain admin user' and it still fails.
>
> No event log errors, on SQL or OS
>
> Any ideas?
>
> Does it only 'work' on VPC?
>
> Thanks
>
>

[ Post a follow-up to this message ]

Yes, I used the same account for both with SQL server running under
integrated security.

Thanks

N

[ Post a follow-up to this message ]

SQL server is left as a standard setup, TCP and Pipes

We can ping ourselves via IP address and machine name

The windows firewall is off (so port 1433 won't be blocked)

I can connect to the virtual SQL Server from the laptop.

[ Post a follow-up to this message ]

Did you check the configuration wizards logfile? Is there any more info in i
t?

Danny.

"Neil R" wrote:

>
> SQL server is left as a standard setup, TCP and Pipes
>
> We can ping ourselves via IP address and machine name
>
> The windows firewall is off (so port 1433 won't be blocked)
>
> I can connect to the virtual SQL Server from the laptop.
>
>

[ Post a follow-up to this message ]

Its telling me I have an issue getting the SSPI credentials.  I've
looked into this and it appears that it may be SP4 for SQL server, this
apparently patched the blaster worm - its been something of an issue
else where, although why its only failing of the VS I'm not sure.

I'm now going to reinstall everything from the virtual up and try
again.


N

[ Post a follow-up to this message ]