Facing issues in creating proxy from Soap WSDL

[GauravServiceNo]

I am trying to generate proxy by adding Service refrence " https://demo.service-now.com/incident.do?WSDL" in my DotNet application but getting error as below:

"Metadata contains a reference that cannot be resolved: 'https://demo.service-now.com/incident.do?WSDL'.
There was no endpoint listening at https://demo.service-now.com/incident.do?WSDL that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (407) Proxy Authentication Required.
If the service is defined in the current solution, try building the solution and adding the service reference again."

I am passing credentials as "admin", "admin"

Note: Somedays back I tried and I was able to create proxy but when I am retrying to add proxy now, getting error.

Also, I tried making my scripting WebService, but then also I am not able to create proxy from the WSDL link given.
Can any please help me that why I am getting error.

[GauravServiceNo]

I am trying to add service refrence in my dotnet application using "https://demo.service-now.com/incident.do?WSDL".
I am getting error as :

Metadata contains a reference that cannot be resolved: 'https://demo.service-now.com/incident.do?WSDL'.
There was no endpoint listening at https://demo.service-now.com/incident.do?WSDL that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (407) Proxy Authentication Required.
If the service is defined in the current solution, try building the solution and adding the service reference again."

I am passing credentials as "admin", "admin"

Can anyone please help me to resolve this.

Thanks,
Gaurav

[john_andersen]

Some of the instances in the ServiceNow datacenter are returning an HTTP instead of HTTPS for the actual SOAP endpoint within the WSDL. You may wish to verify that this is not the case for you.

Check out my information on this and how to fix it at:
http://www.john-james-andersen.com/blog/service-now/correcting-misguided-soap-endpoints-in-servicenow.html