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

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!

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.

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.

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

We are investigating this on the IA side. We may change the way that this search takes place as we are, at present, allowing IA to do the search. We can turn the automatic search off altogether and it will never show the error, but it also requires that you know the SQL Server name...which seems like a simple thing, but we have a number of developers who are not only new to .NET, but new to SQL Server many times as well and this step is more difficult.



Also, I have seen this when people are loading on a VMWare environment as well, just FYI.

All server names I've used have been less than 15 characters, though almost all had a dash.

Add me to the list of users having this problem. My attempted install is on a new Windows XP Pro workstation; had no problem installing on the old workstation. The new workstation's name is SBK012DD62D1EMG, while the old one (which has no problem installing 1.7.0.6) is sbk012cs56d1... so perhaps length is indeed the issue.



By the way, re-reading Michael's post I think he's saying his workstation/VM's name is XXXXXX-YYYYY, not the SQL Server he's looking to connect to.



Due to corporate naming conventions will be difficult to get a name change to the workstation... Any predictions Trent on a new install that will resolve this?



TIA

________________
_____/ Regards,
____/ al

I will be posting a beta very shortly that will resolve this particular issue. For now we will just not scan the network for SQL Servers, which is what is causing the issue. I am waiting for an answer from our installation tool vendor on the root of the issue.

Great. Just to be clear, in our case at least it's not the name of the SQL Servers (they've not changed); it's the name on the workstation on which StrataFrame's being installed. So long as the beta will solve the problem, cool!


________________
_____/ Regards,
____/ al