Enterprise Server Setup

Dear List

I have setup another Enterprise Server on B7332 SP19.1_A1 but I am unable to
start the OneWorld services or run porttest sucessfully for the 1
environment I have on this machine.

The machine in question is a Sun Solaris E450 with an Oracle 8.1.6 database.

The logs following the porttest are shown below :

2138 Tue Aug 6 15:52:20 2002 ipcpub.c3121
process 2138 <porttest> registered in entry 0


2138 Tue Aug 6 15:52:22 2002 netqueue.c138
putExternalQueue (net) failed for msg id 1.


2138 Tue Aug 6 15:52:22 2002 jdeksec.c3195
KNT0000305 - JDENET Error = JDENET eIPCErr: eIPCNotFound


2138 Tue Aug 6 15:52:22 2002 netqueue.c138
putExternalQueue (net) failed for msg id 2.


2138 Tue Aug 6 15:52:22 2002 jdeksec.c3195
KNT0000305 - JDENET Error = JDENET eIPCErr: eIPCNotFound


2138 Tue Aug 6 15:52:22 2002 jdeksec.c812
SEC0000002 - Unable to connect to security server jde7332prd
Running OneWorld with user's signon and password
This may or may not work depending on the databases' security.


2138 Tue Aug 6 15:52:22 2002 jdb_ctl.c2896
JDB1100015 - Failed to complete Security check


2138 Tue Aug 6 15:52:22 2002 ipcpub.c3432
API ipcSawUnregisterProcV1 : process 2138 unregistered in entry 0

Does anybody have any ideas on what may be wrong?

Thanks
Shane Woolley

Many new Enterprise Server errors can be traced to the jde.ini file. If the new server is the same platform as the other you may be able to simply copy the jde.ini from the old to the new.

Also, ensure that the new server has the path codes installed that are referenced in the jde.ini as the default environments.

Ex: If the Default Env is PY7333 then PY7333 must exist on that box.

I know nothing of Oracle or if you have the concept of library lists, so
this may not apply. But, after applying SP19.1_E1 one-off I had to be sure
the JDEOW library was added after B7334SYS in the library list. Reason
being, there was an INI file in JDEOW, and PORTTEST was finding that instead
of our INI in B7334SYS, and failing.





Xe, SP 19.1_D1, Update 6, ES=AS/400 V5R1, CO=AS/400, Thick & Citrix Clients

It sounds to me like you have chosen an IPC Key value that is conflicting with some other process, and OW is unable to create the IPCs (semaphores, messages queues, shared memory) that it needs.

Run 'ipcs -a' when OW is down and compare the key values to your OW ipc key converted to hexadecimal. Anything in the range of IPCKey to IPCkey plus 0x3E8 (decimal 1000) will likely conflict with OneWorld.

The IPC range specified in JDE.INI is not conflicting with any other app.
After setting IPCTrace to 1 I got the following error near to the end of the
log file.
What is it looking for when it's calling Net0Q?

Aug 7 14:13:19 ** 4091 IPC2100013 - Net0Q doesn't exist and create not
specifie
d.
Aug 7 14:13:19 ** 4091 IPC3200007 - unlockSemaphore succeeded, num=0,
index=1/1
, use=1.
Aug 7 14:13:19 ** 4091 putExternalQueue (net) failed for msg id 1.
Aug 7 14:13:19 ** 4091 IPC3100019 - ipcLockResource - idx=17.
Aug 7 14:13:19 ** 4091 IPC3100007 - lockSemaphore pending, num=14,
index=18/18,
use=1.
Aug 7 14:13:19 ** 4091 IPC3100009 - lockSemaphore succeeded, index=18/18.
Aug 7 14:13:19 ** 4091 IPC3200009 - ipcUnlockResource - idx=17.
Aug 7 14:13:19 ** 4091 IPC3200007 - unlockSemaphore succeeded, num=14,
index=18
/18, use=1.
Aug 7 14:13:19 ** 4091 IPC2100039 - ipcGetResource - Net0Q.
Aug 7 14:13:19 ** 4091 IPC3100007 - lockSemaphore pending, num=0,
index=1/1, us
e=1.
Aug 7 14:13:19 ** 4091 IPC3100009 - lockSemaphore succeeded, index=1/1.
Aug 7 14:13:19 ** 4091 IPC2100013 - Net0Q doesn't exist and create not
specifie
d.
Aug 7 14:13:19 ** 4091 IPC3200007 - unlockSemaphore succeeded, num=0,
index=1/1
, use=1.
Aug 7 14:13:19 ** 4091 IPC2100039 - ipcGetResource - Net0Q.
Aug 7 14:13:19 ** 4091 IPC3100007 - lockSemaphore pending, num=0,
index=1/1, us
e=1.
Aug 7 14:13:19 ** 4091 IPC3100009 - lockSemaphore succeeded, index=1/1.
Aug 7 14:13:19 ** 4091 IPC2100013 - Net0Q doesn't exist and create not
specifie
d.


Thanks
Shane Woolley

Re: RE: Enterprise Server Setup

I'm afraid I'm not sure, but that log would probably be enough to get the answer you need from JDE's support line.