ANS1029E Communications have been dropped
I registed a new client and I am unable q the server successfully. These are the messages in my error log: 2/14/02 18:24:28 ANS1029E Communications have been dropped. 12/14/02 18:24:29 sessOpen: Error 137 from signon authentication. 12/14/02 18:24:29 sessOpen: Error 137 from signon authentication. 12/14/02 18:24:29 ANS1029E Communications have been dropped. 12/14/02 18:24:29 sessOpen: Error 137 from signon authentication. 12/14/02 18:24:29 sessOpen: Error 137 from signon authentication. 12/14/02 18:24:29 ANS1029E Communications have been dropped. 12/14/02 18:24:30 sessOpen: Error 137 from signon authentication. 12/14/02 18:24:30 sessOpen: Error 137 from signon authentication. 12/14/02 18:24:30 ANS1029E Communications have been dropped. Can anyone assist? Thanks in advance! -kane
Re: ANS1029E Communications have been dropped
I registed a new client and I am unable q the server successfully. These are the messages in my error log: 12/14/02 18:24:28 ANS1029E Communications have been dropped. That's a common error when one spends Saturday night registering clients... My note in http://people.bu.edu/rbs/ADSM.QuickFacts may help: ANS1029E Communications have been dropped. Could be caused by having the PASSWORDAccess Generate option, and the NODename option as well. If so, eliminate the latter. After you registered the client, from that client did you as root perform a trivial client-server action like 'dsmc q f' to assure interactability and store an automatically-used password on the client, if so configured? Richard
ANS1029E Communications have been dropped
Can anyone help me with next problem ? I did upgrade client to 4.130 on last Friday and since then the daily scheduled backup fails with ANS1029E after having inspected about 512.000 objects (has still some thousands of objects to go) Thanks for any help, Paul Van de Vijver Honda Europe NV Belgium TSM Server 4.2.1.0 running on OS390 TSM Client 4.2.1.30 running on WinNT DSMERROR.LOG 22.03.2002 18:05:33 ConsoleEventHandler(): Caught Ctrl-C console event . 22.03.2002 18:05:33 ConsoleEventHandler(): Cleaning up and terminating Process ... 23.03.2002 00:30:10 ANS1029E Communications have been dropped. 23.03.2002 00:30:10 ANS1512E Scheduled event '35564' failed. Return code = 4. 23.03.2002 23:42:39 ANS1029E Communications have been dropped. 23.03.2002 23:42:39 ANS1512E Scheduled event '35623' failed. Return code = 4. 25.03.2002 00:50:28 ANS1029E Communications have been dropped. 25.03.2002 00:50:28 ANS1512E Scheduled event '35684' failed. Return code = 4. 25.03.2002 08:59:35 Error opening input file t 25.03.2002 09:32:36 ConsoleEventHandler(): Caught Ctrl-C console event . 25.03.2002 09:32:36 ConsoleEventHandler(): Cleaning up and terminating Process ... DSMSCHED.LOG from last days : 25.03.2002 00:50:28 Total number of objects inspected: 512,218 25.03.2002 00:50:28 Total number of objects backed up: 119 25.03.2002 00:50:28 Total number of objects updated: 0 25.03.2002 00:50:28 Total number of objects rebound: 0 25.03.2002 00:50:28 Total number of objects deleted: 0 25.03.2002 00:50:28 Total number of objects expired:251 25.03.2002 00:50:28 Total number of objects failed: 0 25.03.2002 00:50:28 Total number of bytes transferred: 675.31 MB 25.03.2002 00:50:28 Data transfer time:1,784.51 sec 25.03.2002 00:50:28 Network data transfer rate: 387.51 KB/sec 25.03.2002 00:50:28 Aggregate data transfer rate:111.61 KB/sec 25.03.2002 00:50:28 Objects compressed by:5% 25.03.2002 00:50:28 Elapsed processing time: 01:43:15 25.03.2002 00:50:28 --- SCHEDULEREC STATUS END 25.03.2002 00:50:28 ANS1029E Communications have been dropped. 25.03.2002 00:50:28 --- SCHEDULEREC OBJECT END 35684 24.03.2002 23:02:38 25.03.2002 00:50:28 ANS1512E Scheduled event '35684' failed. Return code = 4. 25.03.2002 00:50:28 Sending results for scheduled event '35684'. - 23.03.2002 23:42:39 Total number of objects inspected: 512,122 23.03.2002 23:42:39 Total number of objects backed up: 41 23.03.2002 23:42:39 Total number of objects updated: 0 23.03.2002 23:42:39 Total number of objects rebound: 0 23.03.2002 23:42:39 Total number of objects deleted: 0 23.03.2002 23:42:39 Total number of objects expired:235 23.03.2002 23:42:39 Total number of objects failed: 0 23.03.2002 23:42:39 Total number of bytes transferred: 432.08 MB 23.03.2002 23:42:39 Data transfer time:1,278.21 sec 23.03.2002 23:42:39 Network data transfer rate: 346.15 KB/sec 23.03.2002 23:42:39 Aggregate data transfer rate: 84.48 KB/sec 23.03.2002 23:42:39 Objects compressed by:2% 23.03.2002 23:42:39 Elapsed processing time: 01:27:16 23.03.2002 23:42:39 --- SCHEDULEREC STATUS END 23.03.2002 23:42:39 ANS1029E Communications have been dropped. 23.03.2002 23:42:39 --- SCHEDULEREC OBJECT END 35623 23.03.2002 22:13:10 23.03.2002 23:42:39 ANS1512E Scheduled event '35623' failed. Return code = 4. 23.03.2002 23:42:39 Sending results for scheduled event '35623'. 23.03.2002 00:30:09 Total number of objects inspected: 512,635 23.03.2002 00:30:09 Total number of objects backed up:2,009 23.03.2002 00:30:09 Total number of objects updated: 0 23.03.2002 00:30:09 Total number of objects rebound: 0 23.03.2002 00:30:09 Total number of objects deleted: 0 23.03.2002 00:30:09 Total number of objects expired: 1,678 23.03.2002 00:30:09 Total number of objects failed: 0 23.03.2002 00:30:09 Total number of bytes transferred: 1.58 GB 23.03.2002 00:30:09 Data transfer time:4,224.16 sec 23.03.2002 00:30:09 Network data transfer rate: 393.27 KB/sec 23.03.2002 00:30:09 Aggregate data transfer rate:201.34 KB/sec 23.03.2002 00:30:09 Objects compressed by: 52% 23.03.2002 00:30:09 Elapsed processing time: 02:17:30 23.03.2002 00:30:09 --- SCHEDULEREC STATUS END 23.03.2002 00:30:10 ANS1029E Communications have been dropped. 23.03.2002 00:30:10 --- SCHEDULEREC OBJECT END 35564 22.03.2002 22:07:54 23.03.2002 00:30:10 ANS1512E Scheduled event '35564' failed. Return code = 4. 23.03.2002 00:30:10 Sending results
Re: ANS1029E Communications have been dropped and MSCS
Same thing happened to a number of our TDP schedulers on the cluster. Re-installing only worked part of the time, and in a clustered environment, really a pain. To truly fix it, I ended up modifying the dsm.opt file and set PASSWORDACCESS PROMPT. I then schedule a command line backup and set the password option. Hardly secure (although only admins have any access to the server) or elegant, but it appears to work. Cheers --- "Disler Claude, ABX-SERV-ZH" [EMAIL PROTECTED] wrote: Hi cracks til 3 days ago, the tsm scheduler of one of my cluster nodes works verry well. but now, i've get some errors. errorlog says: 31-01-2001 12:35:14 sessOpen: Error 137 from signon authentication. 31-01-2001 12:35:14 sessOpen: Error 137 from signon authentication. 31-01-2001 12:35:15 ANS1029E Communications have been dropped. schedulelog says: 31-01-2001 12:35:53 Querying server for next scheduled event. 31-01-2001 12:35:53 Node Name: Nodename 31-01-2001 12:35:53 Please enter your user id Nodename: ANS1029E Communications have been dropped. 31-01-2001 12:35:54 Scheduler has been stopped. i removed, and installed the scheduler new, but's always the same. after the installation of the scheduler, i've got the registry entry of this node. but if y start the node with the msc console, the registryentry moves to hell. client: win2k adv. srv with sp1 tsm 4.1.2.0 who has the golden idea? tx Claude Disler Abraxas Informatik AG Waltersbachstrasse 5 CH-8035 Z|rich Schweiz / Switzerland E-Mail: mailto:[EMAIL PROTECTED] ___ Do You Yahoo!? Get your free @yahoo.ca address at http://mail.yahoo.ca
Re: ANS1029E Communications have been dropped and MSCS
You'll need to use the 4.1.1 client, there is an apar out for this issue on the 4.1.2 client. James Thompson - Original Message - From: "Disler Claude, ABX-SERV-ZH" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 31, 2001 5:07 AM Subject: ANS1029E Communications have been dropped and MSCS Hi cracks til 3 days ago, the tsm scheduler of one of my cluster nodes works verry well. but now, i've get some errors. errorlog says: 31-01-2001 12:35:14 sessOpen: Error 137 from signon authentication. 31-01-2001 12:35:14 sessOpen: Error 137 from signon authentication. 31-01-2001 12:35:15 ANS1029E Communications have been dropped. schedulelog says: 31-01-2001 12:35:53 Querying server for next scheduled event. 31-01-2001 12:35:53 Node Name: Nodename 31-01-2001 12:35:53 Please enter your user id Nodename: ANS1029E Communications have been dropped. 31-01-2001 12:35:54 Scheduler has been stopped. i removed, and installed the scheduler new, but's always the same. after the installation of the scheduler, i've got the registry entry of this node. but if y start the node with the msc console, the registryentry moves to hell. client: win2k adv. srv with sp1 tsm 4.1.2.0 who has the golden idea? tx Claude Disler Abraxas Informatik AG Waltersbachstrasse 5 CH-8035 Z|rich Schweiz / Switzerland E-Mail: mailto:[EMAIL PROTECTED]
ANS1029E Communications have been dropped and MSCS
Hi cracks til 3 days ago, the tsm scheduler of one of my cluster nodes works verry well. but now, i've get some errors. errorlog says: 31-01-2001 12:35:14 sessOpen: Error 137 from signon authentication. 31-01-2001 12:35:14 sessOpen: Error 137 from signon authentication. 31-01-2001 12:35:15 ANS1029E Communications have been dropped. schedulelog says: 31-01-2001 12:35:53 Querying server for next scheduled event. 31-01-2001 12:35:53 Node Name: Nodename 31-01-2001 12:35:53 Please enter your user id Nodename: ANS1029E Communications have been dropped. 31-01-2001 12:35:54 Scheduler has been stopped. i removed, and installed the scheduler new, but's always the same. after the installation of the scheduler, i've got the registry entry of this node. but if y start the node with the msc console, the registryentry moves to hell. client: win2k adv. srv with sp1 tsm 4.1.2.0 who has the golden idea? tx Claude Disler Abraxas Informatik AG Waltersbachstrasse 5 CH-8035 Zrich Schweiz / Switzerland E-Mail: mailto:[EMAIL PROTECTED]
