Re: Problem connecting to sql server


"Skanda Subramanian" <skandy.sub@xxxxxxxxx> wrote in message
news:1136374033.705203.47780@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Ajak:
>
> First thing, go to Client Configuation properties on the client machine
> by going to Start->un->cliconfg and check to see if the protocols are
> enabled. You may wish to try using a different protocol tha the one its
> failing with currently, like Named Pipes for TCP.
>

Do you mean Client Network Utility? Is so, then you mean I need to check its
settings on the SQL server, not my machine right?
I need to clarify that I didn't change anything on the SQL server. And my
Web Application works fine before I format and reinstall Win XP on my
machine. That's all I did.

> Check to see if the account your application is trying to see has
> access on SQL Server.

The account my web application is using is the 'sa' account and yes, it has
all the privillege on the SQL server. And I'm sure the connection string is
right because the same conn string used in 2 different types of app, ran on
my one and only development machine -

1) Web Application written in VB.NET (Where I believe run by aspnet_wp.exe)
<-- cannot find the server or access denied
2) Stand Alone EXE written in VB.NET <--- yipeee! I can see the server just
fine!!!

On my mechine, I also installed SQL Client Tool such as Enterprise Maneger,
Query Analyzer... They can find the SQL server without any problem. The same
goes when I created System DSN in ODBC Data Source Administrator.

That means, only the aspnet_wp.exe cannot find the server. Right?

I am going to try connecting using classic ASP and see if the problem is
there as well.

I hope I have explained the situation I'm having clearly.


.

Relevant Pages

  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)
  • Re: Connect pocket pc (2003) to sql sever in trusted/integrated/ss
    ... it was SQL Server that was running in local system account. ... Here's connection string sample, note "Integrated Security=SSPI". ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Best way to populate webpages from multiple tables
    ... tables within hash tables, custom classes etc. ... > Set a session expiring cookie at the client that stores the Customer ID. ... > send it to the client, instead store it in your session mgmt sql server - ...
    (microsoft.public.dotnet.framework.adonet)
  • SOLUTION: Problem connecting to sql server
    ... it is an account problem. ... Not associated with a trusted SQL Server ... go to Client Configuation properties on the client machine ... >> settings on the SQL server, ...
    (microsoft.public.dotnet.framework.adonet)
Quantcast