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!

HI all, We've confirmed the issue is related to what's described in the links above. Our IT group was able to implement a temporary solution that lasts for 1 day, so right now we need to ask in advance for a script to be run when we want to make an update. If you need to talk to your IT team about this, ask about delaying enforcement of the "Deny Add and Customize Pages" setting. It sounds like there are SharePoint changes coming in November of '24 that will block this workaround and require a shift to SharePoint Framework (SPFx) or an alternate solution. So now would be a great time to start engaging your SharePoint admin or IT team for planning purposes.

Hi All, I'm now facing this same issue that everyone here has been describing when publishing to sharepoint using a .aspx file. After investigating with IT and trying the solutions that many of you recommended (thank you!), nothing is working. I have a .aspx file from last year that is publishing just fine, it is the one from 2024 that is not working. When looking at this we realized it doesn't appear to be a Sharepoint issue, we can publish .aspx files just fine. Instead, we think it has to do with the export and something having changed in storyline that is impacting that. Has anyone been able to talk to someone from Articulate support about this issue? If not, does anyone know how to do that?

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.

maybe this has to do with the problem https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#to-allow-custom-script-on-onedrive-or-user-created-sites

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.

.ASPX Files Now Download Instead of Launching from SharePoint

KelleyDoyle-65e
Community Member
6 months ago
Thanks for the feedback. We're still testing exceptions on a couple of sites and waiting for confirmation. Keep your fingers crossed, please!
TaraMcLoughlin
Community Member
6 months ago
We are also experiencing this same issue and I'm looking forward to a solution. Thank you!
ManuelLienem907
Community Member
6 months ago
Hi all,

I run into the same issue. Unfortunately It has worked in the past. Hopefully there will be a solution soon
JordanChristiso
Community Member
6 months ago
Hello we are experiencing this issue as well. Would love to hear from anyone who finds a solution!
AlenaEgorova-5d
Community Member
6 months ago
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...
LenaKloos
Community Member
6 months ago
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!
DanielSantil597
Community Member
6 months ago
Hi, has anyone found any solution?

In my case past Thursday this issue started to happen after updating the index.aspx

I've been researching to try to find a solution but I haven't had any luck
TichelleBerg-d3
Community Member
6 months ago
This started happening for us on July 1. Right now, allowing custom script combined with using the Upload button in Classic view is working, but it's very cumbersome as the Upload won't upload folders, only files. Based on what I'm seeing here, perhaps we're still looking for a permanent solution.
DorjeMcKinnon
Community Member
6 months ago
Hi @KellyDoyle

Thanks for posting about this. I have a similar issue.
There is a possible work around that may work for some of the folks who end up on this thread.

With out of the box SharePoint online functionality you can create an ASPX page which redirects to another page / file / website.

In my case we have a Learning Management System (LMS) which hosts our StoryLine and RISE360 files (so we weren't storing them and trying to open them from a SharePoint library, as most people in this thread are).

In Kelly's case if you can host the Rise and StoryLine files on another site the problem becomes how to I redirect people who use the old ASPX page address to the new location?

e.g. I've got the following Rise360 page which was working but now downloads for all users: /sites/intranet/learning/security101.aspx

Because of this download problem you've moved this course to https://ourinternalserver/learning/security101.html

By adding the "link to a document" out of the box content type to the /sites/intranet/learning/ library, deleting the original security.aspx file and creating a "link to a document" file called security101 with the "document url" of https://ourinternalserver/learning/security101.html your users:

with the bookmark etc will get redirected to the course in it's new home.

SharePoint search will still find the security101.aspx file

Full details on this technique are here https://techcommunity.microsoft.com/t5/sharepoint/redirect-sharepoint-modern-page/m-p/4192276/highlight/true#M82294

It took me a while to work this out but it seems to be robust in our environment.

I hope this helps, if you have an option of another location for your Rise and StoryLine files.
IraBrown-57cd02
Community Member
6 months ago
Glad to know I'm in lots of company with regards to this issue!

I've been searching through many threads to find information on correcting this issue. It occurred around Mid-June for us, and we suspected it was just an SP Admin change that just disabled Custom scripts.

Praying we find a solution to this as we have no other space we can host our content to directly embed into our SharePoint site.