Project Server 2013 - After host header defined, WSSCreateSiteFailure

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”.

Answer 1

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”.