0

I am working inside of a SharePoint 2019 server.

The following is the setup:

  • Managed Metadata Service
  • Web Application

    1. (Enterprise - My Host Site)
    2. Default Site on Port 80
    3. Site extended to include a FQDN on Port 443 (Yes the SSL cert is assigned)
  • User Profile Service

The 443 site is ran through ADFS and the claims/realm/etc has all been setup on the server. ADFS works perfectly for logging me into the SharePoint site either via NTLM or ADFS. No problems.

If I access the website via HTTP(80) the OneDrive will setup appropriately as well as MySite without any issue within 30-45 seconds. If I access the same site that WAS ALREADY setup via HTTP(80), via SSL on NTLM I can access the already provisioned site without any issue. It works and functions normally.

If I access it via SSL NTLM for the first time without provisioning it on HTTP(80) first the site will not setup, and I will still have the issue with MySites as well.

If I access it via ADFS the account is created via my UPN (this is the long term way the site will be accessed as I will be disabling NTLM). Thus I cannot pre-provision on HTTP80 as ADFS is not setup to work there. So the initial setup with the UPN will always fail.

In general anything on the 443 will fail to provision the MySites and OneDrive. Unless it has already been pre-provisioned on HTTP(80) with the same login ID.

Steps I have taken to try and resolve this:

  • Created an additional User Profile Service with the site host set to the FQDN whereas my original User Profile Service is set to the hostname of the localhost. This failed.

  • Went into the User Profile Service, into the My Sites setup. Removed all the read only rights as there was an error and added back domain users (AD and ADFS) and this still failed.

Additional error logging:

