AD UDF Error

[ReitzelTechnology]

I get an error on my complied scripts. Attached error. Only on the ones that have AD.au3 included.

Code is attached too. It is an application that runs all the time and at certain times will make sure the default printer is set. It only does it randomly it seems....

PrintManger_ADGroups.au3

[water]

What version of the UDF do you use in your code? So we can check to which function the line number points to.

[ReitzelTechnology]

The newest one thats stable, 1.2.0

[water]

Line 4054 is a comment line just before function _AD_ObjectExistsInSchema.

Do you use obfuscator to remove unneeded functions and variables?

If yes then you will find a file @Scriptname & _obfuscated.au3 in your script directory. Can you tell me what line 4054 is in this file?

[ReitzelTechnology]

No I did not. Just straight complied it.

[water]

In the code you posted the include statement for the AD UDF is the first statement to be executed. So line 4054 has to be in the AD UDF.

Can you please post line 4054 from your version of the AD UDF and the lines up to the next function?

[ReitzelTechnology]

Here is lines 4054 to 4072. the first line is 4054.

; ===============================================================================================================================
Func _AD_ObjectExistsInSchema($sAD_Object, $sAD_Property = "LDAPDisplayName")
Local $sAD_SchemaNamingContext = $oAD_RootDSE.Get("SchemaNamingContext")
$oAD_Command.CommandText = "<LDAP://" & $sAD_HostServer & "/" & $sAD_SchemaNamingContext & ">;(" & $sAD_Property & "=" & $sAD_Object & ");ADsPath;subtree"
Local $oAD_RecordSet = $oAD_Command.Execute ; Retrieve the ADsPath for the object, if it exists
If IsObj($oAD_RecordSet) Then
  If $oAD_RecordSet.RecordCount = 1 Then
   Return 1
  ElseIf $oAD_RecordSet.RecordCount > 1 Then
   Return SetError($oAD_RecordSet.RecordCount, 0, 0)
  Else
   Return SetError(1, 0, 0)
  EndIf
Else
  Return SetError(1, 0, 0)
EndIf
EndFunc   ;==>_AD_ObjectExistsInSchema

Edited April 24, 2012 by ReitzelTechnology

[water]

Exactly as in my copy of the UDF

Could you compile your script with

$iAD_Debug = 3

after the #include statement?

This will write error information to the default debugging file @ScriptDir & "AD_Debug.txt"

[ReitzelTechnology]

We do not even use that command in any of the applications. They only do it once in a blue moon.

[ReitzelTechnology]

Exactly as in my copy of the UDF

Could you compile your script with

$iAD_Debug = 3

after the #include statement?

This will write error information to the default debugging file @ScriptDir & "AD_Debug.txt"

Ok done

[water]

I suspect that the line number doesn't point to where we are looking at the moment.

I hope the debug information will tell us why the object the UDF expects isn't an object.

[ReitzelTechnology]

Ok. I will post back if something happens. It goes for a while with no errors then has an error.

[water]

Thanks. I'm really curious what the debug file will tell us

[BrewManNH]

When the script is compiled, the comments are stripped, so that's probably throwing the line number off. Also, any other includes would cause the line to move up or down in the script, or lines continued to the next line with the "_" character.

[water]

Hi BrewManNH,

is this (stripping off the comments) true even when the OP doesn't use the Obfuscator?

[BrewManNH]

As far as I am aware of, all comments are stripped when it's compiled, regardless of whether you use Obfuscator or not. Only the developers know for sure though, and I'm not one of them.

[water]

According to the compiler removes all comments (";", "#cs" and "#ce") so line numbers you get from a compiled script are useless.

[BrewManNH]

Guess that answers that question, I knew I had read it somewhere, but for the life of me couldn't dig up the reference for it.

[BrewManNH]

If someone does want a better understanding of how to get the correct line number from a compiled script, might shed some light on the subject. Note that you'd need the beta version of Obfuscator linked in that thread to make it work.

[water]

Right, question answered. In this case we have to wait until the problem occurres again and hope that the debug file gives us some information to locate the error.