Janette

As the site collection administrator, I created a WSS site with the correct look and feel and welcome page layout our customer wanted and saved the site as a site template. The new site coordinator of this site (different user - has full control) is now trying to create a sub site using the site template.

  1. She clicks once on the "Create" option below the "Site Actions" button.
  2. She clicks once on the "Sites and Workspaces" link below the Web Pages header on the Create page.
  3. She enters a valid Title, Description and URL name on the New SharePoint Site page.
  4. She clicks once on the "Custom" tab of the Template Selection and chooses the new site template (is the only option on the "Custom" tab).
  5. She scrolls to the bottom of the page and clicks once on the "Create" button.
  6. She immediately gets an "Error: Access Denied" error.

So we assumed nothing was created, however when she goes back to the parent site (using the "Go back to site" link on the error page), she sees a link on the Quick Launch with her new site's name. Clicking on this link opens a "Template Selection" page. She scrolls down the list of templates and sees the same site template she tried to use in the original creation, selects it and then clicks on the "OK" button. This creates the site! The only "problem" with this new site is the top navigation settings originally defined are not kept.

Can anyone help me fully understand why the original creation fails and the second one does not I have a lot of site coordinators (with full access) who will be generating sub sites (it's all about self service), however it is unacceptable to have them "create it twice" as it were.



Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

Paul Galvin

That's very weird indeed.

I'd try using stsadm to create a subsite using the template (and I'm assuming that's possible; I'm not an stsadm jockey)and see if generates a useful error.

The diagnostic log ought to contain some details too: http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DAA9B8AA!154.entry






Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

Janette

Paul,

Thank you for your response. I will try the stsadm route to see if I get an error that helps. I tried to use the diagnosgic logs and when I generated the error, the logs didn't change. I then went to the Application Event viewer to see if there was anything there and there is an error I've never seen before, however it is not from the time the user error was generated:

Could not execute the following script securityAwareness.vbs. The system cannot find the file specified.

.

I am wondering if this might be a lag issue that is causing mine.

I have also tried to utilize the "Request access" link that appears on the Access Denied page to try to figure out what "resource" the user was needing access to. That generated an e-mail requesting access to the sub site of which the user has full control. Does full control not give the user the ability to create a sub site

Thank you again and any additional suggestions are greatly appreciated.





Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

Paul Galvin

None of this is familiar to me. Let us know how it turns out. Someone else is bound to get with this and when you solve it, it will be good info for the community.






Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

NETDEV

We are experiencing the exact same problem with our MOSS 2007 setup. This doesn¡¯t happen for Site Collection Administrators, only site owners or groups that should have permissions to create sub-sites.

It seems like site owners can do everything but run into Janette¡¯s error when creating sub-sites.





Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

NETDEV

After much help from MS Support, we found that the site creation problem was coming from an invalid list template in the \TEMPLATE\SiteTemplates\SPSSITES\XML\onet.xml file. We removed the lines that referred to list template without paths. After that and an iisreset, everything worked as usual.





Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

Paul Galvin

Any idea how an invalid list template made its way into onet.xml






Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

NETDEV

We aren't sure exaclty, but it looks related to some custom site definitons that were deployed.





Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

CViera

Which lines were removed





Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

NETDEV

If you file compare the onet.xml file from a fresh MOSS installation to the one on a server having the site creation problem you will see. The added code was at the top of the file for us.





Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

brad.payne

None of the proposed solutions worked for me. But what seems to be working here is, breaking the permissions off the template, removing all users there, and assigning Authenticated Users to Full Control over the template. Even after breaking the permissions, the entry for Authenticated Users was "Limited Access" and that was grayed out, so I couldn't modify it.

I did a search for the onet.xml, and many returned, none had been modified since the installation. I may restrict that access to "Read Access" if it continues to work, but seems to be working now.





Re: SharePoint - Design and Customization MOSS 2007 Custom Site Template error on initial creation?

brad.payne

EDIT: Retraction. Problem came back. I don't have time to review the logs and look for possible causes for why the issue just came back after not showing itself for a while.

Just wanted to make people aware that this is not a solution.