I think it may have to do with the length of the computer name used. Even though Windows let you use more than 15 characters I believe it will recognized up to 9 or 15 in some OSs, since Michael changed the computer name to "WIN7VM" and the problem was gone, means that it definitely have something to do with the computer name.



Probably the function used by SF or IA installation has a limitation on the computer name.

Edhy Rijo

Hmmm...I've always installed SF to a SQL server with a dash in the machine name. Never had a problem. Was SQL Server 2k though on Windows Server 2003, if that makes any difference.

That's a very interesting find! All of the computers here have names in the form of "ABC1234-XYZ5678", which explains why the install procedures can't "see" them.



Looking forward to the option to skip SQL detection.

Definately odd! Thanks for the heads up on the machine name. I've run into the same problem on an install of our medical application, but as Trent has mentioned, we've never been able to reproduce it reliably.  I'll have to do some investigation to see if the machine name suspicion pans out with my experience with the issue. We use InstallAware for all of our installs (which we have otherwise had good luck with), so thier in-built SQL detection isn't something we have direct control over.

We did add an option to our medical app to skip the SQL Detection to get around the issue when it came up for me (I wasn't smart enough to check the machine name ). I'll talk to Trent and see if we can get that put into the StrataFrame install for the next build.  Worse case, that will give you a work around in case we can't pin down the sourc eof the problem and it crops up again.

Thanks again!

Had the same trouble. Error 269 when searching for SQL servers. Setup: new VM of Win7 prof. with VS2008 sp1, SQL 2005 express. Everything functioned except the install of StrataFrame. Machine name assigned during the install of Win7 was WIN-7OA2349UYYYAO. Changed the name to WIN7VM and the problems went away for the Strataframe install. If I had to guess, I would blame the dash.......



Mike

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

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?

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 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.

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?