• JDELIST is celebrating its 20 year anniversary today!
  • Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Service Pack 16 Problems

Deborah_Foster

Active Member
Hi,
We tried to install SP16 this past weekend and experienced weird errors. We are
an as400 install currently running sp11.2 b7332. We are also using Citrix but
errors occurred on fat clients also. Did all the one-offs and used the CD to
install the Service pack. While testing we would get a dll registry error when
signing on. We experienced missing data dictionary definitions, Invalid Version
error, UBE PO print was mising all the header information and other reports were
miising data, nothing would print, fetch errors, Next number record lock errors.
Has anyone experienced these? Any guesess on what we might have done wrong?
We also could not rename the librarys back to restore as we were directed to do
by our consultants. We had to do a full restore of jde from back up tape.
All in all it's been a nightmare. Any information you can supply would be
appreciated.


Thank you,
Deborah Foster
Business Systems Analyst
Akorn, Inc.
(847) 353-4935
E-mail: deborah.foster@akrn.com
 

Larry_Jones

Legendary Poster
The DLL Registry error when signing on was discussed extensively here a week or so back. This behavior is seen on Win2K workstations that did not have Administrator (or Power User?) privileges. See the thread on this for more details.

Thats a big jump going from SP11.2 to SP16.

regards,

Larry Jones
ljones@wagstaff.com
OneWorld XE, SP 15.1
HPUX 11, Oracle SE 8.1.6
Mfg, Distribution, Financials
 

Jack_Crouch

Well Known Member
We put down SP16 last Wednesday (from SP14.2). We have two problems (so
far) with it.

1. The OWVER *SRVPGM was still linked to the old JDEKRNL for some reason.
Just used UPDSVRPGM to fix that. This was causing job submission problems.
2. If a FAT client on a SP prior to 16 submitted a job (any job)... then it
acted like a subsystem job. It went to TIMW, wrote a record to F986113 and
everything. Just sat there.





AS400 V4R5, XE+XU1+35ESUs, SP16, NT-SQL7 for CO
 

kastanek

Well Known Member
Hi Jack,

We had your second issue on our AS/400 V5R1, Xe, SP15.1, XU1, CO's in DB/2
installaion. We were able to fix it by:

ENDNET
Delete the JDB_* and the JDE_PGMCTL objects from B7333SYS
CLRIPC
STRNET

After that our jobs stopped hanging in TIMW status.

Regards,
Gerald.








Jack_Crouch
<j.crouch@ssss.co To: jdelistml@jdelist.com
m> cc:
Sent by: Subject: RE: Service Pack 16 Problems
owner-jdelistml@j
delist.com


08/13/2001 02:30
PM
Please respond to
jdelist





We put down SP16 last Wednesday (from SP14.2). We have two problems (so
far) with it.

1. The OWVER *SRVPGM was still linked to the old JDEKRNL for some reason.
Just used UPDSVRPGM to fix that. This was causing job submission problems.
2. If a FAT client on a SP prior to 16 submitted a job (any job)... then it
acted like a subsystem job. It went to TIMW, wrote a record to F986113 and
everything. Just sat there.





AS400 V4R5, XE+XU1+35ESUs, SP16, NT-SQL7 for CO
--------------------------
 
Top