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.
There were no errors when setting up the Teams EOC App but when launching the app, the header information is displayed but the rest of the screen is blank (no login requested). I get the following errors in the App Service log when I reload the EOC app at the client:
2024-03-26T17:48:56 Welcome, you are now connected to log-streaming service. The default timeout is 2 hours. Change the timeout with the App Setting SCM_LOGSTREAM_TIMEOUT (in seconds).
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
@dfoelker , Thank you for reporting this.
Please open teams in browser, then open the app and share console logs and network traces which will help us to troubleshoot the issue.
Also request you to share the manifest files with us.
I was using Teams in a browser. I the information that I provided was the console log from the App Service. Is that what you are asking for? If so, I have copied it below again.
Regarding a Network Trace, are you asking for something like a WireShark capture? Please provide details.
The json files are attached.
2024-03-27T13:09:58 Welcome, you are now connected to log-streaming service. The default timeout is 2 hours. Change the timeout with the App Setting SCM_LOGSTREAM_TIMEOUT (in seconds).
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
IIS Detailed Error - 400.0 - Bad Request
HTTP Error 400.0 - Bad Request
Bad Request
Regards,
Daniel Foelker
Teams Voice Technical Specialist
Modern Work, State & Local Government
Office: Tel:+14255385442
Mobile: Tel:+16084223225
***@***.******@***.***>
***@***.***
From: v-ajaysahu ***@***.***>
Sent: Wednesday, March 27, 2024 2:50 AM
To: OfficeDev/microsoft-teams-emergency-operations-center ***@***.***>
Cc: Mention ***@***.***>; Author ***@***.***>
Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Teams EOC app screen is blank (Issue #183)
@dfoelker , Thank you for reporting this.
Please open teams in browser, then open the app and share console logs and network traces which will help us to troubleshoot the issue.
Also request you to share the manifest files with us.
-
Reply to this email directly, view it on GitHub or unsubscribe.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOS or Android.
@dfoelker , thank you for sharing the details.
However, shared content is not Console logs which we are looking for.
Here are the steps to share the console logs and network trace -
Open Teams in browser
You need to Open Developer tool using F12 key or Ctrl+Shift+i or Go to Browser Menu and More Tools and then Click on Developer Tools and keep it Open
Open TEOC application and try to replicate the issue.
Click on Console from developer tool and select everything copy it and share it.
Click on Network from developer tool click on down arrow button to export the network logs.
Yes, I did confirm the site permissions. I believe that I made some mistake when setting up the service or app. I have deleted everything and am going to try again. I hope to have time in the next couple of days to do this.
I have to say that setting this up is a cumbersome and time consuming process. It also appears to be very susceptible to mistakes. It seems to me that there should be some way to streamline this.
Regards,
Daniel Foelker
Teams Voice Technical Specialist
Modern Work, State & Local Government
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
There were no errors when setting up the Teams EOC App but when launching the app, the header information is displayed but the rest of the screen is blank (no login requested). I get the following errors in the App Service log when I reload the EOC app at the client:
2024-03-26T17:48:56 Welcome, you are now connected to log-streaming service. The default timeout is 2 hours. Change the timeout with the App Setting SCM_LOGSTREAM_TIMEOUT (in seconds). <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
HTTP Error 400.0 - Bad Request
Bad Request
@dfoelker , Thank you for reporting this. Please open teams in browser, then open the app and share console logs and network traces which will help us to troubleshoot the issue. Also request you to share the manifest files with us.
Hello.
I was using Teams in a browser. I the information that I provided was the console log from the App Service. Is that what you are asking for? If so, I have copied it below again.
Regarding a Network Trace, are you asking for something like a WireShark capture? Please provide details.
The json files are attached.
2024-03-27T13:09:58 Welcome, you are now connected to log-streaming service. The default timeout is 2 hours. Change the timeout with the App Setting SCM_LOGSTREAM_TIMEOUT (in seconds). <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
HTTP Error 400.0 - Bad Request
Bad Request
@dfoelker , thank you for sharing the details. However, shared content is not Console logs which we are looking for. Here are the steps to share the console logs and network trace -
Open Teams in browser
You need to Open Developer tool using F12 key or Ctrl+Shift+i or Go to Browser Menu and More Tools and then Click on Developer Tools and keep it Open
Open TEOC application and try to replicate the issue.
Click on Console from developer tool and select everything copy it and share it.
Click on Network from developer tool click on down arrow button to export the network logs.
And share the network logs.
And for Manifest file you should have generated it while creating Team app Package. Please share the Manifest file. https://github.com/OfficeDev/microsoft-teams-emergency-operations-center/wiki/Deployment-Guide#7-create-the-teams-app-packages
EOC Logs.zip The requested files are in the attached zip file.
Thank you.
@dfoelker , thank you for sharing the logs. We went through the logs. Here are things which we found from the logs -
Hello. Thank you for your help with this.
The SharePoint URL is: https://gov833023.sharepoint.com/sites/DWFEOCSite This is a GCC Tenant.
The permissions appear to be correct:
@dfoelker , Can you please check site permission it should be as per this link?
Hello,
Yes, I did confirm the site permissions. I believe that I made some mistake when setting up the service or app. I have deleted everything and am going to try again. I hope to have time in the next couple of days to do this.
I have to say that setting this up is a cumbersome and time consuming process. It also appears to be very susceptible to mistakes. It seems to me that there should be some way to streamline this.
Regards, Daniel Foelker Teams Voice Technical Specialist Modern Work, State & Local Government
Office: Tel:+14255385442 Mobile: Tel:+16084223225<tel:+16084223225> @.**@.>
@.***
From: v-ajaysahu @.> Sent: Wednesday, April 3, 2024 9:35 AM To: OfficeDev/microsoft-teams-emergency-operations-center @.> Cc: Mention @.>; Author @.>; Comment @.***> Subject: Re: [OfficeDev/microsoft-teams-emergency-operations-center] Teams EOC app screen is blank (Issue #183)
@dfoelkerhttps://github.com/dfoelker , Can you please check site permission it should be as per this linkhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/wiki/Deployment-Guide#1-provisioning-teoc-site?
- Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/microsoft-teams-emergency-operations-center/issues/183#issuecomment-2034800985 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZJTLWWUZEP432OZOY3KP4TY3QHRFBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2DAMZSGI2TCOBRHCSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJUGYYTKNBVGMZTPAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMRQHA4TMMBYGA3IFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI2DAMZSGI2TCOBRHCTXI4TJM5TWK4VGMNZGKYLUMU. You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
@dfoelker , We've noted your suggestion. Kindly let us know once you re-deploy.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.