• 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!

WARNING: Possible Template Corruption Exists.

wcgodfrey

Member
List:
Has anyone run into a warning message of "WARNING:
Possible Template Corruption Exists" and if so did
anyone figure out how to get rid of it. It is showing
up on one terminal server but not another. On one
full client but not another and it seems to be
intermintant. Any insight would be appreciated.
This is on a JDE native unmodified application.

Sample from JDE.LOG
1468/1564 Tue Apr 10 15:52:19 2001 JTP_CM1090
JDB9909007 - Unable to obtain driver request handle

1468/1816 Tue Apr 10 15:52:22 2001 DLG_MSGB190
WARNING: Possible template corruption exists.

1468/1816 Tue Apr 10 15:52:32 2001 DLG_MSGB190
WARNING: Possible template corruption exists.


Bill Godfrey
XE SP 14.2
co-existance
AS400 V4R4M0


=====


_______________________________________________________
 

ShaneM

Member
Bill:

Make sure you are updating the spec files on the Terminal Server after each
package build. We had a similar problem where this error would pop-up after
any JITI - ing on the terminal servers.

You have to run the R92TAM (once) and R98CRTGL (once for each environment
directory).
Copy the b7/dddict.ddb,dddict.xdb,ddtext.ddb,ddtext.xdb files to the b7
directory on each terminal server.
Copy the b7/XXXb7333/Spec/glbltbl.ddb, glbltbl.xdb to the spec folder on the
terminal servers.

Good Luck.

Shane McConnell
 
Re: RE: WARNING: Possible Template Corruption Exists.

I can now replicate this problem on a full Client. Even if I delete DDDICT, DDTEXT, and GBLTBL on the fat client (in the environment directory SPEC) and let them re-build I still get the error.

Any thoughts would be appreciated.

This problem started after someone modified a data dictionary element. However they do not remember exactly what they changed. (That option is now secured out)
Thanks.

Bill Godfrey
XE SP 14.2
Coexistant AS400 V4R4M0
 

VickiH

Member
Re: RE: WARNING: Possible Template Corruption Exists.

Have you deleted these files in all environments on the fat client?
 

Zoltan_Gyimesi

Legendary Poster
Re: RE: WARNING: Possible Template Corruption Exists.

Bill,
At first, let me to ask for some information:

1.) When you detect the different behaviour on the two fat clients then do you sig-on with the same User ID into the same Environment?
2.) What kind of difference exist between the two clients (e.g. Full/Partial Package, differrent Path Code, diffent installed package, diffent installed Update Packages, diffent installation time, diffent SP level, etc.)?
3.) When do you receive the warning? When you start a specific UBE or APPL?

Please, tighten your issue as much as possible with information about differences. (I know, sometimes it could help).

At last a hint:
if you receive the warning only when you start a specific UBE or APPL then try to Get/Check-Out it again.

Read you again,
Zoltán


B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 

wcgodfrey

Member
Re: RE: WARNING: Possible Template Corruption Exists.

Zoltan:
I am using the same fat client. I have
successfully copied the DDDICT files from a terminal
server that is working properly put it on the fat
client and all works properly. If I delete the DDDICT
and re-enter one world then I again have the same
problem. I believe it is a data dictionay element
that is corupt.
Do you know of any way to compare DDDICT files to
see where the differences are?

I get the warning when I display records in
P30200 or P3002 and I think it is tied to QNTY however
that may not be the case.

Thank you for your help and suggestions.


Bill Godfrey
XE S14.2

--- Zoltan_Gyimesi <zoltan.gyimesi@synergon.hu> wrote:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OWDEV&Number=8992


_______________________________________________________
 

wcgodfrey

Member
Re: RE: WARNING: Possible Template Corruption Exists.

Zoltan:
I am using the same fat client. I have
successfully copied the DDDICT files from a terminal
server that is working properly put it on the fat
client and all works properly. If I delete the DDDICT
and re-enter one world then I again have the same
problem. I believe it is a data dictionay element
that is corupt.
Do you know of any way to compare DDDICT files to
see where the differences are?

I get the warning when I display records in
P30200 or P3002 and I think it is tied to QNTY however
that may not be the case.

Thank you for your help and suggestions.


Bill Godfrey
XE S14.2
--- Zoltan_Gyimesi <zoltan.gyimesi@synergon.hu> wrote:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OWDEV&Number=8992


_______________________________________________________
 
Zoltan:
This is one you can add to your things to check if you ever encounter this error.
Check your data type (OWTP) field for all data elements used in the application. I had one data element (ITC) that had a One World data type (OWTP) of "S". In my UDC table H98 DT "S" was a valid selection (not any more). After checking with JDE there should be no character values in this UDC table.

As a point of interest there is one field EXC# that has a data type of 95 (which is invalid) and that is also the way it is on the systems at JDE in Denver. I was advised that this is probably suposed to be a 9 - Numeric.

Thanks to all who took the time to respond to my question.

Bill Godfrey
XE SP14.2
Coexistant V4R4
 

johnd

Member
I know this is really old, but I'm updating it with what I've found out today.

I am calling BSFN B952334.FindAStringInAString
It's DSTR is
DL01
EV01
URLXML

I was using TSV as a search field. It's a VarString DD item. and I get this error when calling the BSFN.
If I change what I pass in to match the DSTR, say into a DL01 variable not TSV.....The error disappears.

Seems that E1 BSFNs don't like VarStrings like TSV being used as a input parameter.
 
Top