Connect Sometimes
From: kpg (ipost_at_thereforeiam.com)
Date: 10/08/04
- Next message: roz: "Connecting from Powerbuilder through ole db, column defaults not r"
- Previous message: tajeshwar: "conection pol"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 8 Oct 2004 08:30:45 -0500
I have SQL Server Developer Edition installed on a Win2k machine.
I can connect (over my LAN) to the SQL Server using a simple VB6
program to open the DB, Add Records, etc.
For testing, the VB6 program used both ADO and DAO (with ODBC).
I could connect using either the server NetBios name (SVR001)
or the DNS name (mycompany.com) with either method (ADO or DAO)
In the Client Network Utility (on ther server) I have Named Pipes and TCP.
In the Server Network Utility I also have Named Pipes and TCP. This is
unchanged from when it worked.
At that point I had not yet run the Client Network Utility (cliConfig) on
the
local (client) machine.
Now the Client Network Utility (on the server) uses TCP port 1433, which
is the default port for SQL Server, but on the Server Network Utility it is
2433. Why? I tried to change it to 1433 but it reverts back to 2433.
With my success at connecting with the VB6 program I wrote a simple VB.NET
windows fors program (using SQLClinet) and It also could connect just fine
Now to crank it up a nothch. I wrote a simple VB.NET Web Forms app
and I cannot connect to the SQL Server using the identical code used in the
Windows Forms project.
After reading a SQL Server connection troubleshooting guide, I learned
about cliconfig. I ran it and set TCP and Pipes and then my .NET Web
Forms app started working, but the other .NET Windows Forms program
and the VB6 program stopped working (Access denied or Server not found).
Undoing the the cliconfig changes had no effect. A reboot however put
things
back to the original problem (every thing works except the .NET Web Form
App).
Now changing the cliconfig settings has no effect on the situation. The VB6
and
VB.NET apps can connect, the VB.NET Web Forms App cannot.
I am using Mixed Mode authentication, but I did consider that perhaps the
ASPNET
user account does no have rights except for that time when it did work, so I
dismissed
that.
Today, after booting up the situation is the same.
I did notice that on my server I hace MS SQL Server 2000 listed twice
in Add/Remove Programs. Could this be a problem?
Any Ideas?
kpg
(PS - I posted a similar blurb on .ms.p.sql.setup)
- Next message: roz: "Connecting from Powerbuilder through ole db, column defaults not r"
- Previous message: tajeshwar: "conection pol"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
