Re: Portal Problem

[Stan Quick <stanley.quick@BRIO.COM>]

Frances,
1) This is not the users' group list for Portal questions.  Go to
www.sqrug.com and join the rm-users list. (RM stands for ReportMart, the
previous name for Brio.Portal)
2) What version of Portal are you running?  It sounds like 6.0 or before,
since 7.0 does dynamic configuration. (no stopping and restarting required)
3) Check out the JF_xxxxxxx.log, SB_xxxxxxx.log, and stdout_xxx.log in the
\log subdirectory.  You may have some info that will give you some help in
resolving this.  You can also run the BrioOne/ONESetup program to
put the Portal in Debug mode to help with this.

The JF listens for requests -- it doesn't make them.  It sounds like you may
have some other problem(s) on the
Unix box, but let's start with the logs and the "debug" mode first.

Stan

-----Original Message-----
From: Frances Jordaan [mailto:FrancesJ@BRIOSA.CO.ZA]
Sent: Wednesday, May 09, 2001 4:02 AM
To: SQR-USERS@list.iex.net
Subject: Portal Problem


Hi All,

Please help

A Range of IP Addresses had to be changed within the system, therefore the
portal had to be updated respectively.  The Portal Admin, services,
repository, etc... resides on the NT Machine. These IP Addresses seemed to
have automatically updated. However the Job-factory resides on the Unix
Machine, and did not automatically pick up the changes. Therefore through
the Admin the job factory service was manually changed. The Portal promptly
stated the services had to be stopped and restarted, which was done. The
Job-Factory Service started and then automatically just stopped for no
apparent reason. All the other services worked fine.

Running on an Oracle database

Could anyone suggest why this is happening or give us instructions on how to
solve this.

Thanks

Frances Jordaan