\"MS SQL Server\" command - Server and Instance

[CandiceJones]

That's great to know! Thanks for sharing

[tie_gerben]

When I run the script Detect MS SQL Instances , it pops up a messagebos with '' is not a valid integer value.

So, has anyone found a solution to the original stated problem of this thread?:

it's displaying an error dialog while the "Looking for Servers" dialog displays. The error dialog states:

Runtime error in setup script:
Line 38: '' is not a valid integer value

I've bought the Install Aware Studio v8, and my script has run fine on Windows XP and Windows server 2003. This error pops up on a 2003.

Perhaps unrelated, but when I check the Vista User Account Control Elevation on the Application Requirements, the installer shows a messagebox that This product requires at least User Account Control Elevation, .... on Windows 2003.

[CandiceJones]

We're unable to reproduce that issue at our end, do you have any specific configuration instructions for it? Perhaps you can upload a VM which exhibits this behavior - PM me for our FTP server upload details.

As for your second question, as already documented in the help file, that option explicitly checks for UAC elevation, which is available only on Vista. You might therefore want to wrap that code inside the MSIcode editor around another block which checks whether the OS is Vista or newer, and that will take care of it.

[gls]

We also have this error of "Detect MS SQL Instances" plugin command on one of machines.

IMHO the it is not a big problem that due to some reason in some circumstances it cannot properly detect some SQL Instances. Such things happen.

The REAL problem is that the command is unsafe and crashes entire installation process. Whereas it should simply return an empty list of instances in case of a trouble.

Is there a fix or any workaround availble?

Thanks

[CandiceJones]

Please contact me privately to test a fixed version. Thank you.

[etedali]

Hi Candace,

Thanks for the replay. It is good to know someone will reply.

Actually I figured out the problem and the first post on this thread had the hints to solve the problem. You might pass on that there is a problem with the Sample Project "SQL Server Connection". In the MSIcode on line 72 the SELECTEDSERVER variable is split into SERVERNAME AND INSTANCENAME. Right after that, if INSTANCENAME is blank it is set to "EXPRESS". For SQL2005, INSTANCENAME will almost always be blank and setting INSTANCENAME to "EXPRESS" means you won't connect. Once I changed INSTANCENAME to stay blank if it was blank then the sample project connects just fine.

Hope this helps others trying this. Eval is looking good so far.

Thanks,
Darren

sorry I cant't to connect to Db,can you help me what i must put in Instance?

[FrancescoT]

Dear User,

you should simply enter the MS SQL Instance name and this depends on the MS SQL instance you are trying to connect to.

Regards

[etedali]

Hi All
i want to connect to db that i create in sql server 2008 ,i first click on SQL Database in Server Configuration, and then click new and choose MS SQL script,but i don't jnow but i must write in INSTANCE,
my install can't connect to db,plz help me
thanks
best Regards

[etedali]

Dear User,

you should simply enter the MS SQL Instance name and this depends on the MS SQL instance you are trying to connect to.

Regards

thanks for your answer FrancescoT
how can i understand what is my instance ?

[FrancescoT]

Dear User,

You could use the "Detect MS SQL Instances" command in your script ... for a list of all available Instances on target system.
Please refer to IA documentation for more details.

Regards