InstallAware

Does it require SQL to be installed on the target machine?

I thought it would use the MDAC components in order to connect to a SQL server, I am finding out that on machines that don't have SQL installed i get a CONNECT_ERROR.

I have an installer that installs a web app on the target machine then if the SQL Server is located on a different machine then they provide the necessary infomation to connect to that server but, if the web server doesn't have SQL installed then I get this error.

Any suggestions on what i can do?

Hi,

I am not entirely sure what you are asking - when you use the MS SQL plugin then yes, SQL will be required.

Could you please clarify?

What I would like to know is if there is a way to be able to connect from Server A (No SQL) to Server B (SQL Installed here) using the SQL Plug-In or any other method.

Yep - you can specify the server address (in the Server field) and connect to remote servers..

I didn't make myself clear.

What can I use to connect from Server A (No SQL Installed) to Server B (SQL Installed).

I can't use MS-SQL Plug in because I am getting the CONNECT_ERROR (Read my first Post).

I thought that having MDAC installed would be enough but I am finding that is not the case, what are your suggestions?

I'm running the installer on Windows 7 and it says it has MDAC 6.1 installed.

I figured that if I install SQL Express on Server A then I am able to connect to Server B however, I don't know how to uninstall it once I am done.

I beg to differ on this, but the MSSQL plugin does not require SQL to be installed on the machine. We have been using this quite successfully in numerous situations on systems that do not have SQL on them, but does do connections to a SQL box. If you're getting a CONNECT_ERROR, you need to check several things. First, is the address, user name and password all correct? Are there firewalls involved between the two servers? The single biggest problem I have run into is the fact that the MSSQL plugin does not use the standard SQL port, but rather the SMB port instead and this is commonly blocked by firewalls. If you do a search on this forum for MSSQL and port you should find a thread about the ports used by the plugin.

I have the same problem. No connection from virtual "clean" windows 7 or windows xp client machine.

I also noticed that Detect MS SQL Instances command returns different list compared to MS SQL Management Studio. Why?
If i have a server in TEST\SQLEXPRESS, IA returns 2 lines: TEST and TEST\SQLEXPRESS.

I have not played with the detect SQL instances option at all, so I don't know about it, but for your other problem, can you give more details?


What is the error you get? Is the firewall on/off? Is this from one machine to a remote machine or is SQL server on the same box as the one the installer is being run on? Also, SQLExpress may be the key here, it may not support the right type of connection, I've only worked with connecting to full blown SQL server.