Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2003
    Posts
    66

    Red face Unanswered: [HELP] LTM Problem

    who can help me with LTM(Local Test Manager), many thanks.
    Output as follow
    ------------------------------------------------------------------------------------------------------
    Suite: DefaultSuite StartTime: Mon Oct 13 09:54:51 2003 Version: 02.60.6720.0
    ------------------------------------------------------------------------------------------------------
    Alias: SQLSv Clsid: SQLOLEDB Version: 08.50.1022.00
    Initialization: file=c:\adosql.ini
    Context: CLSCTX_INPROC_SERVER
    Client: Machine: MINGLEI Processor: Intel System: Windows 2000 Version: 5.0 Build: 2195 Service Pack 4 ThreadingModel: Single

    Module: ADO Level 0 Conformance Tests Desc: ADO Provider Tests - Level 0 Version: 01.00.0000.04
    TestCase: cn.Close Desc: Connection Close Tests
    Variation (1) Open Connection, Close Connection
    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = -2147467259
    DESC = Invalid authorization specification
    Source = Microsoft OLE DB Provider for SQL Server

    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = 3704
    DESC = Operation is not allowed when the object is closed.
    Source = ADODB.Connection

    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = -2147467259
    DESC = Invalid authorization specification
    Source = Microsoft OLE DB Provider for SQL Server

    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = 3704
    DESC = Operation is not allowed when the object is closed.
    Source = ADODB.Connection

    FAILED
    Variation (2) Close Connection before opening
    PASSED
    TestCase: cn.Execute Desc: Connection Execute Tests
    Variation (1) Execute valid command string
    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = -2147467259
    DESC = Invalid authorization specification
    Source = Microsoft OLE DB Provider for SQL Server

    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = 3704
    DESC = Operation is not allowed when the object is closed.
    Source = ADODB.Connection

    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = 3704
    DESC = Operation is not allowed when the object is closed.
    Source = ADODB.Recordset

    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = 3704
    DESC = Operation is not allowed when the object is closed.
    Source = ADODB.Connection

    FAILED
    Variation (2) Execute zero length string
    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = -2147467259
    DESC = Invalid authorization specification
    Source = Microsoft OLE DB Provider for SQL Server

    *** FAILED ***

    EXPECTED ERROR = -2147217908
    ACTUAL ERROR = 3704
    DESC = Operation is not allowed when the object is closed.
    Source = ADODB.Connection

    *** FAILED ***

    EXPECTED ERROR = -2147217908
    ACTUAL ERROR = 3704
    DESC = Operation is not allowed when the object is closed.
    Source = ADODB.Connection

    FAILED
    TestCase: cn.Open Desc: Connection Open Tests
    Variation (1) Open connection, check for property count increase
    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = -2147467259
    DESC = Invalid authorization specification
    Source = Microsoft OLE DB Provider for SQL Server

    Property count did not increase after open
    *** FAILED ***

    NO ERROR EXPECTED
    ACTUAL ERROR = 3704
    DESC = Operation is not allowed when the object is closed.
    Source = ADODB.Connection

    FAILED
    Summary: Failures: 4 Warnings: 0 Skipped: 0 Passed: 1 Run: 5 Percent: 20
    ------------------------------------------------------------------------------------------------------
    SuiteEnd: DefaultSuite Status: Complete StopTime: Mon Oct 13 09:54:51 2003
    Fail Warn Skip Pass Percent Alias Module
    4 0 0 1/ 5 20% SQLSv ADO Level 0 Conformance Tests
    ------------------------------------------------------------------------------------------------------

  2. #2
    Join Date
    Oct 2001
    Location
    England
    Posts
    426
    Invalid authorization specification
    Sounds like an error in the connection string.
    Maybe the string is invalid or maybe the server isn't set up to allow sql server authyentication and it is using that.

  3. #3
    Join Date
    Sep 2003
    Posts
    66
    thanks, but every settings is by default, what can I do then ?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •