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

Open IIS 7

C:\Windows\Temp\Msftqws.pdw\$(DllSelfRegisterEx) could not be registered because it was not found

Here is the process explained in steps
First you need to find a file name setup.lst in the package and deployment folder that you have created.
Then open the setup.lst file in notepad.
Replace all instances of DllSelfRegisterEx with DllSelfRegister
Save the setup.lst
Run the installation wizard again.

http://nadiaamir.wordpress.com/2007/03/13/cwindowstempmsftqwspdwdllselfregisterex-could-not-be-registered-because-it-was-not-found/

The Just-In-Time debugger was launched without necessary security permissions. To debug this process, the Just-In-Time debugger must be run as an Administrator. Would you like to debug this process?

How to add .NET Framework to Application Pool / Can’t see .NET framework 2.0 integrated in IIS 7

1.       Register “aspnet_regiis” through command line.

“C:\Windows\Microsoft.NET\Framework\v2.0.50727”

2.       Add Application Pool

Metadata contains a reference that cannot be resolved: 'http://localhost/.......

Metadata contains a reference that cannot be resolved: 'http://localhost/SignTrakService/SignTrakService.svc?wsdl'.
The WSDL document contains links that could not be resolved.
There was an error downloading 'http://localhost/SignTrakService/SignTrakService.svc?xsd=xsd0'.
The underlying connection was closed: An unexpected error occurred on a receive.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Metadata contains a reference that cannot be resolved: 'http://localhost/SignTrakService/SignTrakService.svc'.
Content Type application/soap+xml; charset=utf-8 was not supported by service http://localhost/SignTrakService/SignTrakService.svc.  The client and service bindings may be mismatched.
The remote server returned an error: (415) Cannot process the message because the content type 'application/soap+xml; charset=utf-8' was not the expected type 'text/xml; charset=utf-8'..
If the service is defined in the current solution, try building the solution and adding the service reference again.


Solution:


Just turn of your IIS 7 from Window 7, Restart your computer, and again turn "ON" IIS 7 with all features.

Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.