Did you check to see if port 13782 is open? This sounds like a network issue, Maybe a tcp issue of some sort. Here are some links http://seer.entsupport.symantec.com/docs/271200.htm http://seer.entsupport.symantec.com/docs/285057.htm
Jackson ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, December 17, 2007 8:56 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] (no subject) 12/16/2007 9:48:15 AM - Error bpbrm(pid=4388) bpcd on aag0j6a05 exited with status 24: socket write failed 12/16/2007 9:48:15 AM - started process bpbrm (4388) 12/16/2007 9:48:15 AM - connecting 12/16/2007 9:48:15 AM - Error bpbrm(pid=4388) cannot send mail because BPCD on aag0j6a05 exited with status 24: socket write failed 12/16/2007 9:48:16 AM - end writing socket write failed(24) 12/16/2007 9:48:19 AM - Error bpsched(pid=3960) suspending further backup attempts for client aag0j6a05, policy WinNT_d-r, schedule d-r because it has exceeded the configured number of tries 12/16/2007 9:48:20 AM - Error bpsched(pid=3960) backup of client aag0j6a05 exited with status 24 (socket write failed) What causes a socket write failed(24) ? Anybody ? Help Thanks Philip Curinga ________________________________ "PLEASE NOTE: The preceding information may be confidential or privileged. It only should be used or disseminated for the purpose of conducting business with Parker. If you are not an intended recipient, please notify the sender by replying to this message and then delete the information from your system. Thank you for your cooperation."
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
