I'm fishing here - I am managing an ancient legacy reporting system on Windows 2003 servers until our replacement (not OnDemand ) goes live...
I have OnDemand 7.1.0.12 installed and indexes configured to load PDFs into a series of folders - view-able by end users via ODWEK (arswww.cgi).
(I know, I know... we're over 10 years behind
)
On the back end - indexing and loading is fine - OnDemand ObjSrvr and LoadData services do fine...
Here's my scenario / situation - and hopeful that in your years of experience that you have encountered this, heard of this, seen this...and if you might know what causes it and how to fix it or work around it (without a full upgrade).
Here we go:
A user goes to the OnDemand webpage and selects a folder and searches for a report ID and a hit list with hundreds of links to all the reports of that name appear and they click on one link and voila! The PDF loads fine in the browser and all is well.
Then a user searches for another report by name - same folder perhaps...get's that hit list, clicks on one of the links and they get a perpetual hourglass... nothing opens - they click another link from the same list of this particular report - and no-go! - perpetual hourglass.
Other report IDs or folders keep working fine... just this specific list of this specific report is completely unable to be opened...
On the back end, when clicking on the report(s) that wont open - at the moment of the click, AcroRead32 flashes in task manager and goes out - (on a good PDF open AcroRead32 appears and stays in task manager)
This has gone on for years - the only way we have figured out how to fix it is to reboot the Windows Server.
So - something happens in the reboot that clears up - we don't know what -
I've looked for files, cache, acrobat api configs ini files that change or are replaced or unlocked in a reboot to no avail - I just know the reboot fixes it.
What I don't know, is if there's a condition or switch in one of the ars tables of the ARCHIVE db that is linked to the specific folder in my arscache directories that I could go to or some other thing say, in the registry that I could go to to make a change or whatever to allow my .pdf objects to open in the web page without rebooting the server.
Such a mystery. Rebooting is more and more a bad idea asmy servers quite obviously are getting really really old...
If you've ever heard of such a condition where all reports open but some and there is a fix or workaround besides rebooting - kindly let me know
Thank you!
Jonathan Aronson
