SOLVED

Unable to create sites in on premise 2019 farm

%3CLINGO-SUB%20id%3D%22lingo-sub-1924256%22%20slang%3D%22en-US%22%3EUnable%20to%20create%20sites%20in%20on%20premise%202019%20farm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1924256%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%202019%20farm%20with%20a%20few%20site%20collections.%20I%20noticed%20a%20few%20weeks%20ago%20I%20was%20no%20longer%20able%20to%20create%20new%20site%20collections.%20I%20got%20the%20error%20msg%2C%20Sorry%2C%20something%20went%20wrong.%20I%20zipped%20up%20the%20logs%20and%20sent%20them%20to%20Microsoft.%20Three%20weeks%20later%20we%20still%20have%20no%20solution.%20Let%20me%20give%20the%20clues%20we%20do%20know.%3C%2FP%3E%3COL%3E%3CLI%3E%26nbsp%3BIf%20I%20create%20a%20new%20content%20database%20I%20can%20create%20sites%20in%20that%20database%2C%20but%20here's%20the%20kicker.%20I%20can%20only%20create%20sites%20in%20the%20new%20database%20for%20just%20a%20short%20while(we%20have%20not%20determined%20how%20long%20exactly)%3C%2FLI%3E%3CLI%3EWe%20decided%20to%20update%20the%20farm%20with%20the%20latest%20CU.%20Once%20the%20update%20was%20finished%20I%20could%20again%20create%20sites%20in%20the%20farm....%20For%20a%20short%20period%20of%20time.%3C%2FLI%3E%3CLI%3EEach%20time%20I%20attempt%20to%20create%20a%20site%20collection%20that%20fails%20I%20get%20the%20following%20errors%20in%20the%20Windows%20Server%20Application%20logs%3A%3COL%3E%3CLI%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%226141.png%22%20style%3D%22width%3A%20643px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F235580i99ABA8E90500E6CB%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%226141.png%22%20alt%3D%226141.png%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%225586.png%22%20style%3D%22width%3A%20986px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F235581iDE82A39AB8860047%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%225586.png%22%20alt%3D%225586.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3CLI%3EThe%20content%20database%20all%20check%20out%20and%20seem%20to%20be%20fine.%20In%20fact%2C%20I%20can%20move%20existing%20site%20collections%20to%20other%20existing%20content%20databases%20with%20out%20issue.%3C%2FLI%3E%3CLI%3Eexisting%20site%20collections%20can%20create%20subsites%20without%20issues.%3C%2FLI%3E%3C%2FOL%3E%3CP%3EIf%20you've%20seen%20this%20issue%20I%20would%20appreciate%20guidance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1924256%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

I have a 2019 farm with a few site collections. I noticed a few weeks ago I was no longer able to create new site collections. I got the error msg, Sorry, something went wrong. I zipped up the logs and sent them to Microsoft. Three weeks later we still have no solution. Let me give the clues we do know.

  1.  If I create a new content database I can create sites in that database, but here's the kicker. I can only create sites in the new database for just a short while(we have not determined how long exactly)
  2. We decided to update the farm with the latest CU. Once the update was finished I could again create sites in the farm.... For a short period of time.
  3. Each time I attempt to create a site collection that fails I get the following errors in the Windows Server Application logs:
    1. 6141.png5586.png
  4. The content database all check out and seem to be fine. In fact, I can move existing site collections to other existing content databases with out issue.
  5. existing site collections can create subsites without issues.

If you've seen this issue I would appreciate guidance.

1 Reply
Best Response confirmed by sterbella (Contributor)
Solution

In the end Microsoft was unable to resolve this issue. Since this was a new farm with just a handful of test and sandbox sites I then deleted all site collections, content databases and web applications and started anew. The issue is resolved, I do wish I knew what the actual cause was.