CA Service Management

  • 1.  ITAM Unable to login

    Posted Jan 08, 2019 05:16 AM

    D:\EEMSetup\EEMCertUtilities>EEMCertUtilities.exe 10.121.2.79 APM eiamadmin ca123ca4 ca123ca$
    2019-01-08 15:30:38,586 [4592] ERROR com.ca.eiam.cpoz.PozFactory - attachPoz - unable to attach

    [Attach Error: PozError, Attach Error: PozError, PE_EXCEPTION Exception, PozFactory.attach: unable to attach, PozFactory.attachPoz: error invoking iPoz.ClientAttach on ho
    Admin, APM]
    com.ca.eiam.SafeException: EE_POZERROR Repository Error ---> com.ca.eiam.cpoz.PozException: PozFactory.attach: unable to attach
    at com.ca.eiam.cpoz.PozFactory.attachPoz()
    at com.ca.eiam.SafeContext.attach(String applicationInstance, SafeSession session)
    --- End of inner exception stack trace ---
    at com.ca.eiam.SafeContext.attach(String applicationInstance, SafeSession session)
    at CA.Applications.EEMCertUtilities.EEMCertCreator.CreateEEMCertificate() in C:\Anderson2 Build\Source\SwCM\CA\Applications\CommonInstaller\ITAMWixInstaller\EEMCertUti
    ne 149
    at CA.Applications.EEMCertUtilities.EEMCertCreator.Main(String[] args) in C:\Anderson2 Build\Source\SwCM\CA\Applications\CommonInstaller\ITAMWixInstaller\EEMCertUtilit
    87
    at com.ca.eiam.SafeContext.attach(String applicationInstance, SafeSession session)
    at CA.Applications.EEMCertUtilities.EEMCertCreator.CreateEEMCertificate() in C:\Anderson2 Build\Source\SwCM\CA\Applications\CommonInstaller\ITAMWixInstaller\EEMCertUti
    ne 149
    at CA.Applications.EEMCertUtilities.EEMCertCreator.Main(String[] args) in C:\Anderson2 Build\Source\SwCM\CA\Applications\CommonInstaller\ITAMWixInstaller\EEMCertUtilit
    87

    D:\EEMSetup\EEMCertUtilities>

     

    Thanks,

    +917845144474



  • 2.  Re: ITAM Unable to login
    Best Answer

    Broadcom Employee
    Posted Jan 08, 2019 07:02 AM

    Good Afternoon.

    Please check on the following, somewhat formal kind of statement:
    This 'Community' functionality is meant for relatively simple questions&(quick)answers for CA Service Catalog.
    Looking into this one, it seems/appears that a 'quick answer' can not be made available within this community thread.
    More likely, 'investigation' and/or 'debugging' is needed to find a possible cause and solution for this.
    Therefor I need to ask you to consider to open a 'standard' case.
    Through which you can get standard, full-service and in-depth follow-up by our Support Teams.

    Thanks in advance for your understanding and kind regards, Louis.