locked
FCS Enterprise Manager failed to connect to a down-level database RRS feed

  • Question

  • Hello everyone,

     

    I have the following scenario

     

    4 FCS deployments:

    • 1 management server
    • 1 collection server
    • 1 reporting server
    • updates with WSUS Server

     

    1 Enterprise Manager server

    • all roles in the same server

     

    All servers are on the same ip segment

     

    In the Enterprise Manager´s event viewer appear the following events for all the DLS:

     

    Description

    Enterprise Manager failed to connect to a down-level database.
    Server: aaaaaaa
    Database: one point

     

    Description:
    The connection to a down-level database has been restored.
    Server: aaaaaaaa
    Database: OnePoint

     

    I check permissions in the collection DB, in the local administrators, etc

     

    Any ideas about this issue?

    Friday, April 1, 2011 5:31 PM

Answers

  • Hi,

    Thanks for the post.

    Before using Client Security, you must grant additional permissions to the service
    accounts.

    To grant the correct permissions for the service accounts

    1. On the Client Security server, add the action account to the Administrators group.
    2. Grant the reporting account db_owner permissions on the SystemCenterReporting database.
    3. If you used different accounts for the DAS account and the action account, grant the action account db_owner permissions on the OnePoint database.
    4. If you used different accounts for the DAS account and the reporting account, grant the reporting account db_owner permissions on the OnePoint database.

    To grant permissions to SQL Server databases

    1. On the server with the appropriate database (OnePoint or SystemCenterReporting), start SQL Server Management Studio.
    2. In the console tree, expand Security.
    3. Right-click Logins, and then click New Login on the shortcut menu.
    4. In the Login dialog box, type the appropriate service account (domain\username) in the Login name box.
    5. Under Select a page, click User Mapping, and then in the Map column, select the check box for the appropriate database.
    6. In the Database role membership box, select the db_owner check box, and then click OK.

    Hope this helps.

    Miles


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Bechir Gharbi Tuesday, April 5, 2011 5:58 PM
    • Marked as answer by Miles Zhang Tuesday, May 3, 2011 1:50 AM
    Monday, April 4, 2011 2:43 AM

All replies

  • Hi,

    Thanks for the post.

    Before using Client Security, you must grant additional permissions to the service
    accounts.

    To grant the correct permissions for the service accounts

    1. On the Client Security server, add the action account to the Administrators group.
    2. Grant the reporting account db_owner permissions on the SystemCenterReporting database.
    3. If you used different accounts for the DAS account and the action account, grant the action account db_owner permissions on the OnePoint database.
    4. If you used different accounts for the DAS account and the reporting account, grant the reporting account db_owner permissions on the OnePoint database.

    To grant permissions to SQL Server databases

    1. On the server with the appropriate database (OnePoint or SystemCenterReporting), start SQL Server Management Studio.
    2. In the console tree, expand Security.
    3. Right-click Logins, and then click New Login on the shortcut menu.
    4. In the Login dialog box, type the appropriate service account (domain\username) in the Login name box.
    5. Under Select a page, click User Mapping, and then in the Map column, select the check box for the appropriate database.
    6. In the Database role membership box, select the db_owner check box, and then click OK.

    Hope this helps.

    Miles


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Bechir Gharbi Tuesday, April 5, 2011 5:58 PM
    • Marked as answer by Miles Zhang Tuesday, May 3, 2011 1:50 AM
    Monday, April 4, 2011 2:43 AM
  • Thank´s for your response.

    I check the permissions and i have one account for everything: DAS, Action & Reporting

    I found thaht in the event viewer the event ID 10050 come with this

    0000: 54 00 69 00 6d 00 65 00   T.i.m.e.
    0008: 6f 00 75 00 74 00 20 00   o.u.t. .
    0010: 65 00 78 00 70 00 69 00   e.x.p.i.
    0018: 72 00 65 00 64 00 2e 00   r.e.d...
    0020: 20 00 20 00 54 00 68 00    . .T.h.
    0028: 65 00 20 00 74 00 69 00   e. .t.i.
    0030: 6d 00 65 00 6f 00 75 00   m.e.o.u.
    0038: 74 00 20 00 70 00 65 00   t. .p.e.
    0040: 72 00 69 00 6f 00 64 00   r.i.o.d.
    0048: 20 00 65 00 6c 00 61 00    .e.l.a.
    0050: 70 00 73 00 65 00 64 00   p.s.e.d.
    0058: 20 00 70 00 72 00 69 00    .p.r.i.
    0060: 6f 00 72 00 20 00 74 00   o.r. .t.
    0068: 6f 00 20 00 63 00 6f 00   o. .c.o.
    0070: 6d 00 70 00 6c 00 65 00   m.p.l.e.
    0078: 74 00 69 00 6f 00 6e 00   t.i.o.n.
    0080: 20 00 6f 00 66 00 20 00    .o.f. .
    0088: 74 00 68 00 65 00 20 00   t.h.e. .
    0090: 6f 00 70 00 65 00 72 00   o.p.e.r.
    0098: 61 00 74 00 69 00 6f 00   a.t.i.o.
    00a0: 6e 00 20 00 6f 00 72 00   n. .o.r.
    00a8: 20 00 74 00 68 00 65 00    .t.h.e.
    00b0: 20 00 73 00 65 00 72 00    .s.e.r.
    00b8: 76 00 65 00 72 00 20 00   v.e.r. .
    00c0: 69 00 73 00 20 00 6e 00   i.s. .n.
    00c8: 6f 00 74 00 20 00 72 00   o.t. .r.
    00d0: 65 00 73 00 70 00 6f 00   e.s.p.o.
    00d8: 6e 00 64 00 69 00 6e 00   n.d.i.n.
    00e0: 67 00 2e 00               g...   

    What do you think?

    regards

    Miguel

    Thursday, April 7, 2011 3:53 PM
  • Did you ever get this resolved?  I'm getting the exact same thing on one of my down-level databases and all permissions seem to be the same.
    Friday, June 17, 2011 1:50 PM