I've converted an old VB 6 application to VS 2003/FW 1.1. It runs as expected on my development box and every other developer's box. But when copied to any other user's machine, it throws an error that looks very much like the one displayed when security is not enabled for the executable:

Application has generated an exception that could not be handled.

process id=blah blah blah

Very helpful for debugging purposes.

FW 1.1 is installed on the users' machines. Because it looks like the same error security violation produce, I've tried using the 1.1 Wizard to permit access but still get the error.

Any clue what may be missing on the user's machines?

Will any programs developed on the development box run on the box that's giving you trouble?

This is the first program I've developed that's supposed to run there. I typically do not code for this group of users and am just trying to support this one application which I wrote a while back. However, further testing indicates it fails on any box where VS 2003 has not been installed, including those of users I do support. But I'm now coding 2005/2.0 applications for those machines, so that's still not much of a comparison.

I just performed another test on a pair of machines that were almost miraculously set up to trouble shoot this exact problem. One had VS 2002 with FW 1.0 and the other had 2005/2.0. It failed on both, but with different results. So, I thought it might be related to the framework used with 2003, but version 1.1.4322 is running on these other machines where it fails. Very strange.

I'm going to try converting it to 2.0. If that works, and there's no reason to think it won't when other 2.0 applications run OK, we'll just have to install that framework on the target box. Problem is that might require an act of God - but that might be easier to do than figuring this out.

Well, you never know when the answer to a prayer is going to be "yes" . . .

I was able to figure it out after all. We had to install the JIT debugger on the user's workstation and we were able to get more useful information than VB was providing.

After a little research, I determined that the problem had to so with the use of an array of checkboxes in the VB6 program, which is supported in .NET only with VB6 compatibility turned on. The conversion wizard performed an incomplete conversion and MS's instructions on how to make it compatible manually didn't work, of course. So I replaced the control array with a checked list box and the problem went away.