Share via

Intermittent "Sorry, something went wrong" error when opening PDFs via DMSO-generated URLs without viewid in SharePoint Online — works with viewid or native navigation

Carlos Han 20 Reputation points
2026-01-22T05:47:29.9333333+00:00

Environment:

  • Product: SharePoint Online (Microsoft 365)
  • Authentication: Standard Azure AD (no Conditional Access or Sensitivity Labels configured)
  • Client Browsers: Google Chrome, Microsoft Edge, Chrome Incognito Mode
  • Affected Users: Subset of licensed users with identical permissions
  • File Type: PDF (including very small files, e.g., <10 KB)

Issue Description:

A subset of end users cannot open PDF files through DMSO-generated deep links in SharePoint Online. They encounter the generic SharePoint error:

"Sorry, something went wrong. An unexpected error has occurred."

However:

  • The same PDF files open successfully when accessed directly via the SharePoint UI.
  • Affected users can download and view the files locally using Adobe Reader.
  • Other users with identical permissions can open the same DMSO links without issue.
  • The problem occurs only with DMSO-generated URLs that omit the viewid parameter.

Troubleshooting Performed:

  1. Added viewid to the DMSO URLPDF opens successfully for affected users.
  2. Removed viewid from the SharePoint-native URLPDF still opens successfully for all users.
  3. Confirmed no Conditional Access, Sensitivity Labels, or custom policies are in place.
  4. Verified all users have identical permissions on the document and library.
  5. Issue persists across Chrome, Edge, and Incognito Mode → rules out browser extensions/cache.

Expected Behavior:

All authenticated users with read access should be able to open PDF files via a properly formed deep link — regardless of whether viewid is included — as long as they have permission to the file and the default view.

Request:

Please investigate:

  1. Why omitting viewid in externally generated URLs causes intermittent failures for specific users in SharePoint Online.
  2. Whether this is a known issue related to view resolution, authentication context, or session handling.
  3. Provide a permanent resolution (e.g., configuration guidance, service update, or best practice for deep linking).
  4. Clarify if including viewid is now a required best practice for stable deep linking in SharePoint Online.

WeCom Screenshot_20260122134652

Microsoft 365 and Office | SharePoint | Development
0 comments No comments

1 answer

Sort by: Most helpful
  1. Jayden-P 22,990 Reputation points Microsoft External Staff Moderator
    2026-01-22T10:03:38.82+00:00

    Hi @Carlos Han

    Thank you for reaching out to Microsoft Q&A forum.

    Can you please be more specific about "DMSO-generated deep links" you mentioned? Is it third-party product or any external system you integrated with SharePoint Online?

    Based on my research, in SharePoint Online, the viewid specifies a unique GUID for a document library view (e.g., the default "All Documents" view). When omitted, SharePoint should fall back to the library's default view for authenticated users with read access. However, modern SharePoint might sometimes fail to resolve this correctly due to context differences in how the URL is processed.

    I also did some testing based on this article; SharePoint URLs and the viewid query param, the view could have a different address.

    Note: Microsoft is providing this information as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

    I have created a custom view (this view called custom and it is not set as default view), the viewid stayed the same while the name on the URL changed. These two both point to the same destination despite of the difference. This might also confuse when SharePoint resolve the address.

    sites/sitename/Shared%20Documents/Forms/custom.aspx?viewid=6e852bee-b7d4-43b2-XXXXX

    sites/sitename/Shared%20Documents/Forms/AllItems.aspx?viewid=6e852bee-b7d4-43b2-XXXXX

    I also notice that your URL have different format, did you configure the format of the URL address with DMSO? The usual format would be like this:

    https://companyname.sharepoint.com/sites/sitename/Library%20Name/Document%20Name.pdf?CT=<value>&OR=ItemsView (when open in new window)

    https://companyname.sharepoint.com/sites/sitename/Library%20Name/Forms/viewname.aspx?viewid=<value>&id=<value>pdf&parent=<value> (open with in the same window, with viewid)

    After decoding your URL, it looks like this:

    https://<tenant>.sharepoint.com/_forms/default.aspx?ReturnUrl=/sites/teamdocs/_layouts/15/Authenticate.aspx? Source=/sites/teamdocs/DocLib/Forms/AllItems.aspx? Id=/sites/ 
    

    Can you give more information about this DMSO?

    In conclusion, viewid is not required but to provide a smoother and more consistent experience to end user, it is advised to include viewid in the URL.

    I hope this information helps.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.