UNABLE TO SUBMIT UBE TO SERVER

PLEASE I NEED HELP WITH MY PROBLEM.

WHEN I SEND UBE IN THE WORKSTATION THIS MESSAGE APEAR

"AN ERROR OCURRED WHEN SUBMITTING R0006P VERSION XJDE0001 TO DECENT"

AND IN THE JDEDEBUG.LOG FROM THE SERVER:

================================================
Sep 02 19:42:38.593 - 2968/3464 **** jdeDebugInit -- output to file.
Sep 02 19:42:38.671 - 2968/3464 gethostname returned: DECENT
Sep 02 19:42:38.671 - 2968/3464 process 2968 <jdenet_n> registered in entry 2
Sep 02 19:42:38.671 - 2968/3464 process 2968 <jdenet_n> registered in entry 2
Sep 02 19:43:21.531 - 2968/3464 Net program ended, pid = 2968, signal = 11
Sep 02 19:43:21.546 - 2968/3464 Net program ended, pid = 2968, signal = 11
Sep 02 19:43:21.546 - 2968/3464 API ipcSawZombieProcV1 : process 2968 set to Zombie in entry 2
Sep 02 19:43:21.546 - 2968/3464 API ipcSawZombieProcV1 : process 2968 set to Zombie in entry 2

===================================================
AND IN THE JDE.LOG FROM THE SERVER:

2968/3464 Fri Sep 02 19:42:38.671 IPCMISC.C294
process 2968 <jdenet_n> registered in entry 2

2968/3464 Fri Sep 02 19:43:21.546 NETSIG.C507
Net program ended, pid = 2968, signal = 11

2968/3464 Fri Sep 02 19:43:21.546 IPCMISC.C294
API ipcSawZombieProcV1 : process 2968 set to Zombie in entry 2

We have recently started having this same problem.

Beginning Sunday, if we submit jobs to the workstation, they run fine; if we run a job on the server, submitted from a workstaion, via the scheduler or RUNUBE, we get:

3272/1936 Tue Sep 06 09:43:51.164 IPCMISC.C294
process 3272 <jdenet_n> registered in entry 38

3272/1936 Tue Sep 06 11:08:36.477 NETSIG.C508
Net program ended, pid = 3272, signal = 11

3272/1936 Tue Sep 06 11:08:36.477 IPCMISC.C294
API ipcSawZombieProcV1 : process 3272 set to Zombie in entry 38

Only jobs that have been submitted by the workstation first cause a problem. If jobs have never been submitted by a workstaion, they work fine.

We repaired our JDE_PRODUCTION SQL Server DB on Saturday, and after we brought services up on Sunday, this is when the SPIT-HIT-THE-FAN.

This problem is happening in DV, PY and PD, so it doesn't make sense that the DB rebuild is at issue since only production would have been affected.

EnterpriseOne 8.9 SP 8.93.E1, Win2000SP4, SQL Server 2000 SP3a, No custom code


------

Please post your version of EnterpriseOne, service pack, server type, OS level, DB, DB level

Did anything change on your system that might cause this to happen.

MY PROBLEM HAPPEN WITH ALL THE UBE THAT SEND TO THE ENTERPRISE

=============================
ENTERPRISEONE 8.9 SP2, INTEL NT, WIN2000 SP4, SQL200 SP3a

I HOPE YOU CAN HELP ME

ENTERPRISE 8.9 SP2, INTELNT WIN2000 SP4, SQL2000 SP3a

NO , NO CHANGES

I have been in touch with JunkPam and both of us have had no material changes on our systems that we can think of. I brought down services, backed up the production data DB, rebuilt the production data DB, brought up services. That shouldn't affect DV and PY. That was the only thing that was done while the system was down on Saturday.

From JunkPam's perspective, she says's she doesn't remember any change to the system that could cause the problem, but she hasn't yet expounded on what changes were wrought on the system.

She uninstalled JDESNET -u and reinstalled JDESNET -i her PS services and she reinstalled the service pack to see if that would help and neither are to any avail.

We have tried the same. No luck. We are trying to figure out the problem, not trying to resolve it by trial and error while we're still not sure what is wrong. Since the problem is SYSTEM in nature, it seems logical that a SYSTEM type repair should be made; but a SYSTEM type problem should have caused the issue, right?

Couple of Questions for you

1. Is your Enterprise server the same as your DB server
2. Was any updates made to SQL Server
----Service Pack Upgrade
----Windows Patchess

do you have enough space on you enterprose server to process UBE's
Do you have adequate space on your DB server
What is the current Job number...I know sometimes when the counter exceeds 1M issues can occur.

Did you see this post on the KG


IS GETTING SERVICES BUT WHEN SUBMITTING UBE IN THE LOGGING FILE GETS "API IPC SA

