1. ERROR:
Error connecting to the DTM at [%s : %d]: [%s]
Server execution failed, forcing shutdown of the debugger...
Debugger shutdown complete.
2. CAUSE:
integration service use blocked port to initialize debugger connection back to client.
3. solution;
sepcify port range in integration service custom property
3.1 log into admin console
3.2 select integration service
3.3 click edit on "custom property"
3.4 add
DebuggerMinPort 6001
DebuggerMaxPort 6015
3.5 retry debugger, it should be fine.
reference:
Problem Description
ReplyDeleteWhen debugging a PowerCenter mapping the following error is displayed in the Designer:
Error connecting to the DTM at [%s : %d]: [%s]
Cause
In PowerCenter (versions 8.1.1 SP1 and higher), when initiating the debugging of a mapping, the Designer interaction with the server fails in the following way:
1.The client sends a debugging request to the server, to use the new protocol (introduced in PowerCenter 8.1.1 SP1).
2.The server looks up its hostname (using a gethostname call) and opens a port to listen for client requests.
A range for port numbers can be specified with the DebuggerMinPort and DebuggerMaxPort custom properties of the PowerCenter Integration Service.
If these properties are not specified the port range of 9229-9329 is used and the Integration Service will take the first available port in this range.
3.The server sends an acknowledgment to the client which includes the hostname and port number to be used.
4.The client tries to connect to the server using the given hostname and port.
5.If after 10 tries, if the client still fails to connect to the server, the above error is displayed.
Solution
To resolve this issue, do the following:
1.The server sends a host name, and not an IP address.
If the client cannot resolve the host name issued to a valid IP address, then the connection attempt will fail.
In this case you should enter the host name of the server with its corresponding IP address in the host files of the client (Usually c:\winnt\system32\drivers\etc\hosts on Windows ).
2.If the resolved address of the system, where the debugger will run, is not reachable by the client, then you will get an error.
This can be due to firewall settings and clustering of solutions that hide the real address of the server system.
3.If the address issued is reachable and the port used is blocked by a firewall, the debugging attempt will also fail.
The port range should be configured appropriately using DebuggerMinPort and DebuggerMaxPort , and these ports should be opened in the firewall.
More Information
There is also a third custom property for the Integration Service for debugger called DebuggerConnectTimeOut.
This specifies the communication timeout, in seconds. The default value for this parameter is 240 seconds.
Applies To
Product: PowerCenter 8.1.1 SP1, PowerCenter 8.1.1 SP2, PowerCenter 8.1.1 SP3, PowerCenter 8.1.1 SP4, PowerCenter 8.1.1 SP5, PowerCenter 8.5, PowerCenter 8.5.1, PowerCenter 8.6, PowerCenter 8.6.1, PowerCenter 9.0, PowerCenter 9.0.1