Whenever I try to save I get this error (via javascript console)
POST https://domain.local/_vti_bin/client.svc/ProcessQuery 404 (Not Found)
Any ideas?
For me the problem was twofold:
My server was missing the HTTP Activation in WCF Services in the .NET Framework 4.5 Feature.
Go to Server Manager => Manage => Add Roles and Features => Features and make sure it's checked.
I had to add the Negotiate-provider for Windows Authentication in IIS.
Open IIS, go the the site in question, open Authentication, right click Windows Authentication, click Providers..., add Negotiate from Available Providers. I'm having it below NTLM and that works fine.
Related
I am on Postman 7.5.0.
I am calling one api from the postman, and get an error as "There was an error connecting to ."
But when I executed the curl code generated from the postman, it worked just fine(they were also calling the app running on my pc).
I also tried to copy the link and sent to my coworker and they were getting correct responses too.
I referred to other questions related to this topic and turn off all proxy stuff, they didn't help.
My app has lots of apis and this is the only one that I could not get any response via postman call.
Any thoughts?
In my case I had to go to Settings -> "SSL Certificate Verification" and turn this off, and everything worked great.
Have you used chrome extension Postman Interceptor?
I think Postman is not able to intercept https or http request.
Follow the steps:
To use Interceptor with Postman Chrome, you can take the following steps:
Install Postman from the Chrome Web Store.
Install Interceptor from the Chrome Web Store.
Open Postman, click on the Interceptor icon(near the sync icon) in the toolbar, and toggle to On.
The Postman Chrome app's Interceptor functions as a proxy to capture HTTP and HTTPS requests.
More Information is available at https://learning.postman.com/docs/sending-requests/capturing-request-data/interceptor/#using-the-interceptor-with-postmans-chrome-app
For my case, it was me mistakenly unchecked one of the postman default headers.
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 am using the desktop version of Postman at a client site to test an API. However, I am unable to access any SSL sites in Postman, such as the Git Hib API: https://api.github.com/users/karlgjertsen
However, I can make the same API call through Chrome, so this is Postman specific.
I assume it is down to proxy settings, but I am not sure how to view or update these in Postman. Has anyone had any experienced something similar?
I turned OFF both Global Proxy Configuration and Use System Proxy in Settings->Proxy tab in Postman and it started to work.
This solved my issue :
The option "Respect HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables." was selected by default in the proxy settings. I turned off this option and it worked for me.
Follow these steps on postman -
Go to file=>Settings => Proxy (Tab) and uncheck the "Use System Proxy" checkbox. That should work
Posting as the other solutions presented in this thread did not work in our corporate environment. We have a proxy configured on the network which uses Windows Default Credentials (username and password) for authentication. For whatever reason the browser knows how to pass these details with each request but postman does not by default.
Solution was to update the Default Proxy Configuration under settings -> proxy -> Default Proxy Configuration -> Tick 'This proxy requires authentication' then enter Windows Username and Password. Leave Use the system proxy and Add a custom proxy configuration settings disabled.
From the Windows start menu go to Change proxy settings and configure the host and port there.
This turned out to be a local security policy that was applied to the machine in use. The local SSL proxy had a policy applied and it would not allow me to make a secure connection unless it was through a web browser.
I use a CascadingDropDownList of the AJAXControlToolkit in a ASP.NET MCMS 2002 web application. The CascadingDropDownList works as expected until "Anonymous access" and "Integrated Windows Authentication" flags are both checked (and this is the situation in the production environment) in the Directory Security settings on the website under IIS.
The error I get is:
500 Internal Server Error
No web service found at:
If I uncheck the anonymous access or the windows authentication everything is ok.
Any suggestions?
Modifying:
ServicePath="~/IB20/Services/RegioniProvinceService.asmx"
in:
ServicePath="http:///Services/RegioniProvinceService.asmx"
solved the issue.
It seems that having "Anonymous access" and "Integrated authentication" both checked, brokes the functionality if the ServicePath of the CascadingDropDownList is file-system oriented.
I have a FinalBuilder project where I deploy an ASP.Net website to a remote folder, configured as a website in IIS.
As part of my build script, I want to use the FinalBuilder action HTTP Get File to help determine whether my deployment was succesful.
I'm having difficulty, because the website is configured (under IIS 6) to use Integrated Windows Authentication, and anonymous access is not enabled.
Now the HTTP Get File action, has only a handful of properties, one of which is a security section, containing a UserName and Password. Great I thought! I can just put some valid credentials in there, which FinalBuilder will impersonate, whilst retrieving my file.
It turns out I was mistaken. I receive the following error:
Error retrieving url : Socket Error # 10061
Connection refused.
If I run the action without setting the Security Username and Password, I get the following error:
Error retrieving url : HTTP/1.1 401 Unauthorized Response Code : 401
Here are some facts to help with the context of my problem.
I'm running FinalBuilder 6 Professional, upon a Windows Server 2003 installation, and deploying my ASP.Net website to a remote IIS6 server within our corporate LAN.
If I configure IIS on the remote server to allow Anonymous access, I can run the HTTP Get File action without error. However, running this particular site with anon access is not acceptable in our situation.
Can anyone help suggest a workaround?
For a definitive answer, I think the Finalbuilder Forum is probably your best bet.
My guess, though, is that the HTTP library used by FB doesn't support Windows authentication, and is failing because no common authentication method can be negotiated. Since HTTPS isn't supported either by the 'HTTP Get File action', the possible workaround of allowing basic authentication on your site isn't a good idea, as you would be passing credentials over the network in plain text.
The only remaining workaround I can think of (other than waiting for a future FB release), is creating your own FB action to retrieve the file. Using the .NET Framework System.Net.WebClient, that should be trivial. Just start with a standalone EXE to make sure everything works, then refactor it into a 'real' action using FinalBuilder Action Studio (if that's even required: spawning an external EXE may work just fine in your case).