【トラブルシューティング】2020 年より以前の一部のコンテンツを閲覧できない問題が発生【SV311751】

Read Time:12 Minute, 47 Second

Microsoft が提供する Microsoft 365 のサービス正常性（SV311751）にて、ユーザーが、2020 年より前に Microsoft Stream に保存された一部のコンテンツを閲覧できない問題が発生していることを発表しています。

“SV311751” のサマリー

回避方法

・影響を受けるビデオの所有者権限を持つユーザーは、ビデオを DL（ダウンロード）して、ローカルでの再生を行うことで回避できるほか、該当ビデオの再アップロードで他のユーザーがアクセスできるようにすることが可能です。

現在

・長期的な修正プログラムのデバッグ中に事象の影響の要因の一因になっているコンテンツデリバリーネットワーク（CDN）の設定に関する問題を確認
・コンテンツデリバリーネットワーク（CDN）に対する追加修正を行っており、中長期的な修正プログラムの開発が完了次第、影響を受ける環境に展開予定
・新たに影響を受けたユーザーを特定するためのスクリプトを実行し、手動による緩和策の適用
※ ～ 2022 年 2 月 7 日（月）

原因

・Microsoft Stream の URL ドメインとの互換性向上のための定期メンテナンスにリグレッションが含まれていたことにより発生
・コンテンツデリバリーネットワーク（CDN）の設定にも問題があり、本事象に影響

影響範囲

2020 年以前に Microsoft Stream に保存された一部のビデオコンテンツを視聴しようとするユーザー

A limited number of users can’t view some video content that was stored in the Microsoft Stream service before 2020 – SV311751

サービス：Microsoft Stream

状態：Extended recovery

ユーザーへの影響：Users are unable to view some video content that was stored in the Microsoft Stream service before 2020.

Microsoft 365 のサービス正常性（SV311751）にて、ユーザーが、2020 年より前に Microsoft Stream に保存された一部のコンテンツを閲覧できない問題が発生していることを発表しています。

本事象が発生しているユーザーには以下のエラーメッセージが表示されます。

“That video could not be found”

短期的な緩和策として、影響を受けるビデオの所有者権限を持つユーザーは、ビデオを DL（ダウンロード）してローカルで再生を行うことで回避できるほか、該当のビデオを再度アップロードすることで他のユーザーがアクセスできるようにすることが可能です。

現在は、長期的な修正プログラムのデバッグ中にコンテンツデリバリーネットワーク（CDN）の設定に関する問題を確認し、本事象の影響の一因となっていることを確認しているとのこと。

なお、コンテンツデリバリーネットワーク（CDN）に対する追加修正を開発しており、中長期的な修正プログラムの開発か完了次第、影響を受ける環境に展開する予定となっています。

また、新たに影響を受けたユーザーを特定するためのスクリプトを実行し、手動による緩和策を適用することで早急な復旧を図っています。

この問題は、Microsoft Stream の URL ドメインとの互換性向上のための定期メンテナンスにリグレッションが含まれていたことにより発生している問題になります。

また、コンテンツデリバリーネットワーク（CDN）の設定にも問題があり、本事象に影響しています。

この問題は、2020 年以前に Microsoft Stream に保存された一部のビデオコンテンツを視聴しようとするユーザーに限定し影響する事象になります。

January 31, 2022 3:25 PM

・Title : A limited number of users can’t view some video content that was stored in the Microsoft Stream service before 2020
・User Impact : Users are unable to view some video content that was stored in the Microsoft Stream service before 2020.
・More info : Affected users see the following error message: “That video could not be found”.
As a viable near-term mitigation option, users with owner permissions for an affected video can download the video to play it locally and re-upload to restore access for other users.
・Current status : While we were debugging the long-term fix, we identified a Content Delivery Network (CDN) configuration issue that is also contributing to the impact.
We’re developing an additional fix for this CDN issue. Once we’ve finished developing the full long-term fix, we’ll deploy it to the affected environment.
We’re also continuing to run the daily script to identify any newly impacted users and apply the manual mitigation to provide immediate relief.
・Scope of impact : This issue affects a limited number of users attempting to view some video content that was stored in the Microsoft Stream service before 2020.
・Start time : Thursday, December 23, 2021, 5:02 AM (12/22/2021, 8:02 PM UTC)
・Root cause : Routine maintenance for improving compatibility with Microsoft Stream URL domains contained a regression.
There is also a Content Delivery Network (CDN) configuration issue that is contributing to the impact.
・Next update by : Monday, February 7, 2022, 3:30 PM (6:30 AM UTC)

January 26, 2022 3:03 PM

