Jump to content


jbmartinez_18

Member Since 07 Sep 2005
Offline Last Active Jul 03 2007 12:57 PM
-----

Topics I've Started

Evaluation license

03 July 2007 - 12:55 PM

I am encountering problems using an evaluation license for a testing activity. I am getting logged out of my PROIV session at the middle of my processing. This is not background processing so the session is not idle. There is no fixed time. My session would be logged off between 1.5 - 3 hours after I start running my batch jobs. It would display a message saying that evaluation license has timed out and I need to log back in.

Does this really happen for evaluation licenses?

PRO EVALUATION INSTALLATION

04 June 2007 - 04:17 AM

We have a PROIV Evaluation Copy to test our sytem in a new box.

The details of the box are:

OS : Red Hat Enterprise Linux ES release 4 (Nahant Update 4) Kernel 2.6.9-42.0.10.ELsmp on an i686
PROIV : v5.5 Rev 5.4.3

Our system uses multistreaming/multi threading for several of our jobs. The problem is when a new PROIV session is created for each thread, the session does not eexecute and eventually will time out.

I looked at the logfiles and all I can see is:

This software is provided solely for the purposes of evaluation. Use
for any other purpose is strictly forbidden without the prior written
permission of PROIV Technology, Inc.


Running in Evaluation Mode.

Please contact your supplier to obtain
a license activation key.


Quote your unique Site id which is 261395

Installation details
--------------------
Evaluation License for 10 Development users.
These will expire after Sat Jun 9 2007.
Evaluation License for 10 Runtime users.
These will expire after Sat Jun 9 2007.
Evaluation License for 15 Background jobs.
These will expire after Sat Jun 9 2007.
Evaluation License for 10 Distributed Servers.
These will expire after Sat Jun 9 2007.



Press any key to continue ...

I am not sure but my guess is that it is because of the least line where it says that a key needs to be pressed to continue.

1) Just in case this is the reason is there a way to skip this part?
2) If this is not the reason, would anyone know what's keeping our multi threading jobs from running?

Thanks.