17 replies to this topic

[mikelandl]

Hi All,

I'm probably missing something silly here but when I try connecting to the ProIV IDE Server (0.1.53) I get the following error message:

Timed out waiting for server (Err = 3)

The logon function for COD:IDE OPR:004 is not IDE20000.

Any help would be greatly appreciated.

[Rob Donovan]

Hi,

Just a few questions to see what your Env setup is ....

Have you followed the instructions at this link, for both the 'Server Side' and 'Client' setup?

http://www.proivrc.com/ide.html

Specifically, modifying your pro4.ini file, and running the setup function IDESETUP.

What version of ProIV are you using?

What O/S is the kernel on, Unix, Linux or Windows?

That should help me figure things out a bit more...

Thanks,

Rob.

[mikelandl]

Hi Rob,

I followed the setup instructions (hopefully correctly).
We're running version 5.5000 rev 3.4.5 of the kernel on a Linux RedHat ES3 server.

The following gets displayed in the server window.

2:20:48 PM WriteStatus 1
2:20:48 PM Received Param01: 01
2:20:48 PM Received Param02: AR77
2:20:48 PM Received Param03: 3600
2:20:48 PM Received Param04: mrl
2:20:48 PM Received Param06: 192.168.2.100
2:20:48 PM Received Param07: 60
2:20:48 PM Received Param08: 10
2:20:48 PM Received Param09: 1
2:20:48 PM Received Param10: proivide
2:20:48 PM Received Param11: 1
2:20:48 PM Received Param12: STM
2:20:48 PM Received Param13: MRL
2:20:48 PM Received Param14:
2:20:48 PM WriteStatus 2
2:20:48 PM Connecting to control 0
2:20:48 PM Connecting
2:20:48 PM Connecting
2:20:49 PM Connecting
2:20:49 PM Connecting
2:20:49 PM Eval License
2:20:49 PM WriteStatus 8 COMPANY/DIVISION CODE, TO ACCEPT DEFAULT (3 CHARS. MAX.) 'OFF' =EXIT
2:20:49 PM Timed out waiting for IDE Command prompt.

Server: 192.168.2.100

Status: COMPANY/DIVISION CODE, TO ACCEPT DEFAULT (3 CHARS. MAX.) 'OFF' =EXIT

Function: LOGON

2:20:49 PM WriteStatus 3 LOGON   COMPANY/DIVISION CODE, TO ACCEPT DEFAULT (3 CHARS. MAX.) 'OFF' =EXIT

Edited by mikelandl, 17 April 2006 - 06:25 PM.

[Rob Donovan]

When you run the setup function IDESETUP, it should create a login record for ProIV (in LOGONF) for the CO/DIV 'IDE' and the OPR '004'.

IT looks like that has not happened, since when the IDE Server tries log in, it cant.

Can you check in $OPR, that it is setup, like the screen shot below...

If it is not, can you try running IDESETUP again, and see if that adds in the OPR.

IDESETUP, does quite a bit of setup, so I have to validate that that has run correctly first.

Change                                                                    $OPR
 04/17/06                      OPERATOR SECURITY                   PTI/SYS/109C

                 CO/DIV: IDE       OPERATOR ID: 004          PASSWORD:
 LOGON TO LINK FUNCTION: IDE20000  FORCED HELP?     TRANSPARENT LOGON? Y
       DEFAULT FUNCTION: OFF       TIMEOUT FUN:              EXIT FUN:

 VALID LOGON TERMINAL IDS: ( ALL      ) (          ) (          ) (          )
 (          ) (          ) (          ) (          ) (          ) (          )
 (          ) (          ) (          ) (          ) (          ) (          )
 TIME OUT LIMIT: 000 MINS      FIELD SECURITY - CHANGE:       LOOKUP:

--------FUNCTION SECURITY--------       ----------FILE SECURITY----------
                                                           SECURITY LEVEL
