HTTP Error 404.4 - Not Found - The resource you are looking for does not have a handler associated with it.

Sounds like you have offsite redirects configured.  Take a look at this blog entry on MSDN.

Now it looks like it's not seeing the sql database, which resides on the same machine. I found something online about resetting the connection string but I'm not sure how. Is it on the SQL side or the IIS side? Thank you!


Server Error in '/' Application.
--------------------------------------------------------------------------------

The network path was not found
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ComponentModel.Win32Exception: The network path was not found

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace:


[Win32Exception (0x80004005): The network path was not found]

[SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)]
   System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) +642
   System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection) +116
   System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) +1079
   System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) +6605639
   System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry) +233
   System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry) +278
   System.Data.SqlClient.SqlConnection.Open() +239
   Microsoft.Crm.CrmDbConnection.GetCreateAndOpenConnection() +307
   Microsoft.Crm.CrmDbConnection.Open() +460
   Microsoft.Crm.SharedDatabase.DatabaseMetadata.LoadMetadataXmlFromDatabase(CrmDBConnectionType connectionType, String connectionString, Int32& maxBlobSize) +372
   Microsoft.Crm.ConfigurationDatabase.ConfigurationMetadata.LoadCache(String connectionString) +39
   Microsoft.Crm.ConfigurationDatabase.ConfigurationMetadata.get_Cache() +127
   Microsoft.Crm.ServerLocatorService.RetrieveById(String tableName, Object primaryKey, String[] columns) +64
   Microsoft.Crm.ServerLocatorService.GetFederationProvider(Guid id, String[] columns) +236
   Microsoft.Crm.ServerLocatorService.GetFederationProvider(Guid id) +34
   Microsoft.Crm.LocatorService.GetFederationProvider(Guid id) +46
   Microsoft.Crm.CrmAuthenticationContext.get_DefaultFederationProvider() +91
   Microsoft.Crm.CrmAuthenticationContext.GetFederationProviderInternal(Guid orgId) +693
   Microsoft.Crm.CrmAuthenticationContext.IsClaimsEnabled(Guid organizationId) +99
   Microsoft.Crm.MapOrgEngine.Init(HttpApplication context) +76
   System.Web.HttpApplication.InitModulesCommon() +124
   System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +1710
   System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +390
   System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +178
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +670
 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.34248

>>> [Win32Exception (0x80004005): The network path was not found]

That error is pretty straight-forward.  Given this is a new server, I'm guessing it is because you did not open up your database service to network calls, pipes, or whatever method you are using to connect the two.

Take a look at your connection string to get a hint as to how the application is expecting to connect, then look at your SQL Server (I'm assuming MSSQL?) surface area and make sure that approach is available.

Thank you for your response!

Since I'm pretty new at this, I'm kind of shooting in the dark. Is this a change in the SQL Server Configuration Manager? The 'connection string' is the one in IIS? Sorry, I rather look dumb in front of you than my boss.

Thanks again for the help!

Most likely this is a change required in MSSQL.  You'll need to examine the connection string to be sure.  Can you post it here?  It will either be in the code somewhere, or in the web.config file.

Once you know how the application is trying to connect, you need to go into MSSQL and make sure that method is open and available.  For example, if you're connecting through a named pipe, you need to make sure MSSQL is prepared to accept connections through named pipes.

I grabbed this one from the website in IIS that's suppose to connect to the database. Works fine on the original server.

Thank you!

OK, that is a normal named instance on localhost.  The name of the instance should be "SQLEXPRESS".  Now find out what you named your MSSQL instance, and make sure it is willing to accept connections.

When I do a 'select @@ServerName' in SQL, I get the name of the old server. Is there a way to change it?

OK. I figured how to change that but still no luck with the site. Still gives me the same error. I'm trying to figure out if the SQL instance accepts connections.
Thanks!

I also did the .txt to .udl test and it was successful with the 'Windows integrated security' option when connecting to the new SQL server.