Home Page Link
  Skip Navigation Links
   
View: 
Post
Started: 6/4/2008 2:32 PM
Picture Placeholder: Phillip Conradie
Phillip Conradie
Creating SSP with STSADM
Hi all
 
I am experiencing a very weird problem.
I create the web apps for the SSP and the mysites with host headers http://moss and http://mysites . This is a single server farm. I used the farm administrator account throughout the whole installation as a test.
 
I am trying to create an unattended installation of MOSS.
The Web applications create sucessfully but on creation of the ssp I get access denied. Here is the scripts used.
 
stsadm -o extendvs -ownerlogin "Farm admin" -owneremail user@email.com -sethostheader -url http://moss -exclusivelyusentlm -apidname "SSP - 80" -apcreatenew -apidtype configurableid -apidlogin "farm admin" -apidpwd "password"
 
As I have mentioned its the same account that was used for the entire installation.
Edited: 6/6/2008 8:49 AM
Picture: Michael O'Donovan
Michael O'Donovan
Hi,
 
Couple of points (not that they might be much help).
 
  1. It looks like your STSADM command is not going to provision an SSP, but rather provision a web application for an SSP. Remember, through the central admin web site, you create a My Site web application, then an SSP web application (like your stsadm command) and only then to provision your SSP i.e. tell it to use the My Sites Web App and the SSP Web App, and the Index server etc. etc.
  2. Is your SSP web application really called "MOSS" running on port 80, this of course is a seperate web application to a web application that hosts user WSS/MOSS sites.
  3. Running the STSADM command from the command prompt, will mean that it is executing as the person who is logged into the command prompt (machine). Maybe it is this account that is access denied.
  4. Have you looked in log files for any more detailed error messages e.g. Windows Event Log, C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Logs
  5. Maybe look at using SQL Profiler to see if the access denied is SQL perms issue. It might not be.
  6. Does this all work through the Central Admin?

Hope these pointers help in some way,

Michael

Feedback