I'm installing the Self Service Portal (Beta 2) on its own server. The install gets through to the "Configuring registry settings" step and fails with the following error:
"An error occured while executing a custom action:CreateMOMRegKey.4F63A3C7_CEC3_4397_9A35_DFB0B17966E5"
This is on a brand new VM running Win2k8 Standard. I've installed Forefront Client Security, the IIS components mentioned in the Deployment Guide and .Net 3.5 SP1 so far.

Any idea on how to get by this?

FCS installs a MOM agent which may interfere with the installation of Service Manager components.  Please try uninstalling FCS and then install the portal.

I tried uninstalling FCS via the Control Panel and then re-ran setup. I received the same error. Next I reinstalled the OS and did not install FCS this time. I re-ran setup and still experienced the same error.

Any other ideas?

I should also note that when I installed FCS I had specified the /nomom switch.

Hi,

I also receive the metioned error. I am running the installation on a clean machine with only IIS and neccesary components installed. Unfortunatly I receive the mentioned error.

I have 2 machines one is hosting SCSM perfectly the other machine should host SCSMPortal:81.
In the setup of the portal everything is applied correctly it sees the database etc.
I noticed that the setup does a roll back of the installation after giving: "An error occured while executing a custom action:CreateMOMRegKey.4F63A3C7_CEC3_4397_9A35_DFB0B17966E5".
But it only removes the directory in wwwroot. In IIS the appliction pool and Website still exist.

anyone?

regards,
Robin Turpijn

Is user who runs Portal setup belongs to SM Administrators or not?

And can you send us setup log files located under %homedrive%\%homepath%\appdata\local\Temp (maybe in subfolder 1 or 2) at SCSMBeta*AT*live.com? In the body of the mail, please add a link to this thread and ask that it be forwarded to Oleksandr Golovatyi.

Thanks,
Oleksandr

Can you send us setup log files located under %homedrive%\%homepath%\appdata\local\Temp (maybe in subfolder 1 or 2) at SCSMBeta*AT*live.com? In the body of the mail, please add a link to this thread and ask that it be forwarded to Oleksandr Golovatyi.

Thanks,
Oleksandr

This happens anytime there is a connection issue with the SM server, regardless of whether it is caused by permissions issues or latency issues (we have repro'd this in both conditions). The likeliest cause is that the account you are logged on as while installing the Portal does not have the permissions that it needs to have. Please make sure that the account you are installing Portal with meets this list of criteria:

• Must be a local admin on the Portal, SM Management Server, and SQL Server 2008 boxes
• Must have sysadmin permissions on SQL Server 2008
• Must be the account specified as the Operational Services account when installing Service Manager (You can check what this is by going to Administration->Run As Accounts in the Service Manager Console)

Please make sure the installing user meets all these conditions and re-attempt installation. If it still does not work, let us know. :)

You can also try restarting the following services before running the portal setup.

1. System Center Management Configuration (omcfg).
2. System Center Data Access Service (omsdk).

I figured I'd try the easy solution first so I tried restarting the services as mentioned. Unfortunately that did not help. I next tried Dustin's suggestions. I gave the Operational Services account sysadmin permissions on the SQL Server (which is installed on the SM Management server). I also made it a local administrator on the IIS server. It was already a local admin on the SM Management Server. I ran setup again but no dice. I'm still receiving the same error.

And, just to be certain, you were actually logged into the box as the Operational Services account when you tried installing this time?

• Proposed as answer by Ronny de Jong Thursday, October 15, 2009 11:19 AM
• Unproposed as answer by mdriscoll Thursday, October 15, 2009 1:04 PM

I've solved this issue by installing the SCOM R2 client. After I'd installed the client the setup of the Self Service Webportal went wel.

Regards,
Ronny.

Yes, I was.

I tried installing the SCOM R2 client. Unfortunately that did not solve the problem.

Do you still have that problem?

Hi,

just been having this same problem, I also had a problem wherea remote console would not connect. Checked everything suggested in here and everything was fine as far as I could see. Did a bit more searching for specific errors and found a blog that said if the remote console cannot connect due to SDK service not started or initialised check the firewall on the service manager machine. Sure enough, I'd missed it.
Putting that and that reply from Dustin Hodge above "This happens anytime there is a connection issue with the SM server", I tried the install again after opening up the firewall, and low and behold it worked straight away (I did have to manually remove the site and app pool from IIS though).

Just thought I'd post this in case anyone else needs the info.

Terry.

• Marked as answer by Vladimir BakhmetyevMicrosoft employee Wednesday, December 09, 2009 9:39 PM

Yeah, it's like Terry says. During the installation of the SSP, it connects to the SCSM mgmt. server to update the registry, and if you have the local firewall active, it will block this and the installation will fail.

//Anders

I am getting the same problem. Have trawled all the blogs (seems like lots of people are having the same problem and everybody seems to have a different solution.)

Not had any luck getting this issue resolved my side though.

Windows firewall turned off on both servers.

When I looked on the Server Manager Console, there is no  "Operational Services account". Just an "Operational Database Account" and a "Workflow Account". Cannot determine how to ad an "Operational Services Account"

On the System Center Service Manager Server, make sure that the System Center Data Access Service is started. Once I started this service, my error went away and I was able to install successfully.