madmagi Posted November 21, 2007 Report Share Posted November 21, 2007 We are extensive users of SOA services here. All of our wsdl's pass in complex data types via XML documents, when I use the PowerGadgets Creator the application simply locks up once I click on finish. I have downloaded and applied all updates to get to current release (as of 11/20/07) (it used to crash) Steps to reproduce 1. Select Wsdl 2. Select Method to Invoke 3. Past in xml for the only parameter present I am trying to present that is could be an easy way to retrive data and graph it without any/much programming. Quote Link to comment Share on other sites More sharing options...
marco.shaw Posted November 22, 2007 Report Share Posted November 22, 2007 Is there any kind of external access so that we could try it externally by connecting ourselves? Would you be able to try with the invoke-webservice cmdlet to see if it works alone? Quote Link to comment Share on other sites More sharing options...
madmagi Posted November 26, 2007 Author Report Share Posted November 26, 2007 No i am sorry there is no external access. All of a soa services accept a single parameter which is an xml document, for example: <ProbeServiceRequest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" SchemaVersion="1" xmlns="http://schemas.compassion.com/management/probeservicerequest/2007-04-01"><ServiceName>SomeData</ServiceName></ProbeServiceRequest> In this request the ProbeService reads the xml and responds accordingly (which is also a xml document). This is a very simplistic document, most of the documents have many elements in them. We have others consuming these sevices from .NET applications and ASP applications right now. Lester Quote Link to comment Share on other sites More sharing options...
madmagi Posted November 29, 2007 Author Report Share Posted November 29, 2007 re: trying invoke-webservice, When i open powershell powergadgets console window i get this error:L WARNING: The following errors occurred when loading console C:\ProgramFiles\PowerGadgets\PowerGadgets.psc1:Cannot load Windows PowerShell snap-in PowerGadgets because of the followingerror: The Windows PowerShell snap-in module C:\ProgramFiles\PowerGadgets\PowerGadgets.Commands.dll does not have required WindowsPowerShell snap-in strong name PowerGadgets.Commands, Version=1.0.2769.24553,Culture=neutral, PublicKeyToken=a1878e2052c08dce.Windows PowerShell Quote Link to comment Share on other sites More sharing options...
marco.shaw Posted November 29, 2007 Report Share Posted November 29, 2007 I've seen this type of error when one drops a DLL on top of another DLL, without first unregistering the original DLL properly. Either try a uninstall/reinstall or uninstall/upgrade. Marco Quote Link to comment Share on other sites More sharing options...
madmagi Posted November 30, 2007 Author Report Share Posted November 30, 2007 ok reinstalling powergadgets fixed the open powershell console issue. Trying to invoke using the invoke-webservice also failed PS C:\WINDOWS\system32>invoke-webservice -WSDL http://dcorp77/management/managementservice.asmx?WSDL -Method ProbeService "<?xml version="1.0"?><ProbeServiceRequest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" SchemaVersion="1" xmlns="http://schemas.compassion.com/management/probeservicerequest/2007-04-01"><ServiceName>CRDataProbe</ServiceName></ProbeServiceRequest>"Invoke-WebService'>http://schemas.compassion.com/management/probeservicerequest/2007-04-01"><ServiceName>CRDataProbe</ServiceName></ProbeServiceRequest>"Invoke-WebService : TypeConverter cannot convert from System.String.At line:1 char:18+ invoke-webservice <<<< -WSDL http://dcorp77/management/managementservice.asmx?WSDL -Method ProbeService "<?xml version="1.0"?><ProbeServiceRequest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" SchemaVersion="1" xmlns="http://schemas.compassion.com/management/probeservicerequest/2007-04-01"><ServiceName>CRDataProbe</ServiceName></ProbeServiceRequest>" try again with " escaped in PS C:\WINDOWS\system32> invoke-webservice -WSDL http://dcorp77/management/managementservice.asmx?WSDL -Method ProbeService <?xml version="1.0"?><ProbeServiceRequest "xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" SchemaVersion=\"1\" xmlns=\"http://schemas.compassion.com/management/probeservicerequest/2007-04-01\"><ServiceName>CRDataProbe</ServiceName></ProbeServiceRequest>"The redirection operator '<' is not supported yet.At line:1 char:101+ invoke-webservice -WSDL http://dcorp77/management/managementservice.asmx?WSDL -Method ProbeService <? <<<< xml version="1.0"?><ProbeServiceRequest "xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" SchemaVersion=\"1\" xmlns=\"http://schemas.compassion.com/management/probeservicerequest/2007-04-01\"><ServiceName>CRDataProbe</ServiceName></ProbeServiceRequest>"PS C:\WINDOWS\system32> Any other Ideas? Quote Link to comment Share on other sites More sharing options...
marco.shaw Posted December 1, 2007 Report Share Posted December 1, 2007 Could be the formatting is off, but did you use the backslash "\" to escape the quotes? You must use the backtick "`" in PowerShell to escape special characters. Quote Link to comment Share on other sites More sharing options...
madmagi Posted December 4, 2007 Author Report Share Posted December 4, 2007 ah the backtick, forgot about that with powershell, changed to that, no diff. Quote Link to comment Share on other sites More sharing options...
marco.shaw Posted December 4, 2007 Report Share Posted December 4, 2007 What output do you get now? I'll have to try to find a webservice that requires complex XML as input. I tried it, and just get: PSH> ./invoke.ps1Invoke-WebService : Unable to connect to the remote serverAt C:\invoke.ps1:1 char:18+ invoke-webservice <<<< -WSDL http://dcorp77/management/managementservice.asmx?WSDL -Method ProbeService "<?xml version=`"1.0`"?><ProbeServiceRequest xmlns:xsd=`"http://www.w3.org/2001/XMLSchema`" xmlns:xsi=`"http://www.w3.org/2001/XMLSchema-instance`" SchemaVersion=`"1`" xmlns=`"http://schemas.compassion.com/management/probeservicerequest/2007-04-01`"><ServiceName>CRDataProbe</ServiceName></ProbeServiceRequest>" So it appears to accept the syntax for me at least. You are putting everything in one single line? Marco Quote Link to comment Share on other sites More sharing options...
madmagi Posted December 5, 2007 Author Report Share Posted December 5, 2007 Windows PowerShellCopyright © 2006 Microsoft Corporation. All rights reserved.PS C:\WINDOWS\system32> invoke-webservice -WSDL http://dcorp77/management/managementservice.asmx?WSDL -Method ProbeService "<?xml version=`"1.0`"?><ProbeServiceRequest xmlns:xsd=`"http://www.w3.org/2001/XMLSchema`" xmlns:xsi=`"http://www.w3.org/2001/XMLSchema-instance`" SchemaVersion=`"1`" xmlns=`"http://schemas.compassion.com/management/probeservicerequest/2007-04-01`"><ServiceName>CRDataProbe</ServiceName></ProbeServiceRequest>"Invoke-WebService : TypeConverter cannot convert from System.String.At line:1 char:18+ invoke-webservice <<<< -WSDL http://dcorp77/management/managementservice.asmx?WSDL -Method ProbeService "<?xml version=`"1.0`"?><ProbeServiceRequest xmlns:xsd=`"http://www.w3.org/2001/XMLSchema`" xmlns:xsi=`"http://www.w3.org/2001/XMLSchema-instance`" SchemaVersion=`"1`" xmlns=`"http://schemas.compassion.com/management/probeservicerequest/2007-04-01`"><ServiceName>CRDataProbe</ServiceName></ProbeServiceRequest>"PS C:\WINDOWS\system32> if i change the wsdl to be an incorrect address like it would be in your case, i get the same error you see on your end. Lester Quote Link to comment Share on other sites More sharing options...
madmagi Posted December 7, 2007 Author Report Share Posted December 7, 2007 I believe Powergadgets could be a great tool to be used here at Compassion in other groups, anything i can do to help facilitate this issue? My goal is to show how quickly a admin could create a powergadgets gadget for thier desktop to monitor things such as our soa infrastructure. Showing powergadgets doing things like memory/running process while impressive has not peeked the curiosity much as i would have thought. Showing it against specific applications w/in the environment seems to have a much better response. The key is demonstrating Powergadgets creator and the simplicity for most anyone to perform monitoring tasks rather than software developers in their darkened rooms. Quote Link to comment Share on other sites More sharing options...
marco.shaw Posted December 7, 2007 Report Share Posted December 7, 2007 madmagi, Email me at marcos@_oneline.powergadgets.com (remove "_oneline." though). I still feel like there's a synax error in your command. Maybe if we exchange scripts, we can figure this out, at least the cmdlet. As for why the Creator is having issues, I don't know if that's related or not or something else alltogether. Marco Quote Link to comment Share on other sites More sharing options...
JuanC Posted December 8, 2007 Report Share Posted December 8, 2007 Invoke-WebService (or the PG Creator) was not prepared to call a method that receives an XmlDocument as a parameter. We have an internal build that adds support for this, please send an email to support at powergadgets dot com or marco's email and we should be able to provide a build for you to test early next week. Regards, JuanC Quote Link to comment Share on other sites More sharing options...
madmagi Posted December 13, 2007 Author Report Share Posted December 13, 2007 Ah! That is great news. Thanks. Sent an email to Marcos, waiting on answer. Lester Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.