StrataFrame Forum » StrataFrame Application Framework - V1 » Issues » Installation of 1.7.0 trouble

RE: Installation of 1.7.0 trouble

Ivan George Borges — Fri, 16 Jul 2010 07:32:55 GMT

Glad it worked! ;)

Installation of 1.7.0 trouble

Kirk M Sherhart — Fri, 16 Jul 2010 07:32:55 GMT

I'm getting the following message during installation of 1.7.0. It fails during the "Searching for SQL Servers" part

[codesnippet]Runtime error
Line 269; '' is not a valid integer value[/codesnippet]

RE: Installation of 1.7.0 trouble

dgsoft — Fri, 16 Jul 2010 03:09:41 GMT

Thank you Ivan,
Yes, with new Installation Wizard it works.

RE: Installation of 1.7.0 trouble

Ivan George Borges — Thu, 15 Jul 2010 15:22:43 GMT

It looks like you are on version 1.7.0.6

Have you tried the 1.7.0.7?

RE: Installation of 1.7.0 trouble

dgsoft — Thu, 15 Jul 2010 14:29:29 GMT

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?

RE: Installation of 1.7.0 trouble

Alex Luyando — Thu, 18 Mar 2010 15:30:13 GMT

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

RE: Installation of 1.7.0 trouble

Alex Luyando — Thu, 18 Mar 2010 14:33:43 GMT

[quote][b]Trent L. Taylor (03/18/2010)[/b][hr]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.[/quote]

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! :)

RE: Installation of 1.7.0 trouble

Trent L. Taylor — Thu, 18 Mar 2010 12:57:05 GMT

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.

RE: Installation of 1.7.0 trouble

Alex Luyando — Thu, 18 Mar 2010 11:51:14 GMT

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

RE: Installation of 1.7.0 trouble

Greg McGuffey — Mon, 01 Mar 2010 12:20:15 GMT

[quote][b]Edhy Rijo (02/26/2010)[/b][hr]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...[/quote]

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

RE: Installation of 1.7.0 trouble

Trent L. Taylor — Mon, 01 Mar 2010 08:43:18 GMT

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.

RE: Installation of 1.7.0 trouble

Edhy Rijo — Fri, 26 Feb 2010 14:01:25 GMT

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.

RE: Installation of 1.7.0 trouble

Greg McGuffey — Fri, 26 Feb 2010 13:51:44 GMT

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.

RE: Installation of 1.7.0 trouble

Kirk M Sherhart — Thu, 25 Feb 2010 10:10:12 GMT

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.

RE: Installation of 1.7.0 trouble

Dustin Taylor — Thu, 25 Feb 2010 09:39:13 GMT

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!

RE: Installation of 1.7.0 trouble

Michael Keller — Wed, 24 Feb 2010 14:43:47 GMT

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

RE: Installation of 1.7.0 trouble

Trent L. Taylor — Mon, 12 Oct 2009 09:35:21 GMT

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

RE: Installation of 1.7.0 trouble

Jerry Carter — Sat, 10 Oct 2009 14:54:39 GMT

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?

RE: Installation of 1.7.0 trouble

Trent L. Taylor — Tue, 29 Sep 2009 08:52:14 GMT

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.

RE: Installation of 1.7.0 trouble

Jerry Carter — Mon, 28 Sep 2009 21:32:11 GMT

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.

RE: Installation of 1.7.0 trouble

Jerry Carter — Mon, 28 Sep 2009 20:39:53 GMT

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?

RE: Installation of 1.7.0 trouble

Kirk M Sherhart — Tue, 04 Aug 2009 08:31:13 GMT

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!

RE: Installation of 1.7.0 trouble

Trent L. Taylor — Mon, 03 Aug 2009 22:32:07 GMT

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?

RE: Installation of 1.7.0 trouble

Kirk M Sherhart — Mon, 03 Aug 2009 17:41:55 GMT

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.

RE: Installation of 1.7.0 trouble

Trent L. Taylor — Mon, 03 Aug 2009 17:21:25 GMT

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.