You don't have to worry about debugging as that is only for Visual
Studio.  The only part of the message below that applies is the
Connecting to server failed.  Since the Remedy server is hosting a Web
Service you must have a Mid-Tier server (or it wouldn't be able to
consume the WSDL from the Remedy WSDL url).  Is the Mid-Tier Unix or NT?
 
What do you see in the Mid-Tier logs when Prod TCATS loads the WSDL and
then when it tries to consume the service?  You might compare it to the
Dev Mid-Tier logs for the same tasks.
 
Fred


________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger
Sent: Friday, May 23, 2008 1:55 PM
To: [email protected]
Subject: OT: Web Service Problem



Hello All,

 

I am reaching out to you in the hopes you can shed some light on an
issue we are having. I have pasted together our issue below

 

All thanks in advance for any support you can give, I am stuck and at
this point do not know which way to turn to resolve this issue, so any
help is very much appreciated.

 

Here is the background

 

The Remedy server is a Unix server and the TCATS Server is an NT Server

The Remedy Unix environment is a clustered environment with one Active
and one Passive node. There is a virtual IP in place.

I am not sure what the TCATS environment configuration is

The Remedy server has a Web Service that the TCATS Server is consuming.
The IP in the WSDL is for the Virtual Server

The TCATS Prod Server can load the WSDL and Map the fields but when
TCATS tries to send data via WSDL this error is retuned

 

 

 

 

The problem is happening between the two production environments, this
was not a problem with the Dev environments 

            TCATS Consuming Remedy WSDL; 

TCATS Dev to Remedy Dev no errors

            TCATS Dev to Remedy Prod no errors

            TCATS Prod to Remedy Dev no errors

 

We also have a process where Remedy Consumes a TCATS WSDL and this is
working without any errors in all configurations. 

 

We are also looking at the error from a different angle to cover all
bases, and that is related to the "The debugger cannot connect to the
remote computer".  I have found some threads in VS forums that state a
remote debugger file must be loaded on the remote server but everything
I read is related to NT Servers so the question has be asked, 

The forums thread states - it is necessary to install rdbgsetup.exe in
the server where the web service runs, but this is for the .net web
service. Is there any thing similar to handle this permission wizard for
java apps running on Unix?

I know nothing about Visual Studio so I do not know how relevant this
is.

 

This is a question I have if a debugger file is needed then how did this
work from TCATS Dev to Remedy Prod?

 

Thanks.

 

 

Roger A. Nall

Manager, OSSNMS Remedy

T-Mobile USA

Desk: 813-348-2556

Cell: 973-652-6723

FAX: 813-348-2565

sf49fanv     AIM IM

RogerNall   Yahoo IM

 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

<<image001.jpg>>

Reply via email to