I have a project in VWDExp that works great, exactly as intended. However when I move it to the productions servers, I must be skipping a step or two.
I can't get to any page that requires a database connection. Why does the local "Deveopment Server" work and the productions servers can't do a thing? I have tried hosting on a server2008 and a win7 IIS. This is my first asp.net project and I am getting
very fustrated at why I can't host my own web site. I have done days of search online and read a few ebooks but I can't seem to get it all working.
You need to change your connection string in your web config to match your production server instances. Usually, that is a good step to add to any installer scripts you may build in your deployment wizard.
If you have deployed to a production environment (azure?) with a different database, you'll need to update the connection string in the web.config.
Please confirm the error message that you are receiving. Also confirm that the connection string is pointing to where the sql database lives, and finally that the user has permissions (often when working locally you'd use integrated security=SSPI, but in
production this would swap to a username and password)
Hope this helps.
Please click "Answer" if this hepled in solving your problem.
must match exactly what your service provider for hosting is using. Who are you hosted with? I can probably help you fill in these settings if I know who you are using.
Ok, so its your own in-house SQL Server, ok. Chances are the SQL Server is blocking remote connections. You have to make that change at the SQL Server using the SQL Configuration Manager.
Server is set to allow connections as it is not the first database(or instance) running on that server. The windows firewall is off,
This guy offered to say that "You cannot use Windows Authentication to connect to a remote SQL Server instance." Do you know this to be true or false for 2008 SP0?
that is not true, its in house and I have done this myself about a billion times. What you need to do is to change the configured identity in the application pool to use the domain user you want to use. NT/Kerberos can be very fussy when it comes to permitting
access.
Mark as answer posts that helped you.
Marked as answer by Angie xu - MSFT on Nov 21, 2012 12:46 AM
Blackbird_71
0 Points
5 Posts
First Deployment
Nov 14, 2012 03:09 PM|LINK
I have a project in VWDExp that works great, exactly as intended. However when I move it to the productions servers, I must be skipping a step or two.
I can't get to any page that requires a database connection. Why does the local "Deveopment Server" work and the productions servers can't do a thing? I have tried hosting on a server2008 and a win7 IIS. This is my first asp.net project and I am getting very fustrated at why I can't host my own web site. I have done days of search online and read a few ebooks but I can't seem to get it all working.
Jack
bbcompent1
All-Star
33824 Points
8760 Posts
Moderator
Re: First Deployment
Nov 14, 2012 03:38 PM|LINK
You need to change your connection string in your web config to match your production server instances. Usually, that is a good step to add to any installer scripts you may build in your deployment wizard.
romage
Participant
1753 Points
311 Posts
Re: First Deployment
Nov 14, 2012 03:40 PM|LINK
Hi,
If you have deployed to a production environment (azure?) with a different database, you'll need to update the connection string in the web.config.
Please confirm the error message that you are receiving. Also confirm that the connection string is pointing to where the sql database lives, and finally that the user has permissions (often when working locally you'd use integrated security=SSPI, but in production this would swap to a username and password)
Hope this helps.
Blackbird_71
0 Points
5 Posts
Re: First Deployment
Nov 14, 2012 04:15 PM|LINK
Line 31: } Line 32: set { Line 33: this.SetPropertyValue("domain", value); Line 34: } Line 35: }I have been trying to follow this guide. However I can't find the DefaultAppPool users on the local machine.
But I tried to use a Entity too and I am concerned about that string as well.
bbcompent1
All-Star
33824 Points
8760 Posts
Moderator
Re: First Deployment
Nov 14, 2012 04:17 PM|LINK
Ok, those values in this line:
Server='SERVER'\MSSQLSERVER;Database='Name_of_instance';User ID='DOMAIN'\DBOperator;Password=●●●●●●●●●●
must match exactly what your service provider for hosting is using. Who are you hosted with? I can probably help you fill in these settings if I know who you are using.
bbcompent1
All-Star
33824 Points
8760 Posts
Moderator
Re: First Deployment
Nov 14, 2012 04:19 PM|LINK
Your connection string stuff probably will look more like this:
Blackbird_71
0 Points
5 Posts
Re: First Deployment
Nov 14, 2012 04:20 PM|LINK
It is my own in house SQL server. This is an intranet site with windows authentication.
Thank you for your quick responce.
bbcompent1
All-Star
33824 Points
8760 Posts
Moderator
Re: First Deployment
Nov 14, 2012 04:26 PM|LINK
Ok, so its your own in-house SQL Server, ok. Chances are the SQL Server is blocking remote connections. You have to make that change at the SQL Server using the SQL Configuration Manager.
Take a look here for how: http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx
Blackbird_71
0 Points
5 Posts
Re: First Deployment
Nov 14, 2012 07:43 PM|LINK
Server is set to allow connections as it is not the first database(or instance) running on that server. The windows firewall is off,
This guy offered to say that "You cannot use Windows Authentication to connect to a remote SQL Server instance." Do you know this to be true or false for 2008 SP0?
bbcompent1
All-Star
33824 Points
8760 Posts
Moderator
Re: First Deployment
Nov 15, 2012 11:46 AM|LINK
that is not true, its in house and I have done this myself about a billion times. What you need to do is to change the configured identity in the application pool to use the domain user you want to use. NT/Kerberos can be very fussy when it comes to permitting access.