Home > Archive > LDAP > June 2007 > Error 83 trying to use BigInt with Net::LDAP replace
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Error 83 trying to use BigInt with Net::LDAP replace
|
|
| Mark.Herzfeld@jci.com 2007-06-29, 8:14 am |
| I have a field (18 characters) TimeStamp field that needs to be updated on
an ActiveDirectory Ldap Server.
I have tried to use Net::LDAP to do so, but when the INT gets converted to
a float (e.g. after 15 digits, etc.) the Update fails.
So, I created a variable with Math::BigInt, and passed that variable to
the ldap replace, only to receive the following error:
The modify Returncode is 83
C<Net::LDAP> encountered an error while encoding the request packet that
would
have been sent to the server
I have looked on CPAN and can not find mention of not being able to update
an attribute field that has a great deal of digits (18 to be exact).
If this a known issue?
Thanks
Mark Herzfeld
Johnson Controls
Global Infrastructure Architecture
414-524-2888
| |
| Chris Ridd 2007-06-29, 7:16 pm |
| On 28/6/07 2:46, "Mark.Herzfeld@jci.com" <Mark.Herzfeld@jci.com> wrote:
> I have a field (18 characters) TimeStamp field that needs to be updated on
> an ActiveDirectory Ldap Server.
>
> I have tried to use Net::LDAP to do so, but when the INT gets converted to
> a float (e.g. after 15 digits, etc.) the Update fails.
>
> So, I created a variable with Math::BigInt, and passed that variable to
> the ldap replace, only to receive the following error:
> The modify Returncode is 83
> C<Net::LDAP> encountered an error while encoding the request packet that
> would
> have been sent to the server
>
>
> I have looked on CPAN and can not find mention of not being able to update
> an attribute field that has a great deal of digits (18 to be exact).
>
> If this a known issue?
I think you're doing something wrong, as Net::LDAP shouldn't be attempting
to interpret any numeric attribute values.
It is my guess (not knowing the MAD schema) that a timestamp is transferred
in protocol as a string of digit characters and not a BER INTEGER. So what
happens if you pass in the timestamp as a string, ie surround it with quote
marks?
Cheers,
Chris
|
|
|
|
|