Unable to run TEOC solution and still facing the same issue

[poojarajput55]

Hi @v-ajaysahu,

As discussed we are still facing the same issue while accessing the TEOC solution and still see a blank screen, Could you please have a look.

[v-ajaysahu]

@poojarajput55 , thanks for reporting issue. As discussed, please share the console logs and network traces directly here in GitHub so that we can troubleshoot this issue.

[bennyhoffj]

We are also getting this same error upon login with a blank screen other than Welcome Name. Looking at network trace (F12) in Edge using the Teams browser app I am getting a 400 error. The url I cant hit is :

https://%baseresourcename%.azurewebsites.net/sites/XXXXXX.sharepoint.com:/sites/XXXXX.sharepoint.com/sites/XXXX?$select=id

how can i securely share har file for review.

also of note: during deployment I cant find “accessTokenAcceptedVersion” in the manifest. So I could not find a way to update this from Null to 2.

@v-ajaysahu @poojarajput55

[v-ajaysahu]

@bennyhoffj , Your problem seems to be distinct from the one discussed. Typically, the error you're encountering arises from either capitalizing the Base resource name or using the full SharePoint URL instead of just the endpoint. For instance, if your TEOC site URL is 'https://example.sharepoint.com/sites/TEOCSite', you should enter 'TEOCSite' alone, not the full URL. To confirm this, please go to the Azure Resource group, select "Microsoft.template", and review your inputs. Should the problem continue, consider creating an issue for further assistance.

[poojarajput55]

TEOC.zip

Hi @v-ajaysahu

I have uploaded the logs, can you please check

[bennyhoffj]

Reviewed the input and we did have the full URL. Redeployed the application with the correct convention. However, we are experiencing the exact same problem.

F12 in edge gets a 400 status to https://xxxxx.azurewebsites.net/sites/xxx.sharepoint.com:/sites/xxx.sharepoint.com/sites/xxxxx?$select=id

From: v-ajaysahu @.> Sent: Tuesday, October 8, 2024 3:19 AM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Bennyhoff, Jeff @.>; Mention @.> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Unable to run TEOC solution and still facing the same issue (Issue #264)

You don't often get email from @.**@.>. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification

@bennyhoffjhttps://github.com/bennyhoffj , Your problem seems to be distinct from the one discussed. Typically, the error you're encountering arises from either capitalizing the Base resource name or using the full SharePoint URL instead of just the endpoint. For instance, if your TEOC site URL is 'https://example.sharepoint.com/sites/TEOCSite', you should enter 'TEOCSite' alone, not the full URL. To confirm this, please go to the Azure Resource group, select "Microsoft.template", and review your inputs. Should the problem continue, consider creating an issue for further assistance.

- Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/264#issuecomment-2399449109, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AS72UFVRDLL2JWPONP2DYULZ2OWR5AVCNFSM6AAAAABPPTLKDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJZGQ2DSMJQHE. You are receiving this because you were mentioned.Message ID: @.**@.>>

[NOTICE: This message originated outside of City of Merced -- DO NOT CLICK on links or open attachments unless you are sure the content is safe.]

---

City of Merced records, including emails, are subject to the California Public Records Act. Unless exemptions apply, this email, any attachments and any replies are subject to disclosure on request, and neither the sender nor any recipients should have any expectation of privacy regarding the contents of such communications. The City of Merced shall not be responsible for any claims, losses or damages resulting from the use of digital data that may be contained in this email.

[v-ajaysahu]

@poojarajput55 , We've successfully addressed your issue in the recent meeting. The problem arose because the Client ID: 5e3ce6c0-2b1f-4285-8d4b-75ee78787346 (Teams WebApp Client Id) wasn't added under 'Expose an API' in the App Registration. Additionally, the site was manually created with a prefix of https://example.sharepoint.com/teams/TEOCSite instead of the correct https://example.sharepoint.com/sites/TEOCSite. Now that these steps have been corrected, your issue has been resolved, and we'll be closing it. If you have any further questions, feel free to post them here.