MSDTC on server 'servername' is unavailable

By default, when a stand-alone instance of Microsoft SQL Server exists in a cluster environment, the SQL Server-based instance is set to start automatically. If the host node is rebooted, you may receive the following error message when you issue commands that are related to distributed transactions:

ERROR: MSDTC on server 'servername' is unavailable.

On the server where the trigger resides, you need to turn the MSDTC service on. You can this by clicking START > SETTINGS > CONTROL PANEL > ADMINISTRATIVE TOOLS > SERVICES. Find the service called 'Distributed Transaction Coordinator' and RIGHT CLICK (on it and select) > Start.

Context Has Changed Since the Database Was Created

This article describes and provides the solutions of a common error in Entity Framework: 

"Context has changed since the database was created, Model backing a DB Context has changed, Model backing the context has changed since the database was created."

This is the most frequent error in Entity Framework. This type of error occurred when the model and the database cannot be mapped correctly. That means there is a modification or changed in the database. We made any type of schema change on the table or database after including Entity Data Model in the project or solutions.

To solve this error write the following code in Application_Start() Method in Global.asax.cs file.

Database.SetInitializer<CustomerDBContext>(null);

That means we need to bind our DB context class with a null value. If the database schema is changed, it is mandatory to updates the .edmx file.

An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode

To solve this issue go to Control Panel --> Administrative Tools --> IIS Manager and Change Application site's Managed Pipeline from Integrated to Classic.

The requested page cannot be accessed because the related configuration data for the page is invalid problem in IIS

We need to change the config section applicationHost file

First Open folder path based on this

C:\Windows\System32\inetsrv\config

After open this path we will find applicationHost file.

Now select applicationHost file and right click on applicationHost file and open with Notepad to modify config section.

After open applicationHost file with Notepad

Go to <configSections> under that go to <sectionGroup name="system.webServer">

<section name="handlers" overrideModeDefault="Deny" />
change this value from "Deny" to "Allow"
<section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Deny" />
change this value from "Deny" to "Allow"

After change those values save your applicationhost file and run your application it will work for you.

How to change local folder for TFS

To change local folder path for TFS do the following steps:

1- Connect to your TFS
2- Go to File > Source Control > Workspaces
3- Click on Edit... the workspace which is causing the problem
4- Change the local folder and click on OK.