Sorry your browser is not supported!

The full error:

The instruction at 0x00000000 referenced memroy at 0x00000000. The memory could not be read.

This happened when I ran my game server after doing 2 things.

1. Included EZRotate commands
2. Removed all object related commands

What I've tried so far:

- Searched, and found 1 reference to this error on the forums.
- Tried the suggestion from that thread
- Remove EZRotate commands and it runs fine (not really a solution)
- Added at least one object in the project (didn't help)

I'm doing this in my server application to speed things up. If the server doesn't have to deal with objects then it runs much faster. I still want to use EZRotate to perform the rotations in memory though.

Any thoughts on how to clear up this error? Is there something missing that EZRotate requires?

Thanks.

Try debug mode and see if you can step into the line that produces the error.
You can also try to pick the working version and add the removed lines step by step, so you find the lines of code that raise that exception.
I don't think it is EZRotate, perhaps one of those removed objects is still referenced somewhere...

Ok, just for laughs, and because I don't have DBP installed on the game server, I ran the code in Debug mode on my workstation. It ran fine. I did go back and comment out all the EZRotate commands, and uncomment them one at a time, compiling and running it on the server each time. There's no specific EZRotate command that is causing it. There's something that EZRotate wants installed that the server doesn't have.

That brings me to a good question. Has anyone had troubles running any DBPro applications on Windows Server 2003 Enterprise?

After emailing with Ron Erickson about EZRotate's role in this, I think we've decided that some portion of the .Net framework was missing on the server.

I've since decided to install Windows XP on the server anyway, since Windows Server 2003 Enterprise is really overkill.

So for now this issue remains unresolved. If I get the chance in the next few months I'll try the server app again on a W2K3 Ent server and see what happens.