RE: Connection Open Exemptions

From: Sophie Guo [MSFT] (v-sguo_at_online.microsoft.com)
Date: 02/04/05 

Date: Fri, 04 Feb 2005 06:17:00 GMT

Hello 11Oppidan,
 
Is this a duplicated post of "Security and Logins with ADO.NET"? If so,
please check my answer there and if you need any further assistance on this
particular issue, please reply to me in that thread so I can follow up with
you in time. Also, please don't post the same question in newsgroups in the
future so that our engineers can work on your question efficiently. Your
understanding and cooperation is appreciated.
 
If you'd like to troubleshoot the problem from the client computer, I
recommend you perform the following steps:

1. Install SQL client tools on the client computer. Check if the user can
log into SQL server using SQL Query Analyzer (QA). Check if the user can
run the SQL statement successfully.
 
If the user can log into SQL server using QA, it indicates that the user
has permissions on this SQL server.
 
Note: The user account can be either Windows account or SQL account.
 
After log into SQL server in QA, if the user can run the SQL statement
successfully, it indicates that the user has the correct permissions on the
database.
 
If the user cannot log into SQL server using QA, please try to log into QA
as sa or an administrative user. If the issue still exists, you can refer
to the following article:
 
How to troubleshoot connectivity issues in SQL Server 2000 (827422)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;827422
 

2. Contact Product Support Services (PSS) to get mdactrace tool

If you want more detailed information about ADO connection, I recommend
that you open a Support incident with Microsoft Product Support Services
(PSS) so that a dedicated Support Professional can work with you in a more
timely and efficient manner. If you need any help in this regard, please
let me know.

For a complete list of Microsoft Product Support Services phone numbers,
please go to the following address on the World Wide Web:
<http://support.microsoft.com/directory/overview.asp>

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

3. The output file of "sqldiag Utility".
 
Please execute the following command at the DOS prompt:

        "C:\Program Files\Microsoft SQL Server\MSSQL\Binn\sqldiag.exe"

SQLdiag.exe is a command line utility that puts all the SQL server error
logs and other configuration settings into a text file.

Note:

a. Above command use the default folder. You may need to replace the right
folder which sqldiag.exe locates.
b. The generated log file SQLdiag.txt is located in Log folder.

Check the output file.

4. Windows application log

The following information is for your reference:

Viewing the Windows Application Log
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/a
d_perfmon_5qnn.asp>
 
Check the Windows Application Log file.

You may send me all output files for research at v-sguo@Microsoft.com

I hope above information is helpful.
 
 

Sophie Guo

Microsoft Online Partner Support

 

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================

Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

 

This and other support options are available here:

BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469

Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

 

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.

=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

Relevant Pages

  • Re: Security Update for SQL Server 2005 Service Pack 2 (KB948109)
    ... If you're running Windows Live Mail, sign out then close the application. ... Understand that you can open a free support incident about your issues: ... When you call, clearly state that your problem is related to a Security Update and cite the update's KB number. ... SQL Server Database Services 2005 ENU SP2 ...
    (microsoft.public.windowsupdate)
  • Re: Howto troubleshoot login failure - State 11?
    ... It belongs to a Windows ... group which is granted access to your SQL Server. ... Microsoft Online Community Support ... or a Microsoft Support Engineer within 1 business day is acceptable. ...
    (microsoft.public.sqlserver.security)
  • RE: Hung SSIS package is hanging my database
    ... SSIS logging and log providers let you capture details about the package ... connections, it might be some internal errors in SQL Server, To find out ... has to be done by contacting Microsoft Product Support Services. ... Microsoft Product Support Services so that a dedicated Support Professional ...
    (microsoft.public.sqlserver.dts)
  • Slow performance with windows authentication
    ... Since you can connect to SQL server when logging on as Windows ... you contact Microsoft Product Support Services and open a support incident ...
    (microsoft.public.sqlserver.security)
  • RE: Configuration parameter in SQL database
    ... Welcome to Microsoft Newsgroup Support Service! ... how to store&return the configuration ... SQL Server + SQL Dependency Cache ...
    (microsoft.public.dotnet.general)