Unable to access service interface problem resolution when publishing Web API data Service interface locally

Recently in the Web API interface, for the front-end display to provide data services, in the company publishing interface services everything is normal, but back to the home of their own notebooks, the problem comes, various types of errors, 500,404 ... " The resource you are looking for has been deleted, renamed, or temporarily unavailable. "Is the guy who appears most ...

As for the service release, we can refer to this article:http://www.jb51.net/article/29787.htm, very good, we all like the illustrations of the tutorial, the most important thing is that we commonly used to publish the way the site can be reserved, 2 of 5 times a praise!!!

In the company, according to the above way to publish the site everything is so smooth, but at home is not so optimistic, here to their own problems and solutions to do a small re-disk:

First, the database

In the company, using the intranet server,SQL Server authentication method, requires a user name and password for database connection;

In my den, there is no doubt that the local SQL Server database ,Windows authentication method for database connection;

The local database becomes the fuse of the problem ...

Second, the solution (several key points to solve the problem):

1. Set the database connection string for the login of the user name password in Project Web. config to Windows integrated login

<connectionStrings>
<add name= "Securecloud" connectionstring= "server= (local); Integrated security=true; Database=dw_isecurecloud_empty2.1;pooling=false "providername=" System.Data.SqlClient "/>
<add name= "securecloudentities" connectionstring= "metadata=res://*/securecloudentities.csdl|res://*/ Securecloudentities.ssdl|res://*/securecloudentities.msl;provider=system.data.sqlclient;provider Connection String=&quot;data source= (local); initial catalog=dw_isecurecloud_empty2.1;integrated security=true; Multipleactiveresultsets=true; app=entityframework&quot; "providername=" System.Data.EntityClient "/>
</connectionStrings>

Deploy MVC Web site on 2.IIS, open after 500 error: handler "extensionlessurlhandler-integrated-4.0" has an error module "Managedpipelinehandler" in its module list

"Workaround"

Run the following command as an administrator to register:

32-bit machine:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe-i

64-bit machine:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe-i

3. In IIS Manager, determine the configuration of the application pool: Name--asp.net v4.0 (unlimited , can be arbitrarily named ), managed pipeline mode-- integration ,. NET Framework (version)--. Net Framework 4.0.30319

4. In IIS Manager, application pool->asp.net v4.0-> Advanced Settings, identity, change to localSystem, or the user IIS apppool\ may appear ASP. NET V4.0 ' Login failed ' ERROR.

Ok,binggo! Record this article, is a reminder to yourself, but also hope to meet the same problems of the partners can help, even if so a lost, is very good, haha ~

Cannot access the resolution of the Service interface problem when publishing the Web API data Service interface locally