Works before compilation after not

[AndiSS]

Hi all,

following script:

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_Outfile=\\sprickdi\user\BIS\Programme\OLEDBCheck.exe

#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

$ADO_Access = "Provider=SQLOLEDB.1;User ID=PWD; Password=Yep!;Initial Catalog=identPlus;Data Source=SEMIRAMIS"
;$ADO_Access = "Provider=SQLNCLI.1;Server=192.168.1.3;Database=identPlus;Uid=PWD;Pwd=Yep!"
$oMyError = ObjEvent("AutoIt.Error", "MyErrFunc")
$ObjConn = ObjCreate("ADODB.Connection")

$ObjConn.open($ADO_Access & ";")
If @error Then
    MsgBox(0,"","ObjOpen Failed dude :(")
Else
    MsgBox(0,"","ObjOpen Success!! hahaha we did it :), Query away :)")
EndIf

Func MyErrFunc()
    MsgBox(0,"","AutoItCOM Test" & @CRLF & "We intercepted a COM Error !" & @CRLF & _
            "err.description is: " & @TAB & $oMyError.description & @CRLF & _
            "err.windescription:" & @TAB & $oMyError.windescription & @CRLF & _
            "err.number is: " & @TAB & Hex($oMyError.number, 8) & @CRLF & _
            "err.lastdllerror is: " & @TAB & $oMyError.lastdllerror & @CRLF & _
            "err.scriptline is: " & @TAB & $oMyError.scriptline & @CRLF & _
            "err.source is: " & @TAB & $oMyError.source & @CRLF & _
            "err.helpfile is: " & @TAB & $oMyError.helpfile & @CRLF & _
            "err.helpcontext is: " & @TAB & $oMyError.helpcontext & @CRLF)
    SetError(1)
EndFunc   ;==>MyErrFunc

Runs perfectly on my machine (Win 7 64 bit) either before compiling (F5) and after compiling. The same script works with F5 on two other Win 7 64bit machines, but won't run after compilation. I don't know where to dig now. Can anyone give me a hint, what the problem could be? It seems that somehow the communication with the SQL Server is blocked, when I run the compiled file. But why does it work with F5? The error I get, differs if I use line 6 or 7. With line six it is:  ConnectionOpen PreLoginHandshake()..... So it's usual an network error. Firewall, Windows Defender are disabled. There are no other antivirus programs installed.

AutoIt Version is 3.3.14.0

 

[mLipok]

Can you try _SQL.au3 UDF (look in my signature) ?

 

 

[AndiSS]

Hi,

thanks for the quick reply. 

I tested your UDF with the following example:

#include <_sql.au3>
#include <array.au3>

Opt ("trayIconDebug",1)

Msgbox(0,"","Start the Script and load the error handler")
     _SQL_RegisterErrorHandler();register the error handler to prevent hard crash on COM error

    $oADODB = _SQL_Startup()
    If $oADODB = $SQL_ERROR then Msgbox(0 + 16 +262144,"Error",_SQL_GetErrMsg())


    If _sql_Connect(-1,"SEMIRAMIS","BDE","PWD", "Yep!") = $SQL_ERROR then
        Msgbox(0 + 16 +262144,"Error",_SQL_GetErrMsg())
        _SQL_Close()
        Exit
    EndIf

Unfortunately I get the same result. Without compilation it works on all machines. With compilation it gives me an connection error on the other machines. By the way I have the same error with an AutoIt Script creating an Object with a Crystal report Runtime dll. Here everything works great without compilation. If i use the compiled script everything works fine (loading the report, setting printer etc.) until the machine trys to read the rowsets. Here I also get an connection error.   Why is it working without compiling and why not after compiling. (It makes no difference whether I crate the 32bit or 64bit version)

[AndiSS]

It seems to be the exclamation mark in the password.I changed the password to a password without special characters and it works. Oh my god. Three days of digging....

[mLipok]

Good for you, at this 3 days I hope you get a lot of new knowledge.

Edited July 21, 2015 by mLipok

[AndiSS]

 I don't get it. I don't know why it worked or what I tried out, but now it is not working anymore. Neither with nor without an exclamation mark. So i would be grateful for any hints....

[mLipok]

What AutoIt version ?

Do you use this script on the same computer ?

Did you register COM Error handler ?
What kind of error you see in console ?
 

[AndiSS]

AutoIt Version is 3.3.14.0 (see first post)

Same computer script and exe.  

Yep, I did register the COM error handler and it tells me the above mentioned error of DBNETLIB ConnectionOpen PreLoginHandshake general network error.

