locked
Service MAnager Portal _CreateMOMRegKey RRS feed

  • Question

  • Dear All,

    I had to uninstall SM Portal ( to allow SCOM agent installation) and now re-installing the portal.

    However I'm stuck at the error - 

    "An error occurred while executing a custom action:_CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6"

    This was the same issue, which had occurred when installing the first time. It was due to permissions.

    However not sure, why this is recurring, as I'm re-installing with the service account with all the required permissions sorted out.

    Can Microsoft be ever bug free ?  OR is MS trying to use the public as their test agents after paying for their products?

    Can anyone help fix this issue.. I'm bugged up using the MS products.


    • Edited by i-AM-1 Thursday, May 23, 2013 10:51 AM typo corrections
    Thursday, May 23, 2013 10:50 AM

All replies

  • Are you installing it using the same account you it installed it with the first time?

    Also, here is an article that may help you - http://dougsigmon.wordpress.com/2010/05/21/sm-2010-disaster-recovery-test-the-dreaded-_createmomregkey-error-on-reinstall/

    Thursday, May 23, 2013 1:36 PM
  • Hi, Thank you for your reply.

    Yep... using the same service account to install Service Portal.

    Regarding the encryption key, I generated the key during the installation process; however, couldn't save on the shared drive (from the wizard), as I was supposed to, due to the popup 'unable to/cannot  save'.  

    Cancelled the wizard and forgot to save on the local drives aswell. So do not have the encryption keys. Would it help, generating a new one and trying the steps suggested in the link?


    Thursday, May 23, 2013 5:29 PM
  • Deleted the registry entry and tried re-installation. No go. Same error.

    Point to note- There was only one valid entry, that I could remove, which was Microsoft Operations Manager.

    There was no System Center, however was System Center Operations Manager, related to the SCOM agent installed.

    Also, tried to check the Network name property in the MTV_Computer table in the SM Database ( central db server),  as per the link below.

    http://social.technet.microsoft.com/Forums/en-US/systemcenterservicemanager/thread/09beaef2-3b04-459d-a267-5bb94620bcdd

    To my surprise, there is no entry of the SM server at all..  ( Ideally there should have been an entry here..as I had checked this before aswell  while installing the SM portal first time, as I had faced similar issue)

    Can anyone throw some light on this please.. thank you

    Friday, May 24, 2013 6:55 AM
  • Are there any entries in the event log recorded during the install?
    Friday, May 24, 2013 11:45 AM
  • Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.CreateMOMRegKey
    CreateMOMRegKey: Generating secure key for Primary SDK
    CreateMOMRegKey: Error: Exception of type 'Microsoft.EnterpriseManagement.Security.KeyNotInSyncException' was thrown.
    StackTrace:    at Microsoft.EnterpriseManagement.Security.SecureStorageManager.Initialize()
       at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.CreateMOMRegKey(Session session)
    MSI (s) (E4:50) [12:22:15:324]: NOTE: custom action _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.


    Action start 12:21:49: RegisterMIMEInfo.
    MSI (s) (E4:40) [12:21:49:857]: Doing action: WriteRegistryValues
    Action ended 12:21:49: RegisterMIMEInfo. Return value 0.
    Action start 12:21:49: WriteRegistryValues.
    MSI (s) (E4:40) [12:21:52:025]: Doing action: _Set_CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: WriteRegistryValues. Return value 1.
    MSI (s) (E4:40) [12:21:52:029]: PROPERTY CHANGE: Adding _CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6 property. Its value is 'SCSMWebContentServer 443 C:\inetpub\wwwroot\System Center Service Manager Portal\ KMDCLSCSM1003.PREKMDCLOUD.DK, OU=*, O=KMD A/S, L=*, S=*, C=DK PREKMDCLOUD2\SA_SCSP 7Rm7R6iy'.
    Action start 12:21:52: _Set_CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:029]: Doing action: _CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _Set_CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    Action start 12:21:52: _CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:112]: Doing action: _Set_CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    Action start 12:21:52: _Set_CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:117]: Doing action: _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _Set_CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    Action start 12:21:52: _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:201]: Doing action: _Set_InstallInprocSDKPerfCounters.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    MSI (s) (E4:40) [12:21:52:204]: PROPERTY CHANGE: Adding _InstallInprocSDKPerfCounters.11EE91AB_EABF_48A6_9973_4DCD73190AC6 property. Its value is 'C:\inetpub\wwwroot\System Center Service Manager Portal\ServiceHost\Bin\Microsoft.EnterpriseManagement.DataAccessService.Core.dll'.
    Action start 12:21:52: _Set_InstallInprocSDKPerfCounters.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:204]: Doing action: _InstallInprocSDKPerfCounters.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _Set_InstallInprocSDKPerfCounters.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    Action start 12:21:52: _InstallInprocSDKPerfCounters.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:288]: Doing action: _Set_RegisterAspNet4OnIIS.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _InstallInprocSDKPerfCounters.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    MSI (s) (E4:40) [12:21:52:292]: PROPERTY CHANGE: Adding _RegisterAspNet4OnIIS.11EE91AB_EABF_48A6_9973_4DCD73190AC6 property. Its value is 'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -iru'.
    Action start 12:21:52: _Set_RegisterAspNet4OnIIS.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:292]: Doing action: _RegisterAspNet4OnIIS.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _Set_RegisterAspNet4OnIIS.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    Action start 12:21:52: _RegisterAspNet4OnIIS.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:371]: Doing action: _Set_AddWCSWindowsFirewallPortException.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _RegisterAspNet4OnIIS.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    MSI (s) (E4:40) [12:21:52:375]: PROPERTY CHANGE: Adding _AddWCSWindowsFirewallPortException.11EE91AB_EABF_48A6_9973_4DCD73190AC6 property. Its value is '443 Service Manager (Web Content Server) 0'.
    Action start 12:21:52: _Set_AddWCSWindowsFirewallPortException.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:375]: Doing action: _AddWCSWindowsFirewallPortException.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _Set_AddWCSWindowsFirewallPortException.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    Action start 12:21:52: _AddWCSWindowsFirewallPortException.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:387]: Doing action: _Set_GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _AddWCSWindowsFirewallPortException.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    MSI (s) (E4:40) [12:21:52:391]: PROPERTY CHANGE: Adding _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6 property. Its value is 'PREKMDCLOUD2 SA_SCSP'.
    Action start 12:21:52: _Set_GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6.
    MSI (s) (E4:40) [12:21:52:392]: Doing action: _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6
    Action ended 12:21:52: _Set_GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6. Return value 1.
    Action start 12:21:52: _GrantLocalPermissionsToWCSAccount.11EE91AB_EABF_48A6_9973_4DCD73190AC6.


    MSI (s) (E4:2C) [12:22:08:418]: NOTE: custom action _CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
    MSI (s) (E4:40) [12:22:08:420]: Executing op: ActionStart(Name=_CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6,,)
    CreateWebSite: Saving ContentHost web config changes
    MSI (s) (E4:40) [12:22:08:453]: Executing op: CustomActionSchedule(Action=_CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6,ActionType=17409,Source=BinaryData,Target=CreateMOMRegKey,)
    MSI (s) (E4:50) [12:22:08:477]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI2C57.tmp, Entrypoint: CreateMOMRegKey
    CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI2C57.tmp-\
    CAPACK: CLR version v2.0.50727 is installed.
    CAPACK: CLR version v2.0.50727 is detected.
    CAPACK: CLR version v4.0.30319 is installed.
    CAPACK: CLR version v4.0.30319 is detected.
    CAPACK: Binding to CLR version v2.0.50727


    Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.CreateMOMRegKey
    CreateMOMRegKey: Generating secure key for Primary SDK
    CreateMOMRegKey: Error: Exception of type 'Microsoft.EnterpriseManagement.Security.KeyNotInSyncException' was thrown.
    StackTrace:    at Microsoft.EnterpriseManagement.Security.SecureStorageManager.Initialize()
       at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.CreateMOMRegKey(Session session)
    MSI (s) (E4:50) [12:22:15:324]: NOTE: custom action _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
    CustomAction _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)


    MSI (s) (E4:40) [12:22:15:493]: Executing op: ActionStart(Name=_CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6,,)
    MSI (s) (E4:40) [12:22:15:500]: Executing op: ProductInfo(ProductKey={79A76AB5-3EA0-4C4F-89B9-1CA00438EC2E},ProductName=Microsoft System Center 2012 - Service Manager,PackageName=SM.msi,Language=0,Version=117771097,Assignment=1,ObsoleteArg=0,ProductIcon=ServiceManager.ico,,PackageCode={1B3B79AF-1391-4E6E-9BE2-2BD0832DADE7},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
    MSI (s) (E4:40) [12:22:15:509]: Executing op: ActionStart(Name=_CreatePortalWebSite.11EE91AB_EABF_48A6_9973_4DCD73190AC6,Description=Creating self-service web content portal,)
    MSI (s) (E4:40) [12:22:15:516]: Executing op: ActionStart(Name=WriteRegistryValues,Description=Writing system registry values,Template=Name: [2], Value: [3])
    MSI (s) (E4:40) [12:22:15:519]: Executing op: RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\Eventlog\Operations Manager\Database Modules,,BinaryType=1,,)
    MSI (s) (E4:40) [12:22:15:523]: Executing op: RegRemoveValue(Name=EventSourceFlags,Value=#0,)
    MSI (s) (E4:40) [12:22:15:529]: Executing op: RegCreateKey()
    MSI (s) (E4:40) [12:22:15:534]: Executing op: RegRemoveValue(Name=EventMessageFile,,)
    MSI (s) (E4:40) [12:22:15:566]: Executing op: RegRemoveKey()
    MSI (s) (E4:40) [12:22:15:566]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Operations Manager\Database Modules 3: 2 
    MSI (s) (E4:40) [12:22:15:574]: Executing op: RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\Eventlog\Operations Manager\System Center Virtual Machine Manager Connector,,BinaryType=1,,)

    Friday, May 24, 2013 4:14 PM
  • Hi,  Please find the log below

    I've selected the entries, wherever  _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6 error has occurred.

    ( It's getting worse & pathetic. ) Would be greatful, if you could suggest any steps.

    (http://social.technet.microsoft.com/Forums/en-US/systemcenterservicemanager/thread/09beaef2-3b04-459d-a267-5bb94620bcdd)

    Also, I tried to verify the Network name property , as suggested in the link below; however the entry related to SM server itself was missing.

    Could this be a serious issue ?

    ( I remember seeing the entry,when I had faced the similar error; this was fixed as it was related to user permissions-  admin permission on Service Manager)

    Friday, May 24, 2013 4:19 PM
  • If you are using a SharePoint Farm you could try installing it on a different front end server. It only needs to be installed on one in the farm. 

    As far as the Network Name property, I am not familiar with that table or value, so I'm not really sure what to make of it. Hopefully, someone else on this board will be able to provide guidance on that. 

    Friday, May 24, 2013 5:49 PM
  • I ran into this same issue, after trying just about every solution in every blog, I came across an obscure post that pointed me to my solution and it turned out to be simple. On the server where the System Center Manager was installed, the stupid "System Center Data Access Manager" service was not running even though it was set to Automatic Start. This service controls the validation and creation of the encryption keys used between the servers. Once I started this service, I was able to reinstall and be on my may after wasting several days. I hope your issue could be as simple. Good luck.  

    Rick Short Senior Technical Architect

    Wednesday, May 29, 2013 1:56 PM
  • Dear All,

    Thank you for your inputs.

    All I go to do was a clean re installation with a new DB instance ( as usual this is the only thing that works with Microsoft).

    Very unhappy with MSFT. period.

    Thursday, May 30, 2013 9:59 AM
  • Hi RSII,

    Yes.. I did restarted this service- SC -Data Access Service ( along with other SM services); I made sure to restart the service on SM server, before I started the portal installation, to ensure I do not get this dreaded error. However to no avail. Hence the clean reinstallation, as mentioned above.

    Thursday, May 30, 2013 12:19 PM
  • I had face same issue before, My issue was the self-service portal Server unable to resolve the FQDN for SM Server, after Register the MS again in DNS, this issue resolved.

    Please check that you can ping FQDN for SM Management Server, if no add it in hosts file. 

    Thursday, June 6, 2013 9:10 AM
  • could you solve this problem? I have the same problem. 
    I installed Service Manager on Server1 
    I installed Data Warehouse in Server2 
    I installed the database on a SQL server, Server3 
    I am installing Portal Server4 

    But I get the error "_CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6" 

    Maybe I have to install Portal on the same server as Service Manager? What's the problem?

    Please, can you help me??

    Friday, May 23, 2014 3:34 PM
  • Make sure the port 5724 (TCP) is open against the Service Manager management Server. Then it will work.

    There is probable somewhare in your setup logfile something like this:

    CreateMOMRegKey: Error: The Data Access service is either not running or not yet initialized. Check the event log for more information.


    Richard1980




    Tuesday, June 17, 2014 6:30 PM
  • The port 5724 on the SCSM server is open/listening and there is no mention of the Data Access service in the log
    Monday, September 15, 2014 6:09 PM
  • In my case i had found that, this error related to DNS resolving of Management server/ SQL server not working,

    you can try to ping MS /SQL by Name/ FQDN and make sure it work?

    If you found that not resolved correct the problem by register MS Server in DNS , then try install again.


    Regards, Ibrahim Hamdy

    • Proposed as answer by Ibrahim.Hamdy Tuesday, September 16, 2014 8:59 PM
    Monday, September 15, 2014 7:12 PM