Our customers will have either SQL Server 2008 or SQL Server 2008 Express installed. Our installation script connects to the database and runs a set of scripts for our product. The process is fine for SQL Server 2008 but does not work for Express, failing with error:
Error 27502.Could not connect to Microsoft SQL Server 'localhost'. [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection. (14)
I can't see where to specify the database instance name anywhere in InstallShield.
yes, this happens in SQL Express. because in SQL express the connection is made with the following :
localhost\SQLExpress
whereas in standard edition it connects to SQL only with localhost.
So, please specify localhost\SQLExpress in the machine name where you are using SQL express, other wise your setup will not be able to make connection with the DB.
Thanks for your quick reply... Yes, we tried that but instead received the error:
Error 27502.Could not connect to Microsoft SQL Server 'localhost\SQLExpress'. [DBNETLIB][ConnectionOpen (Connect()).]Specified SQL server not found. (6)
Is this a SQL Server Express configuration problem rather than an InstallShield problem?
I dont think its an IS problem because its working fine for me. There is some configuration problem with your SQL server or there may be some error in your script.
The installation and SQL scripts run fine on a standard SQL Server 2008 (with TCP/IP and SQL authentication enabled).
If we try install on SQL Server 2008 Express with the same options (and specifying the instance name) then it doesn't work.
I'm happy that the scripts work ok, and the configuration appears to ok. What exactly does IS do when it connects to the database? If there's a config problem I need to know more about what IS actually does...
Do you know of anything specific that needs configuring when using SQL Express?
