EMC RepliStor for Microsoft Windows ERROR MESSAGE AND CODE GUIDE P/N 300-002-826 REV A02

EMC RepliStor for Microsoft Windows ERROR MESSAGE AND CODE GUIDE P/N 300-002-826 REV A02 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com

Copyright 2003-2005 EMC Corporation. All rights reserved. Printed November, 2005 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. Trademark Information ii EMC RepliStor for Microsoft Windows Error Message and Code Guide

Contents Preface... v Chapter 1 Chapter 2 Introduction Conventions Used in This Guide... 1-2 Critical Error Messages Critical Messages... 2-2 107... 2-2 108... 2-2 113... 2-2 114... 2-2 119... 2-2 120... 2-3 121... 2-3 124... 2-3 126... 2-3 131... 2-4 132... 2-4 134... 2-4 136... 2-4 227... 2-4 247... 2-5 248... 2-5 250... 2-5 258... 2-5 269... 2-5 270... 2-6 309... 2-6 310... 2-6 311... 2-6 EMC RepliStor for Microsoft Windows Error Message and Code Guide iii

Contents 312... 2-7 313... 2-7 504... 2-7 534... 2-7 543... 2-7 544... 2-7 545... 2-8 546... 2-8 547... 2-8 549... 2-8 589... 2-8 672... 2-8 679... 2-9 684... 2-9 685... 2-9 2000... 2-9 2001... 2-9 2004... 2-10 2006... 2-10 2007... 2-10 2008... 2-10 2009... 2-11 2014... 2-11 2015... 2-11 2017... 2-11 2018... 2-11 2019... 2-11 2020... 2-12 2022... 2-12 2023... 2-12 2024... 2-12 2025... 2-12 2028... 2-13 2029... 2-13 2030... 2-13 2031... 2-13 2032... 2-13 2033... 2-13 2036... 2-14 2037... 2-14 2038... 2-14 2039... 2-14 2040... 2-14 iv EMC RepliStor for Microsoft Windows Error Message and Code Guide

Preface As part of an effort to improve and enhance the performance and capabilities of its product line, EMC from time to time releases revisions of its hardware and software. Therefore, some functions described in this guide may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this guide, please contact your EMC representative. Audience Organization Related Documentation This guide is part of the RepliStor documentation set. The primary audience for this guide is anyone responsible for using RepliStor. This guide consists of the following: Chapter 1, Introduction, describes the conventions used in this guide. Chapter 2, Critical Error Messages, lists the RepliStor critical error codes and messages. The error codes and messages, and the pages on which you can find them are listed in the Table of Contents. The following documents, available on the Legato website at http://web1.legato.com/cgi-bin/catalog?sf=releases, provide additional information about the RepliStor software: EMC RepliStor for Microsoft Windows Version 6.0 Administrator s Guide, P/N 300-002-464, REV A01 EMC RepliStor for Microsoft Windows Version 6.0 Installation Guide, P/N 300-002-463, REV A01 EMC RepliStor for Microsoft Windows Version 6.0 Release Notes, P/N 300-002-461, REV A03 EMC RepliStor for Microsoft Windows Error Message and Code Guide v

Preface An extensive archive of product documentation is available at http://web1.legato.com/cgi-bin/catalog?sf=releases. Most of the documents are in Adobe Acrobat Portable Document Format (PDF), and can be viewed by downloading and installing the Adobe Acrobat Reader. The Reader is available in the /viewers/acroread directory on the Legato Documentation Suite CD-ROM, or directly from Adobe at www.adobe.com. To install and use the Reader on the preferred platform, refer to the instructions in the CD-ROM s /viewers/acroread/readme.txt file or at the Adobe website. Typographical Conventions This document uses the following typographic conventions and symbols to make information easier to access and understand. A note presents information that is important, but not hazard-related. AVANT GARDE Keystrokes Palatino, bold Palatino, italic Dialog box, button, icon, and menu items in text Selections you can make from the user interface, including buttons, icons, options, and field names New terms or unique word usage in text Command line arguments when used in text Book titles Courier, italic Courier Arguments used in examples of command line syntax. System prompts and displays and specific filenames or complete paths. For example: working root directory [/user/emc]: c:\program Files\EMC\Symapi\db Courier, bold User entry. For example: symmpoll -p Options in command line syntax vi EMC RepliStor for Microsoft Windows Error Message and Code Guide

