Compilation Error (With Obfuscator Enabled) - for SAP GUI Scripting

[ericsato]

Hi all,

I tried to compile a script with obfucator enabled. It gave me following error.

1) first error was i used 7zip dll to do archive/zip operation.

2) 2nd error, register an event, to listen SAP gui session.

If compile without obfuscator, then no error. Run like a charms.

Any idea?

Cheers

 

-### Obfuscation Error: Found DllCallbackRegister() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: _7ZipSetOwnerWindowEx

C:DAutoItSAP_ARISE_product7Zip.au3(331,1) Warning for line:$hArchiveProc = DllCallbackRegister($sProcFunc, "int", "hwnd;uint;uint;ptr") 

 

-### Obfuscation Error: Found ObjEvent() statement using unsolvable Func, which will/could lead to problems running your obfuscated script.

>### current Func: btnAttachSAPClick

C:DAutoItSAP_ARISE_productMain Window.au3(164,1) Warning for line:ObjEvent($session, "SESS_") 

 

-#############################################################################################

-#### Obfuscator Found   2 Error(s)!!!!    This means your script could have problems running properly.  ####

-#############################################################################################

+> Obfuscator v1.0.30.4 finished obfuscating 14039 lines, stripped 16808 comment lines. created:C:DAutoItSAP_ARISE_productMain Window_Obfuscated.au3

 

[Melba23]

ericsato,

Welcome to the AutoIt forum.

I could tell you to read the Obfuscator thread where this has been covered many, many times - but that would be a very long read!

Basically Obfuscator looks for commands where it might have problems - normally using a variable within certain function calls, just like your 2 cases above. If you ask Obfuscator to obfuscate the script then these values might not be correct as there is no way for Obfuscator to know what should be in them as they are only determined at run-time.

What are you asking Obfuscator to do? If you are only stripping the script to reduce its size, then you can safely ignore the warnings as the original values will be valid at run-time. If you are actually obfuscating the script then you could well run into problems as the obfuscated values might not match. What parameters are you passing to Obfuscator?

M23

[ericsato]

Hi M23,

I found the solution. Just disable the string encryption and func rename. It works as charm.

Cheers