Hi guys,
using PB2019 R2 ( i know :))
we are having a batch processor executable , that does a whole lot of processing on our clients server. We have been updating some of our clients to our latest version of our software. since this update , we are noticing that our executable has stopped working and dissappeared in the morning , only on these "updated" clients.
we have added a lot of debugging , and we have found out that the latest executed line of code is the one just before the dw_tmp.Saveas function
dw_tmp.Modify("DataWindow.Export.PDF.Method = NativePDF!")
write_logging("just before the save as function")
dw_tmp.SaveAs(ls_file,PDF!,FALSE)
if it was a DLL issue, i would suspect its either always failing and not just after a 12 hour span or os.
This function is a generic function we use throughout our application to save a datawindow into a PDF file.
in the application object /tab PDF export , we have checked both
ALWAYS USE NATIVEPDF! METHOD FOR PDF EXPORT
PACKAGING CUSTOM FONTS IN THE GENERATED PDF FILES
Memory leak could be a cause , but then why always on the same statement ( dw_tmp.saveas) ?
Any idea's as to why this exe is closing itself down please ?
P.S. I havent checked the process manager to see if the .exe is still running there and only the visual gui is gone or not.
TIA
John
trying to answer you as complete as i possibly can
OS version & build ?
=> doesn't matter , any updated client suffers from this new behaviour
How is the batch App started?
=> its a compiled PB exe and is being started by us with admin rights
Under what account is the batch App run?
=> the admin one :)
Are there any mini-crash dumps in the O/S event logs?
=> sure , application error for my exe
Did you add a PB.ini file that turns off Accessibility mode?
=> we have used the same pb ini for years, no change there
Did you add a PB.ini file that turns of DataStore handles (if DS's are used)?
=> we have used the same pb ini for years , no change there.
TIA
John