Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

FileViewer Error in Srv Log, unable to view via jagmanager

4 posts in General Discussion (old) Last posting was on 2000-02-26 14:38:07.0Z
Andrew Hart Posted on 2000-02-11 21:31:51.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 11 Feb 2000 15:31:51 -0600
From: Andrew Hart <Andrew_Hart@harcourt.com>
Organization: The Psychological Corporation
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: FileViewer Error in Srv Log, unable to view via jagmanager
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 31
NNTP-Posting-Host: 167.208.175.68
Message-ID: <347_38A47FC6.F4ED4472@harcourt.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28873
Article PK: 161250

We installed our "production" copy of Jaguar on a server which is locked
up and generally inaccessible. Unfortunately, we're having problems
using the FileViewer utility remotely. We have listeners configured
with the IP address for both TDS and IIOP... we're seeing this message
in the server log:

Feb 11 14:36:06 2000: FileViewer::Initialize - Failed to open log file:
srv.log.
Feb 11 14:36:06 2000: FileViewerImpl::_openLog() -
intl_iocsfopen(srv.log, INTL_IO_READ) Failed.
No such file or directory.

We tried setting the log to an absolute path in the server properties
with no change. We get this, regardless of whether we are using
JagManager locally or remotely. We don't get an error manager in
JagManager. It just comes up empty with a filesize of -1 . Since the
server is usually inaccessible it's kind of important for us to get this
working.

I had a similar problem on our development machine, and I could have
sworn that regenerating the stubs fixed the problem. I didn't really
know about SRV.LOG at that time, so I can't say for sure if the error
message was the same. Doesn't *seem* to help in this instance, but
maybe I'm doing it incorrectly.

Any suggestions?

Thanks.


Scott McReynolds [Sybase] Posted on 2000-02-11 21:47:26.0Z
Newsgroups: sybase.public.easerver
From: "Scott McReynolds [Sybase]" <scottmc@sybase.com>
Subject: Re: FileViewer Error in Srv Log, unable to view via jagmanager
Date: Fri, 11 Feb 2000 14:47:26 -0700
Lines: 42
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: scottmc-pc.sybase.com 157.133.56.75
Message-ID: <347_k9ZKQoNd$GA.305@forums.sybase.com>
References: <347_38A47FC6.F4ED4472@harcourt.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28871
Article PK: 161248

Andrew,

Did you by chance install the server with one id (root) and then are running
the server with a different id (Sybase). it sounds like a permission
problem.

Scott

Andrew Hart <Andrew_Hart@harcourt.com> wrote in message
news:38A47FC6.F4ED4472@harcourt.com...
> We installed our "production" copy of Jaguar on a server which is locked
> up and generally inaccessible. Unfortunately, we're having problems
> using the FileViewer utility remotely. We have listeners configured
> with the IP address for both TDS and IIOP... we're seeing this message
> in the server log:
>
> Feb 11 14:36:06 2000: FileViewer::Initialize - Failed to open log file:
> srv.log.
> Feb 11 14:36:06 2000: FileViewerImpl::_openLog() -
> intl_iocsfopen(srv.log, INTL_IO_READ) Failed.
> No such file or directory.
>
> We tried setting the log to an absolute path in the server properties
> with no change. We get this, regardless of whether we are using
> JagManager locally or remotely. We don't get an error manager in
> JagManager. It just comes up empty with a filesize of -1 . Since the
> server is usually inaccessible it's kind of important for us to get this
> working.
>
> I had a similar problem on our development machine, and I could have
> sworn that regenerating the stubs fixed the problem. I didn't really
> know about SRV.LOG at that time, so I can't say for sure if the error
> message was the same. Doesn't *seem* to help in this instance, but
> maybe I'm doing it incorrectly.
>
> Any suggestions?
>
> Thanks.
>
>


Andrew Hart Posted on 2000-02-11 21:59:57.0Z
Newsgroups: sybase.public.easerver
Date: Fri, 11 Feb 2000 15:59:57 -0600
From: Andrew Hart <Andrew_Hart@harcourt.com>
Organization: The Psychological Corporation
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: FileViewer Error in Srv Log, unable to view via jagmanager
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 47
NNTP-Posting-Host: 167.208.175.68
Message-ID: <347_38A4865D.685BF25E@harcourt.com>
References: <347_38A47FC6.F4ED4472@harcourt.com> <347_k9ZKQoNd$GA.305@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28870
Article PK: 161247

We were logged on as Administrator when we installed Jaguar. It's running as a
Service.
Does the service derive it's permissions from the user it was installed by?

Thanks...

"Scott McReynolds [Sybase]" wrote:

