Backup Exec Error 1050
Backup Exec v9.0 reports 1050 or 1051 error codes - Servers Applicable countries and regions Source RETAIN tip: H177350 Symptom Veritas Backup Exec 9.0 reports errors 1050 or 1051. Affected configurations The system may be any of the following IBM eServer xSeries servers: xSeries 345, type 8670, any model xSeries 335, type 8830, any model xSeries 335, type 8676, any model xSeries 235, type 8671, any model The system is configured with the following option(s): ServeRAID-5i Controller, option part number 25P3492, CRU part number 02R0970 replaces 32P0016, Battery - 25P3482 Note: ServeRAID 5i CRU 02R0970 includes the battery. The system is configured with one or more of the following: Description Option part number Replacement part number (FRU) 20/40GB DDS4 SC40 09N0730 48P7038 20/40GB DDS4 SP40 00N7991 48P7040 40/80GB DLTVS 24P2398 24P2424 100/200GB H/H LTO 24P2396 24P2400 External NetBay Tape Enclosure 0034B0X 59P6732 External FH SCSI Tape Enclosure 3503B0X 03K8703 External FH SCSI Tape Enclosure 3503B1X 03K8703 External HH SCSI Tape Enclosure 3510020 03K8762 External HH SCSI Tape Enclosure 3510030 03K8762 NetMedia Storage Expansion 3551001 . The following Network Operating Systems (NOS) are affected: Novell NetWare, version 5.1 The following Software is affected: Veritas Backup Exec version 9.0 Workaround For error message 1050, please refer to TechNote 248593. To view the referenced TechNote, visit the Veritas home page at http://www.veritas.com and use their Support Knowledge Base. For error message 1051, complete the following steps: Edit the STARTUP.NCF file and change Load NWASPI.CDM to Load C:\NWSERVER\DRIVERS\NWASPI.CDM. Edit the BESTART.NCF located in the path SYS:SYSTEM\BESTART.NCF and make the following changes to match below: a. ; Load BECDM.CDM b. LOAD BKUPEXEC.NLM -n -tl -aa -dy -tc -tj s From the console prompt, type BESTOP and press Enter, then type BESTART and press Enter. Additional information After installing Veritas Backup Exec version 9.0 for Novell NetWare 5.1, "Error 1050: Unable to establish a connection to the server" or "Error 1051: Unable to successfully load the device drivers" may appear when the program loads. Applicable countries and regions Worldwide Back to top Document id:MIGR-50487 Last modified:2014-08-15 Copyright © 2016 IBM Corporation Sign in To access your authorized content and to customize your pages. Footer links Contact Privacy Terms of use Accessibility
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Backup Exec 2010 and 2010 R2 Remote Agent (RAWS) prevent RSH or Telnet connections to Ataman software on Windows 64-bit Operating System. Article:000007900 Publish: Article URL:http://www.veritas.com/docs/000007900 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome https://www.ibm.com/support/entry/portal/docdisplay?lndocid=migr-50487 First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec 2010 and 2010 R2 Remote Agent (RAWS) prevent RSH or Telnet connections to Ataman software on Windows 64-bit Operating System. Error Message Faulting application dotlnetd.exe, version 0.0.0.0, time https://www.veritas.com/support/en_US/article.000007900 stamp 0x4ae11a65, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x001797e8, process id 0x1050, application start time 0x01cb1569dc79e8f9. Cause Ataman TCP Remote Logon Services (ATRLS) by Ataman Software, Inc stops accepting remote Telnet or RSH logins after installing the Backup Exec 2010 remote agent (RAWS) on Windows 64-bit Operating systems.The following Event ID and Error is logged in the Application Log on the host computer running the Ataman software or ATRLS services.Application Log: Log Name: ApplicationSource: Application ErrorEvent ID: 1000Task Category: (100)Level: ErrorDescription:Faulting application dotlnetd.exe, version 0.0.0.0, time stamp 0x4ae11a65, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x001797e8, process id 0x1050, application start time 0x01cb1569dc79e8f9. Solution This issue is resolved in Backup Exec 2010 R3. Backup Exec 2010 R3 is a free upgrade for Backup Exec 2010 customers. WORKAROUND:Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the us
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-2012-job-fails-to-Linux-server-with-firewall-enabled/td-p/538440 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup backup exec Exec : Backup Exec 2012 job fails to Linux server with fi... VOX : Backup and Recovery : Backup Exec : Backup Exec 2012 job fails to Linux server with fi... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer backup exec error Friendly Page Backup Exec 2012 job fails to Linux server with firewall enabled rockshox Level 2 11-15-2012 02:21 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, We have been in the process of migrating from Backup Exec 2010 R3 to Backup Exec 2012. We have several Redhat Enterprise Linux 5 servers that we have been successfully backing up for the last few years. The firewall has been enabled on these servers and we haveopened the necessary ports in the firewall to allow thebackup jobs to complete successfully. Port 10000 and 6101 have been opened, along with a range of 1025-1050. The Backup Exec Media Server is set to use the port range 1025-65535. Sincemigrating to Backup Exec 2012, the jobsto the Linux serversfail. If we turn the firewall off on the server, the backup job completes successfully. We've tried enabling the firewall