Author |
Message |
Pete Melton
Joined: 30 Jan 2002 Posts: 23
|
|
Version 2 to 3 Upgrade |
|
I upgraded one our systems today and I am reciving an error that is quite strange. Distributed Service error. I have tested the agent profile from both machines and connection succeeds. Callbacks to retrieve remote glabal variables fail. This did not occur on the first system we upgraded. Any ideas? Remote Job execution error. Exit Code: -1 Connection to Agent [machine] failed. Distributed service error
|
|
Wed Feb 20, 2002 3:05 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
Re: Version 2 to 3 Upgrade |
|
Check if you have security activated on the remote scheduler/agent and if yes, you have connect privileges. If not, give youself the required permissions. : I upgraded one our systems today and I am reciving an error that is quite : strange. Distributed Service error. I have tested the agent profile from : both machines and connection succeeds. Callbacks to retrieve remote glabal : variables fail. This did not occur on the first system we upgraded. Any : ideas? : Remote Job execution error. Exit Code: -1 : Connection to Agent [machine] failed. Distributed service error
|
|
Wed Feb 20, 2002 4:00 pm |
|
 |
Pete Melton
Joined: 30 Jan 2002 Posts: 23
|
|
Re: Version 2 to 3 Upgrade |
|
Security is not enabled. We have never enabled it before (version 2). I assume if security is turned off this is NOT the issue?
|
|
Wed Feb 20, 2002 4:05 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
Re: Version 2 to 3 Upgrade |
|
Version 2 does not feature security, version 3 does. Try enabling security. By the way, you are not trying to connect using different versions, are you? : Security is not enabled. We have never enabled it before (version 2). I : assume if security is turned off this is NOT the issue?
|
|
Wed Feb 20, 2002 4:13 pm |
|
 |
Pete Melton
Joined: 30 Jan 2002 Posts: 23
|
|
Re: Version 2 to 3 Upgrade |
|
No sir. Enabling Security did not do it either. The connection is immediatly closed. Although the test connection shows success. I have used IP and names both of which exhibit the same behavior.
|
|
Wed Feb 20, 2002 7:33 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
Re: Version 2 to 3 Upgrade |
|
Please turn on tracing (Tools/Options menu; Log page; Trace enabled) and try again. Please let me know what you see in the trace window, specifically if there is "connection denied" or a similar message. : No sir. Enabling Security did not do it either. The connection is immediatly : closed. Although the test connection shows success. I have used IP and : names both of which exhibit the same behavior.
|
|
Wed Feb 20, 2002 8:10 pm |
|
 |
Pete Melton
Joined: 30 Jan 2002 Posts: 23
|
|
Re: Version 2 to 3 Upgrade |
|
This looks like the exception: SMI02 Connection(013FD400): ERROR OCCURRED: Distributed Communications Error: Connect call failed with error WSAEADDRNOTAVAIL, (220) (8004200D)
|
|
Thu Feb 21, 2002 9:12 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
Re: Version 2 to 3 Upgrade |
|
Specified address is not available This error occurs when an application attempts to connect to a remote host, and the address is not available from the local system. Suggestion: try specifying TCP/IP address of the remote computer, and not that computer name. Also try pinging that machine from DOS prompt. Also make sure when you test connection manually and run the job you use the same remote agent profile. : This looks like the exception: SMI02 Connection(013FD400): ERROR OCCURRED: : Distributed Communications Error: Connect call failed with error : WSAEADDRNOTAVAIL, (220) (8004200D)
|
|
Thu Feb 21, 2002 10:07 am |
|
 |
Pete Melton
Joined: 30 Jan 2002 Posts: 23
|
|
Re: Version 2 to 3 Upgrade |
|
The machine can be pinged by name or IP and connection test succeeds. I have used machine name and IP in the agent config to no avail.
|
|
Thu Feb 21, 2002 11:31 am |
|
 |
Pete Melton
Joined: 30 Jan 2002 Posts: 23
|
|
Re: Version 2 to 3 Upgrade |
|
What does WSAEADDRNOTAVAIL mean exactly?
|
|
Thu Feb 21, 2002 11:46 am |
|
 |
Pete Melton
Joined: 30 Jan 2002 Posts: 23
|
|
Re: Version 2 to 3 Upgrade |
|
Trace file of the master shows the following upon initialization.
DPB01 Connection(013FD218): ConnectToServer : application(2002), location(10.25.150.227), driver(WinSock). ... (00000000)
SMI02 Connection(013FD3D8): ERROR OCCURRED: The server '2002' could not be located. It is probably not started. (00000002)
DPB01 Connection(013FD218): ConnectToServer : application(2002), location(10.25.150.227), driver(WinSock). FAILED (80042005)
|
|
Thu Feb 21, 2002 1:00 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
Re: Version 2 to 3 Upgrade |
|
Please check again, if you use the same profile. If you can connect manually, it is unlikely that you get "inavlid host address" when referencing the same agent. Where do you use agent name (script, job properties)? Are you sure you have specified there your agent profile name, not remote machine name? : The machine can be pinged by name or IP and connection test succeeds. I have : used machine name and IP in the agent config to no avail.
|
|
Thu Feb 21, 2002 1:02 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7948
|
|
Re: Version 2 to 3 Upgrade |
|
TCP Winsock reports that it is unable to resolve the specified network name : What does WSAEADDRNOTAVAIL mean exactly?
|
|
Thu Feb 21, 2002 2:27 pm |
|
 |
|