Details: Is getting services but when submitting ube in the logging file gets "api ipc saw zombie proc B1". Seems to takes unix process and sets it to a zombie process. Has recently updated oracle database to oracle 9I ver9.2.

<A>
Errors in logs are showing the following:

3687 Sat Aug 9 15:14:49 2003 netsig.c135
net process: adding process 3689 in Unregister list.

3687 Sat Aug 9 15:14:49 2003 netsig.c328
Kernel Process 3689 has died

3687 Sat Aug 9 15:14:49 2003 netsig.c143
net process: process 3689 set to Zombie

3687 Sat Aug 9 15:14:49 2003 ipcpub.c3621
API ipcSawZombieProcV1 : process 3689 set to Zombie in entry 1

This is happening with all security kernel processes on the system. Client had modified jde.ini on server for DB SYSTEM SETTINGS to use the libora90.sl. Apparently System tables were still loaded on Oracle 8 install. Once he switched the Load Library=libora80.sl, zombie errors went away, and Security Server errors disappeared as well.

Hello,

Check following things. Could you connect thru odbc to from your enterprise server to SQL database ( try connecting using the user account which starts the services)

Try submitting a job on enterprise server using RUNUBE

Look if your secuiryt server came up clean and is the security is defined cleanly.

Is it pssible to post you server's Jde.ini

Thanks

this is my jde.ini

; OneWorld initialization file INI(JDE)
; NT Intel specific version - B9

[JDE_CG]
;TARGET=DEBUG
TARGET=RELEASE
INCLUDES=c:\Progra~1\Micros~1\Vc98\include;c:\Progra~1\Micros~1\Vc98\mfc\include;$(SYSTEM)\INCLUDE;$(SYSTEM)\INCLUDEV;$(SYSTEM)\CG;$(APP)\INCLUDE;
LIBS=c:\Progra~1\Micros~1\Vc98\lib;c:\Progra~1\Micros~1\Vc98\mfc\lib;$(SYSTEM)\LIB32;$(SYSTEM)\LIBV32;$(APP)\LIB32;
MAKEDIR=c:\Progra~1\Micros~1\Common\Tools\WinNT;c:\Progra~1\Micros~1\Common\MSDev98\Bin;c:\Progra~1\Micros~1\Common\Tools;c:\Progra~1\Micros~1\VC98\bin
STDLIBDIR=c:\Progra~1\Micros~1\Vc98\lib;c:\Progra~1\Micros~1\Vc98\mfc\lib
CLASSPATH=D:\peoplesoft\ddp\b9\system\Classes\xalan.jar;D:\peoplesoft\ddp\b9\system\Classes\xerces.jar;D:\peoplesoft\ddp\b9\system\Classes\kernel.jar;D:\peoplesoft\ddp\b9\system\Classes\XTS.jar;D:\peoplesoft\ddp\b9\system\Classes\log4j.jar;D:\peoplesoft\ddp\b9\system\Classes

[DEBUG]
Output=NONE
DebugFile=D:\peoplesoft\ddp\b9\log\jdedebug.log
JobFile=D:\peoplesoft\ddp\b9\log\jde.log
JDETSFile=D:\peoplesoft\ddp\b9\log\JDETS.log
LogErrors=1
ClientLog=0
KeepLogs=1
TamTraceLevel=0
QKLog=0

[SVR]
EnvironmentName=DV9
LibraryListName=DV9
SpecPath=spec
SourcePath=source
ObjectPath=obj
HeaderPath=include
HeaderVPath=includev
BinPath=bin32
LibPath=lib32
LibVPath=libv32
MakePath=make
WorkPath=work

[INSTALL]
B9=D:\peoplesoft\ddp\b9
Double_Byte=0
LocalCodeSet=WE_ISO88591
StartServicePrefix=JDE Update 0

[JDENET]
serviceNameListen=6011
serviceNameConnect=6011
maxNetProcesses=5
maxNetConnections=400
maxKernelProcesses=50
maxKernelRanges=24
netTrace=0
ServiceControlRefresh=5
enablePredefinedPorts=0