> Andrew,
>
> Did you by chance install the server with one id (root) and then are running
> the server with a different id (Sybase). it sounds like a permission
> problem.
>
> Scott
>
> Andrew Hart <Andrew_Hart@harcourt.com> wrote in message
> news:38A47FC6.F4ED4472@harcourt.com...
> > We installed our "production" copy of Jaguar on a server which is locked
> > up and generally inaccessible. Unfortunately, we're having problems
> > using the FileViewer utility remotely. We have listeners configured
> > with the IP address for both TDS and IIOP... we're seeing this message
> > in the server log:
> >
> > Feb 11 14:36:06 2000: FileViewer::Initialize - Failed to open log file:
> > srv.log.
> > Feb 11 14:36:06 2000: FileViewerImpl::_openLog() -
> > intl_iocsfopen(srv.log, INTL_IO_READ) Failed.
> > No such file or directory.
> >
> > We tried setting the log to an absolute path in the server properties
> > with no change. We get this, regardless of whether we are using
> > JagManager locally or remotely. We don't get an error manager in
> > JagManager. It just comes up empty with a filesize of -1 . Since the
> > server is usually inaccessible it's kind of important for us to get this
> > working.
> >
> > I had a similar problem on our development machine, and I could have
> > sworn that regenerating the stubs fixed the problem. I didn't really
> > know about SRV.LOG at that time, so I can't say for sure if the error
> > message was the same. Doesn't *seem* to help in this instance, but
> > maybe I'm doing it incorrectly.
> >
> > Any suggestions?
> >
> > Thanks.
> >
> >


Adam Simmonds Posted on 2000-02-26 14:38:07.0Z
Newsgroups: sybase.public.easerver
Date: Sun, 27 Feb 2000 01:38:07 +1100
From: Adam Simmonds <asimmond@mail.usyd.edu.au>
Organization: University of Syndey
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: FileViewer Error in Srv Log, unable to view via jagmanager
Content-Type: multipart/mixed; boundary="------------DB76450BED5A6144C4BBD6DF"
Lines: 73
NNTP-Posting-Host: pc-70.sis.usyd.edu.au 129.78.248.198
Message-ID: <347_38B7E54F.B1BBFDCD@mail.usyd.edu.au>
References: <347_38A47FC6.F4ED4472@harcourt.com> <347_k9ZKQoNd$GA.305@forums.sybase.com> <347_38A4865D.685BF25E@harcourt.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:27750
Article PK: 159106

Just browsing old messages and this caught my eye
We had some trouble installing on terminal server and then realised we needed to go
to dos prompt and type

change user /install

then install your software

Rgds
Adam

Andrew Hart wrote:

> We were logged on as Administrator when we installed Jaguar. It's running as a
> Service.
> Does the service derive it's permissions from the user it was installed by?
>
> Thanks...
>
> "Scott McReynolds [Sybase]" wrote:
>
> > Andrew,
> >
> > Did you by chance install the server with one id (root) and then are running
> > the server with a different id (Sybase). it sounds like a permission
> > problem.
> >
> > Scott
> >
> > Andrew Hart <Andrew_Hart@harcourt.com> wrote in message
> > news:38A47FC6.F4ED4472@harcourt.com...
> > > We installed our "production" copy of Jaguar on a server which is locked
> > > up and generally inaccessible. Unfortunately, we're having problems
> > > using the FileViewer utility remotely. We have listeners configured
> > > with the IP address for both TDS and IIOP... we're seeing this message
> > > in the server log:
> > >
> > > Feb 11 14:36:06 2000: FileViewer::Initialize - Failed to open log file:
> > > srv.log.
> > > Feb 11 14:36:06 2000: FileViewerImpl::_openLog() -
> > > intl_iocsfopen(srv.log, INTL_IO_READ) Failed.
> > > No such file or directory.
> > >
> > > We tried setting the log to an absolute path in the server properties
> > > with no change. We get this, regardless of whether we are using
> > > JagManager locally or remotely. We don't get an error manager in
> > > JagManager. It just comes up empty with a filesize of -1 . Since the
> > > server is usually inaccessible it's kind of important for us to get this
> > > working.
> > >
> > > I had a similar problem on our development machine, and I could have
> > > sworn that regenerating the stubs fixed the problem. I didn't really
> > > know about SRV.LOG at that time, so I can't say for sure if the error
> > > message was the same. Doesn't *seem* to help in this instance, but
> > > maybe I'm doing it incorrectly.
> > >
> > > Any suggestions?
> > >
> > > Thanks.
> > >
> > >


Download VCard asimmond.vcf