You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will throw an error, stating that it cannot download the wsdl.
New-WebServiceProxy : The remote name could not be resolved: 'www.webservicex.net'
At line:1 char:1
+ New-WebServiceProxy -Uri http://www.webservicex.net/uszip.asmx?WSDL
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (http://www.webs...uszip.asmx?WSDL:Uri) [New-WebServiceProxy], WebException
+ FullyQualifiedErrorId : WebException,Microsoft.PowerShell.Commands.NewWebServiceProxy
PS C:\Users\lifebound\scripts> $Error[1].Exception
There was an error downloading 'http://www.webservicex.net/uszip.asmx?WSDL'.
PS C:\Users\lifebound\scripts> $Error[1].Exception.InnerException
The remote name could not be resolved: 'www.webservicex.net'
this error can be replicated by multiple users, both on public and private networks, when using VSC with the powershell plugin. It cannot be replicated in PowerGUI, Powershell ISE, or the PoSH CLI.
Attached Logs
Logs have been emailed for security, with this issue referenced.
The text was updated successfully, but these errors were encountered:
@lifebound, it seems that Webservicex no longer presents the uszip service, hence you're getting the error. Doesn't seem to be related to PowerShell extension
System Details
$PSVersionTable
:Issue Description
I am experiencing a problem with creating a New-WebServiceProxy object.
Steps to reproduce:
PS C:\> $zip = New-WebServiceProxy -Uri "http://www.webservicex.net/uszip.asmx?WSDL"
This will throw an error, stating that it cannot download the wsdl.
this error can be replicated by multiple users, both on public and private networks, when using VSC with the powershell plugin. It cannot be replicated in PowerGUI, Powershell ISE, or the PoSH CLI.
Attached Logs
Logs have been emailed for security, with this issue referenced.
The text was updated successfully, but these errors were encountered: