Exaprom (iTextSharp) Access Violation from built application

[BowenM]

I have an application that uses exaprom pdf, which calls the iTextSharp dll.  I have the application built and deployed on 5 different computers so far.  It worked fine on all of them without issues.

Come 6th computer, the built app causes an access violation (Exception: Access violation (0xC0000005) at EIP=0x5EE89996), and I have no idea why.

The kicker is that all of the computers are identical.  Same standard corporate Windows 7 image, same model/make, same installed software. Any suggestions to start troubleshooting?  I could remove all of the exaprom calls, but I'd rather not.

Edit:  Full dump log:

####
#Date: Wed, Jul 22, 2015 5:08:25 PM
#OSName: Windows 7 Enterprise Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: PQ500
#Version: 14.0.1 32-bit
#AppKind: AppLib
#AppModDate: 7/16/2015 18:51 GMT
#LabVIEW Base Address: 0x30000000

InitExecSystem() call to GetCurrProcessNumProcessors() reports: 4 processors
InitExecSystem() call to GetNumProcessors() reports: 4 processors
InitExecSystem() will use: 4 processors

<DEBUG_OUTPUT>
7/22/2015 5:08:26.207 PM
Crash 0x00000000: Crash caught by NIER
File Unknown(0) : Crash 0x00000000: Crash caught by NIER
minidump id: a4658aa9-eea4-4fe1-96ec-e0ae2c4dbfcf
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x100011AB - nierInterface <unknown> + 0
0x10005E86 - nierInterface <unknown> + 0
0x1000620C - nierInterface <unknown> + 0
0x75960303 - kernel32 <unknown> + 0
0x77D074FF - ntdll <unknown> + 0
0x77CC9F45 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x30000000 ***
#** Loading: "C:\Program Files (x86)\PQ500\PQ500.exe\1abvi3w\user.lib\Exaprom PDF\VIs\Document\Print PDF.vi"
#** Loading: "C:\Program Files (x86)\PQ500\PQ500.exe\Modules\Plotting\Functions\plot menu control.vi"
#** Loading: "C:\Program Files (x86)\PQ500\PQ500.exe\Modules\Plotting\plot main gui.vi"
#** Loading: "C:\Program Files (x86)\PQ500\PQ500.exe\Main\acquire vxi main.vi"
*** End Dump ***

[diabeticdaniel]

Does the access violation occur on every run of your built application? If you believe the access violation is occuring in an attempt to access the iTextSharp DLL, you can remove these DLL calls and see if there is any change in behavior.

Access violation errors can be extremely generic and hard to track down. If you notice consistent crashing when you try to call that DLL, make sure there aren't any file permissions set on the DLL that would prevent reading or writing.

[BowenM]

Thanks for your reply. The dump made it look like it was the iTextSharp DLL. I went and looked through all of the file permissions to make sure that the DLL wasn't locked, etc. Rebooted the computer several times, and the access violation happened on every single application launch.

Then I let the computer sit for a couple of days and it... magically went away. Just stopped happening. There were no updates installed, nothing changed. Still NO idea what caused it, and why only on 1 out of 6 computers it was installed on.