none
Project Server 2013 - After host header defined, WSSCreateSiteFailure RRS feed

  • Question

  • after configuring webapplication and provisioning PWA (URL: http://<server_name>:<port>/pwa), i have extended the webapp to use host header and SSL protocol. now URL become something like this https://mycompany.com/pwa 

    if users access the site using this new URL, project site creation gives an error in queue as following. in ULS logs there is nothing useful as well. and if i open/publish the same project again, it gives me an error that project site is already in use.

    once point which may can makes a difference is that security certificate for above URL is yet to be configured, and due to this users are getting this certificate error in their browser while access site. could this be a cause?

    however if users use the site using the same old URL, project site get successfully created.

    any guesses?

    General
    • CreateWssSiteContent: Creating project site failed! Project Uid=6b33f03d-b3af-e311-93fd-00155d01a359, site URL=https://epm/Projects/Project Site Teset, site name=Project Site Teset. :
      • WSSCreateSiteFailure (16400). Details: id='16400' name='WSSCreateSiteFailure' uid='0809ce4e-b3af-e311-93fd-00155d01a359' projectUID='6b33f03d-b3af-e311-93fd-00155d01a359' workspaceUrl='https://epm/Projects/Project Site Teset' projectWorkspaceName='Project Site Teset'.
    • Queue:
      • GeneralQueueJobFailed (26000) - CreateWssSite.CreateWssSiteMessage. Details: id='26000' name='GeneralQueueJobFailed' uid='0909ce4e-b3af-e311-93fd-00155d01a359' JobUID='df8efb43-b3af-e311-93fd-00155d01a359' ComputerName='191cfefc-7d92-4801-a9d5-37d90cb6465e' GroupType='CreateWssSite' MessageType='CreateWssSiteMessage' MessageId='1' Stage='' CorrelationUID='1fe97e9c-2dfa-d087-6465-e3809f2d856d'. For more details, check the ULS logs on machine 191cfefc-7d92-4801-a9d5-37d90cb6465e for entries with JobUID df8efb43-b3af-e311-93fd-00155d01a359


    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )
    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.



    • Edited by Khurram Jamshed Wednesday, March 19, 2014 11:40 PM more details
    Wednesday, March 19, 2014 11:20 PM

Answers

  • Hello,

    The error that you are seeing is quite the same as the documented error for the AAM issue but I would still try the workaround of setting the new URL as the default zone url and the shorter server name as the custom zone.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Thursday, March 20, 2014 9:01 AM
    Moderator

