MS SQL Server Plugin - What method of connection?

[wbrussell]

Ran into an issue on a customer site this week trying to test whether SQL was connecting during the installation (using IA15).

They had a remote SQL server (2008 R2) with standard TCP port 1433 being used for connections. SQL browser and UDP 1434 was also enabled.

My installer setup was using the SQL Server Script plugin and doing the test by sending the connection info along with the single "GO" sql script to the master database on the remote server.

It would never connect. When they ran wireshark on it, they said is was trying to use SMB to discover the server which was blocked by that server. I had to have them manually install the sql scripts remotely. The connection from my application worked fine once we bypassed the installer dialogs.

Can someone explain what is being used to discover and establish a connect to SQL instances?

Thanks,

Brian

[FrancescoT]

Dear Brian,

Honestly, I never used WireShark and I don't follow you when you say;

they said is was trying to use SMB to discover the server which was blocked by that server

Can you try to be more clear?

Anyway, could you post as "IntallAware Clipboard Format" the command you used?

Regards

[wbrussell]

Wireshark is just a packet capture utility

SMB is server message block protocol

Code: Select all

~InstallAware Clipboard Data~
~MS SQL Server~
~{04B717CB-C6E5-41F7-9058-72A196150C14}~
~$SERVERNAME$,$INSTANCENAME$,master,$SQLUSER$,$SQLPASSWORD$,SQLTEST,GO,0,0~
~mMSSQLIDE.dll\mMSSQLExec.dll~

[FrancescoT]

Dear Brian,

the code you posted doesn't contain the values you used to test your connection (server name, instance & so on).
However, I have just verified (using the project sample that comes with IA) to connect with remote SQL server 2008 R2 wich uses a standard TCP port 1433 ... and works fine.

I can only suspect that you are passing (maybe) not correct paramenters.

Regards