November 19, 2008 02:23am pst

1. jkr 194,497
2. DanRollins 89,475
3. alb66 35,670
4. Gurudenis 19,800
5. evilrix 17,555
6. fridom 16,450
7. itsmeandn... 15,248
8. AndyAins... 13,278
9. graye 12,750
10. JohnGaby 12,350
11. Zoppo 11,730
12. jaime_oliv... 10,622
13. Idle_Mind 9,911
14. mahesh1... 7,100
15. Infinity08 6,664
16. KCTS 6,348
17. ziolko 6,150
18. mannujam 6,000
18. CSecurity 6,000
18. Christian... 6,000
21. oBdA 5,800
22. BSonPosh 5,750
23. rstaveley 5,650
24. peetm 5,400
25. Castorix 4,800

1. jkr 1,563,400
2. NickRepin 431,192
3. chensu 379,040
4. DanRollins 260,651
5. jhance 218,474
6. AlexFM 195,135
7. Madshi 143,955
8. nietod 143,235
9. thui 115,530
10. jaime_oliv... 114,660
11. mxjijo 109,133
12. alexo 92,791
13. roshmon 90,068
14. nonubik 79,238
15. AlexViroc... 68,760
16. _nn_ 58,566
17. itsmeandn... 58,497
18. robpitt 57,849
19. Idle_Mind 53,986
20. Zoppo 51,632
21. mahesh1... 50,200
22. cwwkie 46,765
23. AndyAins... 45,083
24. BeyondWu 43,307
25. pjasnos 41,172

01.21.2008 at 05:31PM PST, ID: 23099945

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.4

Windows 2003 64-bit error 0x8007000B with a 32-bit dll - how to resolve w/o recompile?

Asked by blhayes in Windows Programming, .Net Editors & IDEs, Windows 64-bit

Greetings,

Thank you for assisting me with this show stopper. Apparently I'm attempting to run an app with a 32-bit dll on a 64-bit .net 2.0 system (hosted server, I can't fall back to Win2003 32-bit) and when this 32 bit dll code is executed (program runs fine for over a minute before this dll's code is required) I get a stack trace and the message just below. The vendor is not interested in my configuration, so I'm thinking that there must be some way to encapsulate or otherwise provide this code with a nice cozy 32-bit box in which to happily run.

Attempting to run a packaged product on Win2003 Svr 64-bit w .Net 2.0 ( 1@1 hosted server).

Got message:
Type: System.BadImageFormatException
Message: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)

Doing research on the problem, these posts:

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=93912

http://www.devnewsgroups.net/group/microsoft.public.dotnet.framework/topic46570.aspx

Lead me to believe that a DLL was compiled and bound to run "anycpu" and it should have been bound and to run "x86".

If the above is true, how may I set the dll to run x86?

If the above is not true, please suggest workarounds. The vendor seems unwilling to recompile his dll set to explicitly state x86 / 32-bit.

I THOUGHT the whole goal of going 64-bit with the MSIL was to ensure backwards compatibility for things like 32-bit DLLs loaded and running in a 64-bit environment. Surely the 64-bit system architects did not plan to have every packaged software provider recompile all of their kits for 64-bit, requiring everyone to maintain 2 sets of binaries.

Thanks in advance for any advice or ideas on how to do this.

Also, the DLLs for this product seem to be encased in <name>.dll.deploy files. A pointer to get me up to speed on deployment packages and how to look inside and edit the dll characteristics (in anticipation of my having to edit a dll characteristics) would be muchly appreciated.

Thanks you!
Start Free Trial

Keywords: Windows 2003 64-bit error 0x8…

	Title
1	Deploying a VB.NET DLL
2	Terminating VB Active-X DLL
3	Recompilation of DLL
4	recompiling a dll
5	Deploying VB.Net Class Libraries
6	Deploying of Activex Documents

Loading Advertisement...

20080716-EE-VQP-32 / EE_QW_2_20070628

Windows 2003 64-bit error 0x8007000B with a 32-bit dll - how to resolve w/o recompile?

Asked by blhayes in Windows Programming, .Net Editors & IDEs, Windows 64-bit

About this solution