There are a couple of options.
1. Reverse engineer the assembly. There are various decompilers out there.
If the assembly creator obfuscated, you are largely out of luck.
2. Read the vendor documentation and ensure that you are not doing something
wrong. By reading the exception message, you should get a better idea of
what is happening.
3. Search support.microsoft.com if it is a common exception and see if you
might be missing some other software necessary to run this assembly.
The first thing you have to do is determine that this is definitely a bug.
If so, the vendor should fix it.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
**********************************************************************
Think Outside the Box!
**********************************************************************