Preface Where to Get Help For questions about technical support, call your local sales office or service provider. If you have a valid EMC service contract, contact EMC Customer Support at: United States: (800) 782-4362 (SVC-4EMC) Canada: (800) 543-4782 (543-4SVC) Worldwide: (508) 497-7901 Follow the voice menu prompts to open a service call and select the applicable product support. If you are located outside North America, call the nearest EMC office for technical assistance. Sales and Customer Service Contacts Your Comments For the list of EMC sales locations, please access the EMC home page at: http://emc.com/contact/ For additional information on the EMC products and services available to customers and partners, refer to the EMC Powerlink Website at: http://powerlink.emc.com Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send a message to techpub_comments@emc.com with your opinions of this guide. Your technical enhancement suggestions for future development consideration are welcome. To send a suggestion, log on to http://powerlink.emc.com, follow the path Support, Contact Support, and choose Software Product Enhancement Request from the Subject menu. EMC RepliStor for Microsoft Windows Error Message and Code Guide vii

Preface viii EMC RepliStor for Microsoft Windows Error Message and Code Guide

Invisible Body Tag 1 Introduction This chapter describes how to use this guide. The topic in this chapter is: Conventions Used in This Guide...1-2 Introduction 1-1

1 Introduction Conventions Used in This Guide Chapter 2 of this guide includes a list of critical messages you may receive while using EMC RepliStor. Figure 1-1 illustrates the conventions used in this guide. Error code numbers are arranged in sequence. 108 This is the error code message text. Critical Messages Message: Fatal failure to allocate memory for %1/%2 Cause: The device driver attempted to allocate internal memory for the object specified. Increase the size of the paging file and then reboot the system. An explanation of each error message containing the cause of the error and the recommended action follows the error code number and text. 114 Message: Registry error (fatal) retrieving %1. %n%2 Cause: A registry value required for RepliStor to run cannot be read. Reinstall RepliStor. Figure 1-1 Conventions Used in this Guide You can find a collated list of all messages covered in this guide and the pages on which they appear in the Table of Contents. 1-2 EMC RepliStor for Microsoft Windows Error Message and Code Guide

Invisible Body Tag 2 Critical Error Messages This chapter lists and describes the critical error messages reported by RepliStor, the reason for the message, and the recommended user action. Errors with numbers 2000 and higher are generated by the RepliStor kernel driver. These errors are mostly used to help EMC Customer Support diagnose replication problems. The topic in this chapter is: Critical Messages...2-2 Critical Error Messages 2-1

2 Critical Error Messages Critical Messages 107 Message: Fatal failure to allocate memory for %1 Cause: The device driver attempted to allocate internal memory for the object specified. Increase the size of the paging file and then reboot the system. 108 Message: Fatal failure to allocate memory for %1/%2 Cause: The device driver attempted to allocate internal memory for the object specified. Increase the size of the paging file and then reboot the system. 113 Message: Process create failed for %1. %n%2 Cause: A process could not be created. This could be a result of running a script file that did not exist or was specified incorrectly. The message text will show which process could not be started and the reason. Fix the script reference and/or determine why the script failed. 114 Message: Registry error (fatal) retrieving %1. %n%2 Cause: A registry value required for RepliStor to run cannot be read. Reinstall RepliStor. 119 Message: The time for running the %1 demo has expired! Please call Sales Representative to order a retail version. Cause: The RepliStor demo has expired. Purchase a retail version of RepliStor by contacting your local EMC sales office. For the list of EMC sales locations, please access the EMC home page at http://emc.com/contact. 2-2 EMC RepliStor for Microsoft Windows Error Message and Code Guide

