Client drives and "path"

[wilsona]

I have come across a problem that is driving us crazy.... We have an oracle thick-client program accessed as a published application as normal. Some users have their client drives mapped. Some of these users get SQLnet errors when trying to access the application, some don't. If we turn off those users client drive mappings, they are OK. These users seem to be those who also have sqlnet installed locally on their PC. The path variable on the metaframe servers does not include any local drives, but when they run the app it looks at their local drives when trying to connect to the backend database...Anybody got any ideas why?

 

[BeerGood]

Don't you just hate it when your clients are thick? ;-)

Anyhoo, I'd check the settings in the ODBC/DSN on the server. Eg the dsn may be setup on the server to check for "stuff" on c: and for some users their drive c (after connecting to citrix) is their local hard drive, and for others it's the c: drive on the server? Might not be your problem, but just a thought.

Cheers

 

[wilsona]

Thanks for the reply but it's an oracle backend database which is accessed via sqlnet, so there is no ODBC stuff involved. It definitely is looking for an sqlnet component on hte client.

 

[CitrixEngineer]

I think it's checking the path for the Oracle "ORAHOME" variable (or similar, depending on your version).

It'd be better if all clients ran their Oracle apps via thin client (or not, depending on the front end - some are nasty bloated Java affairs!).

Anyway, if you can persuade your users to standardise...

Hope this helps

CitrixEngineer@yahoo.co.uk

 

[BeerGood]

For the same reasons mentioned re odbc, perhaps also check any Oracle config files such as sqlnet.ora for any references to a drive that gets remapped on the "problem" clients....

Cheers