・Title : Some users are unable to view some stored video content within the Microsoft Stream service
・User Impact : Users are unable to view some stored video content within the Microsoft Stream service.
・More info : Affected users see the following error message: “That video could not be found”.
As a viable near-term mitigation option, users with owner permissions for an affected video can download the video to play it locally and re-upload to restore access for other users.
・Current status : We’re making additional changes and debugging the long-term fix to ensure it will fully remediate the impact.
We’re also continuing to run the daily script to identify any newly impacted users and apply the manual mitigation to provide immediate relief.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view some stored video content within Microsoft Stream.
・Start time : Thursday, December 23, 2021, 5:02 AM (12/22/2021, 8:02 PM UTC)
・Root cause : Routine maintenance to the streaming infrastructure intended to improve compatibility with Microsoft Stream URL domains contained a regression that led to impact.
・Next update by : Monday, January 31, 2022, 3:30 PM (6:30 AM UTC)

January 19, 2022 1:14 PM

・Title : Some users are unable to view some stored video content within the Microsoft Stream service
・User Impact : Users are unable to view some stored video content within the Microsoft Stream service.
・More info : Affected users see the following error message: “That video could not be found”.
As a viable near-term mitigation option, users with owner permissions for an affected video can download the video to play it locally and re-upload to restore access for other users.
・Current status : We’re continuing to apply the manual mitigation method on newly impacted users to provide immediate relief, while we continue to wait for the long-term solution to be implemented.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view stored video content within Microsoft Stream.
・Start time : Thursday, December 23, 2021, 5:02 AM (12/22/2021, 8:02 PM UTC)
・Estimated time to resolve : We expect a long-term solution to be implemented to permanently resolve this issue by Monday, January 31, 2022.
・Root cause : Routine maintenance to the streaming infrastructure intended to improve compatibility with Microsoft Stream URL domains contained a regression that led to impact.
・Next update by : Wednesday, January 26, 2022, 3:30 PM (6:30 AM UTC)

January 12, 2022 2:12 PM

・Title : Some users are unable to view some stored video content within the Microsoft Stream service
・User Impact : Users are unable to view some stored video content within the Microsoft Stream service.
・More info : Affected users see the following error message: “That video could not be found”.
As a viable near-term mitigation option, users with owner permissions for an affected video can download the video to play it locally and re-upload to restore access for other users.
・Current status : We’ve identified additional impacted users and have applied the manual mitigation method to provide relief.
As we wait for the long-term fix to be in place by the end of January 2022, we’ll continue to run a daily script to identify newly impacted users and resolve their impact.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view stored video content within Microsoft Stream.
・Start time : Thursday, December 23, 2021, 5:02 AM (12/22/2021, 8:02 PM UTC)
・Estimated time to resolve : We expect a long-term solution to be implemented to permanently resolve this issue by Monday, January 31, 2022.
・Root cause : Routine maintenance to the streaming infrastructure intended to improve compatibility with Microsoft Stream URL domains contained a regression that led to impact.
・Next update by : Wednesday, January 19, 2022, 3:30 PM (6:30 AM UTC)

January 11, 2022 2:02 AM

・Title : Some users are unable to view some stored video content within the Microsoft Stream service
・User Impact : Users are unable to view some stored video content within the Microsoft Stream service.
・More info : Affected users see the following error message: “That video could not be found”.
As a viable near-term mitigation option, users with owner permissions for an affected video can download the video to play it locally and re-upload to restore access for other users.
・Current status : We’re continuing the process of manually implementing a configuration change to mitigate the issue for all known affected users.
We expect that most affected users should experience impact relief by our next update.
As we focus on the development of a long-term solution, we’re running a script daily to detect any newly identified affected users and applying the mitigation accordingly.
We estimate that the long-term solution should permanently resolve this issue by the end of January 2022.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view stored video content within Microsoft Stream.
・Start time : Thursday, December 23, 2021, 5:02 AM (12/22/2021, 8:02 PM UTC)
・Estimated time to resolve : We expect a long-term solution to be implemented to permanently resolve this issue by Monday, January 31, 2022.
・Root cause : Routine maintenance to the streaming infrastructure intended to improve compatibility with Microsoft Stream URL domains contained a regression that led to impact.
・Next update by : Wednesday, January 12, 2022, 3:30 PM (6:30 AM UTC)

January 8, 2022 10:06 AM

・Title : Some users are unable to view some stored video content within the Microsoft Stream service
・User Impact : Users are unable to view some stored video content within the Microsoft Stream service.
・More info : Users will see the following error message: “That video could not be found”.
As a viable near-term mitigation option, users with owner permissions for an affected video can download the video to play it locally and re-upload to restore access for other users.
・Current status : We’ve determined that manually implementing a configuration change is the most effective mitigation action for this issue.
We’ve started applying the to fix and users will experience remediation as the process progresses.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view stored video content within Microsoft Stream.
・Start time : Thursday, December 23, 2021, 5:02 AM (12/22/2021, 8:02 PM UTC)
・Root cause : Routine maintenance to the streaming infrastructure intended to improve compatibility with Microsoft Stream URL domains contained a regression that led to impact.
・Next update by : Tuesday, January 11, 2022, 3:00 AM (1/10/2022, 6:00 PM UTC)