[JDENET_KERNEL_DEF1]
krnlName=JDENET RESERVED KERNEL
dispatchDLLName=jdenet.dll
dispatchDLLFunction=_JDENET_DispatchMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF2]
krnlName=UBE KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchUBEMessage@28
maxNumberOfProcesses=3
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF3]
krnlName=REPLICATION KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_DispatchRepMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF4]
krnlName=SECURITY KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchSecurity@28
maxNumberOfProcesses=2
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF5]
krnlName=LOCK MANAGER KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_TM_DispatchTransactionManager@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF6]
krnlName=CALL OBJECT KERNEL
dispatchDLLName=XMLCallObj.dll
dispatchDLLFunction=_XMLCallObjectDispatch@28
maxNumberOfProcesses=10
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF7]
krnlName=JDBNET KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchJDBNETMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF9]
krnlName=SAW KERNEL
dispatchDLLName=jdesaw.dll
dispatchDLLFunction=_JDEK_DispatchSAWMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF10]
krnlName=SCHEDULER KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchScheduler@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF11]
krnlName=PACKAGE BUILD KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchPkgBuildMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF12]
krnlName=UBE SUBSYSTEM KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchUBESBSMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF13]
krnlName=WORK FLOW KERNEL
dispatchDLLName=workflow.dll
dispatchDLLFunction=_JDEK_DispatchWFServerProcess@28
maxNumberOfProcesses=5
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF14]
krnlName=QUEUE KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_DispatchQueueMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF15]
krnlName=XML TRANS KERNEL
dispatchDLLName=XMLTransactions.dll
dispatchDLLFunction=_XMLTransactionDispatch@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF16]
krnlName=XML List Kernel
dispatchDLLName=xmllist.dll
dispatchDLLFunction=_XMLListDispatch@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF19]
krnlName=EVN KERNEL
dispatchDLLName=jdeie.dll
dispatchDLLFunction=_JDEK_DispatchITMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF20]
krnlName=IEO KERNEL
dispatchDLLName=jdeieo.dll
dispatchDLLFunction=_JDEK_DispatchIEOMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF21]
krnlName=OPE KERNEL
dispatchDLLName=jdeope.dll
dispatchDLLFunction=_BBOPE_DispatchMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF22]
krnlName=XML DISPATCH KERNEL
dispatchDLLName=xmldispatch.dll
dispatchDLLFunction=_XMLDispatch@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF23]
krnlName=XTS KERNEL
dispatchDLLName=xtskrnl.dll
dispatchDLLFunction=_JDEK_DispatchXTSMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF24]
krnlName=XML SERVICE KERNEL
dispatchDLLName=xmlservice.dll
dispatchDLLFunction=_XMLServiceDispatch@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[NETWORK QUEUE SETTINGS]
QKActive=1
QKOnIdle=300

[BSFN BUILD]
BuildArea=D:\peoplesoft\ddp\b9\packages
OptimizationFlags=/FD /Gz /O2 /Zi /MD /W4 /EHs /Gy
DebugFlags=/FD /GZ /Gz /Od /Zi /MDd /W4 /EHs /Gy /D "_DEBUG"
InliningFlags=
DefineFlags=/D "WIN32" /D "_WINDOWS" /D "IAMASERVER" /D "KERNEL" /D "UNICODE" /D "_UNICODE"
CompilerFlags=/nologo /c
OSReleaseLevel=5.0
LinkFlags=/DLL /DEBUG /SUBSYSTEM:windows /FORCE:MULTIPLE /FORCE:UNRESOLVED /INCREMENTAL:YES /VERBOSE /WARN:3
LinkLibraries=jdekrnl.lib jdel.lib jdenet.lib jdeipc.lib owver.lib jdeunicode.lib v_verify.lib xerceswrapper.lib
SimultaneousBuilds=5

[JDEIPC]
ipcTrace=0
;CLSID=
startIPCKeyValue=6000

[JDEMAIL]
Rule1=90|OPT|MAILSERVER=mail.jdedwards.com
Rule2=100|DEFAULT|[email protected]
Rule3=110|DEFAULT|[email protected]
Rule4=120|DEFAULT|[email protected]
Rule5=130|OPT|MERGELOCAL=1
Rule6=140|OPT|UPDATELOCAL=0
ClientType=Windows

[DB SYSTEM SETTINGS]
Version=43
Default User=JDE
Default Pwd=JDE
Default Role=*ALL
Default Env=DV9
Default PathCode=DV9
Base Datasource=DECENT - B9 Server Map
Object Owner=SVM9
Server=DECENT
Database=DECENT - B9 Server Map
Load Library=
Decimal Shift=Y
Julian Dates=Y
Use Owner=Y
Secured=Y
Type=S
Library=
Library List=
DatabaseName2=JDE9
DatabaseInstance=
ServerPort=1433
JDBNETUse=N
UnicodeFlag=Y
LOBFlag=N

[UBE]
UBEDebugLevel=0

[LOCK MANAGER]
Server=
AvailableService=NONE
RequestedService=NONE

[SERVER ENVIRONMENT MAP]
JDEPLAN=JD9

[SECURITY]
SecurityServer=DECENT
User=JDE
Password=JDE
Default Role=*ALL
DefaultEnvironment=DV9
DataSource=System - B9
History=0

[INTEROPERABILITY]
FilteredEvents=*NONE
RegisteredEvents=

[SAMPLE_EVENT]
DS1=DXXXXXXXX
DS2=DYYYYYYYY
DS3=DZZZZZZZZ

