CONNECTION_ERROR on SQL Server 2008 R2

[Bar_BQ]

Hi,

My installer in the end of installation process needs to connect to a fresh SQL Server 2008 instance (installed in the beginning of installation) and run an sql script. But unfortunately I get error message CONNECTION_ERROR.
I have already spent three days on trying to solve this but I checked all known to me possibilities without a result.
I installed IA9R2 the newest update, and changed the SQLServer installation options to install Connectivity tool.

I found that if I would installed SQL Server 2005 first and then 2008 version then it works fine.

Any idea?

BarBQ

[MichaelNesmith]

Are you installing all required capabilities, such as enabling network connections and such?

Did you try to connect on alternate ports?

[Bar_BQ]

I am testing the setup on VirtualPC. This is commandline:

/q /ACTION=Install /SECURITYMODE=SQL /SAPWD="$SQLPASSWORD$" /INSTANCENAME="$SQLINSTANCE_NAME$" /FEATURES=SQLEngine,Replication,BC,Conn,SSMS,SDK
/SQLSVCACCOUNT="NT AUTHORITY\NETWORK SERVICE" /SQLSYSADMINACCOUNTS="$SQLSYSTEMADMIN$"
/NPENABLED=1 /TCPENABLED=1 /AGTSVCACCOUNT="$SQL_USER_NAME$" /AGTSVCPASSWORD="$SQLPASSWORD$" /AGTSVCSTARTUPTYPE="Automatic" /IAcceptSQLServerLicenseTerms=TRUE

I haven't used different ports yet. In the plugin I put just "localhost" because the database is going to be restored on an local instance (with different name than SQLEXPRESS).

What is more, I can connect to the server using sqlcmd tool with no problems, so could it be a plugin related issue? Or maybe Virtual PC?

[MichaelNesmith]

What ports did you try with the plug-in?

ENABLENETWORKPROTOCOLS=1 might also be required on the setup command line.

[Bar_BQ]

I only tried port 1433.

I got through the installation from commandline guide (http://msdn.microsoft.com/en-us/library/ms144259.aspx) but I couldn't find option you mentioned... I think this functionality is provided with TCPENABLED and NPENABLED options, am I right?

[MichaelNesmith]

Excellent research, yes I believe I mistakenly quoted the parameter which was valid for the old version of SQL Server (2005).

[Bar_BQ]

Thank you

But are we getting closer to solution?

[MichaelNesmith]

Did you try those parameters?

[Bar_BQ]

Of course, unfortunatelly it didn't help

[MichaelNesmith]

It seems like it'd have to be some kind of configuration issue nonetheless - since an upgrade install works for you but a fresh install doesn't.