Forum Discussion

Sox's avatar
Sox
Level 4
11 years ago

EV10 database migration

I have one problem with our EV console. Our database admin was make migration of all databases (including EV databases) from single server to clustered SQL instance. He didn't consult with me before migration of EV databases, and now EV console won't connect. he keep the same SQL instance name, he configure named pipes and tcp settings regarding Symantec recommendations, he put evservice account on cluster nodes in local admins group, he give all proper permissions to SQL instance to evservice account. Even after that we cannot start EV console now. All EV services are running. Can any anybody help me to solve this problem? Thank you in advance
Enterprise Vault
Information Governance
Windows Server (2003-2008)
  • A_J1's avatar
    A_J1
    11 years ago

    Hello Sox,

    Following is an excerpt from the Dtrace log on what i see:

    *****************************************************************

    417         14:00:03.761       [4304]  (DirectoryService)           <4932> EV:M     The SQL database server for Provider=SQLOLEDB;Server=CLSQL08-2\EVSILOS;Database=MASTER;Integrated Security=SSPI is not available: |Check that the SQL Server is valid and is running|Internal reference(CC1)|Additional Microsoft supplied information:|Source:       Microsoft OLE DB Provider for SQL Server|Number:       0x80004005|SQL State:    08001|Native Error: 17|HRESULT|0xc0043433

    418         14:00:03.761       [4304]  (DirectoryService)           <4932> EV:L       CADOContext::CreateConnection exit. source:Provider=SQLOLEDB;Server=CLSQL08-2\EVSILOS;Database=MASTER;Integrated Security=SSPI hr=The SQL database server for %2 is not available:      Check that the SQL Server is valid and is running         Internal reference(%8)   Description:      %1     Additional Microsoft supplied information:     Source:       %3   Number:       %4   SQL State:    %5   Native Error: %6   HRESULT  %7        (0x8004344a)

    419         14:00:03.761       [4304]  (DirectoryService)           <4932> EV:H      CDirectoryServiceObject::CheckDirectoryEntry - Directory database existence check has failed. The connection to SQL Server could not be established.   The connection will be tried repeatedly until the Directory Service is stopped.   SQL Server : %1      (0xc0042198)

    420         14:00:03.761       [4304]  (DirectoryService)           <4932> EV~E      Event ID: 8600 The connection to SQL Server could not be established. |The connection will be tried repeatedly until the Directory Service is stopped. |SQL Server : CLSQL08-2\EVSILOS |

    421         14:00:03.761       [4304]  (DirectoryService)           <4932> EV:L       CADOContext::CreateConnection entry

    *******************************************************

    So EV is trying to connect to Provider=SQLOLEDB;Server=CLSQL08-2\EVSILOS is it the right instance ??

    Show the above error to your SQL DB and see if he can identify anything from SQL side.

    I hope this helps !!!

    Regards,

    A_J

  • Sox's avatar
    Sox
    Level 4
    11 years ago

    Hello A_J,

    Here we go again :),

    It's not so been long after we successfully setup backup of EV, now my DB guys give me a hedache...

    Unfortunatelly, I was read that article, but my DB admin didn't before he migrade databases...

    So, he didn't follow the proper procedure, either, he didn't consult with me before migration...

    I just hope, that the database is not corrupted...

  • Sox's avatar
    Sox
    Level 4
    11 years ago

    Hello Tony,

     

    I got Event ID error 8600:

    The connection to SQL Server could not be established.

    The connection will be tried repeatedly until the Directory Service is stopped.

    SQL Server : SQLSERVER\DBinstance

  • Sox's avatar
    Sox
    Level 4
    11 years ago

    Just one info,

    I don't know does it matter, but now, databases on SQL cluster (2 nodes), migrated from single SQL server.

  • Sox's avatar
    Sox
    Level 4
    11 years ago

    And when I try to open VAC I got error:

    "Could not connect to the Enterprise Vault Directory on 'EV Server'

    Check that 'EV Server' is available on the network and that the Enterprise Vault Directory Service is running."

     

    And also, all services are started, but I cannot connect which is really confusing.

  • GertjanA's avatar
    GertjanA
    Moderator
    11 years ago

    Sox,

    You need to verify that all the steps as outlined by AJ have been executed properly. The possible reason you cannot connect using the console is because the directory service is unable to connect to the database. It might very well be that if you check the eventviewer on the EV-server you are trying to connect to, you see events indicating the directory service is trying to connect to the database. YOu probably do not see an event indicating that the directory service started properly.

    What I would do is stop all ev-services, and then only start the admin and directory service. You then need to get an event stating "directory service started succesfully". when that is ok, try connecting using the console.

    If that works, start the other services, verify they all start successfully.

  • Sox's avatar
    Sox
    Level 4
    11 years ago

    Hello GertjanA,

    As I mentioned, my DB admin didn't follow procedure from article that A_J provide me, when it comes from steps 1 - 4..

    Can I still follow further procedure from that article (steps 5 - 6)?

     

    Just to mention, what You propose didn't work. I still cannot connect to console.

     

    Another quiestion:

    If nothing help, can we run setup of EV again, with "repair" function?

  • Sox's avatar
    Sox
    Level 4
    11 years ago

    I have update:

    1. Even though I cannot start EV admin console, and even if all services are started, I connect to SQL enterprise studio on new SQL server and check with Activity monitor, I can see that connections to SQL are established to EV databases

    2. What I've noticed on EV server is a numeruos DCOM errors in system log which point to CLSID and APPID for EV Directory Service, and it recurse every few seconds:

    The application-specific permission settings do not grant Remote Launch permission for the COM Server application with CLSID

    {F4D3EB5B-C7C5-11D1-90DB-0000F879BE6A}

    and APPID

    {95DCB63F-C982-11D1-90E0-0000F879BE6A}

    to the user domain\evservice SID (User SID) from address 'EV Server IP address'. This security permission can be modified using the Component Services administrative tool.

    - And if I search in Component Services adminstrative tool, I don't see Enterprise Vault Directory Service component:

     

    I found it in registry, but from permissions point of view, all permissions are ok (administrators - full control, users - read)

    I don't know if that is the reason why console won't open.

     

  • A_J1's avatar
    A_J1
    Level 6
    11 years ago

    Hello Sox,

     

    Can I still follow further procedure from that article (steps 5 - 6)? -- Yes you have to.

    About the Dcom error you can search with the name DirectoryService and you should find it

    check the screenshot.

    Untitled picture.png

    After that if issue still persists, Please follow the below steps.

    1.Stop all EV Services

    2. Enable Dtrace from command line (Follow article:http://www.symantec.com/docs/TECH38122 )

    You need to enable dtrace on following process

    DirectoryService

    MMC

    AdminService

    AuthServer

    3. Once Dtrace is enabled on the above process

    4. Start the Admin Service followed by Directory Service.

    5. Don't start any other EV Services.

    6. Now try to open the console. (to reproduce the issue)

    7. Stop the Dtrace

    Please upload the Dtrace so that we can analyze and find out the the root cause.

     

    Regards,

    A_J