Critical Error Messages 2 120 Message: Invalid or non-existent license key. Cause: You are using either an invalid or non-existent RepliStor license key. To license and register RepliStor, go to the EMC Legato licensing website. For questions about licensing, use one of the following contact methods: Licensing and Registration Contact EMC Legato licensing website http://legato.com/support/licensing Telephone number (650) 812 6000 (option 3, option 2) a +31 23 554 8881 b Fax number (650) 745-1477 a +31 23 554 8808 b E-mail licensing@legato.com a licensingemea@legato.com b a. Contact information for the Americas, Asia, and the Pacific. b. Contact information for Europe, the Middle East, and Africa. 121 Message: Event wait exceeded max error count %1. %n%2 Cause: This indicates an internal error. Contact EMC Customer Support. 124 Message: File create error (fatal) %1. %n%2 Cause: Error creating the specified file in the RepliStor data directory. This error may indicate that required files or directories for RepliStor to run have been deleted or have become inaccessible. The action depends on the file that cannot be created (replaces the %1), and the error that occurred (replaces the %2). 126 Message: File open error (fatal) %1. %n%2 Cause: Error opening the specified file in the RepliStor data directory. This error may indicate that required files or directories for RepliStor to run have been deleted or have become inaccessible. The action depends on the file that cannot be opened (replaces the %1), and the error that occurred (replaces the %2). Critical Messages 2-3

2 Critical Error Messages 131 Message: File read error (fatal) %1. %n%2 Cause: Error reading the specified file in the RepliStor data directory. This error may indicate that required files or directories for RepliStor to run have been deleted or have become inaccessible. The action depends on the file that cannot be opened (replaces the %1), and the error that occurred (replaces the %2). 132 Message: File write error (fatal) %1. %n%2 Cause: Error writing to the specified file in the RepliStor data directory. This error may indicate that required files or directories for RepliStor to run have been deleted or have become inaccessible. The action depends on the file that cannot be opened (replaces the %1), and the error that occurred (replaces the %2). 134 Message: File write mismatch (fatal) %1. Wrote %2, actual %3. Cause: Error writing to the specified file in the RepliStor data directory. This error may indicate that required files or directories for RepliStor to run have been deleted or have become inaccessible. The action depends on the file that cannot be opened (replaces the %1), and the error that occurred (replaces the %2). 136 Message: File position error (fatal) %1 to offset %2. %n%3 Cause: Error setting file position on the specified file in the RepliStor data directory. This error may indicate that required files or directories for RepliStor to run have been deleted or have become inaccessible. The action depends on the file that cannot be opened (replaces the %1), and the error that occurred (replaces the %2). 227 Message: Fatal error repositioning to offset %1 from offset %2 in kernel %3 after command rewrite. %n%4 Cause: After updating a kernel log command, the process could not position back to the next message to process. 1. Use the Windows error text to resolve the problem. 2. Restart the service. 2-4 EMC RepliStor for Microsoft Windows Error Message and Code Guide

Critical Error Messages 2 247 Message:!!! ERROR!!! A wrong version %1 of the %2 Driver is running. You must reinstall %3 since it not compatible with this version of Windows (%4.%5). Cause: When the kernel driver responded with its operating system version, it was not compatible with the operating system. Reinstall. 248 Message: No response to kernel poll. %n%1 Cause: The process polled the kernel driver for status and the driver failed to communicate. Use the Windows error text to resolve the problem and then restart the service. 250 Message:!!! WARNING!!! %1 Driver cannot be started. %n%2 Cause: Kernel driver could not load into the kernel or it was unable to start correctly. 1. Reboot the affected server. 2. If the error message persists, reinstall RepliStor. 3. If the error is still encountered after the reinstall, call EMC Customer Support. 258 Message: The error threshold for previous error reached. Process will terminate. Cause: Invalid OC$nnnnn log files were encountered. Perform a Delete Data Directory and resynchronize all specifications. 269 Message:!!! ERROR!!! A wrong version %1 of the %2 Driver is running. Expected version %3. Probable cause: Must reboot after an install. Cause: The driver does not match the version or build expected by the service and is not compatible with the service. The driver is ignored and no mirroring or synchronization can take place. However, existing data is forwarded to target sites. This error usually occurs because the system was not rebooted after installation and the new driver is not running. Critical Messages 2-5