January 7, 2022 10:00 AM

・Title : Some users are unable to view some stored video content within the Microsoft Stream service
・User Impact : Users are unable to view some stored video content within the Microsoft Stream service.
・More info : Users will see the following error message: “That video could not be found”.
As a viable near-term mitigation option, users with owner permissions for an affected video can download the video to play it locally and re-upload to restore access for other users.
・Current status : We’re testing a potential fix for the regression as a possible remediation step and we anticipate reviewing the results by our next update.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view stored video content within Microsoft Stream.
・Root cause : Routine maintenance to the streaming infrastructure intended to improve compatibility with Microsoft Stream URL domains contained a regression that led to impact.
・Next update by : Saturday, January 8, 2022, 11:00 AM (2:00 AM UTC)

January 6, 2022 10:21 AM

・Title : Some users are unable to view some stored video content within the Microsoft Stream service
・User Impact: Users are unable to view some stored video content within the Microsoft Stream service.
・More info : Users will see the following error message: “That video could not be found”.
As a viable near-term mitigation option, users with owner permissions for an affected video can download the video to play it locally and re-upload to restore access for other users.
・Current status : We’ve identified a viable near-term mitigation option which is described in the “More info” section.
In parallel, our analysis of infrastructure and service telemetry is ongoing to help us better understand the full scope of the issue and determine the best path toward remediation.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view stored video content within Microsoft Stream.
・Root cause : Routine maintenance to the streaming infrastructure intended to improve compatibility with Microsoft Stream URL domains contained a regression that led to impact.
・Next update by : Friday, January 7, 2022, 11:00 AM (2:00 AM UTC)

January 6, 2022 5:45 AM

・Title : Some users are unable to view some stored video content within the Microsoft Stream service
・User Impact : Users are unable to view some stored video content within the Microsoft Stream service.
・More info : Users will see the following error message: “That video could not be found”.
・Current status : After further log review, we’ve determined that a past change to the Microsoft Stream URL domain had occurred, to which a workaround was implemented so that videos coded with the old URL domain can remain accessible.
However, when this recent streaming infrastructure migration occurred, which is part of routine maintenance, the workaround code wasn’t added to the target environment, resulting in impact to the viewability of some stored video content.
We’re looking into the infrastructure and service telemetry to determine the best path toward remediation.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view stored video content within Microsoft Stream.
・Root cause : A workaround code that was implemented within the streaming infrastructure to continue supporting the old Microsoft Stream domain wasn’t added to the environment targeted during a recent migration as a part of routine maintenance, causing impact.
・Next update by : Thursday, January 6, 2022, 11:00 AM (2:00 AM UTC)

January 6, 2022 3:04 AM

・Title : Some users are unable to view stored video content within the Microsoft Stream service
・User Impact : Users are unable to view stored video content within the Microsoft Stream service.
・More info : Users will see the following error message: “That video could not be found”.
・Current status : After reviewing provided HTTP Archive format (HAR) logs, we suspect that a recent streaming infrastructure migration didn’t properly update its routing pathway to the correct Domain Name System (DNS), resulting in impact.
We’re continuing to review available logs to confirm this cause and assess potentially viable options, such as manually updating the DNS, to successfully remediate impact.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users attempting to view stored video content within Microsoft Stream.
・Next update by : Thursday, January 6, 2022, 5:30 AM (1/5/2022, 8:30 PM UTC)

January 6, 2022 12:45 AM

・Title : Some users are unable to view stored video content within the Microsoft Stream service
・User Impact : Users are unable to view stored video content within the Microsoft Stream service.
・More info : Users will see the following error message : “That video could not be found”.
・Current status : We’re reviewing details in the provided support cases to determine the source of the issue before we assess our mitigation options.
・Scope of impact : Your organization is affected by this event, and the issue impacts some users.
・Next update by : Thursday, January 6, 2022, 3:00 AM (1/5/2022, 6:00 PM UTC)

Microsoft Store をチェックするなら、このボタンをタップ

Microsoft Stream 関連記事一覧

Microsoft Stream のメッセージセンター関連情報一覧

Microsoft Stream のメッセージセンター関連記事一覧

マイクロソフトストアをチェックするなら、このボタンをタップ

Microsoft Stream サービス正常性関連記事一覧

・【トラブルシューティング】Microsoft Stream 上の一部のグループおよびビデオにアクセスできない SI（サービスインシデント）が発生【SV302438】【復旧済み】

“SV311751” のサマリー