SQL Server Errors or Failures from Error: 35003 to Error: 35210

SQLServerF1

Error: 35003, Severity: 16, Cannot move node to one of its children

Error: 35004, Severity: 16, Could not find server group
Error: 35005, Severity: 16, An invalid value NULL was passed in for @server_group_id.
Error: 35006, Severity: 16, An invalid value NULL was passed in for @server_id.
Error: 35007, Severity: 16, Could not find shared registered server.
Error: 35008, Severity: 16, Cannot delete system shared server groups.
Error: 35009, Severity: 16, An invalid value NULL was passed in for @server_type.

Error: 35010, Severity: 16, An invalid value %d was passed in for parameter @server_type.
Error: 35011, Severity: 16, The @server_name parameter cannot be a relative name.
Error: 35012, Severity: 16, You cannot add a shared registered server with the same name as the Configuration Server.
Error: 35100, Severity: 16, Error number %d in the THROW statement is outside the valid range. Specify an error number in the valid range of 50000 to 2147483647.
Error: 35201, Severity: 10, A connection timeout has occurred while attempting to establish a connection to availability replica ‘%ls’ with id [%ls]. Either a networking or firewall issue exists, or the endpoint address provided for the replica is not the database mirroring endpoint
Error: 35202, Severity: 10, A connection for availability group ‘%ls’ from availability replica ‘%ls’ with id [%ls] to ‘%ls’ with id [%ls] has been successfully established. This is an informational message only. No user action is required.

Error: 35203, Severity: 16, Unable to establish a connection between instance ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] due to a transport version mismatch.
Error: 35204, Severity: 10, The connection between server instances ‘%ls’ with id [%ls] and ‘%ls’ with id [%ls] has been disabled because the database mirroring endpoint was either disabled or stopped. Restart the endpoint by using the ALTER ENDPOINT Transact-SQL statement with STAT
Error: 35205, Severity: 16, Could not start the AlwaysOn Availability Groups transport manager. This failure probably occurred because a low memory condition existed when the message dispatcher started up. If so, other internal tasks might also have experienced errors. Check the SQL
Error: 35206, Severity: 10, A connection timeout has occurred on a previously established connection to availability replica ‘%ls’ with id [%ls]. Either a networking or a firewall issue exists or the availability replica has transitioned to the resolving role.
Error: 35207, Severity: 16, Connection attempt on availability group id ‘%ls’ from replica id ‘%ls’ to replica id ‘%ls’ failed because of error %d, severity %d, state %d.
Error: 35208, Severity: 16, Availability-group DDL operations are permitted only when you are using the master database. Run the USE MASTER command, and retry your availability-group DDL command.
Error: 35209, Severity: 16, The %ls operation failed for availability replica ‘%.*ls’, because the backup priority value is outside the valid range. The valid range is between %d and %d, inclusive. Set the backup priority to a value within this range, and retry the operation.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *