Home/ Questions/Q 980983
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T04:28:12+00:00

This is driving me crazy. I written a simple ASP.NET MVC 1.0 application I

  • 0

This is driving me crazy. I written a simple ASP.NET MVC 1.0 application I published this onto my local machine and onto the production server. Both the local and production connects to the same 3rd database server.

The application works fine on the local machine but not on the production server. On the production server I get an error message like: “A network-related or instance-specific error occurred while establishing a connection to SQL Server…”

The production server is running IIS6 and I already enabled wild card. I also tried to delete all references to aspmembership by removing the accountcontroller.
The funny thing is even when I try to make a default ASP.NET MVC 1.0 application and publish it onto the production I get the same error message and there are no database connections anywhere.

How do I solve this or where do I start? Is this a MS SQL problem or a ASP.NET MVC 1.0 on IIS 6 problem?

THANK YOU SO MUCH

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I had the same issue when trying to make MVC 1 and WebForms co-exist. In the end I had to include this into the web.config file.

    <add name="UrlRoutingModule" type="System.Web.Routing.UrlRoutingModule, System.Web.Routing, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>

            <remove name="UrlRoutingModule"/>
            <add name="UrlRoutingModule" type="System.Web.Routing.UrlRoutingModule, System.Web.Routing"/>

    asp.net-mvc and webforms co-existing

    • 0