The located assembly's manifest definition does not match the assembly reference

In my case this was the issue with Referencing of Log4net Dll.

My web was using absolute reference of Log4net Dll from shared assebmlies folder and was also consuming another Library(Email Template for sending Emails which was also using log4net Dll)

so that was the reason for conflict between them, after investigating a lot i found that EmailProcessor was referencing log4net , not from shared folder but from its own bin folder .

so issue was fixed by deleting bin folder of EmailProcessor and adding the correct reference of Log4net Dll to project.

Ms project Server Publish job 0% complete. Expected Wait Time 0s

I was having this issue while publishing my project to enterprise server ,
i tried with differnt names because while trying the same name it was saying that name already exists but was not uplaoding to project server .

the problem was with project srever , the server was crashed and its services were stopped last night ,

so by restarting the Project Server Eventing and Queuing Services Fixed for me.

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

Running the following command.

%SystemRoot%\system32\inetsrv\appcmd migrate config "Default Web Site/".

and then  refreshing the webpage and everything will work perfectly!

Another thing we can try is that , changing the web's application pool from "Default applicaion pool" to FrameWork 4.0 classic also do the trick some times.

Team Foundation server Reporting Services Error

Error 28805 (Setup cannot finish the request to the SQL Server 2005 Reporting Service report server. Verify that the report server is installed and running and that you have sufficient privileges to access it) - Check the following to resolve this problem:




1. In the SQL Reporting Services Configuration Tool, click on the Database Setup tab and make sure

you are using Windows Credentials.

2. Delete encryption keys in reporting service configuration if they exist.

potentially dangerous request.form asmx web service

I was having this issue while using http post protocol on a web service (asmx) .

i was pasing xml string to the browser and on local network it worked fine on windows 2003 server (Developed on visual studio 2008)

application was moved to windows server 2008 and on .net framework 3.5 on deployment server .

i came to know the following solution but was not allowing me to add this in web.config because of the reason , i was using visual studio 2008 for updating web.config

The solution was to update the project to visual studio 2010 and to add the following line in web.config file
<
httpRuntime requestValidationMode="2.0"/>