Forum Discussion
.ASPX Files Now Download Instead of Launching from SharePoint
Hello all,
My organization has recently discovered an issue with .aspx files hosted on SharePoint. We've been using them to launch Storyline and Rise files so they act like web pages (like this). However, we just recently found that after reuploading the file or folder to SharePoint, SharePoint no longer opens the page. If you navigate to the .aspx file, it force-downloads the file. If you use the direct URL, you get a File Not Found error.
We suspect this is a SharePoint issue that has to do with the upload process. My IT department has asked me to check here to see if anyone else has experienced this problem, and if so, what the root cause was (e.g., Microsoft update, policy change, etc.)?
We're looking at SharePoint because:
- It happens to multiple people in multiple offices (not a computer issue).
- It happens with Chrome and Edge. Modifying the URL to add ?web=1 has no effect. Clearing cache and cookies has no effect (not a browser issue).
- I tested the "old" file to confirm it worked, then downloaded the .zip package from SP. When I reuploaded the exact same package back to SP, the file now force-downloads/is not found (so it's not the files or the Storyline version).
- I copied a file that's still working and uploaded the copy. The original opens as a web page, the copy doesn't (again, not the files).
Thanks in advance for your feedback!
54 Replies
We have multiple SharePoint Online sites and some don't have the custom scripts permission enabled due to the IT and security restrictions, hence the asp files will force download instead of open in the browser on those sites. The workaround for us is to get a site owner to upload the asp file to the SharePoint site that has the custom scripts enabled, then use the "move to" or "copy to" SharePoint feature to transfer the files to the other SharePoint sites. For some reason the permission retains, and the asp files would open in browser on all sites regardless the custom scripts permissions. Not sure if this method will continue work as the future SharePoint updates may block it, but at least it works for us now.
I have run into the same problem today and need to publish a newsletter by lunchtime! What are people doing as an alternative? The only thing I can think of is to share the link to preview the course but then it doesn't sit on our intranet like all the previous newsletters.
I'm so glad for this community - I thought the problem was just me!
Hi, We have the same issue. Our IT answered that the custom script option is disabled in Global settings as SharePoint online is cloud environment and custom scripting is restricted by ISD. If there is some workaround how to share articulate 360 content on SharePoint, please share it with us. Currently, we can't share any new content there...
Hello we are experiencing this issue as well. Would love to hear from anyone who finds a solution!
Hi all,
I run into the same issue. Unfortunately It has worked in the past. Hopefully there will be a solution soonWe are also experiencing this same issue and I'm looking forward to a solution. Thank you!
Thanks for the feedback. We're still testing exceptions on a couple of sites and waiting for confirmation. Keep your fingers crossed, please!
maybe this has to do with the problem
We have this same issue now, and what i can see is that when the owner of the site uploads (who also is a administrator) the aspx file it gets the proper string to launch the file in sharepoint: ?web=1 etc.., but if a member of the site uploads, its only a force download link for aspx files.
Dunno if this is helpful.We tried all the different permission settings on my account, without fixing the issue for myself. But for some reason my colleauge can download my aspx file and re-upload it and it works again. Still looking for why.
This doesn't work for us. My ID team are all listed as owners of the SP site and we're experiencing the same issue. :(
Thanks for the feedback, We're currently looking at a custom script setting as the possible cause of the problem: https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#to-allow-custom-script-on-other-sharepoint-sites.
We're working to see if changing the site permissions to custom script allowed to see if that solves the problem. Implementation is still in progress but this might be worth investigating.
