Jump to content


Photo
- - - - -

Pro IV Bus and Task Error


9 replies to this topic

#1 cdi_sabu

cdi_sabu

    Newbie

  • Members
  • Pip
  • 4 posts
  • Gender:Male

Posted 26 May 2011 - 06:07 AM

Hi All

This is my first Post :-). Appreciate your help

While trying to run the Bus and Task, we are getting the following error

E:\Test>E:\APPS\P4TASK\P4TASK.EXE /task:TK_C_EDIBUS /params:TK_AP_CCN=BRH,TK_REV

IEW_ONLY=N, /user:Redwood:Redwood /env:GSS_PRO_RUN /oper:AP:AP /codiv:PTI

Machine name NOT specified, using localhost.doConnect: connect failed: Host 'U4V

DD2GAPPSIT5', port 5432

last WIN32 error 10061 / winsock error 10061: Connection refused

p4OpenPro4: sockOpen to bus daemon failed

No error

p4OpenPro4 failed: Last Error 1, StatusCode 1, FailReason 97, SubError 97



E:\Test>PAUSE

Press any key to continue . . .

Any help would be much appreciated

Regards
Sabu




#2 Wim Soutendijk

Wim Soutendijk

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 211 posts
  • Gender:Male
  • Location:Netherlands

Posted 26 May 2011 - 06:23 AM

Hi Sabu,

if the machine name is not found you can specify it in the /task parameter:
E:\APPS\P4TASK\P4TASK.EXE /task:machineip:TK_C_EDIBUS /params:TK_AP_CCN=BRH,TK_REVIEW_ONLY=N, /user:Redwood:Redwood /env:GSS_PRO_RUN /oper:AP:AP /codiv:PTI

I always use the ip address of the proiv server, but a name is also supported

if that still fails, find out in the proiv control panel which port number is used for bus and tasks. you can find that setting in PROIV Gateway, gateway name, configuration.
if the Listen Port field is not 5432, specify your port number in the task parameter:
E:\APPS\P4TASK\P4TASK.EXE /task:machineip:port:TK_C_EDIBUS /params:TK_AP_CCN=BRH,TK_REVIEW_ONLY=N, /user:Redwood:Redwood /env:GSS_PRO_RUN /oper:AP:AP /codiv:PTI


hope this helps,

wim


#3 cdi_sabu

cdi_sabu

    Newbie

  • Members
  • Pip
  • 4 posts
  • Gender:Male

Posted 26 May 2011 - 07:18 AM

Hi Wim

Thanks for your response, now I get a new error message, please find the details below

E:\Test>E:\apps\P4task\P4TASK.EXE /task:localhost:5433:TK_C_EDIBUS /params:TK_AP
_CCN=BRH,TK_REVIEW_ONLY=N, /user:Redwood:Redwood /env:GSS_CST_RUN /oper:AP:AP /c
odiv TI
recvReplyHeader: sockRecv error, len -1, data d0 63 18
last WIN32 error -2 / winsock error -2: Unknown
recvReplyReqInfoBlock: sockRecv error, len -1, data 42 00 00
last WIN32 error -2 / winsock error -2: Unknown
p4OpenPro4: recv Reply failed
last WIN32 error -2 / winsock error -2: Unknown
p4OpenPro4 failed: Last Error 30, StatusCode 30, FailReason 97, SubError 97

E:\Test>PAUSE
Press any key to continue . . .

Appreciate your help

Regards
Sabu

Hi Sabu,

if the machine name is not found you can specify it in the /task parameter:
E:\APPS\P4TASK\P4TASK.EXE /task:machineip:TK_C_EDIBUS /params:TK_AP_CCN=BRH,TK_REVIEW_ONLY=N, /user:Redwood:Redwood /env:GSS_PRO_RUN /oper:AP:AP /codiv:PTI

I always use the ip address of the proiv server, but a name is also supported

if that still fails, find out in the proiv control panel which port number is used for bus and tasks. you can find that setting in PROIV Gateway, gateway name, configuration.
if the Listen Port field is not 5432, specify your port number in the task parameter:
E:\APPS\P4TASK\P4TASK.EXE /task:machineip:port:TK_C_EDIBUS /params:TK_AP_CCN=BRH,TK_REVIEW_ONLY=N, /user:Redwood:Redwood /env:GSS_PRO_RUN /oper:AP:AP /codiv:PTI


hope this helps,

wim



#4 DARREN

DARREN

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 396 posts
  • Gender:Male
  • Location:Florida,USA

Posted 26 May 2011 - 01:12 PM

According to the documentation, error code 30 is "Error starting a kernel session" with a further description of error 97 - No current Virtual Machine session. Can occur if you issue P4API requests out of order, or issue a request before a successful p4OpenPro4.This value can also be returned in the Reason or Sub-Error fields.

Everything is pointing to the Gateway not being able to start a PROIV session. Although you do not state explicitly, I am assuming you are on PROIV version 6 or above. As Wim stated, re-confirm that the listening port is correct via the control panel settings for the gateway configuration. I am aware that at least for Linux, the Environment Name is case sensitive so confirm that it is defined as all upper case (caps) in your configuration.

I have attached a screen shot of the config of our development gateway. Note that this is Linux and not windows.

Attached Thumbnails

  • GatewayManagerScreenShot.gif

Things should be made as simple as possible, but not simpler

#5 Vol Yip

Vol Yip

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 393 posts
  • Gender:Male
  • Location:Hong Kong