LN#     CATEGORY   SECURITY LEVEL       LN#     CATEGORY    A   C   D   L
  1     BOOT             9
  2     IDE              9
  3     TEST             9
  4     USER             9

[mikelandl]

Ran $OPR and everything checks out fine. Looks exactly the same way you say it should. Still no luck.

Edited by mikelandl, 17 April 2006 - 07:01 PM.

[Rob Donovan]

OK,

Can we verify that your Linux logon script is working correctly then.

What 'shell' are you using?

My setup example (http://www.proivrc.com/ideunix.html) does not have an example for Linux. Did you modify it at all to suit Linux?

Can you try running the commands from a Linux prompt to see if it starts ProIV.

Setup PROTERM, PROPATH, PRORUNTYPE, then try to start proiv with the following, replacing '/usr/bin' with your path to your pro kernel.

/usr/bin/pro 004 IDE

What happens? It should log into ProIV, and run a function IDE20000. This function is just a blank screen with a few input fields on it.

Does it login, or do you get the LOGON default screen?

Rob.

[mikelandl]

Using Bash.

When I enter all the commands from the prompt I end up with the following:

GUI START
                !        oD

Then if I hit Enter twice, I get:

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.

etc..........

Does your client handle "entering" through this message?

[Rob Donovan]

Yes, the IDE client should cope with all that.

Can you try it now from the ProIV client (not from ProIV IDE client).

Firstly, change your .login script (.profile or what ever it is in Linux) and remove the 'IF' statements that you put in to startup IDE... so that it runs it all the time, and does not check the TERM var...

IE, something like....

PROTERM=GUIDEV export PROTERM
cd /usr/proiv/develop
PROPATH=boots export PROPATH
PRORUNTYPE=DEV export PRORUNTYPE

/usr/bin/pro 004 IDE

exit

Start up the ProIV client, and connnect using your username and password (ie the one your have modified your .login script to include my startup commands).

Does this log you into ProIV, or leave you at the LOGON screen?

Rob.

[mikelandl]

Leaves me at the LOGON screen. Company/Division is populated with IDE, User ID and Password are both blank.

[Rob Donovan]

Hmmm, strange.

At that point, can you enter in 004 as the OPR and 004 as the password?

Does that log you in?

Have you managed to ever get ProIV to login transaprently / automatically before on Linux?

Normally, starting 'pro' with 004 and IDE as the 2 parameters, should pass them as the CO/DIV and the OPR...

Rob.

[mikelandl]

It won't let me log in, I get the error message "Invalid Division Company code".
I login transparently all the time at work.

[Rob Donovan]

Can you do an iskeys on logonf.pro in your boots dir, and post the result.

If you dont want to post it publically, give me an email...

And also, what Kernel version and revision are you on?

Rob.

[mikelandl]

Hi Rob,

I sent you an email lastnight. If you didn't receive it just let me know.

[Rob Donovan]

Hi,

I replied, 5 minutes later, last night... maybe you didnt get it...

Anyway...

The iskeys you did, did not show the IDE004 in logonf.pro

When you run IDESETUP, it creates a record in logonf.pro with the key 'IDE004', ie CODIV IDE, OPR 004.

Do you have multiple environments setup on your Linux box?

Are you sure that you were in the correct environment (or had the correct PROPATH), when you ran IDESETUP?

Can you search for logonf.pro in you linux system, and see if any of then have a 'IDE004' key...

Thanks,

Rob.

[mikelandl]

Hi Rob,

Turns out I had my PROPATH set incorrectly in my .bash_profile script. Fixed that and it's working like a charm now. Thanks for all your help.

So far it looks impressive. Good layout and much faster than VIP. Haven't tried any coding yet so I can't comment on that side of things at the moment. One issue I did come across was with the help file. When I choose it from the help menu it gets minimized and when I click on it to maximize it, it takes a very long time to display on the screen. Might be my computer but I've never really come across something like that before.