Can not creat Site collection in wss 3 release version

Can not creat Site collection in wss 3 release version

• cherriesh

  Hello--

  We have the same problem with setting up wss 3 in AD mode. We got the following error:

  Event Type: Error
  Event Source: Windows SharePoint Services 3
  Event Category: Topology
  Event ID: 6141
  Date: 7/17/2007
  Time: 21:24:55
  User: N/A
  Computer: XXXXXX
  Description:
  The site / could not be created. The following exception occured: There is no such object on the server. (Exception from HRESULT: 0x80072030).

  For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

  Reading this forum made us think that we set up our Organizational Unit (OU) in a wrong place (we did under in-built Domain Controllers). When we set up it under our main domain and repeated all Delegation tasks described in the forum, we thought that we had to reinstall wss 3 again (not again!). But to our big surprise when we applied (again) the command STSADM.EXE -o createsite -url http://VirtualServer -title "SiteName" -sitetemplate sts#0 -owneremail "UserEmail" -ownername "DOMAIN\username", it worked. The site was created and it was able to create new user accounts via email (under Add User).

  We hpe this will help,

  Mark and Eugene

  
  

• Vlad Iliescu

  Hi! ArifMahmood

  Thanx for the reply....

  Yes, I came across sharepoint Ver 2.0 documentation and came to know all about this...

  Still there is no documentation regarding sharepoint 3.0 :(

  When i use the following command

  stsadm -o createsite -url http://servername -owneremail you@domain.com -sitetemplate sts#0

  it display error that you will first have to upgrade your server use UpdateFarmCredentials

  when i try to use UpdateFarmCredentials it says you can not upgrade this farm :(

  What to do

  why can things work with just installation and go to admin console..

  rather that doing all this R&D and getting to roadblocks one after another.......

  
  
  

• kins_z

  Thanks JBenisek for pointing out Account Creation mode and Domain Controller issue. You are correct that it can be setup. At the same time I believe it would help in the long run to stay away from setting up an application in a way that is not supported. If nothing else, you feel left out when trying to find a resolution to a problem because not many people would have set it up in a non-supported way. Anyhow here are some more thoughts about troubleshooting further (assuming you are not running WSS v3 on Domain Controller, pls let me know if you are).

  1. Make sure your service account used for Web Application isn't locked out or need a new password You should set "Password Never Expires" for this account. The easiest thing to check if the account doesnt require password change etc. is to try to login to a machine using this account. Once you are sure the account is good,
  2. Use Central Administration to specify the password for the application pool service account. Go to Central Administration | Opertions | Service Accounts.
  3. Make sure this service account is given "dbcreator" and "securityadmin" roles in SQL.
  4. Make sure this service account is delegated required rights at the OU. To rule this out, test with giving Domain Admin rights to this account OR use Delegate Control wizard in ADUC to give Full Control to the OU.
  5. Make sure this service account is member of local Administrators group.
  6. Make sure this service account has "Local Launch" and "Local Activation" right to "IIS WAMREG admin Service" application within DCOM Config. Go to Start | Run | dcomcnfg | expand Computers | My Computer | DCOM Config | right click IIS WAMREG admin Service and go to Properties | Security | click Edit in Launch and Activation permissions and select the service account. Make sure it has Local Activation and Local Launch set to "Allow".
  7. If you are running SQL 2005, Enable "TCP/IP and named pipes" for Remote Connections for SQL. You can do this from SQL Server 2005 Surface Area Configuration under Database Engine | Remote Connections. Select "Local and remote connections and choose "Using both TCP/IP and named pipes.

  On a side note;

  1. Argueably, it will help you not to install WSS v3 on the failed installations OR when you had to uninstall and reinstall WSS v3 on the same machine.
  2. The things above a more a like a sanity check to ensure you have a good WSS 3 installation. Obviously there are a lot more steps you have to take to setup from scratch. I am listing some things that cause common pain...

  
  

• BrinaD1

  I have the same problem,

  on the admin site I get "The page cannot be displayed because your server's current configuration does not support it. To perform this task, use the command line operations in Stsadm.exe."

  on the STSadm tool I tried:

  C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN>stsadm -o createsite -url "http://saturno/" -title "Team Site" -owneremail "administrator@xpto.pt" -ownerlogin "xpto\administrator"

  And get a error again, this time:

  There is no such object on the server. (Exception from HRESULT: 0x80072030)

  
  

• Raj127799

  before you install WSS, try deleting the default web site and the default application pool. Course 5060 WSS says in Mod 3 on page 4 in the Best Practice that you should do that because the default app pool does not work properly- doesn't say why though.
  

• Jasocl

  hi all..

  today i found that when i click on Central Administration > Application Management >

  Self-Service Site Management

  this also shows same error that

  "This page cannot be displayed your current system condiguration dosent support it."

  but if i delete all the sites from Sharepoint then all these links work only difference is that i do not have any site to configure, as when i creat any site all these links says your current config dosent support.....

  Please can someone help me.......

  thanx

  
  
  

• Grayson Peddie

  There are some consideration when setting WSS 3 in Account Creation mode.
  1. You cannot run Account Created Mode with WSS 3 is setup on Domain Controller
  2. You should get SMTP working in order to receive UserID & Password for the site owner. I dont think you will be able to create a site if the site creation process can't send the email. You can always use Active Directory Users and Computers to reset the password and use that to login.
  3. You have to use stsadm to create site in Account Creation mode such as "stsadm -o createsite -url http://servername -owneremail you@domain.com -sitetemplate sts#0"
  4. You should enable Basic Authentication for the Web Application in order to login from a non-domain member machine (like over the internet). By default Integrated Authentication using Kerberos is enabled.

  Let me know if I can help more.

  Arif

  
  

• globemast

  Hmm... Well I got this, I'm doing everything one 1 server, because it's all the client has and I'm doing Account Creation Mode too.

  However, I've got past this to where I don't get an error. However, when I go to the site I get a 404 error. I think because I havn't selected a template to use anywhere. However, I'm not sure how to do that and can't find any support docs on it.

  I couldn't get past this until I did this. http://support.microsoft.com/ kbid=828813&FR=1

  I was getting a can't find domain error because I didn't use the right domain syntexs. however this seems to have got me the past where you are. I would atleast read it.

  If anyone know the stsadm commands to get me past the 404 error that would help. When I look at the site in the iis manager everything looks good other then there is no default.aspx.

  
  
  

• Struan

  Everyone with this problem,

  I have lots to say. However, I did this a while ago and was working on many things to try and get this to work.

  1st - It is not true that this will not work on an ADC, I know this because I have a company up and running with 1 server running in Active Directory Account Creation Mode on v3. I also know this because Microsoft themselves say you can do it. It's just not supported. Re-read the v2 info. You will not find anything major about this in v3 because it's been downgraded and will not be in v4. Because of security issues and other problems they now want you to use a diffrent kind of account create which I have been trying to read up on. The sql server as I have read can do it or you can use 3 other forms of account management for v3. I think all allow the same usage as Account Creation mode. However, I don't know how to do these so I did it the old way. :-)

  My Setup:

  Dell 1800 - Windows 2003 R2 | SQL 2005 Express w/mangement studio (a must)

  Problems I had when doing all of this and things to check:

  Make sure you are using the netbios Domain Name when setting up the Account Creation Mode, Make sure your use the right SQL server name. Express uses servername/sqlexpress or something like that. Verify the account used for the Application pool has rights to the OU and SQL you can always check this in the how to's for Account Creation Mode in v2 or review the links below. Make sure you create a new Application Pool each time you try. I had to use my Domain Admin acccount to get this all to work.

  Note to the people that say to delete the all IIS sites before reinstalling sharepoint v3. I have install and reinstall a good 10 times never deleted the Default site as it has my Exchange OWA information in it and I still got it all to work.

  I never followed every step as I was never in the same place as these websites and other people are. Take the how to's from where you are at and try them. Verify like I'm sure you have that you did the previous step as they say. I didn't find one great how to the made it all work but you must do this in CMD.

  Most the steps here seem to work for AD Creation

  http://www.sharepointu.com/forums/Configuring_WSS_in_AD_Account_Creation_Mode/m_8407/tm.htm

  Domain not found solution was the NETbios name. I think I had to use the server name not the servername.local or whatever you have. This also applies when doing this on your exchange server outgoing mail server is servername NOT "mail.servername.com, servername.local..." Side note, when install this solution on an Exchange server you can not us the incoming mail system. Sharepoint can not get mail because the Exchange Server has already installed an SMTP connector.

  http://www.kbalertz.com/828813/Domain.Exist.Could.Error.Message.Extend.Virtual.Server.Windows.SharePoint.Services.aspx

  Other thoughts while I'm just giving them out here.

  I have spaces in my Domain Administrators password. When I got this to work I used a freshly creation domain admin account with a password with no spaces. In some of these cmd's you put in you are required to put the account username and password in. If there is a space it will error out. I did try "domain password" however I still had problems and do not know if this is a good syntex command with "" I don't think so.

  When I did get it working, I didn't do anything special my problems were syntex based not magic. Make sure you review what options there are for each command you are using and verify you don't need to add more flags or information to the command I beleave this was my problem. However, finding the right options took me weeks. Microsoft has a list of all commands for version 3 and their syntex I would review them for each command you are doing.

  If you would like more help I would be more then happy to try and help out. Please email me at jb@dontpanic.biz and I will try and give you more information.

  
  
  

• okiebugmv

  As an update for those trying this. I will be uninstall and reinstall this solution for a duel login setup of Domain and Form Based. I have setup a test site and I like the features and setup of the Form Basic setup much better.

  I have setup a site with self registration and forgotten password options. Great solution.

  
  
  

• Zadoras

  HI.. Jbenisek

  I am now trying the same...

  All setup on One Server but its a Domain Controler.. Windows 2003

  and I get struck on the same point "Create Site collection ".. error : "This page cannot be displayed your current condiguration dosent support it."

  But i wonder why beta version works fine and not the release version on the same setup

  am the only one who is getting this error on 5 different servers (Both 2003 and 2003 R2) on 3 diff places

  I am knocked out...

  can somebody please ... please...... guide me where i am going wrong

  Steps i follow

  1) Windows 2003 Installed

  2) IIS installed

  3) Domain Controler Created

  4) Sql 2005 server installed

  5) Framwork 3 Installed

  6) Sharepoint Services 3.0 Release version installed

  I even tried first "dcpromo" after that installing IIS but SAME error..

  What i guess is that siomething is to be done with IIS setings..... as before creating any sharepoint site the "Create site Collection" works fine but as i dont have any site created the site selection dropdown is Blank..

  After i create sharepoint site and go to Create site collection... I get Error.. "This page cannot be displayed your current condiguration dosent support it.".......

  Please someone Help me..

  thanx

  
  
  

• igor_22

  hi ....Jbenisek
  

  You have writen that you got same error  but  now have passed this error

   

  can you please let me know how did you pass this error... what did you do that this error dissapeared..

   

  Please let  me know as i am still struck on this error only...

   

  Thanx

   

  
  
  

• Developer Dan

  Hi gary999

  Thanx for the reply...

  I tried it..

  1) Deleating Default App Pool

  2) Deleting Default Site ..

  3) then Installing WSS 3 Release Version

  But Now the problem is that....

  before creating any site in sharepoint... I can access Create Site collection with no errors

  but as soon as i creat a site in sharepoint...

  The error returns and i am not able access "Create Site collection ".. error : "This page cannot be displayed your current condiguration dosent support it."

  If i delete the site in sharepoint then again i am able to access "Create Site collection ",

  so the error occurs only after the site creation and before that it works and after deleating it works....

  any hints or pointers....

  Thanx

  
  
  
• Can not creat Site collection in wss 3 release version