2 Critical Error Messages 1. Reboot the machine. 2. If the error persists, uninstall and then reinstall. 270 Message: Mirroring and Receiving have been stopped. Free Disk has reached %1MB. Cause: Free disk space has reached the requested stop point. Mirroring has stopped and has blocked remote (source) sites from sending any more data. Receiving resumes automatically when disk space reaches the initial notify point. 1. Determine the cause of disk space usage and correct the problem. 2. Resynchronize the source files to the target and start mirroring. 309 Message: Can't create server thread. %n%1 Cause: The main RepliStor service thread did not start. This may indicate a serious server problem. The error code should describe the issue. A reinstall may be necessary. 310 Message: Server thread never initialized. Cause: The main service routine waited for the main application thread to initialize but it never did. This is a fatal error and the process terminates. 1. Check the message log and the Windows event log for reasons that may have caused the thread not to initialize. 2. If the problem persists, contact EMC Customer Support. 311 Message: Server thread wait failed. %n%1 Cause: While the main service routine was waiting for the main application thread to initialize, the wait function returned an error. This is a fatal error and the process will terminate. 1. Check the message log and the Windows event log for reasons that may have caused the thread not to initialize. 2. If the problem persists, contact EMC Customer Support. 2-6 EMC RepliStor for Microsoft Windows Error Message and Code Guide

Critical Error Messages 2 312 Message: StartServiceCtrlDispatcher failed. %n%1 Cause: Communication with the service control manager failed. This may indicate a serious server problem. The error code should describe the issue. A reinstall may be necessary. 313 Message: SetServiceStatus failed. %n%1 Cause: The main service routine tried to report its status to the service control manager and the report failed. 1. Check the message log and the Windows event log for reasons that may have caused the failure. 2. If the problem persists, contact EMC Customer Support. 504 Message: The KernelCache may be corrupt and mirrored data may been lost. A Delete Data Dir needs to be performed. Cause: Data within the KernelCache has become corrupt. Perform a Delete Data Directory. Resynchronize all specifications. 534 Message: Error: waiting on too many events (%1) Cause: This indicates an internal error. Contact EMC Customer Support. 543 Message: Unable to attach to or create the shared memory containing performance data. Cause: This indicates an internal error. Contact EMC Customer Support. 544 Message: Unable open "Performance" key of 'HKEY_LOCAL_MACHINE\%1' in registy. Status code is returned in data. Cause: Missing/deleted or locked registry key containing performance monitor information. 1. Ensure the registry is open and the required registry key exists. 2. If the registry entry is missing or corrupt, reinstall RepliStor. Critical Messages 2-7

2 Critical Error Messages 545 Message: Unable to read the "First Counter" value under the Performance Key. Status code is returned in data. Cause: Missing/deleted or locked registry key containing performance monitor information. 1. Ensure the registry is open and the required registry key exists. 2. If the registry entry is missing or corrupt, reinstall RepliStor. 546 Message: Unable to read the "First Help" value under the Performance Key. Status code is returned in data. Cause: Missing/deleted or locked registry key containing performance monitor information. 1. Ensure the registry is open and the required registry key exists. 2. If the registry entry is missing or corrupt, reinstall RepliStor. 547 Message: Unable to gain ownership of mutex: %1. Cause: This indicates an internal error. Contact EMC Customer Support. 549 Message: Unable to release ownership of mutex: %1 Cause: This indicates an internal error. Contact EMC Customer Support. 589 Message: Timeout waiting for all sites to synchronize after Kernel Cache reset: %1 Cause: While attempting to switch back to the KernelCache after using OC$nnnnn files, all sites could not be reset to the KernelCache within the time allocated. Perform a Delete Data Directory, and resynchronize all specifications. 672 Message: The %1 Service did not shut down cleanly. All specifications may need to be re-synchronized on this server, as well as all specifications where this server is a target. Cause: An unscheduled server outage/blue screen caused the server to crash. Re-synchronize all specifications on this server, as well as all specifications where this server is a target. 2-8 EMC RepliStor for Microsoft Windows Error Message and Code Guide

