Glad it worked!

Thank you Ivan,

Yes, with new Installation Wizard it works.

It looks like you are on version 1.7.0.6

Have you tried the 1.7.0.7?

Hmmm...today I have the same problem when I try to install StrataFrame on home Windows 7 machine.

What the solution for this? Rename my machine computer name? How many characters it must be? Why installer not fixed if its well known problem?

FWIW in case it helps someone else - Was able to rename the workstation (dropped 3 characters to bring the total character count for the name to 3) and the install is working (i.e., it's gotten beyond the error point).




________________
_____/ Regards,
____/ al

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

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.

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

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

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.