mangled somewhere in the transfer. Applied the correct connection string and
"Charles Wang[MSFT]" wrote:
> Hi Dan,
>
> I understand that your ASP.NET application failed to connect to your SQL
> Server 2005 however another web application could connect to the SQL Server
> 2005 on the same server.
> If I have misunderstood, please let me know.
>
> Since the other ASP.NET application could connect to your SQL Server 2005,
> I think that there might be some differences between the two client
> connections. I recommend that you check the following:
> 1. Check if the two connection strings are same;
> 2. Run "sqlcmd /Snp:<servername>\<instance name> /Usa /P<password>" to
> connecto to your SQL Server to see if it can succeed;
> 3. Run "cliconfg.exe" from command line to add an alias with Named Pipes
> protocol and then check if you can connect to your SQL Server with that
> alias;
> 4. If that does not work, try adding an alias with TCP/IP protocol and then
> use the alias in your connection string to connect to your SQL Server.
> You may refer to:
> How to connect to a named instance of SQL Server 2005 or SQL Server 2000 by
> using the client tools in the earlier version of SQL Server
>
http://support.microsoft.com/kb/265808 > Creating a Valid Connection String Using TCP/IP
>
http://msdn2.microsoft.com/en-us/library/ms191260.aspx > Creating a Valid Connection String Using Named Pipes
>
http://msdn2.microsoft.com/en-us/library/ms189307.aspx >
> If this issue persists, I also would like to know the startup information
> of your SQL Server. Please mail me (changliw_at_microsoft_dot_com) the SQL
> Error logs (%ProgramFiles%\Microsoft SQL Server\MSSQL\LOG) for further
> research.
>
> Hope this helps. If you have any other questions or concerns, please feel
> free to let me know.
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> =====================================================
> Get notification to my posts through email? Please refer to:
>
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications
>
> If you are using Outlook Express, please make sure you clear the check box
> "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
>
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
>
http://msdn.microsoft.com/subscriptions/support/default.aspx. > ======================================================
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================
>