SOLVED

Site Provisioning - Modern Team Sites - 500 internal server error

Brass Contributor

Hi All,

 

We have implemented as site provisioning solution using Azure WebJob/Flow/PnP and it is working for ~3-4 months now. We use REST call _api/GroupSiteManager/CreateGroupEx (HTTP/1.1) to create a site and it was working nicely and created many sites so far.

 

However, we receive 500 - Internal error today suddenly and sites are not getting created. There is no change from our end and same happens in my Dev tenant as well.

 

Is there any changes from Microsoft in this area? Please guide me as our business is getting impacted as user requests for new sites are failing.

 

Thanks in advance.

 

Regards,

Vishwa

9 Replies
Hi,
We are also facing same issue from today.Have you got any solution?
Regards,
Shrinivas

Are the 500 internal server errors accompanied by a more descriptive error message?

Hi Paul Pascha,

We implemented some functionality in our project using this API. We were very happy with its performance but then suddenly, since yesterday unable to create sites and getting "500 Internal server error".

Error:

code: "-1, Microsoft.SharePoint.Client.UnknownError"

message: "Unbekannter Fehler." (Unknown Error)

 

Unfortunately, no further information is returned.

Yesterday, few POST requests were successful(around 8 PM CET) while i executed many since yesterday morning.

 

Could you be of any help in this matter?

We need to get it fixed and i did not find any other equivalent alternative to implement the same functionality.

 

Thanks,

Chitra

 

Hi Paul,

 

There isn't a much information on the error. It only shows:

Error:

code: "-1, Microsoft.SharePoint.Client.UnknownError"

message: "Unbekannter Fehler." (Unknown Error)

 

Regards,

Vishwa

Hi Paul,

 

I think we need to escalate this with Microsoft urgently as this is affecting our business :(

 

I have a call with Microsoft support engineer in another 30 minutes and hope he will direct this to the appropriate channel.

 

Regards,

Vishwa

Hi All,

 

I had a call with MS Engineer.

 

Looks like issue is identified and resolved. The REST has been updated by MS with a new CreationOptions array value. The documentation has not been updated and hence we were getting 500 error:

 

Please use below request (highlighted in Red - Basically need to pass additional CreationOptions  array field :(

 

namespace AUR.DPS.SP.StandAloneApp.Entities
{
    public class SiteRequest
    {
        public SiteRequest()
        {
           optionalParams = new OptionalParams();
        }
        public string displayName { get; set; }
        public string alias { get; set; }
        public bool isPublic { get; set; }      
        public OptionalParams optionalParams { get; set; }
    }

    public class SiteResponse
    {
        public object DocumentsUrl { get; set; }
        public object ErrorMessage { get; set; }
        public string GroupId { get; set; }
        public int SiteStatus { get; set; }
        public string SiteUrl { get; set; }
    }

    public class OptionalParams
    {
        public OptionalParams()
        {
            Owners = new List<string>();
            CreationOptions = new List<string>();
        }

        public string Description { get; set; }
        public List<string> Owners { get; set; }
        public List<string> CreationOptions { get; set; }
    }

    public class SiteAliasResponse
    {
        public string value { get; set; }
    }
}

 

Hope this helps for all

 

Regards,

Vishwa

best response confirmed by Vishwanatha Nayak (Brass Contributor)
Solution
Hi Vishwa,
Thanks for update.After changing the code as suggested by you,it started working again.

Regards,
Shrinivas

Worked for me as well. Thanks a ton Vishwa :)

Hey Shrinivas,

 

Are yo facing any new issues as we started to face a strange one - https://techcommunity.microsoft.com/t5/SharePoint-Developer/Modern-Team-Site-Creation-Error-Suddenly...

 

Just wondering if you face the same.

 

Regards,

Vishwa

1 best response

Accepted Solutions
best response confirmed by Vishwanatha Nayak (Brass Contributor)
Solution
Hi Vishwa,
Thanks for update.After changing the code as suggested by you,it started working again.

Regards,
Shrinivas

View solution in original post