'ResB ^LogMessages3233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131[ODBC MSG]{0}Executing: {0}Restore succeeded.Unknown action typeFailed to initalize RAICannot connect to nbars.Unsupported schedule type.Restore complete succeeded.Failed to open database: {0}Failed to drop database: {0}Credential encryption failed.Failed to open instance: {0}.MSSQL Server is not installed.SQL statement still executing.Failed to offline database {0}.Cannot connect to instance: {0}Invalid URI segment detected: {0}Failed to bind SQL parameter. {0}.Processing SQL Server instance: {0}Processing SQL Server database: {0}MSSQL application state capture failedFailed to get disk list from discoveryDirectory creation failed for path : {0}Log truncation failed for database : {0})The SQL Server instance {0} was not found)No databases were found for instance {0}.)Memory allocation failed for object: {0}.*Restore complete failed for database : {0}+Failed to reset SQL parameter binding. {0}.+No filegroups were found for database: {0}.,Connection to {0} failed. Error Message: {1},Backup preparation failed for database : {0},No filestreams were found for database: {0}.-Failed to obtain databases for instance: {0}.-Failed to stop SQL services for instance: {0}-Restore preparation failed for database : {0}-Failed to execute the sql statement: {0}. {1}.Filegroup {0} was not found for database: {1}..Failed to start SQL services for instance: {0}.Starting SQL Server services for instance: {0}/Failed to allocate ODBC object: {0} Error: {1}./Filestream {0} was not found for database: {1}.2Failed to obtain filegroup list for Database: {0}.2No fulltext catalogs were found for database: {0}.2No database snapshots were found for database: {0}3Failed to obtain filestream list for Database: {0}.3Starting recovery of database: {0} on instance: {1}3No availability groups were found for instance: {0}4{0} backup of database: {1} on instance: {2} failed.4Instance: {0} availability group: {1} was not found.5Failed to obtain replicas for availability group: {0}5{0} restore of database: {1} on instance: {2} failed.5Fulltext catalog {0} was not found for database: {1}.6No transaction log files were found for database: {0}.6No Availability Group cluster resources were detected.6Database {0} is in the {1} state and cannot be opened.6Failed to cancel pending sql statement: {0} Error: {1}7Failed to obtain availability groups for instance: {0}.7There is no group named {0} in the instance repository.8MSSQL application state capture was partially successful8{0} on {1} is not registered in the instance repository.8Failed to obtain fulltext catalog list for Database: {0}9Failed to obtain database snapshot list for database: {0}:The specified database {0} does not exist in instance {1}.;Failed to determine server\instance name for instance: {0}.;Failed to obtain filelist for Database: {0} Filegroup: {1}.;Skipping database {0}. Portions of it are on an iSCSI disk.<Skipping database {0}. Portions of it are on a virtual disk.<No memory optimized filegroups were found for database: {0}.<No availability groups replicas were found on instance: {0}.=Failed to obtain transaction log file list for Database: {0}.@Memory optimized filegroup: {0} was not found for database: {1}.ASkipping database {0}. Portions of it are on an independent disk.AFailed to obtain filegroup size for Database: {0} Filegroup: {1}.BFailed to disconnect ODBC connection for instance: {0} Error: {1}.BFailed to obtain memory optimized filegroup list for Database: {0}BNo databases were found for instance: {0} availability group: {1}.BDropping database: {0} on instance: {1} in preparation for restoreBFailed to obtain filelist for Database: {0} Fulltext Catalog: {1}.BSkipping database: {0}. An error occurred while attempting access.CFailed to open instance: {0}. Could not connect to master database.DFailed to obtain databases metadata for instance: {0} database: {1}.EFailed to obtain filegroup metadata for Database: {0} Filegroup: {1}.FFailed to obtain filestream metadata for Database: {0} Filegroup: {1}.FAn error occurred while trying to determine if SQL Server is installedFSkipping database {0}. Portions of it are on a unsupported filesystem.GMSSQL application state capture was cancelled by administrator request.JA primary replica was not found for instance: {0} availability group: {1}.JSkipping database {0}. Portions of it are on a volume mounted on a folder.MNo fulltext catalog files were found for Database: {0} Fulltext Catalog: {1}.NSkipping database {0}. The Availability Group replica role is still resolving.OFailed to obtain the primary replica for instance: {0} availability group: {1}.OFailed to open instance: {0}. Could not obtain configured server\instance name.ORecovery of database: {0} on instance: {1} is complete. Database is now online.OFailed to determine if database: {0} is hosted on the preferred backup replica.OSkipping database {0}. The database is in standby mode and cannot be protected.PRequired component VMware Tools is not installed on this VM. Aborting operation.PSkipping database {0}. The database is in the {1} state and cannot be protected.QAn error occurred while trying to access the registry for SQL Server instance {0}QThe current user: {0} has not been granted the required SQL Server sysadmin role.QFailed to obtain the list of databases for instance: {0} availability group: {1}.SAn error occurred while attempting to query sysadmin role information for user: {0}SFailed to obtain fulltext catalog metadata for Database: {0} Fulltext Catalog: {1}.SCannot perform application state capture. The specified policy type is unsupported.U{0} restore of database: {1} on instance: {2} was cancelled by administrator request.XUnable to perform the requested operation. A NULL or empty input parameter was detected.XFailed to create log dump directory for database: {0}. Unable to perform log truncation._An error occurred while attempting to query metadata for instance: {0} availability group: {1}._Instance {0} on {1} is set as inactive. NetBackup skips any inactive instances during a backup.`Stopping SQL Server services for instance: {0} in preparation for system database restore of {1}aFailed to configure Veritas VSS provider for full VSS backups. Backup will proceed as a VSS copy.bSkipping log truncation for database {0}. It is a primary database in a log shipping configurationbDatabase {0}{1} on {2} is set as inactive. NetBackup skips any inactive databases during a backup.cSkipping database {0}. All or part of it is on the system disk and the policy is set to exclude it.fSkipping database: {0}. An error occurred while attempting to obtain the database filegroup file list.gSkipping database: {0}. An error occurred while attempting to obtain the database filestream file list.gFailed to obtain memory optimized filegroup metadata for Database: {0} Memory Optimized Filegroup: {1}.hAn error occurred while trying to determine if SQL Server Availability Groups are present on the system.kNo supported VSS provider has been found on this VM. Unquiesced snapshots for SQL Server are not supported.lSkipping database: {0}. An error occurred while attempting to obtain the database transaction log file list.mSkipping database: {0}. An error occurred while attempting to obtain the database fulltext catalog file list.rInstance: {0} is at SQL Server release level: {1} which does not support the always on availability group feature.uThe availability group was not found in the instance repository. Cluster: {0}, name: {1}, availability group ID: {2}.vSkipping database {0}. Unable to obtain database file list. Please check the ncfnbcs client logs for more information.vRequired component SQL Server VSS Writer Service is not installed or has been disabled on this VM. Aborting operation.wSkipping database: {0}. An error occurred while attempting to obtain the database memory optimized filegroup file list.}Required component Hyper-V Volume Shadow Copy Requestor is not installed or has been disabled on this VM. Aborting operation.}Skipping log truncation for database {0}. It is using the simple recovery model and does not support log backups w/truncation܅A connection to SQL Server instance {0} was denied. Please ensure that the current user {1} has permissions to access SQL Server. {2}ܐSkipping database {0}. The database is an Always On Availability Group secondary replica database which is not currently supported by the agent.ܒAn access denied error occurred while attempting to access {0}. Please ensure that the current user {1} has permissions on the specified resource.! % $(,048<@D)HLPTX\`dhl-pt159=AEIMQUY]aeimqu,/258;>ADGJMPSVY\_behknqtwz}|E <] r 14.F~  {\ # 9 Jv U jB<KC!S : $  Y1A"XkO k A   [_%yb B H1 HaK;u Y N{ P!