Joseph Michael Pesch
VP Programming

MVC and/or Web API Url Routes Resulting in Page Not Found (http 404 error)

by 16. May 2014 08:39

I was running an MVC/API site on my local development machine using Visual Studio 2013 and when I deployed the site to a development server all the URL routes resulted in page not found (404 error).  To resolve I added the following to the the configuration file.

<system.webServer>
<modules runAllManagedModulesForAllRequests="true" />
<handlers>
<remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" /> <remove name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" /> <remove name="ExtensionlessUrlHandler-Integrated-4.0" /> <add name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" path="*."
verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS" modules="IsapiModule"
scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll"
preCondition="classicMode,runtimeVersionv4.0,bitness32"
responseBufferLimit="0" /> <add name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" path="*."
verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS" modules="IsapiModule"
scriptProcessor="%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll"
preCondition="classicMode,runtimeVersionv4.0,bitness64"
responseBufferLimit="0" /> <add name="ExtensionlessUrlHandler-Integrated-4.0" path="*."
verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS"
type="System.Web.Handlers.TransferRequestHandler"
preCondition="integratedMode,runtimeVersionv4.0" /> </handlers>
</system.webServer>


Tags: ,

C#

Migrating SQL Server Database from Newer version (SQL 2012) to Older Version (SQL 2008 r2)

by 16. May 2014 07:08

I was trying to backup and restore a SQL 2012 database to a SQL 2008r2 server; however, that is not supported (you can only go from previous versions to newer version and not the other way). An alternative method is to use the SQL "Tasks > Copy Database" option when right-clicking on the source database.  Steps to use this method:

  • Right click on source database and select "Tasks > Copy Database"
  • Select source server
  • Select target server
    • Note: If using the "Use Windows Authentication" option make sure to add the necessary login to the source database.  (typically it would be in the form of DOMAIN\MACHINENAME$).
  • On the next screen you will have the option for either "Use the detach and attach method"; or, "Use the SQL Management Object method".  You must use the second option as the detach/attach method will fail similar to a backup/restore (i.e. cannot go from higher version to lower version).
  • Select source database
  • Select destination database
  • Provide package name
  • Schedule the package
  • Finished

At this point there will be a new SQL Agent Job on the target server with the name defined above.  Make sure the target database does not exist before running the job (there is an option to setup the job to overwrite the database if you prefer when setting up the initial job).

 

Tags:

SQL Server