[JDEITDRV]
DrvCount=4
Drv1=RT:rtdrv.dll
Drv2=WF:wfdrv.dll
Drv3=Z:zdrv.dll
Drv4=JDENET:jdetrdrv.dll

[LREngine]
System=D:\peoplesoft\ddp\b9\output
Repository_Size=20
Disk_Monitor=YES

[WORKFLOW]
; Workflow Runtime Interop, inbound (server only)
WRIUser=xxx
WRIPassword=xxx
WRIEnvironment=xxx
WRIRole=*ALL
; Workflow Runtime Interop, outbound
PrimaryEvnServer=xxx
SecondaryEvnServer=xxx

[JAS PREFERENCE]
JasServer=
Port=80
Servlet=/jde/servlet/html.login

;[TRANSPORTS]
;TransportName1=xxxTransportExeNamexxx
;TransportParams1=xxxTransportParametersxxx

[XAPI]
XMLDirectory=D:\peoplesoft\ddp\b9\log

[XMLLookupInfo]
XMLRequestType1=list
XMLKernelMessageRange1=5257
XMLKernelHostName1=local
XMLKernelPort1=0

XMLRequestType2=callmethod
XMLKernelMessageRange2=920
XMLKernelHostName2=local
XMLKernelPort2=0

XMLRequestType3=trans
XMLKernelMessageRange3=5001
XMLKernelHostName3=local
XMLKernelPort3=0

XMLRequestType4=JDEMSGWFINTEROP
XMLKernelMessageRange4=4003
XMLKernelHostName4=local
XMLKernelPort4=0
XMLKernelReply4=0

XMLRequestType5=xapicallmethod
XMLKernelMessageRange5=14251
XMLKernelHostName5=local
XMLKernelPort5=0

XMLRequestType6=realTimeEvent
XMLKernelMessageRange6=14251
XMLKernelHostName6=local
XMLKernelPort6=0
XMLKernelReply6=0

[XTSRepository]
XTSRepositoryPath=D:\peoplesoft\ddp\b9\system\XtsRepository
XSL-JDE-BIRDS-REQUEST=birds.xsl
XSL-JDE-V2_2_NATIVE-REQUEST=v2toNative.xsl
XSL-JDE-V1_NATIVE-REQUEST=ml.xsl
XSL-JDE-V1_NATIVE-RESPONSE=lm.xsl

[XTS]
XTSTemplateSelector1=com.jdedwards.xts.xtsm.XTSMJDETemplateSelector
XTSTraceLevel=2
XTSDelay=0

[MTR VALIDATION]
EnterpriseDiskInMB=3000

[TCENGINE]
TraceLevel=1

THE JOBS THAT THE SCHEDULER SEND TO THE I-ACTIVE QUEUE RUN I NEED TO DO MORE TESTS

SOMEBODY CAN TELL ME HOW TO MAKE THE I-ACTIVE THE QUEUE BY DEFAULT

JunkPam,

When this is resolved, you should consider changing the JDE password. Not only do you have too simple of a password, but you just shared it with the entire list.....

IN FACT THE ORIGINAL PASSWD WAS CHANGE IN THE INSTALLATION, TO POST MADE THE CHANGE TO JDE

We upgraded from XE to 8.10 in July. We have had this problem happen twice now.

The first time 14 days after the upgrade. We rebuilt the application server. JDE could not find the problem.

This happened to us again on Monday. We have switched to another application server and are currently working with JDE to figure out the issue. JDE has said that they have another customer reporting this issue now as well.

We did not make any changes. I would like to talk to people having the same issue so we can compare notes.

Faisal
804-515-7054
++++++++++++++++++
8.10 - 8.93R1
Enterprise Win2K
Enterprise SQL2K-SP3a
Citrix MetaFrame XP FR1

Hey there

Are you sure this is you jde.ini... If you on E810 should your path code and encironment be DV810 and not dv9..... Please check this.... This does nto look right

Sory I though yuo were on e810.... ignore my previous mail

Under the D setting Clear

Database=DECENT - B9 Server Map

It should be empty

Also, Could you post the logs when you start your enterpriserver's service

To reply to you, Soul Glo;

1. Enterprise server = DB server
2. No SQL Server updates - updated to SP3a immediately after installing SQL 2000 a year ago
Windows 2000SP4 patches are up-to-date

Enterprise Server available disc space is more than adequate (380GB+ DB drive, 200GB+ Log drive, next extent < 35GB)
Since DB Server=Enterprise Server, yes there is more than adequate space on the DB server

Current Job Number = 14,96x,xxx. I think if we were having a problem because of it being over 1M, we would have seen that problem over 13M ago?

I spoke with Oracle today and it seems that there are about 5-7 customers so far that have run into problems after 09-01-2005 with this same issue and very vew and far between before this. These 5-7 customers claim to have made no changes to their system and it just started misbehaving this week. Coincidence?