developer
1612 Topics404 error downloading file versions via CSOM (SharePoint 2013 On-Prem)
I need to download historical versions of a document from a SharePoint 2013 On Premises document library using a C# console application, so I can migrate them chronologically to SharePoint Online along with their column properties. While downloading the current latest version works perfectly, downloading older historical versions always fails. Standard CSOM methods fail because ListItem.Versions does not exist in the SharePoint 2013 v15 SDK. Reverting to direct HTTP endpoints consistently throws an error. Here is the exact exception message I receive: System.Net.Http.HttpRequestException: Response status code does not indicate success: 404 (Not Found). Below is the minimal reproducible code example demonstrating how the connection is initialized, how properties are loaded, and where the download fails on historical versions: using System; using System.IO; using System.Net.Http; using Microsoft.SharePoint.Client; using SP = Microsoft.SharePoint.Client; class Program { static void Main() { string siteUrl = "https://example.com"; using (ClientContext sourceCtx = new ClientContext(siteUrl)) { sourceCtx.Credentials = System.Net.CredentialCache.DefaultCredentials; List sourceList = sourceCtx.Web.Lists.GetByTitle("MyLibrary"); CamlQuery query = CamlQuery.CreateAllItemsQuery(); ListItemCollection items = sourceList.GetItems(query); sourceCtx.Load(items, ic => ic.Include( item => item.Id, item => item.File, item => item.File.Versions, item => item.File.ServerRelativeUrl )); sourceCtx.ExecuteQuery(); foreach (ListItem item in items) { if (item.File == null || !item.File.Exists) continue; foreach (FileVersion ver in item.File.Versions) { string absoluteVersionUrl = siteUrl.TrimEnd('/') + "/" + ver.Url.TrimStart('/'); using (var handler = new HttpClientHandler { Credentials = sourceCtx.Credentials }) using (var client = new HttpClient(handler)) { client.DefaultRequestHeaders.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f"); client.DefaultRequestHeaders.Add("User-Agent", "Mozilla/5.0"); // CRITICAL FAILURE HERE: Always throws 404 Not Found HttpResponseMessage response = client.GetAsync(absoluteVersionUrl).Result; response.EnsureSuccessStatusCode(); using (Stream fileStream = response.Content.ReadAsStreamAsync().Result) { // Upload logic to SPO goes here } } } } } } The version URL returned inside the property matches the following virtual folder layout format: _vti_history/512/Folder/Doc.docx My specific environment queries are: Why does navigating to the absolute history folder URL over an authenticated HttpClient trigger a 404 Not Found error in SharePoint 2013 on premises, even though the path token is extracted directly from the version url metadata property? Is there an alternative legacy REST endpoint routing structure or an alternative file stream extraction method available in the SharePoint 2013 (v15) SDK that allows an external client application to fetch older version binaries successfully?46Views0likes0CommentsHow to hide the Modify this view and Create View as per users available in groups
Hi All, I have classic view of SharePoint in list/libraries. I have group(for Managers). I just want want to show and hide the Create View/Modify View/Modify this view depends on users available in group. If user available in group(for Managers) then they can do anything like Create View/Modify View/Modify this view but if user is not a part of the group(for Managers) then they can not modify any Public views but the can create Personal view. Is there any way how I can achieve this functionality?145Views0likes1Commentpnp-modern-search does not work in the local SharePoint workbench
Version used 4.9.0 (SPFx 1.15.0) Describe the bug The solution works correctly when deployed using the .sppkg package in SharePoint Online, but it does not work in the local SharePoint workbench. There are two related issues: When running gulp serve, the build/runtime reports an error related to microsoft/sp-webpart-workbench/lib/api/, suggesting a failure in loading or resolving the local workbench API module. When adding the web part to the local workbench page, the web part fails to render with the following error: Error: Cannot find module './15.js' The second error appears to be related to a missing or incorrectly resolved chunk/module during bundle loading. The issue only occurs in the local workbench. The deployed .sppkg solution in SharePoint Online works correctly. Node.js version: 16.8.0 (compatible with SPFx 1.15.0). Dependencies installed via npm install without errors. To Reproduce Clone the repository Run npm install Run gulp serve Open the local SharePoint workbench Add the web part to the page Observe: Error during gulp serve related to microsoft/sp-webpart-workbench/lib/api/ Web part fails to load with Cannot find module './15.js' Expected behavior The web part should load and render correctly in the local workbench without module resolution errors. Desktop : Browser: Chrome Node.js: 16.8.0 SPFx: 1.15.051Views0likes1CommentAbility to schedule email of SharePoint post
We've started using SharePoint to create and send mass emails in our organization, but its a huge pain that I can't schedule them ahead of time to send at a specific time/date. Could you work on creating a way to schedule not just the publishing of a SharePoint news post, but when it is shared via email? That would be amazing.67Views1like2CommentsSharePoint Video Playback Quality Defaults to 480p – Horrendous
I manage multimedia training for over 600 locations and two distribution centers, supporting nearly 10,000 team members. We have made a significant investment in producing high-quality training content through professional equipment, structured scripting, and dedicated production and editing time. However, once videos are uploaded to SharePoint, the default playback quality often degrades the experience to what appears to be approximately 480p. As a result, professionally produced content can look noticeably poor on initial playback. Many of our store-level team members are not in a position to manually adjust playback settings, so the default experience matters. The source files are high resolution, but the default playback does not reflect that quality. This also creates issues when leadership reviews training content, because the playback quality can reflect poorly on the production even though the original video is clear. We moved away from third-party hosting due to ad exposure during onboarding and the need for a controlled internal platform. We are intentionally using SharePoint and Stream as part of our existing Microsoft 365 ecosystem for scalability, governance, and centralized access. Introducing additional paid hosting platforms or external streaming solutions is not a direction we are pursuing. From an enterprise training standpoint, defaulting to low-resolution playback undermines engagement and credibility. Are there plans to allow administrators to define a default playback resolution for SharePoint or Stream videos? Are there recommended encoding settings that influence the initial playback quality more reliably? Are there roadmap updates around improving adaptive streaming behavior or default resolution selection? Any guidance or insight would be appreciated.135Views0likes1CommentSharePoint List Migration to new Tenant
Hi All, I am preparing for a tenant-to-tenant migration of 60+ SharePoint lists that function as the back-end for various PowerApps. Since we are doing a staggered cutover, I need to perform an initial migration now and then run 'Delta' syncs over the next few weeks to catch new records, updates, and deletes. My primary challenge is that SharePoint's native ID column is not preserved during manual migrations (PowerShell/CSV), which will break our App logic and Lookups. How have others handled cross-tenant list synchronization at this scale? Specifically: How do you maintain record relationships and deep links when the system IDs change? What is the most efficient way to handle deltas across 60 lists without buying expensive 3rd-party migration tools? thanks, Jake160Views0likes1CommentLeave Request System in SharePoint
Hi, I need to develop a Leave Request System similar to this video, https://www.youtube.com/watch?v=5DfW8yT-4NA However, that video only shows a demo of how it works but not how to develop it. Can I know how to develop the system similar to that video step by step without any help from any 3rd party tools? As I'm totally a beginner at SharePoint? Thank you. RobElliott Adin_Calkic SteveKnutson Kerem Yuceturk John Wynne ganeshsanap ChrisWebbTech VesaJuvonen Mark-Kashman jcgonzalezmartin Dean_Gross Brent Ellis49KViews0likes13CommentsClassic SharePoint features appearing on a Modern Site
I have a modern SharePoint site, with a modern list that has never been associated with classic SharePoint features. But today, two users have experienced intermittent instances of the list appearing in the classic interface. They have not accessed this site before now so I do not believe there should be a cache issue. Does anyone know why this is happening and how it's possible when this site has no association with Classic features? They are using the same browser, same permissions across the site but sometimes the list opens in Classic mode, sometimes it opens in Modern. It also is happening in incognito mode. They are unable to use the site while in Classic Interface at all - the people pickers deny them access ("Error: Sorry, you do not have permission to query for users" and they cannot edit anything because of this error.386Views0likes2CommentsSPFx Debug Manifests Not Loading localhost - Debug Query String Not Recognised
Hi everyone, We are currently facing an issue with debugging an SPFx solution in SharePoint Online. Previously, we were able to debug our solution using the standard debug query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js However, recently this has stopped working in our development environment. Current Behaviour When we paste the debug query string into the SharePoint page URL, the page loads normally but the debug manifests are not recognised or loaded. The “Allow debug scripts” warning banner does not appear on the page as expected. Even after clicking “Load debug scripts”, the browser still does not load the debug manifests. The browser does not attempt to load https://localhost:4321/temp/build/manifests.js. Because of this, our local debug build is not injected into the page, making it impossible to debug the solution. Additional Observations There are no console errors at the moment. The issue occurs across multiple machines (Windows and Mac). Tested on multiple browsers: Microsoft Edge Google Chrome Safari The SPFx solution itself has no issues and previously worked correctly with the same debugging method. Troubleshooting Already Attempted We followed the recommended steps, including: Allowing the browser permission to access local network devices Running gulp trust-dev-cert Verifying the debug query string format Confirming the manifest path: https://localhost:4321/temp/build/manifests.js Checking browser console logs Testing with CSP parameters Allowed to run custom scripts in the site from the SharePoint Admin centre. None of these resolved the issue. Microsoft Support Response We also contacted SharePoint Technical Support through the Microsoft Service Hub, and the response we received was that this behaviour is now "by design" and that serving debug manifests through the debug query string is no longer supported. The workaround suggested by Microsoft Support was to package the solution and deploy it to test changes instead of using the debug query string. Potential Impact If this change is indeed by design, it could have a significant impact on development workflows for organisations building SPFx solutions. The ability to load debug manifests from localhost is a core part of the SPFx development and debugging process. Without it, developers would need to package and deploy the solution for every small change, which would introduce a considerable amount of additional time, effort, and overhead during development and testing. Questions Has anyone else recently experienced this issue with SPFx local debugging? Has the debugManifestsFile query string approach been deprecated or restricted in SharePoint Online? If so, what is the recommended approach for debugging SPFx solutions locally now? Any insight from the community would be greatly appreciated. Thanks.923Views3likes5Comments