BUT, in the meantime I found out, that the fault is, that I start the exe from a Network drive. If I start the exe from the desktop, then it works. So it must have something to do with the UAC or other group policy management stuff. Any advise? As a workaround i will start the exe from the local drives.

Thank you.

 

[mLipok]

Each AV software when sees that the program is run from a network environment treats him with increased caution.
How you have set TimeOut - try to use following function 

_SQL_CommandTimeout()
_SQL_ConnectionTimeout()

 

from UDF which I mention before.

Edit: do you have instaled SQLNCLI ??

Which SQL Server Version ?

Edited July 21, 2015 by mLipok

[AndiSS]

CommandTimeout is 30 and ConnectionTimeout is 15. Changing does not work, because of the rights the user has. 

I have installed SQLNCLI and if i use that in my connection string I get the error "named pipes provider no process is on the other end of the pipe" although named pipes are activated in my SQL Server (2005 by the way)

 

Something else I found out. If I am logged in as a Active Directory Administrator it works even from the network drive. The non working user has also full rights on the network drive, but not in the active directory.

 

[mLipok]

I have installed SQLNCLI and if i use that in my connection string I get the error "named pipes provider no process is on the other end of the pipe" although named pipes are activated in my SQL Server (2005 by the way)

how you are using SQLNCLI in your Connection string ?

try to use 
_SQL_Connect()

look also inside 
_SQL_CONNECTION_STRING_SQLAuth($sServer, $sDBname, $sUserName, $sPassword)

 

[mLipok]

Something else I found out. If I am logged in as a Active Directory Administrator it works even from the network drive. The non working user has also full rights on the network drive, but not in the active directory.

You are using SQL USER or Windows User authentication to connect to your SQL server ?.

[AndiSS]

I tried both. Same result

I am not atat the Keyboard anymore. I will try tomorrow.  Thanks for your help. 

Edited July 21, 2015 by AndiSS

[Bowmore]

Did you compile your exe as 64 bit by any chance? A lot of COM stuff is only available as 32 bit and won't work when called from a 64 bit exe.

Try adding the following line near the top of your script and recompiling.

#AutoIt3Wrapper_UseX64=N

 

 

Edited July 21, 2015 by Bowmore

[mLipok]

Did you compile your exe as 64 bit by any chance? A lot of COM stuff is only available as 32 bit and won't work when called from a 64 bit exe.

Try adding the following line near the top of your script and recompiling.

#AutoIt3Wrapper_UseX64=N

I check it with my scirpt and _sql.au3 UDF.

To be sure I used also this:

MsgBox(0, '@AutoItX64', @AutoItX64)

 

And there is no difference (for me) if I use 32 or 64 bit AutoIt.

_sql.au3 works correctly.

but I have no Active Directory on my Home notebook (where I test it), and I have SQL 2014 Express on my home notebook.
So my test environment is different.

and Waiting for OP response.

 

[AndiSS]

Ok. First of all thanks for all your help.

I do not believe that the fault is caused by either

• 32bit or 64 bit compilation (tried it often)
• wrong connection string or use of the mLipoks UDF (works perfectly on the same machine, if I start the exe from a local drive an not from the network drive)
• wrong configured SQL Server  (works, if the autoit exe is started from a local drive)
• use of SQLNCLI or SQLOLEDB (both work started from local drive and do not work stated from a network drive)
• use of windows user or sql user authentication (both work started from local drive and do not work stated from a network drive)

So it works, if

• I start the script by F5 (surely because then it is started locally) or
• I start the compiled exe from a local drive or
• I start the script as a domain admin (for example if i put the used domain user domainname\bis to the domain admin group of our active directory it works, if I take him away from that group it does not work)

So i believe the error has something to do with the Windows rights management. I will play around some more with the UAC, trusted sites, policy management etc.

 

[mLipok]

AV/Firewall software?  

Edit:

Of course if this AV/Firewall software have config related to yours domain user,  loged to this compute. 

Edited July 22, 2015 by mLipok

[mLipok]

BTW. Do you check SQL server log? Is there any information about rejecting this connection? 

[AndiSS]

I had already disabled the Firewall and the AV. No effect.

The SQL server and the Windows Security log say nothing about rejecting.

UAC and Intranet Securitiy settings (internet explorer setting) do not have any effect.

It works, if i make the user a member of the domain admin or member of the also built in group backup operator or server operator. But that can not be the solution.

For now, I wrote an addition script which copys the exe from the network drive to the local drive and starts it from there. Now the machine is in the production again and our palettes are being packed and labeled again. It's a workaround, but it should be ok for now.