Edventures in Normalcy

Restore of database ‘NEWDB’ failed. (Microsoft.SqlServer.Management.RelationalEngineTasks) ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: BACKUP LOG cannot be performed because there is no current database backup. (Microsoft.SqlServer.SmoExtended) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.2100.60+((SQL11_RTM).120210-1917+)&LinkId=20476

Lets take a look in the SQL Server error log, to do so:
In Object Explorer, expand a server, expand Management, and then expand SQL Server Logs.
Right-click a log and click View SQL Server Log.

The errors (combined below for readability) generated for this is not much more helpful.

Date 11/20/2012 11:56:40 AM
Log SQL Server (Current – 11/20/2012 12:03:00 AM)

Source Backup

Message
Error: 3041, Severity: 16, State: 1.

BACKUP failed to complete the command BACKUP LOG NEWDB. Check the backup application log for detailed messages.

As it turns out, I also had the warning of  ‘A tail-log backup of the source database will be taken.  View this setting on the Options page.’  This was also a just created database.  When I unchecked the box for ‘Take tail-log backup before restore’ under the ‘Tail-Log backup’ section I was then able to run my restore and get past this error.  This is the first time I have run into this error, I am unsure if this is a change with SQL 2012.