Forum Stats

  • 3,769,815 Users
  • 2,253,026 Discussions
  • 7,875,215 Comments

Discussions

DCOM intermittent issue FDM classic

user2134449
user2134449 Member Posts: 18 Blue Ribbon
edited Oct 13, 2015 11:56AM in EPM System Infrastructure

Over the past few months our FDM website would become unavailable intermittently.  While reviewing windows logs we find that most times DCOM errors or Complus messages suppressing duplicated DCOM messages.  We are running 11.1.2.3.500 FDM classic in a distributed topology (two FDM servers with a single File server share).  Restarting the Services or COM application does not seem to help, we usually have to restart the server.

Can someone tell me what can cause the DCOM issue with FDM?  Is there an update to the fdmFM11XG6C COM application that we should investigate?

Tagged:

Answers

  • Sh!va
    Sh!va Member Posts: 1,035
    edited Oct 13, 2015 9:47AM

    its better if you share Event viewer logs at time of issue ....So that all can able to suggest

    Cheers!

    Sh!va

  • user2134449
    user2134449 Member Posts: 18 Blue Ribbon
    edited Oct 13, 2015 11:15AM

    Log Name:      System

    Source:        Microsoft-Windows-DistributedCOM

    Date:          10/5/2015 8:32:35 PM

    Event ID:      10004

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      FDMserver2.domain.com

    Description:

    DCOM got error "1787" and was unable to logon domain\serviceaccount in order to run the server:

    {E652643D-6CC1-48AC-915D-01842B04F292}

    __________

    At the same time I also see this:

    Log Name:      Application

    Source:        Hyperion Financial Data Quality Management - Task Manager Service

    Date:          10/5/2015 8:32:35 PM

    Event ID:      0

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      FDMserver2.domain.com

    Description:

    Unable to create Load Balance Manager object!

    Configuration directory could not be located.

    Error=-2147467238 - Retrieving the COM class factory for component with CLSID {E652643D-6CC1-48AC-915D-01842B04F292} failed due to the following error: 8000401a.

    Source=TaskManagerService -    at TaskManagerService.TaskItem.fGetConfigFolder()

  • user2134449
    user2134449 Member Posts: 18 Blue Ribbon
    edited Oct 13, 2015 11:16AM

    also no other items (warnings, information events) happen at this time.  It seems as if the DCOM error happens then FDM does not recover.

  • Sh!va
    Sh!va Member Posts: 1,035
    edited Oct 13, 2015 11:56AM

    you need to check the connectivity of domain and that service account...and you can do one thing, create a session on FDM server with that service account(windows login) , see if you still get this error.

    Cheers!

    Sh!va

This discussion has been closed.