I have set up DNN on Win2K3 using a database locally (either localhost or the hostname, works fine either way) and it connects just fine. I have set up DNN on Win2K3 using a database located on a Win2K workstation and it works just fine. Also, I have set up
DNN on WinXP using a database located on Win2K and it works flawlessly. However, I cannot, cannot, cannot get DNN on Win2K or WinXP to connect to a database on Win2K3 - every time I try I encounter this: Server Error in '/biyntech' Application. --------------------------------------------------------------------------------
SQL Server does not exist or access denied. 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.Data.SqlClient.SqlException: SQL Server does not exist or access denied. 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: [SqlException: SQL Server does not exist or access denied.] System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +474 System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString
options, Boolean& isInTransaction) +372 System.Data.SqlClient.SqlConnection.Open() +384 DotNetNuke.PortalSettings.GetPortalByAlias(String PortalAlias) +153 DotNetNuke.HTTPHandler.OnBeginRequest(Object s, EventArgs e) +143 System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
+60 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573 However, if I create an ODBC DSN, and test it, it tests fine. Also, I can connect to the database through query analyzer or Enterprise Mangler and it connects fine. DNN just WILL NOT CONNECT. Here is the connect string from my web config:
the Win2K3 machine is testwks, and it does resolve correctly if I pink or nslookup the machine name, so DNS is properly configured. Also, the Win2K machine is NOT multihomed (which isn't an issue either, I can connect to a multihomed Win2K box, see above).
I changed the password to foo thinking that a long password might be causing it to flake out, but that's not the issue; it still occurs with foo. The database IS configured for mixed-mode access. IP filtering on this box is not enabled. Any ideas? Am I missing
something obvious?
Katse ~ I wish I had an idea for you, you are always so thorough. But have you tried connecting ANY ASP.NET application to SQL Server in that configuration? You might at least narrow down to a general configuration problem vs. a DNN specific configuration problem.
I can only imagine that the W2K3 machine will have tighter security requirements ~ so it makes sense to me that this configuration is the one giving you grief. What credentials does W2K3 require of an older platform requesting resources from it? If I had enough
hardware I'd try it out for you :( Good Luck ~ Scott
Scott Willhite
Director of Community Relations, DotNetNuke
It is only with the heart that one can see rightly... what is essential is invisible to the eye.
~ Antoine de Saint-Exupéry
Thanks Scott. I might end up moving back down to Win2K tomorrow on my development machine, but I would like to solve this problem because when I implement sites, clients' ISPs may be running that configuration. additional info: The Win2K3 Server is not a DC,
but is a member of my company's domain. It of course does have a machine account, and SQL Server is running under the system account. The servers and workstation I am attempting to access it from are also members of that same domain. Also, for more background:
I have verified that SQL Server does have both named pipes and TCP/IP enabled, and the configuration is the default. AFAIK, the only resources SQL Server requires, when set to mixed mode, is that you use the SQL Server username and password, but I may be mistaken.
As far as other DNN apps and SQL sever, I have not tried that but it should make no difference, right?
Thanks Scott. I might end up moving back down to Win2K tomorrow on my development machine, but I would like to solve this problem because when I implement sites, clients' ISPs may be running that configuration. additional info: The Win2K3 Server is not a DC,
but is a member of my company's domain. It of course does have a machine account, and SQL Server is running under the system account. The servers and workstation I am attempting to access it from are also members of that same domain. Also, for more background:
I have verified that SQL Server does have both named pipes and TCP/IP enabled, and the configuration is the default. AFAIK, the only resources SQL Server requires, when set to mixed mode, is that you use the SQL Server username and password, but I may be mistaken.
As far as other DNN apps and SQL sever, I have not tried that but it should make no difference, right?
Katse, I too have the same config. I have DNN on an XP box with the DB on a Win2K3 box that is local. Both machine are running v1.1 of .NET Framework. Conn String: I have not had an issue. Can you connect with Query Analyzer using your (sa or uid) connection
string info? Does Kim (uid) have dbo rights on KimTech?
username Kim does have dbo rights. I can connect using Query Analyzer from Win2K. I do not have SQL Server nor the client tools installed on the WinXP box however. I am not installing SQL Server on that box as my goal is to make this configuration work. The
XP box has Visual Studio .net installed, and I am attempting to FINALLY get a debug environment up and running, but on this particular environment I need to get the distributed implementation up and running. Does that connect string work through query analyzer?
Quite honestly I do not know how to create a connection in query analyzer by that method. Could you give me some guidlines on this and I will post the results? As usual, thanks for the help, guys! :)
Perhaps a suggestion would be to create a UDL file. This will allow you to mimic connecting via OLEDB as DSN's use ODBC. Theres a quick guide on the microsoft site
here. This will save you installing the client tools. If you get a correct working string, the connectivity with client libraries/ports is fine. To test a generic asp.net app, open the UDL file in notepad, and it will show you what the OLEDB string looks
like. Create a onepage asp.net application to connect to the database with that connection string, and see if that works. Cathal
Katse, The idea of using the Query analyzer was to see if you could login to the server/database with the credintials you supplied, this is opposed to connecting with Windows user/pass. Also, you may consider installing the SQL client tools, I find them to
be tools that I could not live without.
I can connect from Win2K to Win2K3 using Query analyzer, but DNN fails to connect from that Win2K box. I am not installing Query Analyzer on that particular XP box just yet (I am trying to limit the variables until this is solved), but I have connected from
another XP box using Query Analyzer just fine, but DNN fails from that other XP box (the one with Query Analyzer) as well.
Katse
Participant
950 Points
190 Posts
Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 03:12 AM|LINK
zoltar@|maqsonNOSPAMmaqson@|biyndevelopment.com
mrswoop
Star
11177 Points
2240 Posts
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 03:24 AM|LINK
Director of Community Relations, DotNetNuke
It is only with the heart that one can see rightly... what is essential is invisible to the eye.
~ Antoine de Saint-Exupéry
Katse
Participant
950 Points
190 Posts
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 03:32 AM|LINK
zoltar@|maqsonNOSPAMmaqson@|biyndevelopment.com
Katse
Participant
950 Points
190 Posts
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 03:33 AM|LINK
zoltar@|maqsonNOSPAMmaqson@|biyndevelopment.com
Katse
Participant
950 Points
190 Posts
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 03:48 AM|LINK
zoltar@|maqsonNOSPAMmaqson@|biyndevelopment.com
cjsmitty
Star
8010 Points
1600 Posts
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 07:19 AM|LINK
Net Data Design
706Horsman.us
Katse
Participant
950 Points
190 Posts
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 04:03 PM|LINK
zoltar@|maqsonNOSPAMmaqson@|biyndevelopment.com
cathal
Star
13648 Points
2702 Posts
MVP
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 05:57 PM|LINK
cjsmitty
Star
8010 Points
1600 Posts
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 14, 2003 06:18 PM|LINK
Net Data Design
706Horsman.us
Katse
Participant
950 Points
190 Posts
Re: Problem connecting DNN to SQL Server on Win2K3
Aug 15, 2003 05:31 PM|LINK
zoltar@|maqsonNOSPAMmaqson@|biyndevelopment.com