Hi All

I just wanted to give a heads up. I installed some tools patches last week to update my system. After doing that, I found some baan (IVc4) reports in "run away" mode. I had tmp files in the tmp directory that were just huge!

I found out that the system was stuck in an endless loop while trying to retrieve text.

Bottom line is that I spend two days in debug mode before I foud the problem.

I had data in ttttxt001 (ttttxt001.opwd) that refererenced a text window that did not exist in ttttxt004. In running a report, the report would issue a query to retrieve ttttxt004.coln. In this case, because the text window got deleted, a NULL value was returned and that created a run away process.

It really got ugly when the report went beyond 9,999 pages. Then I got format overflow allerts added to the event log and I got windows messages that the application log file was full.

To be safe, I recomend everyone to do a check to make sure that all the text windows that exist in txt001 are defined in txt004.

Baan will let you delete the text window even though it exist in txt001.

I logged a case with support even though I fixed the problem on my system.

Roy Nelson

Here is the response I got from Support.

Hi Roy,

The solution that nailed you was: 143542.

I've created a defect, I'm not sure how they will choose to solve it. As if see it, there are 3 options:

1) Fix the reference between tttxt004->tttxt001, currently it is Mandatory / No Check / No Check / No Reference Check. (Reference mode / Update / Delete / Check By DBMS )
This would most likely cause tttxt001 to be reconfigured which is not an ideal solution, and could result in loss of data..

2) Fix the code of "Maintain Text windows" to manually do a check, this is a good option, but it still leaves
text in tttxt001 with bad text windows.

3) Resolve whatever problem in repdll causes the looping. This is the ideal solution from my point of view, however, it may not be possible if there is no other way to code the fix made in sol 143542.

I will keep you informed of the status as I find out more.

Dave

I have had the similair problem in 5.0b this week.

ONe of our exchange scheme's uses the text.write function with a non existing window. It hang on executing this function.

Regards,
Han

2) Fix the code of "Maintain Text windows" to manually do a check, this is a good option, but it still leaves
text in tttxt001 with bad text windows.
Hans, I think we had a similar issue but not bad as in Nelson's case.
Then I wrote a 3-GL program to cleanup/fix all the texts in all the system, I couldnt find that program now.
But later we came up with standard text templates(windows, groups, authorizations etc), which are created during company creations.

I got a fix from Baan Support.

Roy


Baan case number: 2036155
Your case reference:
Created: 6/9/2004 2:33:15 PM
Priority: 20 - Major Problem
Solution type: QR: New Error Std. Software

Registered by: Hypro, Inc.
Registered for: Hypro, Inc.

Registered at: BGS, Grand Rapids
Handled by: BGS, Grand Rapids
Assigned to: Dave Kerr


--- CASE SUMMARY ---


TLS-NA: Missing Text windows results in run away processes


--- SOLUTION ---

TOOLS VERSION(S):
B40_c

SITUATION IDENTIFIED IN:
"Report Library" (ttstprepdll)

SITUATION DESCRIPTION:
In any session that prints text, if your text is missing a Text Window (e.g.
because the Text Window linked to your text is deleted), the session will
loop infinitely.


SOLUTION DESCRIPTION:
The text window is used to determine the width of the text to be printed. If
the text window does not exist, a width of 80 characters is used. The text
will be printed as expected.





SPECIAL INSTRUCTIONS:
None.

PATH NAME IN DIAL-UP DIRECTORY/WEB SITE:
Below are the supported VRC's based on the Baan standard derivation
structures.

If your Current Tools VRC is:
B40_c, B40_c1, B40_c4:
http://secure.support.baan.com/ftpdownload/updates/B40_c/144439stnd



COMMENTS:
Please read solution <sol_nr> 100017 </sol_nr> for installation
instructions.