January 11, 2008 at 12:04 pm
how to configure sql 2000 server allow remote access
January 11, 2008 at 12:09 pm
If you are not on SP4, apply it. That may resolve your issue.
January 14, 2008 at 9:03 am
I think you mean sql 2000 sp4.
According to above link
Important: SQL Server 2000 Service Pack 4 is not supported on Windows NT 4.0, Windows Millennium Edition and Windows 98 platforms.
January 14, 2008 at 2:23 pm
Run
sp_configure
you can see "remote access"
Turn it on (set the value to 1 to enable the remote access).
January 15, 2008 at 6:12 am
I used SP_CONFIGURE to check remote acces config_value is 1 realdy. so.. why I still get the error.
checked
remote access0111
January 15, 2008 at 6:17 am
What error are you getting?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 15, 2008 at 7:02 am
it is web application.
application connect to the remote sql2000 server
http://localhost:2132/HRHSKeyContact/HRHSKeyContact.aspx?HID=1 viewable in the local machine
http://webserver(computername)/HRHSKeyContact/HRHSKeyContact.aspx?HID=1 not viewable in the local machine
I just do not understand the difference.
error msg:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
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: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I used the vb 2.0 to access the remote sql 2000 server.
January 15, 2008 at 7:08 am
I find that particular error message very misleading. I've seen it several times where the problem had nothing to do with remote access.
It could be that the server name is incorrect in the web app's connection string
It could be that the server is offline (but if you're querying it, that's not the case)
It could be incorrect password.
That error is the 2005 version of the old message
"SQL Server does not exist or access is denied"
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 15, 2008 at 9:25 am
I do not think the error is connection string
http://localhost:2132/HRHSKeyContact/HRHSKeyContact.aspx?hid=2
it is view. it connected to remote database.
http://computername/HRHSKeyContact/HRHSKeyContact.aspx (html file)
it is viewable. web server is working.
http://computername/HRHSKeyContact/HRHSKeyContact.aspx?hid=2
it has database connection problem.
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
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: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
I do not have ms sql 2005 install in that server at all.
January 16, 2008 at 7:50 am
If you are working with SQL Server 2005 and used the "SQL Server Surface Area Configuration" Tool ...
Start >> All Programs >> Microsoft SQL Server 2005 >> Configuration Tools >> SQL Server Surface Area Configuration >> Surface Area Configuration for Services and Connections >> Remote Connections >> (default is: Local connections only)
... and make any changes, it will give a warning window that states that you will have to restart the SQL Server Service for changes to take effect. In my experience, restarting the SQL Server service has not worked. I have had to reboot the server for those changes to allow remote connections to that instance.
Note that Remote Connections are DISABLED by default, for SQL Server 2005.
Hope This Helps
"Key"
MCITP: DBA, MCSE, MCTS: SQL 2005, OCP
January 16, 2008 at 7:54 am
I do not have ms sql 2005 installed in my server at all.
January 16, 2008 at 8:12 am
Frances,
My apologies for reading the posting too quickly.
All I have been able to find is a reference on page 388 in the ebook:
After executing:
exec sp_configure 'remote access', 1
reconfigure
The paragraph below also states "After enabling remote access, you'll need to shut down and restart each server".
There are also notes on how the database user(s) need to be configured on pages 388 and 389+
Hopefully these steps will help.
"Key"
MCITP: DBA, MCSE, MCTS: SQL 2005, OCP
January 16, 2008 at 8:49 am
When you open SQL Server's "Server Network Utility" what protocols are enabled? It sounds like you need Named Pipes enabled as that is what your error message is complaining about. I have TCPIP and Named Piples enabled.
Can you connect to this SQL Server instance from a remote machine using Enterprise Manager?
Another common problem I've seen is DNS server sending your connection requests to the wrong machine. I have a server right now that everytime I try to connect to it from one area of our network I actaully connect to a sales person's laptop and not the server I want. The DNS folks are looking into it, but most likely the DNS tables are just messed up. I figured it out by using remote desktop to make the connection and realized it was not the machine I was expecting. OK, I also kicked the guy off of is machine when I logged on and he was logged out, but that story is for another day...
I now you said you can't install SQL Server 2000 SP4 because you are running on NT 4.0, how about SQL Server SP3. I know on Windows2000 you had to be on at least SQL Server SP3 otherwise the network connections were disabled. I'm not sure what SQL Server's support is for NT 4.0.
-Tony
January 16, 2008 at 9:00 am
You said that
http://computername/HRHSKeyContact/HRHSKeyContact.aspx
works, but
http://computername/HRHSKeyContact/HRHSKeyContact.aspx?hid=2
doesn't.
If you look at the aspx page, what's done differently if the querystring is passed, compared to not passed. Can you post the relevant portions of the code from the aspx page?
Is the web server on the same machine as the SQL server?
Is SQL Native access client installed on the web server (if it is, it would explain why you're getting a 2005-related error with a 2000 server.)
The particular error that you're getting is the generic 'server not found or access is denied' message that a 2005 client library will generate if it can't connect. Often is has nothing to do with remote access not been enabled. Especially on a SQL 2000 machine, where remote access is enabled by default.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 16, 2008 at 9:36 am
<asp:DetailsView ID="dvInfo" runat="server" DefaultMode=ReadOnly AutoGenerateRows="False"
DataSourceID="dsKeyContact" HeaderText="Review the info and make the necessary change" DataKeyNames="HID"
Width="692px" OnItemUpdated="dvInfo_ItemUpdated" OnDataBound="dvInfo_DataBound" Font-Bold="True" Font-Size="Large">
<asp:DropDownList id="dpBusUnit" runat="server"
DataSourceID="dsBusUnit"
DataTextField="BusUnit" DataValueField="BusUnit"
SelectedValue='
<asp:DropDownList id="dpDept" runat="server"
DataSourceID="dsDept"
DataTextField="Dept" DataValueField="Dept"
SelectedValue='
<asp:CustomValidator ID="ValidPhoneLength" runat="server" ControlToValidate =txtOfficePhone ClientValidationFunction="ValidPhoneLenght"
ErrorMessage="The length of the phone should not more than 10">*
<asp:RegularExpressionValidator ID="vrREmail" runat="server" ErrorMessage="Check the email again. It must contain @" ControlToValidate =txtEmail
ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*">*
"
SelectCommand="SELECT [HName], [Title], [BusUnit], [Department], [OfficePhone], [Mobile], [Pager], [Home], [AlternatePhone], [Email], [LastUpdate], [HID] FROM [KeyContactPhone] WHERE ([HID] = @HID)"
UpdateCommand="UPDATE KeyContactPhone SET Title =@Title, HName =@HName, BusUnit =@BusUnit, Department =@Department, OfficePhone =@OfficePhone, Mobile =@Mobile , Pager =@Pager, Home =@Home, AlternatePhone =@AlternatePhone, Email =@Email WHERE ([HID] = @HID)" ProviderName="
"
SelectCommand="SELECT Dept from Dept order by Dept " ProviderName="
"
SelectCommand="SELECT BusUnit from BusUnit order by BusUnit " ProviderName="
When you open SQL Server's "Server Network Utility" what protocols are enabled? It sounds like you need Named Pipes enabled as that is what your error message is complaining about. I have TCPIP and Named Piples enabled.
The 'remote access is set up as 1 already.
You said that
http://computername/HRHSKeyContact/HRHSKeyContact.aspx
works, but
http://computername/HRHSKeyContact/HRHSKeyContact.aspx?hid=2
doesn't.
What I tried to say is the web server did not have problem to display the web site.
Here is my aspx code. The query string should not be issue. Since
http://localhost/HRHSKeyContact/HRHSKeyContact.aspx?hid=2
will show the result as I expected.
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply