I have a 3rd party webservice that runs by posting a soap message directly to a dll.
It runs perfectly on my development machine, but when I try and deploy it to Windows 2008 R2 64-bit using IIS 7 it fails, indicating error 404 2 1260 in the IIS7 log.
I have done all of the normal stuff, including:
Setting the ISAPI and CGI Restrictions,
Adding the Handler Mappings and setting them to Execute,
Setting Handler Mappings Feature Permissions to Execute
but none of that helps.
When I enable Failed Request Logging, the lowest-level detail that I can get is:
Error Code 0x800704ec
Error Code 2147943660
Error message IsapiModule This program is blocked by group policy
What is going on!?
The DLL was a 32-bit DLL.
By default, IIS 7 running on Windows Server 2008 R2 64bit doesn't allow 32bit dlls to run.
There's a little setting in the Application Pool Advanced Settings called Enable 32-Bit Applications. Set it to True in the application pool to which your web service belongs, and it should start working!
Related
I'm on SP 2013 enterprise single server dev machine
I have prepped SP to host a remote on prem hosted app.
I navigate to /_layouts/15/AppRegNew.aspx and enter the App Id, Secret, etc and hit create ... error ID 3 and 1309 are thrown:
ID 3 is:
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/1660113
Exception: System.ServiceModel.ServiceActivationException: The service '/9fabc3ed921a42739ebeb5576c6b4e6a/AppMng.svc' cannot be activated due to an exception during compilation. The exception message is: Microsoft SharePoint is not supported in 32-bit process. Please verify that you are running in a 64-bit executable.. ---> System.PlatformNotSupportedException: Microsoft SharePoint is not supported in 32-bit process. Please verify that you are running in a 64-bit executable.
followed by 1309:
Exception information:
Exception type: ServiceActivationException
Exception message: The requested service, 'http://servername:32843/9fabc3ed921a42739ebeb5576c6b4e6a/AppMng.svc' could not be activated.
The app management and subscription services are started and running. I have a valid trust setup.
Thoughts?
In IIS there were app pools that had enable 32-bit set to true, so I set it to false and was enable to register the app.
New Windows server 2012 R2 installation, added ASP.Net and .Net 3.5
Getting following error when trying to browse web service file svc:
Could not load type '%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll'.
Any thoughts?
Open command prompt as administrator
Navigate to C:\Windows\Microsoft.Net\Framework\v3.0\Windows Communication Foundation
and execute the command:
ServiceModelReg.exe /i
Navigate to c:\windows\Microsoft.NET\Framework\v4.0.30319
and execute the command:
aspnet_regiis -iru
Some roles and features are required on the server
enable server role "Internet Information Services", all underlaying services will be included
enable feature "HTTP Activation", this both under .NET framework 3.5 and .NET framework 4.5
In IIS make sure there is a "handler mappings" configured for the "*.svc" files
That error message turned out to be a bit of a red herring when I encountered it. I simply didn't have a HEAD route setup in WebApiConfig and was getting hundreds of HEAD requests per day. So, if you've verified that you have all the necessary Windows Features installed, then next check that you have default routes setup for each HTTP request method.
I developed a webservice that I'm testing on my development machine using IIS. If I call the webservice from the local machine (http://localhost/BaanWeb/service1.asmx, click on the webservice) the debugger hits a breakpoint.
If I call the same webservice from a remote machine (http://ipaddress/baanweb/service1.asmx, click the webservice) the webservice is called, I see a value being returned, but the breakpoint is not hit, so I cannot debug.
You need to attach to the remote server (at "ipaddress"): http://msdn.microsoft.com/en-us/library/233w9kd4(v=vs.90).aspx
This article may also help (even though it is asp.net specific): http://www.codeproject.com/Articles/38132/Remote-IIS-Debugging-Debug-your-ASP-NET-Applicatio
I am working with a fresh install of CF10 on a Windows Server 2008R2 machine.
I am getting the following error:
HTTP Error 500.0 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "C:\ColdFusion10\config\wsconfig\1\isapi_redirect.dll" failed
Detailed Error Information
Module
IIS Web Core
Notification
Unknown
Handler
StaticFile
Error Code
0x80070005
Requested URL
https://127.0.0.1:443/cfide/administrator/
Physical Path
C:\ColdFusion10\cfusion\wwwroot\CFIDE\administrator\
Logon Method
Not yet determined
Logon User
Not yet determined
Can anyone point me in a direction on how to fix this? I have followed installed and uninstalled the connectors several times using wsconfig with no success.
I had to actually reboot the entire server for wsconfig updates to take effect.
I've implemented a WMI provider (Window service, Instance, Methods and Properties provider).
It works fine on Windows Server 2003, but when it run on Windows Server 2008 with non-local administrator user, I cannot query it.
The error I get is 0x8004101d - unexpected error.
When the service user is a local admin everything is OK.
What could it be???
Thanks!
OK, the problem was that I didn't specify the HostingModel, so it defaulted to NetworkServiceHost. The one needed one is LocalSystemHostOrSelfHost (that is the default in prior to Vista OSs).