Please note: this solution is considered to be obsolete
Errors:
Code: Select all
Error occurred during LocalDB instance startup: SQL Server process failed to start
Veeam.Backup.Common.CSqlException: Microsoft SQL server hosting the configuration database is currently unavailable. Possible reasons are heavy load, networking issue, server reboot, or hot backup.
Please wait, and try again later.
Preparation:
1. Before you go, check:
- Your antivirus is not blocking the installation process.
- Microsoft SQL Server 2012 Express LocalDB is installed. If you have any installation issues - the best option is to install the version included in the setup
- SYSTEM accout has full access permissions to systemprofile folder C:\Windows\System32\config\systemprofile
2. Download, install and open PS Tools:
- Download PSTools:
http://download.sysinternals.com/files/PSTools.zip
- Install it, for ease of use it could be unpacked to C:\PSTools\
- Go to Run > cmd as administrator
- cd C:\PSTools (or the folder you used for during unpacking)
- Run PsExec.exe –i –s cmd.exe (accept the user agreement message may pop up )
3. Uninstall Veeam Endpoint Backup BETA via Control Panel > Programs and Features
Resolutions:
Case A: Instance was corrupted during setup and must be deleted:
1. Download, install and open PS Tools like described in preparation step 2
2. Delete corrupted instance by typing the following commands in PS Tools command prompt:
Code: Select all
whoami
//Response nt authority\system
“C:\Program Files\Microsoft SQL Server\110\Tools\Binn\SqlLocalDB.exe” delete VeeamEndPoint
//Response: “LocalBD instance “VeeamEndPoint” deleted”
3. Reboot and to install Veeam Endpoint Backup.
Case B: The Case A solution did not help. Instance creation continues to fail during Endpoint setup.
1. Install the following components (reboot if required for each component):
- Microsoft System CLR Types for SQL Server 2012 (is included in Endpoint setup)
- Microsoft SQL Server 2012 Management Objects (is included in Endpoint setup)
- Microsoft SQL Server 2012 Express LocalBD (is included in Endpoint setup)
- Microsoft SQL Server 2012 Native Client
- Microsoft SQL Server 2012 Command Line Utilities
2. Add the following string values for SQL instance login/password in the registry via regedit.exe
Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup
//the following string values generated by QA
"SqlLogin"="VeeamLogin"
"SqlPassword"="75f00cdb-d8db-45ab-8024-8cc576df15b1"
3. Download, install and open PS Tools like described in preparation step 2
4. Re create the instance by typing the following commands in PS Tools command prompt:
Code: Select all
whoami
//Response nt authority\system
“C:\Program Files\Microsoft SQL Server\110\Tools\Binn\SqlLocalDB.exe” delete VeeamEndPoint
//Response: “LocalBD instance “VeeamEndPoint” deleted”
SqlLocalDB create VeeamEndPoint
//Response: “LocalBD instance “VeeamEndPoint” created with version 11.0.”
SqlLocalDB start VeeamEndPoint
//Response: “LocalBD instance “VeeamEndPoint” started”
SqlLocalDB info VeeamEndPoint
//Response example (12345678 is an example – you will have other output): “Instance pipe name: np:\\.\pipe\LOCALDB#12345678\tsql\query”
//Copy np:\\.\pipe\LOCALDB#12345678\tsql\query from the previous query
sqlcmd -S np:\\.\pipe\LOCALDB#12345678\tsql\query
// Command prompt cursor will change to 1>
// Type in each line and hit enter one by one
USE [master]
GO
CREATE LOGIN [VeeamLogin] WITH PASSWORD=N'75f00cdb-d8db-45ab-8024-8cc576df15b1', DEFAULT_DATABASE=[master], CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
GO
EXEC master..sp_addsrvrolemember @loginame = N'VeeamLogin', @rolename = N'sysadmin'
GO
EXIT
// Command prompt cursor revert back to normal
SqlLocalDB stop VeeamEndPoint
// Response “LocalBD instance “VeeamEndPoint” stopped”
Additionally:
- Microsoft SQL Server 2012 Native Client and Microsoft SQL Server 2012 Command Line Utilities can be found here:
http://www.microsoft.com/en-US/download ... x?id=29065
If the LocalDB and sqlcmd fail:
During LocalDB and sqlcmd installation path variables are automatically pushed into the system. If SqlLocalDB or sqlcmd commands fail, you may need to type a full path instead:
- SqlLocalDB should be replaced by “%Program Files%\Microsoft SQL Server\110\Tools\Binn\SqlLocalDB.exe” (with quotes)
- sqlcmd should be replaced by “%Program Files%\Microsoft SQL Server\110\Tools\Binn\SqlCmd.exe” (with quotes)
Still having installation issues?
Collect and share:
- The full setup logs from C:\ProgramData\Veeam
- Windows Event logs from windows event viewer (Custom View > Administrative events)
- LocalDB error log from %systemroot%\system32\config\systemprofile\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\VeeamEndPoint\ (it should look like error.log, error1.log, error2.log etc)
- Pack and send it via any available cloud storage (Dropbox/Google Drive/OneDrive etc)
- Ping me via PM or posting to this thread