Critical Error Messages 2 679 Message: Encrypted File Protect Slot table overflow (%1) Cause: An internal error occurred replicating NTFS encrypted files. Contact EMC Customer Support. 684 Message: Free Disk has reached %1MB. Disk Space Monitor Auto-recover starting. The data directory will be deleted and all specs will be re-synchronized. Cause: Auto Recover is configured. The configured threshold has been reached. No action required. RepliStor will automatically recover and resynchronize after performing the delete data directory operation. 685 Message: Disk Space Monitor Auto-recover has been disabled. After deleting the data directory, the free disk space is still under the STOP value (%1MB). Cause: Auto Recover is configured. The configured threshold has been reached. After performing a Delete Data Directory, the free disk space is still under the Stop value. Mirroring has been automatically turned off. 1. Free up disk space. 2. Turn Mirroring back on. 3. Resynchronize all specifications. 2000 Message: Kernel log file disk is full. Kernel not active. Cause: The kernel driver could not write mirrored data to the kernel OC$nnnnn log file. 1. Create more room for the kernel log files. The service may not be deleting the log files because a site is blocked. 2. Turn Mirroring back on. 3. Resynchronize all specifications. 2001 Message: Kernel log file write error. Kernel not active. Cause: Kernel driver could not write update data to the OC$nnnnn file. Mirroring has stopped. 1. Make room on the disk for the log files. Critical Messages 2-9

2 Critical Error Messages 2. Turn Mirroring back on. 3. Resynchronize files that may contain lost updates. 2004 Message: Allocation Error (%2). Kernel not active. Cause: The kernel tried to allocate memory and failed. Since replication failed and data may be missing, further mirroring has been turned off. This message suggests a serious operating system problem. 1. Determine what is causing the operating system resources to be used up; remove or reconfigure. 2. Turn Mirroring back on. 3. Resynchronize files that may contain lost updates. 4. If this error persists, contact EMC Customer Support. 2006 Message: IoQueryFileName failed (%2). Cause: This indicates an internal error. Contact EMC Customer Support. 2007 Message: Attach failed (%2). Cause: Replistor kernel failed to attach to specified device. If the device does not exist on the system, and will not be used for replication, this error can be ignored. If the device exists and needs to be attached to for replication, please contact EMC Customer Support. 2008 Message: Create device failed (%2). Cause: RepliStor kernel was unable to create a device that is needed to capture I/O operations or recognize newly mounted drives. This could result from unavailable resources, programming or configuration issues. The result is that no replication takes place on the drive the device create failed for, or newly-mounted drives are not recognized. If the problem persists, contact EMC Customer Support. 2-10 EMC RepliStor for Microsoft Windows Error Message and Code Guide

Critical Error Messages 2 2009 Message: Wait failed (%2). Cause: RepliStor kernel made an API call to wait on an event either while creating a device or issuing an I/O. This represents an internal coding error or an operating system resource problem. If the problem persists, contact EMC Customer Support. 2014 Message: File set size failed (%2). Cause: RepliStor kernel was setting the size of the kernel cache during initialization and an error was returned. Reconfigure the kernel cache to a reasonable size or adjust permission and try again. If the problem persists, contact EMC Customer Support. 2015 Message: File write failed (%2). Cause: A file write operation was attempted on the target server and failed. 1. Ensure the target disk device is accessible with sufficient free space to receive the file. 2. Check event log for disk I/O errors and/or failures. 2017 Message: File open failed (%2). Cause: During a synchronization a file pointer is placed into the KernelCache. Once the Replistor driver gets to this link, it attempts to read and send the file to the target system. However, in this case, the file was deleted or moved on the source. No action required. 2018 Message: Security Descriptor create failed (%2). Cause: RepliStor kernel could not create a security descriptor and received this error. This can occur during the initialization of the kernel cache or when mapping a file for reading. If the problem persists, contact EMC Customer Support. 2019 Message: Security Descriptor set dacl failed (%2). Cause: RepliStor kernel could not create a security descriptor and received this error. This can occur during the initialization of the kernel cache or when mapping a file for reading. If the problem persists, contact EMC Customer Support. Critical Messages 2-11