Posted 08 June 2011 - 06:30 AM

Looks like it is a Glovia application so he is probably in PROIV 4.6

#6 Matthews Estrice

Matthews Estrice

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 241 posts
  • Gender:Male
  • Location:Henley-on-klip

Posted 08 June 2011 - 10:10 AM

Hi Sabu,

If you are in version 6, the following test should work,it works on my environment.

in the 1st instance, verify that the Gateway is functioning correctly with the following test:
* In a DOS window, go to :\Program Files\Northgate\PROIV Version 6\Virtual Machine
* run the command - p4task /t:localhost:5435:TK_Z_TASKTEST /c:PTI /o:TSK
* This should return something similar to this:
p4ExecTask returned: # out params 9, length 192, # out sysvars 0, length 0:
Company_Division_Code=PTI,Operator_ID=TSK,PROIV_Licensee=--<< Not Specified\
>>--,PROIV_Ver_Date=June 02, 0,PROIV_Version=6.1.51.0-PR,Server_Date=23 O\
CT 2008,Server_Time=15:40:35,TEST1=,TEST2=

Now to test the ActiveWeb API, in a browser go to http://localhost:808...roiv/tasks1.xsp
Enter the following to test:-
PROIV Host machine name: localhost
PROIV Company/division code: PTI
PROIV Operator ID: TSK
PROIV Password: <blank>
System user ID: <blank>
System password: <blank>
PROIV Environment: <blank>
Port: 5435
The PROIV password field is ignored.
System userID/password are not relevant on Windows systems, and are not used in Version 6 anyway.
The PROIV Environment is optional, but must match the Gateway Server name if supplied - in your case 'test'.

Regrads,
Matthews Estrice

#7 Anthony Lim

Anthony Lim

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 29 November 2012 - 03:15 AM

Hi,

I'm using Pro-Iv Version 4.6, revision 5.6.6

I'm trying to use bus&task to call the pro-iv task function. But have encounter this problem similar with Mr. Sabu.
C:\WINDOWS\system32>P4TASK.EXE /task:MIS-NB-NB1:5435:TK_X_TEST /params:START=01,END=05,, /user:xxx:xxx /env:ENV_BUS /oper:TSK:TSK /codiv:MDC
recvReplyHeader: sockRecv error, len -1, data bc 8e 8c
last WIN32 error 2 / winsock error 2: Unknown
recvReplyReqInfoBlock: sockRecv error, len -1, data 42 00 00
last WIN32 error -2 / winsock error -2: Unknown
p4OpenPro4: recv Reply failed
last WIN32 error -2 / winsock error -2: Unknown
p4OpenPro4 failed: Last Error 30, StatusCode 30, FailReason 97, SubError 97


If I am using port 5432 it will give this error as below :

last WIN32 error 10061 / winsock error 10061: Connection refused
P4OpenPro4: sockOpen to bus daemon failed
No error
P4OpenPro4 failed: Last Error 1, StatusCode 1, FailREason 97, SubError 97

Please help.


Anthony Lim

#8 DARREN

DARREN

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 396 posts
  • Gender:Male
  • Location:Florida,USA

Posted 29 November 2012 - 06:29 PM

could I first suggest that you upgrade to at least version 6.2 or better yet version 7, as 4.6 is nearly 15 years old !

Secondly, could you provide the contents of your pro4.ini - it should be in your windows directory.

Have you ever had this working ?

Hi,

I'm using Pro-Iv Version 4.6, revision 5.6.6

I'm trying to use bus&task to call the pro-iv task function. But have encounter this problem similar with Mr. Sabu.
C:\WINDOWS\system32>P4TASK.EXE /task:MIS-NB-NB1:5435:TK_X_TEST /params:START=01,END=05,, /user:xxx:xxx /env:ENV_BUS /oper:TSK:TSK /codiv:MDC
recvReplyHeader: sockRecv error, len -1, data bc 8e 8c
last WIN32 error 2 / winsock error 2: Unknown
recvReplyReqInfoBlock: sockRecv error, len -1, data 42 00 00
last WIN32 error -2 / winsock error -2: Unknown
p4OpenPro4: recv Reply failed
last WIN32 error -2 / winsock error -2: Unknown
p4OpenPro4 failed: Last Error 30, StatusCode 30, FailReason 97, SubError 97


If I am using port 5432 it will give this error as below :

last WIN32 error 10061 / winsock error 10061: Connection refused
P4OpenPro4: sockOpen to bus daemon failed
No error
P4OpenPro4 failed: Last Error 1, StatusCode 1, FailREason 97, SubError 97

Please help.


Anthony Lim


Things should be made as simple as possible, but not simpler

#9 DARREN

DARREN

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 396 posts
  • Gender:Male
  • Location:Florida,USA

Posted 29 November 2012 - 06:34 PM

One of the engineers here says it is a windows permissions error on the socket i.e. you do not have permissions to access it. I would speak with your admin. You can also add the ,Debug option to your task call command line. That should give you a bit more detail.
Things should be made as simple as possible, but not simpler

#10 Anthony Lim

Anthony Lim

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 30 November 2012 - 07:56 AM

Hi Darren,


Thanks for your help. I have no control of upgrading to higher version. After much testing I found out that it is not the security issue because I have mark the USERNAME_VALIDATE=N. It is because I'm using the lower version p4api.dll from system32. After I replace with the higher version it work fine now.



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users