This project is read-only.

Install failing at the 1st hurdle - any ideas?

May 14, 2009 at 12:11 PM

Hello All,

Trying this out without much success. Heres my scenario.

On a Virtual 2003 server installed Moos 2007 as a standalone version and have it patched upto date.

Noticed a DCOM 10016 error so followed the advice of the following to remove them:

Created a new web app with  a new app pool account that is in the machine's local admins group then created a new collaboration portal site collection on this app.

Gone to the command line and executed the SSM command and pointed it at the web app and not the site collection like the instructions say on page 6.

The install just sits there sulking with the following error in the ssm.log file:


The other thing that I have noticed is the following error on Sharepoint Operations page for 'Timer Job Status'

'Application Server Administration Service Timer Job' - Failed 100%.


I am doing the install as the local admin.


Any clues would be great.


Thanks in advance,



May 15, 2009 at 4:27 PM

Cisswalk, did you installed the MOSS service pack ?

I don't know what is the problem, but my installation worked fine under MOSS 2007 with service pack 1 and the hotfix. However, and in my opnion, if you are installing in a single server, make an complete installation, by clicking into "advanced" install, that gives you the oportunity to expand your server farm whenever you want. Standalone installs sqlexpress and don't permit you to expand your server farm.

Did you restored your site collection by a backup? Problems with timer job usually happend in this situation without service pack.

Verify the pre-requisites. or try to install in a virtual machine gave from Microsoft

Hope it help you in something

May 19, 2009 at 12:08 PM

Thanks - can someone confirm that the SSM command is indeed suposed to install to the web application or onto the site collection?




May 22, 2009 at 1:53 PM

There are folks talking about installing PKS onto a site collection that is not at the root, but that is considered an advanced option. It this is your first attempt, you probably just want to try a basic install. So, put in on the root site collection for the web app. So the url should look something like: