Joshua Carmody's questions

Our production database server is backing up its databases nightly to Azure Blob Storage, using the BACKUP TO URL command in SQL Server 2014 Standard. I'm now attempting to restore those backups to a new SQL Server VM we set up in Azure, which is also running SQL Server 2014 Standard. I'm running the following SQL command:

RESTORE DATABASE Example FROM URL = 'https://exampleaccount.blob.core.windows.net/livedbbackups/ExampleBackup-2015-10-15T01-13-08.bak';
WITH CREDENTIAL = 'AzureBackupCredential', 
MOVE 'Example' TO 'C:\Databases\Example.mdf',
MOVE 'Example_log' TO 'C:\Databases\Example.ldf',
STATS = 5;

When I do this, the restore runs for 10+ minutes, and I can see it making progress in the "Messages" window of SQL Server Management Studio. However, right before it gets to 100% done, the following error message is displayed.

Output on Azure VM running Microsoft SQL Server 2014 - 12.0.4213.0 (X64) Standard Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor):

85 percent processed.
90 percent processed.
95 percent processed.
Msg 3013, Level 16, State 1, Line 5
RESTORE DATABASE is terminating abnormally.

Googling for "SQL Server Error 3013" or "SQL Server restore database terminating abnormally" produces a lot of pages suggesting my database file is corrupt. However, I don't think it is, because I can run the exact same SQL on my laptop running SQL Server 2014 Express, and I get the following output:

Output on Laptop running Microsoft SQL Server 2014 - 12.0.2269.0 (X64) Express Edition (64-bit) on Windows NT 6.3 (Build 10240: ) (Hypervisor):

85 percent processed.
90 percent processed.
95 percent processed.
100 percent processed.
Processed 233600 pages for database 'Example', file 'Example' on file 1.
Processed 5 pages for database 'Example', file 'Example_log' on file 1.
RESTORE DATABASE successfully processed 233605 pages in 205.802 seconds (8.867 MB/sec).

Both of these restore statements were run against the exact same URL, with the same unaltered backup file. If it restores correctly on my local copy of SQL Server Express, it can't be corrupt, right?

Here are some other possible causes I tried to rule out:

• Version mismatch - The backup was run on a server running Microsoft SQL Server 2014 - 12.0.2269.0 (X64) Standard Edition (64-bit). The restore was run on a server running Microsoft SQL Server 2014 - 12.0.4213.0 (X64) Standard Edition (64-bit). These version numbers were determined by running SELECT @@VERSION on each of the servers.
• Perimssions errors - Both RESTORE HEADERONLY and RESTORE FILELISTONLY work correctly on the Azure VM that won't restore the database.
• Free space - The C: drive on the Azure VM has more than 80 GB free.
• Network connectivity - I haven't done any extensive testing, but given that the VM running SQL Server is running inside Azure, and the backup file is also in Azure, I imagine it's pretty stable. File downloads and simple tests with the browser seem to indicate that the connection is both stable and fast.

The database in question is about 2 GB when restored, with a 5 GB log file. I have other backups of the same database stored in Azure, and I get the same results when trying to restore any of them (works on local SQL Server Express 2014, fails on Azure VM SQL Server Standard 2014).

Any ideas what might be causing this and how to fix it?

I've been trying to get ASP.NET 4.0 to work on Windows Server 2003 R2, 64-bit OS, IIS 6.0 in 32-bit mode. The latest thing I tried in the process was to run aspnet_regiis -s "W3SVC/12345/root" to try to change the version of ASP.NET being run on the site. This seems to have worked, and ASP.NET 4.0 code is now running properly.

However, this seems to have caused a new problem. IIS is no longer recognizing default documents of any type! I have Coldfusion installed on the server and it's default documents are not working either. When I visit http://www.myserver.com or http://www.myserver.com/subfolder, I get "404, file not found". But when I visit http://www.myserver.com/index.cfm or http://www.myserver.com/subfolder/Default.aspx, it works. I've looked at the "documents" tab in the site properties in IIS and both index.cfm and default.aspx are listed there. Why won't IIS recognize them? This was working before, how did I break it?

Edit 1:

I've found that if I create a new site in IIS with all the same settings but running on a different port - ie. http://www.myserver.com:8080/ - the default documents for ColdFusion work again. However ASP.NET default documents still don't work on the newly created site. I have to manually type in http://www.myserver.com:8080/subfolder/Default.aspx instead of http://www.myserver.com:8080/subfolder/.

I've been developing an ASP.NET 4.0 application on my local machine, and today I tried to deploy it to the server. After deploying, I got the following message when trying to visit the site in my browser:

Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.

Ok, no problem. That means the server's still running ASP.NET 2.0. I'll just upgrade it, right?

It hasn't been that simple.

First I installed the .NET Framework v4.0. I followed the instructions that I found at this link to enable the ASP.NET ISAPI DLLs in IIS. When I run "cscript iisext.vbs /listfile " I can see the ASP.NET 4.0 DLLs listed, and that they're enabled. However, the behavior of my application hasn't changed. I still get the same error message.

I suspect I need to change the ASP.NET version in the web site configuration in IIS. However, I can't find any way of doing so. When I right-click on either the website, the virtual directory housing my application, or the application pool in IIS, and then click "Properties" from the context menu, I expected to find an "ASP.NET" tab among the properties pages that would let me change the ASP.NET version for that site/application. However, there is no "ASP.NET" tab or properties page for some reason. Why not? How do I fix this and switch my app to .NET 4.0?

Again, this is Windows Server 2003 R2, I believe the IIS version is 6.

I have a folder on my server like this one:

C:\inetpub\wwwroot\blah

In IIS, I also have a "/blah" virtual folder set up, pointing to C:\BLAH

Naturally, when site visitors type in http://www.myserver.com/blah/test.html, IIS looks for C:\BLAH\test.html, not C:\inetpub\wwwroot\blah\test.html. For the most part, this is the behavior I want, because most of the files are in C:\BLAH. However, when the file DOES exist in C:\inetpub\wwwroot\blah, I'd like the server to look for it there first, and then look in C:\BLAH if it doesn't find it. Basically I'd like the files in C:\inetpub\wwwroot\blah to be an "exception" to the virtual directory. Have the server return the files from that folder, if they exist, but if they don't pull them from C:\BLAH instead of returning a 404.

I am running IIS 5.0 on Windows Server 2000.

Is this possible? Thanks.