Hi Trent



I agree that being disconnected "shouldn't" affect the installation. But something must have changed from v1.6.7 to v1.7.0 that prevents the installation.



Still working on this end... I used to be able to see many dozen installation of SQL Server here, but now I see none! I can't believe everyone simultaneously stopped using the Browser service here.



Again... If we can't find a solution to this installation problem, is there a "manual" install option?

Well, the code that actually is looking for the SQL Servers is not something that we wrote, but rather the installer pulls back. In regards to a manual installation, if you type in the SQL Server and click next, is this where you get the error?



Worst case, check the "Skip deploy structures" option and then after the install you can open up the DDT and manually deploy the StrataFrame.pkg file. That would be the only "manual" way to do this. It sounds like the failure is happening on the search or authentication. I need to know which because the search is not us and the authentication is.

The error pops up almost immediately after the "Status: Searching, please wait..." in the "Searching for SQL Servers" panel. No other input is requested. Once OK is clicked, the installation process is blown away.

OK, so this is actually coming from the MSI then, not our assembly.  This isn't making any logical sense as there is no difference between 1.7 and 1.67 in this regard.  In fact, this goes back much further than that.  So that iis what is confusing me as you have said that 1.6.7 is working and the 1.7 is not.

Do you have a copy of SQL Server loaded on your local machine?  Do you have more than one version of SQL native client loaded?

Hi Trent



I only have the copy of SQL Server that came with VS2008 (I'm normally an Oracle user.) Using SQL Server Configuration Manager shows only my local SQL Server (and Browser Services) running. The available client protocols are Shared Memory, TCP/IP and Named Pipes.



When I install v1.6.7, the only option for a SQL Server given is for my local machine. None of the network servers are visible (which is why I'm still pursuing the issue with our IT group.) I get the same thing when trying to finding databases via VS2008's Tools/Connect to Database... dialog.



I know it's strange!

I'm having the same problem. I'm running a fresh install of Windows 7 with VS2008, SQL 2008 and an instance of SQL Express. This thread is a few months old. Any new ideas? 

I do not have v1.6.7 but I was able to install v1.6.6. I should also add that the version I'm getting the error with is v1.7.2.

Well, for whatever this is worth, this is not reproducable which tends to mean that there is an environmental issue. Also, it is important to note that this logic has not changed in a very long time. So I would ensure that you have TCP/IP turned on and setup for SQL Server to make sure that it can be reached via sockets. If SQL Server is on the same machine as VS then this should not matter. But the one difference that you may be experiencing is that support for SQL Server 2008 and SMO 10 whereas 1.6.6 did not have this support.



So the first thing that I would do is turn on TCP/IP support for SQL Server through the configuration manager, restart the SQL services, and then make sure that you can connect to the localhost.

I've tried just about everything that I can think of. TCP was already enabled. I've completely patched VS2008 and SQL Server 2008. I do not have much else loaded on my laptop. It's a pretty fresh install. I installed Windows 7 when it became available. I guess the next step is to completely uninstall and reinstall. What do you think?

I believe that the issue may be Windows 7. I will load a VM and see if that is the case.