2 Critical Error Messages 2020 Message: Event create failed (%2). Cause: RepliStor kernel could not create an event to notify the server process and received this error. This can occur during the initialization of the kernel cache. If the problem persists, contact EMC Customer Support. 2022 Message: Section create failed (%2). Cause: RepliStor kernel could not create a shared memory section and received this error. This can occur during the initialization of the kernel cache or performance monitor section, or when mapping a file for shared read. If the problem persists, contact EMC Customer Support. 2023 Message: Section map view failed (%2). Cause: RepliStor kernel could not map a shared memory section. This can occur during the initialization of the kernel cache or performance monitor section, or when mapping a file for shared read. If the problem persists, contact EMC Customer Support. 2024 Message: Kernel Cache header invalid (%2). Cause: RepliStor KernelCache corruption may have been caused by server crash, virus, or other file access method. 1. Disable Replistor and reboot the affected server. 2. Restart Replistor and perform a Delete Data Directory operation. 2025 Message: Some other driver is using our completion routine. Cause: Another software driver is accessing RepliStor s internal completion routine. 1. Investigate any recent software additions to the affected system and remove any new applications. 2. If the problem persists, contact EMC Customer Support. 2-12 EMC RepliStor for Microsoft Windows Error Message and Code Guide

Critical Error Messages 2 2028 Message: Device get object pointer failed (%2). Cause: An unexpected error return from an API call made by the RepliStor kernel. This error can occur during a device attach to a volume. No replication will occur on that volume. If the problem persists, contact EMC Customer Support. 2029 Message: Device open file failed (%2). Cause: An unexpected error return from an API call made by the RepliStor kernel. This error can occur during a device attach to a volume. No replication will occur on that volume. If the problem persists, contact EMC Customer Support. 2030 Message: Device reference file object failed (%2). Cause: An unexpected error return from an API call made by the RepliStor kernel. This error can occur during a device attach to a volume. No replication will occur on that volume. If the problem persists, contact EMC Customer Support. 2031 Message: Device get related object failed (%2). Cause: An unexpected error return from an API call made by the RepliStor kernel. This error can occur during a device attach to a volume. No replication will occur on that volume. If the problem persists, contact EMC Customer Support. 2032 Message: Device vpb is null (%2). Cause: An unexpected condition was found by the RepliStor kernel. This error can occur during a device attach to a volume. No replication will occur on that volume. If the problem persists, contact EMC Customer Support. 2033 Message: Device attached failed (%2). Cause: An unexpected error return from an API call made by the RepliStor kernel. This error can occur during a device attach to a volume. No replication will occur on that volume. If the problem persists, contact EMC Customer Support. Critical Messages 2-13

2 Critical Error Messages 2036 Message: Section open failed (%2). Cause: RepliStor kernel could not open the shared memory section for performance monitor. This can occur during the initialization of the performance monitor section after the application has started. If the problem persists, reinstall RepliStor. 2037 Message: File Object create failed. Cause: Replistor attempted to create a file and failed. 1. Ensure the target disk device is accessible with sufficient free space to create the file. 2. Check event log for disk I/O errors and/or failures. 2038 Message: Irp Allocate failed. Cause: An I/O request packet could not be allocated during an open by file id for the purpose of querying the file name. This error is most likely due to low system resources or invalid parameter. If the problem persists, contact EMC Customer Support. 2039 Message: Kernel Exception. Cause: A kernel exception occurred during an open by file id for the purpose of querying the file name. This error is most likely due to an invalid parameter. If the problem persists, contact EMC Customer Support. 2040 Message: Kernel Copy Read Failed. Cause: An error occurred while reading a file during synchronization. The error is reported to the RepliStor application and should be in the application message log. 1. Try to correct the problem using the error status (for example, permissions error). 2. If the problem persists, contact EMC Customer Support. 2-14 EMC RepliStor for Microsoft Windows Error Message and Code Guide