You are attempting to protect a computer with one or more installed SQL 2008R2 or later instances. Although the pairing operation went well, you notice that the SQL instances metadata is not shown on the core and that the account you used for protection does not have the rights to access the SQL server hosted on the protected machine. Since this means that your SQL databases backups are in a crash consistent state, you try to find credentials that would allow you to log as a sysadmin for one or more instances of that SQL server but you are out of luck as the correct information just cannot be found. You need to find a way for adding a login with sysadmin permissions without having access to any credentials with such permissions.
A powershell script to address this situation has been prepared. To run it you need Powershell 3.0 or later, you need to launch an elevated console and the execution policy to be set to "remotesigned" or more permissive.
This script requires you to have local administrator rights on the machine hosting the SQL server.
When you run the script you are prompted for the user to be added as a login. It needs to be entered in the format
if it is a local account. The instances hosted on the server are found and presented in a gridview so you can choose one or more for which you need to add the new login.
Refreshing (in most cases twice) the metadata for the protected machine will show in the SQL information table the databases pertaining to the SQL instances and successful backups will be in a application consistent state.