Several scripts will not run on NEW users pc

[MarkH0708]

As the title states, we have several scripts used to strip address information from a PDF (it links to an Access Database to gather coordinates based on the customer selected).  I have a NEW employee who is unable to run these scripts.  I tried logging into his PC as my user and also could not run them even though they run fine from my PC.

I have the code for these scripts, but the error "line number" doesn't match up with the code as it exceeds the code length.

I also tried a very simple code that I wrote while trying to learn some basics.  This user IS able to run that simplistic script with no difficulties.

I am out of ideas as to what to look for.  I have already installed, uninstalled, installed, uninstalled, and then installed.

I'm including a snip of the error as an attachment.  We get different errors when running the EXE version than when the AU3 is run.

 

Any help would be greatly appreciated.

 

Edited March 13 by Melba23
Removed image

[JLogan3o13]

Without seeing the actual code, it is more than a little difficult to divine what the issue is. However, from the error it appears the $PDFLib object is not being properly created, thus you are unable to call the UnlockKey method. It appears that you need to add some error-checking around whichever function/lines create the object itself to ensure that section does not fail.

[Danp2]

Which PDF library are you using to access the PDF files? It's possible that you need to install it or register a DLL.

P.S. You may want to obscure it if that's your actual unlock key above. 😧

[MarkH0708]

@Danp2  I can't see how to obscure.  It won't allow me to edit it any longer.

[Danp2]

@MarkH0708Likely because you are viewed as a new user. One of the mods will be by to unlock that feature for you.

[Melba23]

MarkH0708,

You should now have "Edit" priviledges.

M23

Edit: And I have removed the image in question - just replace it with a redacted version.

Edited March 13 by Melba23

[MarkH0708]

20 minutes ago, Melba23 said:

MarkH0708,

You should now have "Edit" priviledges.

M23

Edit: And I have removed the image in question - just replace it with a redacted version.

THANK YOU!

[mistersquirrle]

2 hours ago, MarkH0708 said:

I have the code for these scripts, but the error "line number" doesn't match up with the code as it exceeds the code length.

The reason for this is that when the script is compiled, all the code from the #include's are combined into 1 source file. As well there may be some things expanded/stripped/replaced in the version that gets compiled. There's an option when compiling to output the "stripped" version that should point you to the correct line:

Quote

Au3Stripper: /mo : Just merges the Include files into the source and strips the Comments.
      This is similar to aut2exe and helps finding the errorline.

#Au3Stripper_Parameters=/mo

Now when I compile I go from a ~175 line script to a 23571 line script (because I have a lot of included files in this test script). The files I have now are test.au3 (original), test_stripped.au3 (stripped/expanded original that should match your line number, though it may be 1 off now since you need to add the #Au3Stripper_Parameters line), and text.exe.

 

Other than that JLogan3o13 and Danp2 posts are probably the answer, in that however you're creating your PDF object isn't working because the DLL or COM object isn't registered. You should add some logging/error checking around where you create the PDF object (ObjGet/ObjCreate) and make sure there's not an error. If there is, output the error and exit the script.

Something else that you can do is if you're using a specific DLL or file for this PDF object, you can try to include it in the main script/exe with FileInstall: https://www.autoitscript.com/autoit3/docs/functions/FileInstall.htm

But as mentioned, it's hard to give more information without knowing what you're using, and how you're creating the object. If you get the chance, try to post some code that is centered around where you're getting this error (likely with the ObjCreate/Get, and then calling the unlock part, obviously without your unlock code).

[MarkH0708]

We will begin digging into the DLLs to check on registration.  As these scripts (both AU3 and EXE files) run for 3 of us in the department, I don't believe the code is wrong.  I was just unsure what to be looking for. 

As you can imagine, deciphering someone's undocumented code that no longer works here is challenging.

Thanks for the suggestions so far.