RES: [Mono-devel-list] ASP.NET and SQL SERVER 2000
danielmorgan at verizon.net
Thu Sep 23 18:43:16 EDT 2004
Do you have multiple instances of Microsoft SQL Server installed on your
If so, this could be the cause of your problem.
Does your code work on .NET on Windows?
From: mono-devel-list-admin at lists.ximian.com
[mailto:mono-devel-list-admin at lists.ximian.com] On Behalf Of falconn at free.fr
Sent: Thursday, September 23, 2004 11:23 AM
To: mono-devel-list at lists.ximian.com
Subject: Re: RES: [Mono-devel-list] ASP.NET and SQL SERVER 2000
Your are right Ericson, when I configure the connection string like you, it
works perfectly. But it should work in both mode, shouldn't it ? It seems to
be a bug... We should make a bug report, shouldn't we?
> Hi all,
> the connection only works for me with SERVER=SQLSERVER,1433 in the
> connection string, where 1433 is the port configured for tcp
> connection in "Server Network Utility".
> -----Mensagem original-----
> De: mono-devel-list-admin at lists.ximian.com
> [mailto:mono-devel-list-admin at lists.ximian.com] Em nome de
> falconn at free.fr Enviada em: quinta-feira, 23 de setembro de 2004 04:58
> Para: mono-devel-list at lists.ximian.com
> Assunto: RE: [Mono-devel-list] ASP.NET and SQL SERVER 2000
> Yes I am. I use SQL Server authentication. I've already thought about
> timing issue. I've added the option "ConnectionTimeOut" or something
> like that to the ConnectionString but it changes nothing. Thanks for
> your help Daniel.
> Selon Daniel Morgan <danielmorgan at verizon.net>:
> > Are you using a instance name for the server name, such as,
> > Server=MYHOST\MYINSTANCE
> > You appear to be using SQL Server authentication instead of NT
> > Authentication.
> > It sounds like a timing issue. The SqlClient provider maybe timing
> > out.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
Mono-devel-list mailing list
Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list