NOTE: Backup Exec could also be installed in another SQL Instance exhibiting the same issue.īackup Exec 2012 requires SQL 2005 SP4 which is applied during the time of the upgrade of Backup Exec. This could have been caused by a failed attempt to apply a SQL 2005 Express service pack to the BKUPEXEC instance and the installation never completed successfully. The current Backup Exec SQL instance (BKUPEXEC) is using is in a suspended installation state. V-225-210: Unable to connect to SQL Server SERVER\BKUPEXEC. Only one administrator can connect at this time. V-225-206: Connection attempt 1 failed: Login failed for user 'DOMAIN\BEaccount'. Error MessageĮRROR: Failed to install SQL Express BKUPEXEC instance with error 1627 or error 2259. The Backup Exec 2012 installation will fail and roll back and the existing Backup Exec service may not start. This will allow you to use sqlcmd to generate the login you need to regain access.Įnjoy 😉 Posted in Windows and tagged cluster, failover, single user, SQL, sqlcmd.During upgrade to Backup Exec 2012 the installation fails and reports the Backup Exec database SQL instance (BKUPEXEC) is in single user mode. The way around this is to start the MSSQL$INSTANCENAME using the net start command manually on one of the nodes and not using the Failover Cluster Manager. dll will allows get the first and only connection before you have a hope in hell of getting it.
The important thing to note is that the cluster resource. (Microsoft SQL Server, Error: 18461)” error.įound this great page on MSDN which you should pay close attention to if you are in a clustered environment as we are: Ran into an issue today with one of our SQL instances where we needed to bring it up in Single User mode to recover the sysadmin role, however every time we tried to login we got the fateful “Only one administrator can connect at this time.
0 kommentar(er)
