Report fails at first run

[samantha_sana]

Hi all,
We have a custom report and it has five versions.This report is failing in Production frequently and randomly.All versions are failing but it is random.When rerun the job compeltes successfully all the times.Tools release of production is 8.97.25.our qa is upgraded to tools 8.98.33.This report had long lines and udnerlines for constants which was the suspected cause for the failure as in SR ID 876836.1(attached).I have removed all the lines and symbols like "*" assigned to constants from this report but still it is failing with error "prt_AllocatePrintInfo+87C".As per the solution in the attached SR it is assumed to be fixed in next release when upgraded but still i need to understand what is causing the issue.
Has anyone faced this issue and have any solution?Please advise.
error "

46312/42476 MAIN_THREAD Mon Aug 15 22:16:02.879000 Runbatch.c319
INITIALIZING RUNBATCH job: 195623

46312/42476 MAIN_THREAD Mon Aug 15 22:16:02.879001 ipcmisc.c299
process 46312 <runbatch.exe> registered in entry 35

46312/42476 MAIN_THREAD Mon Aug 15 22:16:02.895000 Runbatch.c464
Startup for User=PD_TIDAL, Env=PD812, Role=*ALL, Job#=195623

46312/42476 MAIN_THREAD Mon Aug 15 22:16:02.895001 Runbatch.c481
bAPListening=0

46312/42476 MAIN_THREAD Mon Aug 15 22:16:04.129000 zdrv.cpp328
Initializing the Z Driver

46312/42476 MAIN_THREAD Mon Aug 15 22:16:04.129001 zdrv.cpp342
Gettting user data from hEnv

46312/42476 MAIN_THREAD Mon Aug 15 22:16:04.129002 zdrv.cpp364
User data is PD_TIDAL, PD812

46312/42476 MAIN_THREAD Mon Aug 15 22:16:04.129003 zdrv.cpp373
Creating XML Session

46312/42476 MAIN_THREAD Mon Aug 15 22:16:06.864000 ntexhnd.cpp101
Exception code: C0000005 ACCESS_VIOLATION

46312/42476 MAIN_THREAD Mon Aug 15 22:16:08.004000 ntexhnd.cpp151
====> Exception occurred with call stack:

prt_AllocatePrintInfo+87C E:\JDEdwards\E812\DDP\system\bin32\jdekrnl.dll

INFO: Done setting IPC Handle State structures to abandoned. Process exiting. iParam: 0000052360
Aug 15 22:16:02.863000 - 46312/42476 **** jdeDebugInit -- output disabled in INI file.


Thanks
89725

 

[samantha_sana]

attaching solution
E1: UBE: Access Code Violation for UBEs Containing '----' Hyphen Constants [ID 876836.1]
________________________________________
Modified 17-AUG-2010 Type PROBLEM Status PUBLISHED
In this Document
Symptoms
Cause
Solution
________________________________________
Applies to:
JD Edwards EnterpriseOne Tools - Version: 8.98 to 8.98 - Release: 8.98 to 8.98
JD Edwards EnterpriseOne Tools - Version: 8.98 to 8.98 [Release: 8.98 to 8.98]
Information in this document applies to any platform.
Symptoms
Since upgrading to EnterpriseOne Tools Release 8.98, all reports that have a long line of hyphens or underline text constants are failing with an Error 'E' status when run on the Enterprise Server.

Logs show errors like the following:

Exception code: C0000005 ACCESS_VIOLATION

====> Exception occurred with call stack:

PRT_GetFontHeight+1662 D:\JDEdwards\E900\DDP\system\bin32\jdekrnl.dll
prt_AllocatePrintInfo+7ECC D:\JDEdwards\E900\DDP\system\bin32\jdekrnl.dll
prt_AllocatePrintInfo+9BB4 D:\JDEdwards\E900\DDP\system\bin32\jdekrnl.dll
0000:00000000
0000:00000000

--UBE--[3]-- Processing Do Object RptConstObj in Section Page Header
--UBE--[0]-- { "------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------", 11640, 1320, 1, 10530, 2
Cause
The issue with the long string of hyphens or underscores is a buffer overrun issue. The buffer overrun occurs when there is a long string (up to 256 max in RDA) of hyphens and the JDE.INI [UBE] stanza has UBEPrintPDFData=1 in order to produce PDF metadata for 3rd party output management software such as CreateForm.
The bug is reported in SAR BUG:8934000.

Solution
SAR BUG:8934000 - UBEPrintPDFData and buffer overrun, is fixed in Tools Release 8.98.1.3. To resolve the issue, apply Tools Release 8.98.1.3 or later.

To workaround the issue until this tools release can be applied, either remove the underscore/hyphen text constants within the report or change the jde.ini setting to UBEPrintPDFData = 0.
NOTE: This overrun issue has been reported for the standard EnterpriseOne report R186405 - Timecard Template Processing.

Related
________________________________________
Products
________________________________________
• JD Edwards EnterpriseOne > Tools and Technology > EnterpriseOne Tools > JD Edwards EnterpriseOne Tools
• JD Edwards EnterpriseOne > Tools and Technology > EnterpriseOne Tools > JD Edwards EnterpriseOne Tools
Keywords
________________________________________
R186405; CALL STACK; METADATA; ACCESS_VIOLATION; C0000005 ACCESS_VIOLATION

 

[samantha_sana]

I have created a new report without copying the original one but still the newly created report also fails the same way .Any thoughts please let me know.

 

[peterbruce]

Samantha,

Firstly some questions so that I understand your situation.

Your first report had constants containing large numbers of hyphens, underscores, etc. - please confirm this. Were any of these more than 256 chars in length?

You then removed all the hyphens, underscores, etc. and it still fails - please confirm this. Did you delete the constants and replace them with new ones? Or did you change the constants?

You then created a new report from scratch and this one fails too - please confirm this. Does this UBE have constants containing large numbers of hyphens, underscores, etc.?

Do you have a debug log of the problem for any of the UBEs (Original, Changed original, New) in either production or test?
Does this happen in test?

 

[samantha_sana]

Hi peter,
First there was one report which had long lines and constants.It was failing in PD randomly and after seeing the Solution from metalink i removed all long lines and then moved it to production.The report again failed randomly.So i have created a new report without any long lines but with underlined constants.This report also failed randomly in Production.So again i have removed those small underlines for constants and promoted to production but still it is failing in production.I am amazed as this problem happens only with this report and that too after removing all underlines.I was suspecting of some * named on constants so i have removed those too but still no use.
This is just a display report without much coding or any additional functionality.
All the time the report fails with the mentioned error in Production only.Our production tools is 89725 .There is no failure in DV or TEST and the tools release of DV or TEST is 89833.Any inputs on this will be very helpful.
Many said that it will solve when tools is upgraded but the problem is now the report doesnt have anythign to suspect but still it is failing.
Thanks

 

[RGSINDHAVA]

Hello samantha,

I would like to suggest you that create that report again but this time do not type whole code at one shot or put all BSVW field or variable at a same time.

Go one by one and also run after update any variable or code. It might be possible that certain variable or code causing this error.

Verify and update us whether this help?

 

[peterbruce]

Samantha,

This may be related to the fact you have two different Tools Releases for Test and Production. Have you been creating/changing the UBEs in test and promoting to production? If so, try creating the UBE in production - taking the different tools releases out of the equation. There is no risk as you have said the report does not update anything.