Post by jeremyz on Sept 11, 2007 9:03:48 GMT -5
I have a strange problem on a VM where I am running Windows Server 2003. VBCorLib is apparently being caught by the Data Execution Prevention. The following link describes what I am seeing: support.microsoft.com/kb/875351.
I have a very small test program that calls some basic VBCorLib function such as Convert.ToBase64String(). The app works fine in my dev environment. However, when I run the program in my Server 2003 environment, as soon as a VBCorLib function is called the app simply disappears. I eventually get an error message described in the above link.
I was able to get it to work by viewing my DEP configuration (Control Panel > System > Advanced > Performance Options > DEP tab) and choosing to allow my app to run. Everything ran fine after that, except that several minutes later my host machine blue screened. It is strange that on this machine Windows thinks VBCorLib is a virus.
Does anyone know what might be going on? I want to use the library, but I'm afraid of bumping into this on a client machine.
I have a very small test program that calls some basic VBCorLib function such as Convert.ToBase64String(). The app works fine in my dev environment. However, when I run the program in my Server 2003 environment, as soon as a VBCorLib function is called the app simply disappears. I eventually get an error message described in the above link.
I was able to get it to work by viewing my DEP configuration (Control Panel > System > Advanced > Performance Options > DEP tab) and choosing to allow my app to run. Everything ran fine after that, except that several minutes later my host machine blue screened. It is strange that on this machine Windows thinks VBCorLib is a virus.
Does anyone know what might be going on? I want to use the library, but I'm afraid of bumping into this on a client machine.
I can understand why DEP is kicking in, though I've never tried using it on 2K3. There is assembly code that is held in byte arrays that I execute, so I'm sure the byte array memory is marked as non-executable. I can't tell you why your VM blue screened, however. I'll need to get my hands on 2K3 and do some investigation if you continue to have the problem.