Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
HTTP 500 errors when referencing VFP dll
Message
General information
Forum:
ASP.NET
Category:
Web Services
Environment versions
Environment:
ASP.NET
OS:
Windows Server 2008
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Miscellaneous
Thread ID:
01577871
Message ID:
01577981
Views:
67
Thank you so much for your reply, Frank. You were definitely on the right track with the 32-bit dll within a 64-bit environment. I have finally decided to move my project away from our SBS 2011 server as I ran into many layers of problems that are still unresolved at this time. However, I installed IIS 7.5 on win8 and got the project running within an hour, so I'm setting up a virtual machine to purely host this project, which should be ready this afternoon.


>>I have an ASP.NET web service wrapper for some VFP functions that I have developed. In my development machine using Visual Studio 2008 (and have now tried VS 2013 preview) and the internal web server, all runs well. When I deploy my web service to a production server, even the HelloWorld function returns an HTTP 500. It seems that as soon as I have a DLL referenced in my web service, the whole project dumps. Considering this works in the local Visual Studio web server/browser, shouldn't it work on the IIS 7 server as well?
>>
>>I have tried the following:
>>
>>1. Successfully registered the amsync_web.dll with regsvr32 on the server in the development directory. I get the HTTP 500
>> *note* that there is also an interop.amsync_web.dll in the bin directory of the web folder.
>>2. Removed the interop.amsync_web.dll from the bin folder. Now I get a compilation error BC30002: type 'amsync_web.amsync_web' is not defined.
>>3. Fine, I unregistered the development copy of the dll and tried to register the interop copy in the bin directory. Get ugly error and unable to register.
>>
>>Can anyone help steer me on what I thought should be a fairly straightforward process? Much gratitude to anyone who can keep me from wasting any more hours of time on this...
>
>Check if the production server is running in 64-bits only mode. If it is, your vfp com object (which is 32 bits only) needs to run out-of-process. The easiest way (at least for me) is to create an .exe instead of a .dll. In my case, I also had to change the web service from 2.0 to 4.0, so you could check that one as well.
>
>Regards,
>Frank
Steve Howie, owner
DaSH Technology
Denver, CO
Previous
Reply
Map
View

Click here to load this message in the networking platform