comptonb
2006-06-21 17:41:53 UTC
History: I have successfully used the NDS ODBC driver for years to do
user auditing with MS Access97 on WinNT and Win2000. For the last couple
of years our IS Security group has been using several versions of Excel
from 97 to 2003 to do the same thing, all on Win2000.
Recently we have gone through several Novell consulting projects and due
to their recommendations many NetWare/eDirectory upgrades were performed.
With those changes, Excel on the Security PC's started returning hex
numbers for the true/false fields and date/time fields (like Login
Disabled and Login Time.) I could not reproduce that error on my machines
with Access but upgrading Security to the latest ODBC R/W driver fixed
that problem. At the same time as all of this we upgraded to Novell
Client 4.91 SP2 and ConsoleOne 1.3.6e. However I was able to eliminate
those as the cause so I believe it was the backend changes.
PROBLEM: Over a weekend in which I have not been able to locate any
changes, the Security group came in and their Excel MS Queries to our
largest organization object, they suddenedly responded in one of two ways:
either Excel crashed completely or the query returned no data. I had
them reproduce the error while querying soley on "NDS_FullName" from the
table "UserNDS". Using both and new MDAC's as well as different NDS ODBC
versions, we have reproduced the errors on all Win2000 SP2 and SP4
computers and in both Access97 and Excel2003. But on both my WinXP SP1 and
WinNT 4 SP6a machines, I can still do queries fine in Access97 and Crystal
Reports 8. It fails on my Win2000 SP2 machine. Other than the OS I can
not find anything different on my working systems from the failing
systems. I've also tried a variety of credentials with various privilege
levels.
Fyi, we are running Identify Manager 2.0 (upgraded from 1.1) using the
NDS-NDS and NDS to AD drivers plus a custom driver that just calls a
command line utility to sync passwords in the foreign application. We
have both the DirXML 1.1 and IDM 2.0 driver set eDir partitions present
now in that organization. But again I have not been able to identify any
changes in the time frame involved.
Any ideas? Known bug of some kind?
Thanks,
Bill
user auditing with MS Access97 on WinNT and Win2000. For the last couple
of years our IS Security group has been using several versions of Excel
from 97 to 2003 to do the same thing, all on Win2000.
Recently we have gone through several Novell consulting projects and due
to their recommendations many NetWare/eDirectory upgrades were performed.
With those changes, Excel on the Security PC's started returning hex
numbers for the true/false fields and date/time fields (like Login
Disabled and Login Time.) I could not reproduce that error on my machines
with Access but upgrading Security to the latest ODBC R/W driver fixed
that problem. At the same time as all of this we upgraded to Novell
Client 4.91 SP2 and ConsoleOne 1.3.6e. However I was able to eliminate
those as the cause so I believe it was the backend changes.
PROBLEM: Over a weekend in which I have not been able to locate any
changes, the Security group came in and their Excel MS Queries to our
largest organization object, they suddenedly responded in one of two ways:
either Excel crashed completely or the query returned no data. I had
them reproduce the error while querying soley on "NDS_FullName" from the
table "UserNDS". Using both and new MDAC's as well as different NDS ODBC
versions, we have reproduced the errors on all Win2000 SP2 and SP4
computers and in both Access97 and Excel2003. But on both my WinXP SP1 and
WinNT 4 SP6a machines, I can still do queries fine in Access97 and Crystal
Reports 8. It fails on my Win2000 SP2 machine. Other than the OS I can
not find anything different on my working systems from the failing
systems. I've also tried a variety of credentials with various privilege
levels.
Fyi, we are running Identify Manager 2.0 (upgraded from 1.1) using the
NDS-NDS and NDS to AD drivers plus a custom driver that just calls a
command line utility to sync passwords in the foreign application. We
have both the DirXML 1.1 and IDM 2.0 driver set eDir partitions present
now in that organization. But again I have not been able to identify any
changes in the time frame involved.
Any ideas? Known bug of some kind?
Thanks,
Bill