search

OfficeDev / microsoft-teams-emergency-operations-center

The Microsoft Teams Emergency Operations Center (TEOC) solution template leverages the power of the Microsoft 365 platform to centralize incident response, information sharing and field communications using powerful services like Microsoft Lists, SharePoint and more.
MIT License
95 stars 40 forks source link

Updated - WebApp Does not login but Teams Work #163

Closed sanjaymittaluk closed 9 months ago

sanjaymittaluk commented 10 months ago

Hello, I have successfully deployed all the setup and configuration; however, I can open the web app via URL < it just goes round and round in a circle and does not open anything with a message saying Please Wait.

I have managed to upload the app to Teams, where it opens, but When I click on Login, it opens the login window. I try to log in, but nothing happens, And I go back to the Login Window.

https://github.com/OfficeDev/microsoft-teams-emergency-operations-center/assets/156114106/ad7d8802-55b2-4203-b9d6-30b36ba513c4

I have tried to open this in the Web Version of Teams, but it is the same.

It appears it is unable to authenticate. I have restarted the Webapp.

What can I do to log in and troubleshoot?

Thank you

sanjaymittaluk commented 10 months ago

Hello, Sorry to bother you. I found the mistake in API> I used the instructions from the Browser console and found the API name was wrong, and as soon as I updated. it started to work in Teams. However, I can not make the web app work. It is still stuck at please wait and keep on going in a circle. thank you

v-asshrirao commented 10 months ago

@sanjaymittaluk, Thank you for reporting this. Can you please open TEOC app in web version of teams and share the console logs and network trace with us for troubleshoot the issue?

sanjaymittaluk commented 10 months ago

Screenshot 2024-01-22 124219

If I open the browser version of Teams by going to teams.microsoft.com, then the App Works fine.

URL IS - azurewebsites.net/#/tab

v-asshrirao commented 10 months ago

@sanjaymittaluk, Can you please confirm is you are able to create and update incident successfully in web version of teams. And share network trace with us for further troubleshooting.

Meanwhile we will try to troubleshoot this issue from our end

sanjaymittaluk commented 10 months ago

Yes, No problem with anything else so far. I did, however, have an issue where I could not open or edit an incident, but then I removed it from the List and created it again, and it worked.

v-asshrirao commented 10 months ago

@sanjaymittaluk, Thank you for your confirmation. azurewebsites.net/#/tab URL will always show loader that is how it is designed. Can you please try creating one new incident now and confirm if it is working fine for you? In this case if everything is working fine for you we will close this issue.

sanjaymittaluk commented 10 months ago

v-asshrirao

 An error has occurred, please try to create your incident again

v-asshrirao commented 10 months ago

@sanjaymittaluk , Can you please share console logs and network trace with us for troubleshooting.

sanjaymittaluk commented 10 months ago

v-asshrirao

I have the same problem I had before, I created an incident which created after 3 attempt and now I can not open the incident or edit it and it goes on Please wait . If I delete this record from List , it will work

v-asshrirao commented 10 months ago

@sanjaymittaluk, For troubleshooting we will need logs for below scenarios.

  1. When you try to create incident and its failing.
  2. When incident created successfully after few attempts but you are not able to open it or edit it.

Can you please help us with logs and network trace for both scenarios.

sanjaymittaluk commented 10 months ago

@sanjaymittaluk, For troubleshooting we will need logs for below scenarios.

  1. When you try to create incident and its failing.
  2. When incident created successfully after few attempts but you are not able to open it or edit it.

Can you please help us with logs and network trace for both scenarios.

Screenshot 2024-01-24 155205

sanjaymittaluk commented 10 months ago

I am not sure what has happend but we can not create incident anymore and this is completely broken

v-asshrirao commented 10 months ago

@sanjaymittaluk, Can you please try to create incident and copy the logs from console in text file and share with us along with network trace. Without analysing the logs we will not be able to find the root cause and help you on this issue further.

Request you to kindly attach logs and network trace in GitHub ticket itself because we will not be able to open logs if you share over an email.

sanjaymittaluk commented 10 months ago

@sanjaymittaluk, Can you please try to create incident and copy the logs from console in text file and share with us along with network trace. Without analysing the logs we will not be able to find the root cause and help you on this issue further.

Request you to kindly attach logs and network trace in GitHub ticket itself because we will not be able to open logs if you share over an email.

teams.microsoft.com-1706115136500.txt

sanjaymittaluk commented 10 months ago

network trace in GitHub ticket

Screenshot 2024-01-24 165715

v-asshrirao commented 10 months ago

@sanjaymittaluk, Thank you for sharing the logs. We will analyse this and try to get back to you ASAP.

sanjaymittaluk commented 10 months ago

@sanjaymittaluk, Thank you for sharing the logs. We will analyse this and try to get back to you ASAP.

do you think , it could be because one of the app service is on free with 60 minutes limit ?

sanjaymittaluk commented 10 months ago

Hello, do you know if we need to do anything about an issue which is not allowing us to create an incident? I saw an update that a patch has been issued. Do you know if it's automatically applied, or do we need to update it somewhere?

v-saikirang commented 10 months ago

Hi @sanjaymittaluk,

May I know which hot fix are you referring to. The hot fix we have been waiting is not deployed yet. We will keep you posted once its deployed. Thanks.

sanjaymittaluk commented 10 months ago

the one where

Hi @sanjaymittaluk,

May I know which hot fix are you referring to. The hot fix we have been waiting is not deployed yet. We will keep you posted once its deployed. Thanks.

it is the one where we could not create a new incident

v-saikirang commented 10 months ago

Hi @sanjaymittaluk,

Yes, the Create Incident failure is happening due to an issue with a graph call and i am referring to the hot fix for the same. This is not deployed yet. We will let you know when it's ready. Thanks for your patience on this. Thanks.

sanjaymittaluk commented 10 months ago

Hi @sanjaymittaluk,

Yes, the Create Incident failure is happening due to an issue with a graph call and i am referring to the hot fix for the same. This is not deployed yet. We will let you know when it's ready. Thanks for your patience on this. Thanks.

Thank you, would it be automatic or does it require any action from us

v-saikirang commented 9 months ago

Hi @sanjaymittaluk,

Once the fix is deployed, we will share the instructions as well. Thanks.

v-asshrirao commented 9 months ago

@sanjaymittaluk, Thank you for your patience on this. We have released the hotfix for this issue. Request you to kindly sync the code by following steps mentioned in this link

If you are still facing the issue we suggest you to clear cache and try again.

sanjaymittaluk commented 9 months ago

@sanjaymittaluk, Thank you for your patience on this. We have released the hotfix for this issue. Request you to kindly sync the code by following steps mentioned in this link

If you are still facing the issue we suggest you to clear cache and try again.

You guys are Gods.. All is good now, and I can create a new Incident. So that you know, All I had to do was Click on Sync and wait. Permissions were already there.

v-asshrirao commented 9 months ago

@sanjaymittaluk,Glad to hear that it worked. We will go ahead and close this ticket now.