I'm pushing a copy of our application over to a new dev server (IIS7) and the application is blowing up on a line inside of a try-catch block. It doesn't happen locally, it actually obey's the rules of a try-catch block, go figure. Any idea why this would be happening? Shouldn't it just be failing silently? Is there something environmental I need to enable/disable?

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Line 229:           Try
Line 230:
Here >> :               _MemoryStream.Seek(6 * StartOffset, 0)
Line 232:               _MemoryStream.Read(_Buffer, 0, 6)
Line 233:
                     Catch ex As IOException

                     End Try

Although it doesn't matter for answering this question, I thought I would mention that it's third party code for the Geo IP lookup.