Program Fails to Start: Access Violation Error (SOLVED)

Question

0.00/5 (No votes)

See more:

Hi guys,

Our application is currently failing to start up on a client's 64-bit Windows 7 workstation. There are no error dialogs, but fortunately, using dependency walker, we've got some logs that seem to suggest a second-chance Access Violation error.

We have done an array of tests, such as DEP, administrator privileges, and security settings with the firewall. The past version of our program runs perfectly fine, and we've repeated the installation a few times, so we've ruled out hardware.

Changes between the last build and the current build include the addition of some DLLs, one of which is a mixed DLL. We are using VS 2003, but we don't really meet any of the conditions specified in the mixed DLL problem documented by MS. This has not happened, and can't be reproduced on our local 64-bit Windows 7 machine.

Any experience with similar problems/advices for debugging would be appreciated!

Thanks in advance!

EDIT (SOLUTION) ===============

The problem appears to be resolved with the delay loading of some of the mixed DLLs in our application. Just in case someone else runs into a similar problem.

Posted 12-Nov-10 9:33am

Rock Bottom

Updated 20-Jan-11 7:35am

#realJSOP

v3

Add a Solution

Comments

Sergey Alexandrovich Kryukov 20-Jan-11 12:34pm

Asking just in case: perhaps you tried to link some 32-bit executable to some 64-bit or visa versa, could that be possible?

4 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Tamer Hatoum · Answer 1 · 2010-11-12T10:28:00

hello; have you tried running it on other machine having windows 7?
some times this error comming if he upgraded the RAM...
Make older programs run in this version of Windows (Windows 7)
http://windows.microsoft.com/en-us/windows7/Make-older-programs-run-in-this-version-of-Windows
As to the Access Violation message, what might help is if you right-click on the shortcut or .exe for the program and select the "Run As Administrator" option.
The other Access error messages might be solved via this.
How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
http://support.microsoft.com/default.aspx/kb/929135It also might pay you to do a bit of a malware check.

check that also Link1[^]
link2[^]
hope this will help...

Debojyoti Majumder · Answer 2 · 2011-01-20T07:27:00

Solution 4

For visual studio 2010 , there is a Remote Debugger you can use that tool.
And before building your project in 64bit always check your "References" in "Solution Explorer", to see the reference do support 64bit environment or not.

Posted 20-Jan-11 7:27am

Debojyoti Majumder

#realJSOP · Answer 3 · 2011-01-20T07:33:00

Solution 5

Make sure your client's .Net configuration matches yours. If it runs fine on your local machines, that's got to be the problem. maybe something isn't in the GAC that needs to be - remember to check that too.

Posted 20-Jan-11 7:33am

#realJSOP

Nish Nishant · Answer 4 · 2011-01-20T07:39:00

I've run into this in the past. The C# assemblies can be compiled as AnyCPU, which means they will run as either x86 or x64 depending on the OS. You cannot do that with the mixed mode DLLs. One workaround (easy/dirty) we have used is to force x86 so that everything runs in 32 bit mode (even on 64 bit OSes). The alternative is to maintain 2 installers, one for 32 bit and one for 64 bit.

[Edit]
---------

Delay loading may have just hidden potential problems. Once your app is loaded as 64 bit (meaning the 64 bit CLR is in use), then you cannot interop with a 32 bit mixed mode DLL.

Program Fails to Start: Access Violation Error (SOLVED)

4 solutions

Solution 1

Solution 4

Solution 5

Solution 6

Add your solution here

Preview 0