none
Event ID 9, Event ID:_139, Event ID 18054 RRS feed

  • Question

  • Hello,

    New users unable to use RMS.

    I found the following events:

    Event Type:    Error
    Event Source:    RMS
    Event Category:    Certification
    Event ID:    9

    Description:
    A general error occurred. The following information was reported: System.Data.SqlClient.SqlException: Error 60002, severity 5, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.
       at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.DigitalRightsManagement.Certification.CertificationGen._GetUser(Identification identification)
       at Microsoft.DigitalRightsManagement.Certification.CertificationGen._GetUserKeysAndCertificateWithQuota(String userName, Identification identification, DateTime passportAccountCreation, Byte[] machinePublicKeyHash, Boolean persistent, RsaKeyBlob& userKeys, PersonaCertificate& certificate, QuotaResponse& quota)
       at Microsoft.DigitalRightsManagement.Certification.CertificationGen.Certify(String userName, Identification identification, String machineCertificate, DateTime passportAccountCreation, Boolean persistent)
       at Microsoft.DigitalRightsManagement.Certification.Pipeline.Certify(CaType caType, CertifyParams[] requestParams, HttpRequest request, IIdentity userIdentity)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 7b 65 31 62 34 36 32 66   {e1b462f
    0008: 63 2d 36 32 63 63 2d 34   c-62cc-4
    0010: 32 34 64 2d 61 36 65 32   24d-a6e2
    0018: 2d 64 61 39 34 62 34 65   -da94b4e
    0020: 65 39 62 62 63 7d 2e 36   e9bbc}.6



    Event Type:    Error
    Event Source:    RMS
    Event Category:    Certification
    Event ID:    139


    Description:
    The search of Active Directory failed. The following information was reported: Microsoft.DigitalRightsManagement.Utilities.ADEntrySearchFailedException: Failed to find an entry in the Active Directory: id=S-1-5-21-1017322921-541892195-3522951270-2070.
       at Microsoft.DigitalRightsManagement.Certification.Pipeline._GetPrincipalIdentifier(String principal, String desiredIdentifier)
       at Microsoft.DigitalRightsManagement.Certification.Pipeline._ProcessEmailAddress(IDrmsPropertyBag propertyBag, CaType caType, String& emailAddress, Identification identification)
       at Microsoft.DigitalRightsManagement.Certification.Pipeline.Certify(CaType caType, CertifyParams[] requestParams, HttpRequest request, IIdentity userIdentity).

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 7b 33 32 37 37 30 34 65   {327704e
    0008: 33 2d 39 35 38 65 2d 34   3-958e-4
    0010: 66 31 64 2d 61 37 32 61   f1d-a72a
    0018: 2d 61 30 30 62 30 63 31   -a00b0c1
    0020: 66 33 33 39 37 7d 2e 38   f3397}.8



    Event Type:    Error
    Event Source:    MSSQLSERVER
    Event Category:    (2)
    Event ID:    18054


    Description:
    Error 60002, severity 5, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 86 46 00 00 10 00 00 00   ?F......
    0008: 05 00 00 00 46 00 4e 00   ....F.N.
    0010: 44 00 42 00 00 00 19 00   D.B.....
    0018: 00 00 44 00 52 00 4d 00   ..D.R.M.
    0020: 53 00 5f 00 43 00 6f 00   S._.C.o.
    0028: 6e 00 66 00 69 00 67 00   n.f.i.g.
    0030: 5f 00 66 00 6e 00 65 00   _.f.n.e.
    0038: 74 00 5f 00 74 00 65 00   t._.t.e.
    0040: 73 00 74 00 5f 00 38 00   s.t._.8.
    0048: 30 00 00 00               0...   


    Best Regards --- Abduljalil Abolzahab Technical Specialist - Microsoft Technical Forum: http://Forum.fourtyfivecorp.net
    Monday, February 15, 2010 12:52 PM

Answers

  • Hello,

     

    Based on my research, the event log error refers to a problem with the sysmessages table. To do so, follow the steps in the suggestion section.

    Suggestions:
    ==================

    1. On the server running SQL Server that is missing the sysmessages, start Query Analyzer. This is located in the SQL Server program group on the Start Menu.

    2. When Query Analyzer is opened, you will see a dialog asking you to log in. Ensure that the SQL Server: field contains either "."(without the quotes) or the name of the local server. If the SQL Server was installed as a named instance,
    this field should contain <ServerName>\<InstanceName>. If you are unsure of whether or not SQL Server is a named instance, it most likely is not.

    3. For the login, you can choose Windows Authentication if you are using a default installation of SQL Server and are currently logged in to the server as a local administrator. If connecting with Windows Authentication fails, you will need to choose SQL Server authentication and specify a login and password of a valid SQL Server login that is a SQL Server system administrator. The sa login has these
    rights by default.

    4. Once connected to SQL Server, paste the following script into the query window:

    exec sp_addmessage 60000, 5, 'Unexpected activation error', 'us_english', false, 'REPLACE'

    exec sp_addmessage 60001, 5, 'Bad parameter %s in procedure %s', 'us_english', false, 'REPLACE'

    exec sp_addmessage 60002, 5, 'User %s not found', 'us_english', false, 'REPLACE'

    exec sp_addmessage 60003, 5, 'Machine quota, %d, for user %d exceeded', 'us_english', false, 'REPLACE'

    5. To run the script, either click the Run button (the green play button) or press F5.

    6. A lower pane should appear in the window with multiple lines indicating some rows were affected. This indicates that the script ran successfully.

    7. Close SQL Server Query Analyzer.


    If you have any questions or concerns, please feel free to let me know. I will be glad to help.
     
    Best regards,

    Tom Zhang


    Tom Zhang – MSFT
    Tuesday, February 16, 2010 7:25 AM
    Moderator