ld.so.1: arserverd: fatal: libclntsh.so.10.1: open failed

2007-02-22 Thread Ankur Gulati (GR/EIL)
Hi Listers,
 
A wicked error is giving me a hard time.. Here's the scenario:
 
OS: Solaris 9
ARS: 6.0.1 and 7.0.1
DB: Oracle, oracle 9.1 client for 6 and 10.2 client for 7
 
Yes I have two different versions of remedy running on same server, till
morning both were running perfectly fine. Few hours back we noticed that
one of our users (not with Admin rights) started getting ARERR [90]
Cannot establish a network connection to the AR System server :
testserver(0) : RPC: Miscellaneous tli error - System error (Connection
refused). but it was working fine for users with admin rights.
 
I tried to restart the server and since then I all the processes start
except arserver for version 7.0. Other versions which are on 6.0.1 run
fine. The error which I recieve when I try to start arsystem is
ld.so.1: arserverd: fatal: libclntsh.so.10.1: open failed: No such file
or directory

I have checked the rights of this file and its fine, all the path
variables are set properly too.  
 
Just dont know what went wrong suddenly. The last thing that I remember
doing on this arsystem was to import the user records from 6.0 to 7.0
and then also it worked fine for a day and now this has resulted in
tired afternoon and evening and might have a sleepless night.
 
what to do?
 
 
Ankur

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the 
Answers Are


Re: ld.so.1: arserverd: fatal: libclntsh.so.10.1: open failed

2007-02-22 Thread Jiri Pospisil
** 

Ankur,

 

try running ldd command against the library which gives the error. The command 
should look something like:

 

ldd ld.so.1

 

ldd shows dynamic dependencies of executable files or shared objects.

Hopefully you will see the path it is trying to use to find the 
libclntsh.so.10.1 . You can then take it from there.

 

Regards

Jiri Pospisil

 

Technology Support Systems

▪T▪ ▪ ▪Mobile UK▪

 

 

-Original Message-
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] 
On Behalf Of Ankur Gulati (GR/EIL)
Sent: 22 February 2007 14:25
To: arslist@arslist.org
Subject: ld.so.1: arserverd: fatal: libclntsh.so.10.1: open failed

 

Hi Listers,

 

A wicked error is giving me a hard time.. Here's the scenario:

 

OS: Solaris 9

ARS: 6.0.1 and 7.0.1

DB: Oracle, oracle 9.1 client for 6 and 10.2 client for 7

 

Yes I have two different versions of remedy running on same server, till 
morning both were running perfectly fine. Few hours back we noticed that one of 
our users (not with Admin rights) started getting ARERR [90] Cannot establish a 
network connection to the AR System server : testserver(0) : RPC: Miscellaneous 
tli error - System error (Connection refused). but it was working fine for 
users with admin rights.

 

I tried to restart the server and since then I all the processes start except 
arserver for version 7.0. Other versions which are on 6.0.1 run fine. The error 
which I recieve when I try to start arsystem is

ld.so.1: arserverd: fatal: libclntsh.so.10.1: open failed: No such file or 
directory

I have checked the rights of this file and its fine, all the path variables are 
set properly too.  

 

Just dont know what went wrong suddenly. The last thing that I remember doing 
on this arsystem was to import the user records from 6.0 to 7.0 and then also 
it worked fine for a day and now this has resulted in tired afternoon and 
evening and might have a sleepless night.

 

what to do?

 

 

Ankur

__20060125___This posting was submitted with HTML in it___

NOTICE AND DISCLAIMER:
This email (including attachments) is confidential.  
If you have received this email in error please notify the sender immediately 
and delete this email from your system without copying or disseminating it or 
placing any reliance upon its contents.  We cannot accept liability for any 
breaches of confidence arising through use of email.  Any opinions expressed
 in this email (including attachments) are those of the author and do not 
necessarily reflect our opinions.  We will not accept responsibility for 
any commitments made by our employees outside the scope of our business.  
We do not warrant the accuracy or completeness of such information.