Page 1 of 1

MS SQL Server connection failure

Posted: Tue Nov 13, 2012 3:25 am
by tzachk
Hi Francesco,

I'm trying to connect to MS SQL DB and always get CONNECT_ERROR.
I've double checked the credentials and of course can manually connect to the DB.

Is there a plcae I can get the real connection error instead of the CONNECT_ERROR? as this will shed light on what is the problem.

Regards,
T.

Re: MS SQL Server connection failure

Posted: Tue Nov 13, 2012 8:44 am
by FrancescoT
Dear Tzachk,

In addition to the error values returned by "MS SQL SERVER" command, when Abort Execution on Script Error is checked, and an error occurs during script execution (where database and server connections succeeded), this variable holds detailed error information as follows: The variable is split into two parts, delineated by the string literal DELINEATOR. The first part of the variable holds the exact textual error message. The second part of the variable holds the exact SQL script fragment where execution errors occured. You may parse the variable using the Parse String function to extract both fields and utilize them separately.

Hope this helps you.

Regards

Re: MS SQL Server connection failure

Posted: Tue Nov 13, 2012 8:47 am
by tzachk
Hi Francesco,

When you say "this variable", which variable you refer to?

Regards,
T.

Re: MS SQL Server connection failure

Posted: Tue Nov 13, 2012 10:10 am
by FrancescoT
Dear Tzack,

I mean the one you used with "Return result in variable" command field.

Regards

Re: MS SQL Server connection failure

Posted: Wed Nov 14, 2012 2:13 am
by tzachk
Hi Francesco,

This variable just returns CONNECT_ERROR, not the actual issue of why it can't connect.
I'm logging the SQL server connections and I can't see any record that the installer is trying to connect to the server.

ideas?

Regards,
T.

Re: MS SQL Server connection failure

Posted: Wed Nov 14, 2012 3:18 am
by tzachk
Hi Francesco,

I found the problem.
I'm trying to connect to the SQL server to see if a specific Database exists.
It seems that the MS SQL Server command returns CONNECT_ERROR even if it can connect to the server, but the database do not exist. According to the documentation is should return CONNECT_DATABASE_ERROR, and it is important that it shall return this error as I check it during the install.

Any idea on this?

Regards,
T.

Re: MS SQL Server connection failure

Posted: Wed Nov 14, 2012 8:33 am
by FrancescoT
Dear Tzack,

if you can post a sample project that demostrate the issue I will try to verify it.

Regards

Re: MS SQL Server connection failure

Posted: Thu Nov 15, 2012 7:25 am
by tzachk
Hi Francesco,

The sample project attached
Fix the credentials in the MS SQL server to match your DB server.
If you add a value for Database that does not exists field and try to connect you'll get CONNECT_ERROR, when you need to get CONNECT_DATABASE_ERROR. If you remove the Database value, you'll get SUCCESS (if the login credentials are correct that is).

Regards,
T.

Re: MS SQL Server connection failure

Posted: Thu Nov 15, 2012 9:13 am
by FrancescoT
I will test it ASAP.

Regards

Re: MS SQL Server connection failure

Posted: Mon Nov 19, 2012 8:21 am
by tzachk
i Francesco,

This issue is becoming urgent.
Can you please update me on the status.

Regards,
T.

Re: MS SQL Server connection failure

Posted: Tue Nov 20, 2012 4:16 am
by lbertoldi
Same here, I get this error for no obvious reasons on different target machines.
Thanks

Re: MS SQL Server connection failure

Posted: Tue Nov 20, 2012 7:57 am
by FrancescoT
Dear Users,

actually I can only confirm this behaviour.
I'm fowarding my test results to our dev team.

I will post further informations as soon as I receive an answer.

Regards

Re: MS SQL Server connection failure

Posted: Sun Nov 25, 2012 1:44 am
by tzachk
Hi Francesco,

Any news?
Two weeks have passed since I published this issue.
Do I need (AGAIN!), to code a workaround for this issue?

Regards,
T.

Re: MS SQL Server connection failure

Posted: Mon Nov 26, 2012 8:52 am
by FrancescoT
Dear Tzack,

The issue has been logged to our fixes list but actually, I can tell you when a fix will be available.

As possible workaround you could check via MS-SQL script if the passed database exist.

Regards