[SOLVED] SOAP call: HTTP Get not supported
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-17-2013 04:34 AM
Hi,
I've been working on creating tickets from System Center Operations Manager into SNOW by using a task.
Now, the code worked all fine in our dev environment but our production denies me for some reason and we can't find what the issue is. The user roles are all the same, the SOAP settings are all the same but still it won't work.
Here's a little sample code using PowerShell. It works in dev, but in PROD I get "The request failed with an empty response."
# PROD Ticket
$ciuri = "https://snow/cmdb_ci.do?wsdl"
$secpasswd = ConvertTo-SecureString "password" -AsPlainText -Force
$mycreds = New-Object System.Management.Automation.PSCredential ("username", $secpasswd)
# ci
$ciproxy = New-WebServiceProxy -Uri $ciuri -Class servicenow -Namespace webservice -Credential $mycreds
$getci = new-object webservice.getrecords
$getci.name = "ServerName"
$ciproxy.getrecords($getci)
Of course this doesn't generate a ticket but I get the same error when trying to generate one. And prior to that I query for user id and the cmdb item.
Now, I tested it in SoapUI to see if I can get a more detailed error and here it's pretty much the same. Works fine in DEV, but not in our Production system raising an error: Error completing SOAP request - HTTP GET not supported
Is there something we have overlooked in the security settings?
We have other applications that run the same queries against users, etc. and they seem to just work fine. I even tried their user and got the same error. Might it be some web service setting?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-18-2013 07:01 AM
Got it to work now by changing my project to use a Service Reference and the SoapClient object instead of a Web Reference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-09-2021 11:02 PM
I have the same issue, could you kindly elaborate on how you got it fixed?