Acrobat crashes during VB Script when workstation is locked

Question

Very strange problem, maybe only related to my particular configuration but was hoping someone had some ideas. I've been working this issue for months and haven't been able to figure it out. I have an outlook macro that processes emails, downloads PDFs and prints, etc. On some computers acrobat will crash if the workstation is locked, but only when processing back to back PDFs.
I've narrowed the code down to what I'm including here. I can now duplicate the problem using this simple VB Script outside of Outlook.
I can launch this script, do a ctrl-alt-del and when the second PDF attempts to pull up, acrobat will throw up a fatal exception. This does not happen if the screen is unlocked. Eventually the problem seems to go away, but I can duplicate it again if I delete the profile on the workstation, log back in and launch the script.
I can usually mitigate the problem if I use timeouts, like 5 or 8 second delays between documents, but not always. I'd rather sovle the problem than try and guess timeouts that won't work the same on all workstations.
I have tried MANY combinations of Adobe SDK coding to fix this, nothing but the timeouts work so far.
I have to use IE to download the document, and I need it to run in a loop because the code will process many emails in an automated environment, often times one after the other.
Adobe is configured to open PDFs outside of IE, I uncheck the Edit/Preferences/Internet - open in IE window, so that I can then use the advod and pddoc methods to process the document.
Any help at all on this is appreciated! This is a very simple example below, but this exact code will cause acrobat to crash. I use the 4000 sleep where I normally have a loop to check for opendocs.
Configuration: Windows XP SP3, Adobe Acrobat Pro 9
=====================
Set WshShell - Wscript.CreateObject("WScript.Shell")
do until count > 1
count = count + 1
Set AcroApp = CreateObject("AcroExch.App")
set ie = createobject("InternetExplorer.Application")
hlink = "c:\temp\test.pdf"
ie.navigate hlink
wscript.sleep 4000
acroapp.closealldocs
acroapp.hide
loop

Answer 1

Ok so acrobat isn't designed to run like this in a loop. If I keep the documents open, I need to be able to test the suspected current document that just downloaded to determine if it matches with the parameters I've already obtained (document number, case information, etc). The title of the document is random, so that won't work. The document may not be OCR scanned so I can't rely on findtext, is there some other way to determine that the document that I am processing is the one that just downloaded? This is assuming I have multiple documents open already because the scritp is running in a loop, against say 15 to 20 documents before it stops and closes the documents and releases the script objects.