|
| Not a valid 32-bit dll when opening page |
| Started by Antonio Diaz, Feb., 19 2025 4:21 AM - 1 reply |
| |
| | | |
|
| |
| Posted on February, 19 2025 - 4:21 AM |
Hi everyone,
I'm facing an issue while trying to run my WebDev project on a server. One of my DLL files (oentrega.dll) is causing an error:
"oentrega.dll is not a valid Win32 application."
What I have checked so far:
✅ The DLL is in the correct directory and has the right name.
✅ I tried unlocking it (Right-click → Properties → Unblock).
✅ I checked the DLL architecture using dumpbin and confirmed it matches my WebDev environment (both are 64-bit).
✅ I used Dependency Walker to verify missing dependencies, but nothing critical showed up.
✅ I attempted running WebDev in 32-bit mode just in case, but the error persists.
✅ I also tried recompiling the DLL and redeploying, but no luck.
Environment details:
WebDev running on Windows Server
WebDev Server is set to listen
IIS is running on port 80
Has anyone encountered this issue before? Any ideas on what could be causing this?
Any help or suggestions would be greatly appreciated!
Thanks in advance!
Antonio Diaz |
| |
| |
| | | |
|
| | |
| |
Registered member
3 messages |
|
| Posted on April, 15 2025 - 9:18 AM |
Since you've already checked most of the usual suspects, here are a couple of ideas to try out. Have you looked at the IIS application pool settings? Sometimes, IIS might default to 32-bit, even when you’re working with 64-bit DLLs, and that could be the cause of the problem. You can check that by going into the application pool settings and making sure it’s configured to use 64-bit.
Also, it's worth thinking about any other possible conflicts. WebDev or IIS could sometimes have trouble with specific DLLs, especially if there’s a registry or configuration issue floating around. A good move might be to clear out any temporary files or, if possible, reinstall the WebDev components just to be on the safe side. It sounds like you're already on top of things, but clearing everything out might fix something that’s hidden away.
Lastly, have you tried running the DLL on its own, outside of the WebDev setup? That might help you see if the issue is with the DLL itself or with how it’s interacting with WebDev. |
| |
| |
| | | |
|
| | | | |
| | |
|