ODBC Driver for eDirectory doesn't work in XP Sp2?

Hi,

I was previously using the ODBC driver with Windows XP SP1 without any
problems, but after upgrading to SP2 the driver no longer allows me to
navigate the eDirectory tree to select a context.  The navigation pane on
the interface is greyed out.  I've tried disabling the Windows Firewall
but this made no difference.

Can you please confirm for me that the driver has been successfully used
with XP Sp2?  It's possible that there is a profile customisation in our
SOE which is blocking the application.

Thanks in advance,
Rob

Hi

It's working for me... Microsoft Windows XP Professional Version 2002 
Service Pack 2.

just to state the obvious, you need to uncheck the use default box to 
un-grey the browser window.

You might try turning on tracing to see if there's anything useful in 
root_dir\sql.log.

Also did you change anything about the NW client?  preferred server or tree 
etc?  Can you make connections using the novell client login?

Thanks
Susan 

Susan Perrin wrote:
> It's working for me... Microsoft Windows XP Professional Version 2002 
> Service Pack 2.

OK, that's bad.  It means most likely there's something in the network
Windows profiles killing ODBC.  Now I have to figure out a way of logging
into Novell without applying the profile but still ending up as an
Administrator.  Think I'll have to create my own test profile.

> just to state the obvious, you need to uncheck the use default box to 
> un-grey the browser window.

Yes.  However, when the ODBC driver is working, the root of the tree is
displayed even when the checkbox is ticked.  On this PC, the tree
navigation pane is blank regardless of the checkbox state.  I tried
entering a context manually but using the DSN failed.

> You might try turning on tracing to see if there's anything useful in 
> root_dirsql.log.

The log using the above broken DSN doesn't tell me much more useful than
the error displayed by MS Access; "[Novell][ODBC Driver For
eDirectory][Client32] Could not resolve tree or server name."

> Also did you change anything about the NW client?  preferred server or tree

> etc?  Can you make connections using the novell client login?

The client is version 4.91E for XP.  At the time I have tried to create
the DSN I am logged into Novell and able to navigate network drives.  I am
an eDirecory admin in the context so it isn't a permissions issue -
besides, it works perfectly on another PC which doesn't have SP2. 
Interestingly, both computers are using the same XP profiles, logged into
the same context with the same account.

Thanks for your response!

Rob

Hi

> OK, that's bad

If you don't mind my saying so,  from my perspective it's good.

> "Could not resolve tree or server name"

That might be useful... If you disconnect all your connections and then hit 
the Novell client login button, advanced, trees, do you see any trees?  What 
is your preferred server set to?  What is your preferred tree?  I wonder if 
it's related to a slp problem...

Thanks for mentioning the admin rights... that rules out a couple of things.

Susan

Susan Perrin wrote:
> > OK, that's bad
> If you don't mind my saying so,  from my perspective it's good.

:) Naturally - it means you have a support OS and the driver still works. 
However, it means that something our gurus in Brisbane have done in the
profiles has probably broken ODBC.

> > "Could not resolve tree or server name"
> That might be useful... If you disconnect all your connections and then hit

> the Novell client login button, advanced, trees, do you see any trees?

I'll try it and see.

> What is your preferred server set to?  What is your preferred tree?

Those are no different to the settings on the other non-SP2 PC on which
the ODBC drivers work.  We don't set a preferred server because we are
logging into a cluster.

> I wonder if it's related to a slp problem...
> Thanks for mentioning the admin rights... that rules out a couple of
things.

I'll try the above and post again later.

Rob