All replies

  • Khurram,

    not a guess.

    Project Server provisioning process will retain the URL that the PWA site was provisioned on.  So in your case the servername/pwa flavored URL.

    SharePoint may be able to provide all sorts of extra help with Web Application URL's, but these will never make it over to Project Server / PWA and certainly not in the way the provisioning retains the URL.

    The only correct way I have found for "all to be well with my PWA" is to provision on the FINAL URL you expect users to access.  This always works.

    You will also discover that the BI center area also retains the original URL and writes that into the ODC files.

    that one is correctable, but a hassle.

    Hope that helps,


    Thanks, Eric S. Pcubed

    Thursday, March 20, 2014 2:56 AM
  • Hi Eric, thanks for your reply.

    so in your opinion,i  need to re-provision PWA using host header check box selected and PWA path to be defined as: http://epm/projects ? can you please verify this if possible?

    but isnt this option is there to define host header for PWA site collection? to override web application host header? because i have a contraint in my situation that i have to use "Projects" as my PWA path name beecause its a migrated site, and when you migrate you have to stick with the same name in order for project sites to work.

    thanks.


    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )
    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.


    Thursday, March 20, 2014 6:33 AM
  • Hello,

    what patch level is the farm? There was a fix in either the March 2013 PU or April 2013 CU for creating projects sites with an alternate access mapping.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Thursday, March 20, 2014 7:52 AM
    Moderator
  • Hey Paul, good to see you mate :)

    and yea i think now we are hitting more on the target.

    patch level is 0, its a RTM version without any update. and applying any kind of patch is also not easily possible, because its one server hosting a very complex and huge SharePoint portal as well. 

    with your clue, i have got Brian's blog related to this exact issue: http://blogs.technet.com/b/projectsupport/archive/2013/01/10/project-server-2013-project-sites-alternate-access-mapping-and-themes.aspx

    here he has mentioned a workaround until we apply patch, and also quoted it as a good way of configuring.

    From Brian's Blog:

    The first would be to use the fully qualified domain name (FQDN) as the Default zone Url, and then add an Internal Url to the same Default zone for the server name – http://Project2013/.  Another option would be to set the FQDN as the Default zone Url and then add the shorter version as the Intranet zone or Custom zone.  Either of these would mean that the strings wouldn’t get confused and the site would get created.

    now in my case, assuming machine name is: ServerA, and while creating webapplication which going to host PWA site i am defining required host header assuming: epm. 

    provisioning my PWA using this web app and defing PWA path as "Project" because its a migrated site so i have to use the same name, and the URL i am going to get in the end would be: http://epm/project

    AAM is, default zone: http://<server>:<port> and intranet zone: http://epm

    is the above complying with the first option of Brian?



    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )
    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

    Thursday, March 20, 2014 8:32 AM
  • Hello,

    The error that you are seeing is quite the same as the documented error for the AAM issue but I would still try the workaround of setting the new URL as the default zone url and the shorter server name as the custom zone.

    Paul


    Paul Mather | Twitter | http://pwmather.wordpress.com | CPS

    Thursday, March 20, 2014 9:01 AM
    Moderator
  • Hi Khurram,

    yes, you need to re-provision - with my method - notwithstanding there are workarounds mentioned in this post.

    however NO, do not check the check box for host header on the Provisioning page.

    what you need to do it build your Web Application on the correct / final URL, then Provision PWA on that Web App.

    Project Server retains the origianl root web site (or the host header if you prefer) as you are seeing and these other articles confirm.  Really this is a SharePoint thing here also, as the first URL given to a new Web Application is the one it is known by.  AAM is just an Alias, not the real identity.  Project Server picks up the real URL (the original) to use.

    imo, the correct way to build out a PWA is to begin with the Web Application using the FQDN (host header) so that all the internals of SharePoint and ultimately PWA know this as the "real" URL.

    AAM's, as mentioned are a SharePoint construct, not a Project Server construct.  Sure, much of Project Server / PWA are SharePoint, but some bits are not.  To avoid all this headache you are experiencing, start with the Web Application on the final / correct host header URL.

    everything else will take care of itself from there.

    also, on the "migrated" question, that applies only to the "/PWA" portion of the full URL.

    you are free to change the SharePoint Web Application URL that your content DB is attached to.

    you can migrate from http://myfirstURL/pwa to http://mysecondURL/pwa - that's no problem.  Just keep the /pwa part the same and Provisioning will hook it all back up.

    Hope this helps,


    Thanks, Eric S. Pcubed


    • Edited by ErockP3 Thursday, March 20, 2014 2:59 PM
    Thursday, March 20, 2014 2:55 PM
  • Hello,

    i can confirm that the issues i was facing was exactly because of the reason mentioned in Brian's post. Since i was unable to apply any patch at this point in time, i applied the workaround of setting host header URL as default in AAM and other URL as intranet zone and this worked well for me.

    thanks Paul for pointing out this blog post.

    cheers.


    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )
    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

    Monday, March 24, 2014 8:44 AM
  • Hi Eric,

    thanks for your help mate.

    however ideally the configuration i have mentioned in my question should work, but as its mentioned in Brian's post that it was known issue in 2013 and is fixed through April or afterwards CUs or SP1. but workaround shared by Brian was equally helpful for me as well.

    cheers.


    Khurram Jamshed - MBA, PMP, MCTS, MCITP ( Blog, Twitter, Linkedin )
    If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

    Monday, March 24, 2014 8:46 AM
  • Khurram,

    yes, glad to see that, so exactly, that's why I always provision on the FQDN as the initial or default URL.  Just as the Brian Smith article says - "and it could even be considered that these are probably the better way to
    configure things anyway.  The first would be to use the fully qualified domain
    name (FQDN) as the Default zone Url,"

    I do this as a matter of practice and never have these issues.

    Glad to hear you are back on track...


    Thanks, Eric S. Pcubed

    Monday, March 24, 2014 3:07 PM
  • Dear All,

    I am facing the same issue, where i have configured my pwa site https://epm.company.com/Projects as my default url. here when i try to create a project, my project site gets created successfully. 

    Whereas in my intranet url http://epm/projects project site is not getting created and i am shown the error in queue jobs Project Site update failure. 

    This site was working fine for past 2-3 months. Suddenly i am facing this issue. 

    Could this be security certificate issue?

    Any help would be appreciated


    manikantan

    Thursday, June 19, 2014 7:41 PM