Jump to content

_AD_Open Fails When Script is Compiled


 Share

Recommended Posts

I kept having problems with my Active Directory scripts. I finally discovered that they work fine before being compiled but after compiling they fail. I have narrowed it down to simply testing _AD_Open. For instance, any script that includes "$iResult = _AD_Open()" works until I compile the script. The compiled script fails with @Error = 4. Please note that I only log onto the computer with my Domain account. What am I missing here? Also, I do not use SciTE, I use Notepad++ if that matters...

Link to comment
Share on other sites

Copy the exe to another location and try again. I once had problems with "secure locations" in Windows. You can only start programs from directories defined as secure.
http://blogs.technet.com/b/askds/archive/2008/01/31/security-policy-settings-and-user-account-control.aspx

My UDFs and Tutorials:

Spoiler

UDFs:
Active Directory (NEW 2022-02-19 - Version 1.6.1.0) - Download - General Help & Support - Example Scripts - Wiki
ExcelChart (2017-07-21 - Version 0.4.0.1) - Download - General Help & Support - Example Scripts
OutlookEX (2021-11-16 - Version 1.7.0.0) - Download - General Help & Support - Example Scripts - Wiki
OutlookEX_GUI (2021-04-13 - Version 1.4.0.0) - Download
Outlook Tools (2019-07-22 - Version 0.6.0.0) - Download - General Help & Support - Wiki
PowerPoint (2021-08-31 - Version 1.5.0.0) - Download - General Help & Support - Example Scripts - Wiki
Task Scheduler (NEW 2022-07-28 - Version 1.6.0.1) - Download - General Help & Support - Wiki

Standard UDFs:
Excel - Example Scripts - Wiki
Word - Wiki

Tutorials:
ADO - Wiki
WebDriver - Wiki

 

Link to comment
Share on other sites

I think you are on to something. I just held shift key and right clicked the exe so I could choose run as a different user. I then entered my username and password and it worked fine with one caveat, I had to copy the exe to the desktop. If I tried to run it from the mapped network drive it told me that the drive did not exist. I see this all the time at my location and I finally found that I have to turn on "enablelinkedconnections" in the registry (change registry setting from 0 to 1). This must be the problem. As a side note, I have been working very hard on some scripts that use your AD.au3 UDF. I want to tell you how great it is to know that you support it. You are truly a fantastic person and I thank you!

Link to comment
Share on other sites

Thanks! Glad you like the UDF and the support you get from the forum :)

My UDFs and Tutorials:

Spoiler

UDFs:
Active Directory (NEW 2022-02-19 - Version 1.6.1.0) - Download - General Help & Support - Example Scripts - Wiki
ExcelChart (2017-07-21 - Version 0.4.0.1) - Download - General Help & Support - Example Scripts
OutlookEX (2021-11-16 - Version 1.7.0.0) - Download - General Help & Support - Example Scripts - Wiki
OutlookEX_GUI (2021-04-13 - Version 1.4.0.0) - Download
Outlook Tools (2019-07-22 - Version 0.6.0.0) - Download - General Help & Support - Wiki
PowerPoint (2021-08-31 - Version 1.5.0.0) - Download - General Help & Support - Example Scripts - Wiki
Task Scheduler (NEW 2022-07-28 - Version 1.6.0.1) - Download - General Help & Support - Wiki

Standard UDFs:
Excel - Example Scripts - Wiki
Word - Wiki

Tutorials:
ADO - Wiki
WebDriver - Wiki

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...