Elinore, We ran into a similar issue when we upgraded across the 7.0.1 patch 004 threshold where we had to recreate those filters consuming external webservices. What version was your dev environment when you created the filter? If it was created on a system that was 7.0.1 patch 003 or below, you may need to recreate the filters with all components on 7.0.1 patch 004 or above due to Remedy change to how they handled namespaces.
There's a note in the compatibility matrix that says that "Use of webservices requires that all ARS/Mid-tier/Admin Tool components be at 7.0.1 patch 004 or above, or all be at 7.0.1 patch 003 or below". What it doesn't say anywhere that I could find was that when you cross this threshold that existing webservices components may break. Hope this helps! Dennis Ruble Rockwell Collins Elinore AR <elinore.ex...@gmail.com> Sent by: "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> 04/07/2009 11:28 PM Please respond to arslist@ARSLIST.ORG To arslist@ARSLIST.ORG cc Subject Prod ARS 7.0.1 p006 cannot consume a webservice hi all, we are having a critical Production issue regarding Remedy consuming a webservice and was hoping someone here can help us. we are using ARS 7.0.1 p006 MT 7.0.1 p006 AR Admin 7.0.1 p006 we have a filter that we created in a Dev server sometime ago that consumes an external webservice. this works just fine and now we are ready to move this filter to Production. we did and lo and behold, the filter does not work. no problems with permission, proxy settings and all, but we keep getting issues: 1) takes too long for the call to respond when the filter is fired. 2) when it does respond, we get either: a) timeout error on the database (the database takes too long to respond) b) "ARERR [9130] An exception occurred from the WebService class : Unknown Error" as a test, I created a filter that calls to a public webservice found in the BMC Developer Network http://ws.cdyne.com/ip2geo/ip2geo.asmx?wsdl and mapped the input and output fields to our test form in production. then I created a record on the form that fires a filter calling that webservice. I tested this same script in our devel server and I can consume that same webservice just fine. but errors out in production. our filter log shows this: > Checking IP2Geo (500) > --> Passed -- perform actions > 0: Set Fields <-- this is where the web service is called */Stop filter processing > An exception occurred from the WebService class > Unknown Error > **** Error while performing filter action we did a arplugin log compare at both times and here's what we saw: we noticed that on our Dev, the line: <FINE> URL Auth User = null <FINE> URL Auth Password = <hidden> is not getting called (does not appear in the log), while in Prod this appears in the log. another significant difference is that when the web service is called, the logs show: DEV ? it used ROOT as the element <FINE> soapInputDocument = <ROOT xmlns="urn:IP2Geo" xmlns:ns1="http:// ws.cdyne.com/IP2Geo" xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <ns1:ipAddress>206.190.60.37</ns1:ipAddress> <ns1:licenseKey/> </ROOT> while in: PROD ? there is an appended text ?ns0:? before ROOT <FINE> soapInputDocument = <ns0:ROOT xmlns:ns0="urn:IP2Geo" xmlns:ns1="http://ws.cdyne.com/IP2Geo"; xmlns:xsd="http://www.w3.org/ 2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <ns1:ipAddress>149.122.21.107</ns1:ipAddress> <ns1:licenseKey/> </ns0:ROOT> can this difference be the root cause on why the exact same filter calling the same webservice on different servers (with the same ARS version, patch, OS, DB, Mid-Tier) is giving us different results on our Production server compared to our Devel server? does anyone have any idea on what could be causing this on our Production server? any help is greatly appreciated!!! _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