Mysite provisioning failed for user:[i:0e.t|trusted identity provider (adfs)|jreich_admin@reichnetwork.com] with correlationid:[a9f6abb9-cdb2-48af-8670-cbc46ea4aa8f] on retry attempt:[0] on queue type:[]. Error:[SiteProvisioningException: ExceptionType: SelfServiceSiteCreate InnerException: System.ArgumentException: <nativehr>0x80070057</nativehr><nativestack></nativestack>
   at Microsoft.SharePoint.Library.SPRequestInternalClass.SscCreateSite(Guid gApplicationId, String bstrUrl, String bstrServerRelativeUrl, Int32 lZone, Guid gSiteId, Guid gDatabaseId, Guid gSiteSubscriptionId, String bstrDatabaseServer, String bstrDatabaseName, String bstrDatabaseUsername, String bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32 nLCID, String bstrOwnerLogin, String bstrOwnerUserKey, String bstrOwnerName, String bstrOwnerEmail, String bstrSecondaryContactLogin, String bstrSecondaryContactUserKey, String bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean bADAccountMode, Boolean bHostHeaderIsSiteName, Int32 iDatabaseVersionMajor, Int32 iDatabaseVersionMinor, Int32 iDatabaseVersionBuild, Int32 iDatabaseVersionRevision, Int32 iSprocsVersionMajor, Int32 iSprocsVersionMinor, Int32 iSprocsVersionBuild, Int32 iSprocsVersionRevision, String bstrSiteSchemaVersion, Boolean bCreateFromMaster, String bstrDenyPermMaskGroupId, Guid gDesignPackageId, Guid gDepartmentId)
   at Microsoft.SharePoint.Library.SPRequest.SscCreateSite(Guid gApplicationId, String bstrUrl, String bstrServerRelativeUrl, Int32 lZone, Guid gSiteId, Guid gDatabaseId, Guid gSiteSubscriptionId, String bstrDatabaseServer, String bstrDatabaseName, String bstrDatabaseUsername, String bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32 nLCID, String bstrOwnerLogin, String bstrOwnerUserKey, String bstrOwnerName, String bstrOwnerEmail, String bstrSecondaryContactLogin, String bstrSecondaryContactUserKey, String bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean bADAccountMode, Boolean bHostHeaderIsSiteName, Int32 iDatabaseVersionMajor, Int32 iDatabaseVersionMinor, Int32 iDatabaseVersionBuild, Int32 iDatabaseVersionRevision, Int32 iSprocsVersionMajor, Int32 iSprocsVersionMinor, Int32 iSprocsVersionBuild, Int32 iSprocsVersionRevision, String bstrSiteSchemaVersion, Boolean bCreateFromMaster, String bstrDenyPermMaskGroupId, Guid gDesignPackageId, Guid gDepartmentId)
   at Microsoft.SharePoint.Administration.SPSiteCollection.AddInternal(SPSiteCollectionAddParameters param)
   at Microsoft.SharePoint.Administration.SPSiteCollection.Add(SPSiteCollectionAddParameters param)
   at Microsoft.SharePoint.SPSite.SelfServiceCreateSite(SPSiteCollectionAddParameters param)
   at Microsoft.Office.Server.SiteProvisioning.SiteProvisioningManager`1.<>c__DisplayClass33.<CreateSiteCore>b__32()Microsoft.Office.Server.SiteProvisioning.SiteProvisioningException: Exception of type 'Microsoft.Office.Server.SiteProvisioning.SiteProvisioningException' was thrown. ---> System.ArgumentException: <nativehr>0x80070057</nativehr><nativestack></nativestack>
   at Microsoft.SharePoint.Library.SPRequestInternalClass.SscCreateSite(Guid gApplicationId, String bstrUrl, String bstrServerRelativeUrl, Int32 lZone, Guid gSiteId, Guid gDatabaseId, Guid gSiteSubscriptionId, String bstrDatabaseServer, String bstrDatabaseName, String bstrDatabaseUsername, String bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32 nLCID, String bstrOwnerLogin, String bstrOwnerUserKey, String bstrOwnerName, String bstrOwnerEmail, String bstrSecondaryContactLogin, String bstrSecondaryContactUserKey, String bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean bADAccountMode, Boolean bHostHeaderIsSiteName, Int32 iDatabaseVersionMajor, Int32 iDatabaseVersionMinor, Int32 iDatabaseVersionBuild, Int32 iDatabaseVersionRevision, Int32 iSprocsVersionMajor, Int32 iSprocsVersionMinor, Int32 iSprocsVersionBuild, Int32 iSprocsVersionRevision, String bstrSiteSchemaVersion, Boolean bCreateFromMaster, String bstrDenyPermMaskGroupId, Guid gDesignPackageId, Guid gDepartmentId)
   at Microsoft.SharePoint.Library.SPRequest.SscCreateSite(Guid gApplicationId, String bstrUrl, String bstrServerRelativeUrl, Int32 lZone, Guid gSiteId, Guid gDatabaseId, Guid gSiteSubscriptionId, String bstrDatabaseServer, String bstrDatabaseName, String bstrDatabaseUsername, String bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32 nLCID, String bstrOwnerLogin, String bstrOwnerUserKey, String bstrOwnerName, String bstrOwnerEmail, String bstrSecondaryContactLogin, String bstrSecondaryContactUserKey, String bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean bADAccountMode, Boolean bHostHeaderIsSiteName, Int32 iDatabaseVersionMajor, Int32 iDatabaseVersionMinor, Int32 iDatabaseVersionBuild, Int32 iDatabaseVersionRevision, Int32 iSprocsVersionMajor, Int32 iSprocsVersionMinor, Int32 iSprocsVersionBuild, Int32 iSprocsVersionRevision, String bstrSiteSchemaVersion, Boolean bCreateFromMaster, String bstrDenyPermMaskGroupId, Guid gDesignPackageId, Guid gDepartmentId)
   at Microsoft.SharePoint.Administration.SPSiteCollection.AddInternal(SPSiteCollectionAddParameters param)
   at Microsoft.SharePoint.Administration.SPSiteCollection.Add(SPSiteCollectionAddParameters param)
   at Microsoft.SharePoint.SPSite.SelfServiceCreateSite(SPSiteCollectionAddParameters param)
   at Microsoft.Office.Server.SiteProvisioning.SiteProvisioningManager`1.<>c__DisplayClass33.<CreateSiteCore>b__32()
   --- End of inner exception stack trace ---
   at Microsoft.Office.Server.SiteProvisioning.SiteProvisioningManager`1.<>c__DisplayClass33.<CreateSiteCore>b__32()
   at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
   at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
   at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
   at Microsoft.Office.Server.SiteProvisioning.SiteProvisioningManager`1.CreateSiteCore(Uri absoluteUri, DateTime creationStartDateTimeUTC, Double& preProvElevatedChecksMillisec, Double& getElevatedRootSiteMillisec, Double& monitoringUpdatesMillisec)

The site /personal/jreich_admin_reichnetwork_com could not be created.  The following exception occurred: <nativehr>0x80070057</nativehr><nativestack></nativestack>.
  • Keep in mind you can continue using AD FS with a non-claims aware relying party with Kerberos configured on the Web Application. – Trevor Seward Nov 2 at 4:38
  • Interesting thought. I suppose that could potentially solve the greater issue. Unless it changes the SSL issues. I'd likely still have problems with the initial space creation from the SSL space even with Kerberos through a non-claims aware. – usdbinary Nov 3 at 21:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.