Try our conversational search powered by Generative AI!
AI OnAI Off
Problem with Page Files with site installed on Azure VM
I have cms 6 on a vm machine in azure and it is working fine. Not using a the azure storage but ordinary folider on c: for a vm based on 2012 server edition of windows. So it should work since it is a ordinary vm as any other.
Have you tried just installed a cms 6 with deployment center on the same server. could be good to test that first. If that is working you probably have an issue in your configuration, if not you have problem on server :)
Feb 12, 2016 22:02
You also have the pageFolderVirtualPathProvider attribute on the sitesettings element in Web.config that specifies what VPP to use for page files. Careful of not using default though since it will mess up upgrading to 7.5
Feb 13, 2016 1:02
Thank you all for the quick responses.
Thank you Daniel, the issue was that the pageFolderVirtualPathProvider was not correctly configured.
Feb 15, 2016 14:23
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
We successfully deployed our EPiServer website to a VM on Azure. All is working perfectly, except Page Files. When clicking on the File Manager icon, the Page Files folder is listed below the Starting Point heading instead of the Folders heading. When clicking on the Page Files directory, all the numerical folders are listed instead of displaying the content related to the currently selected page.
The same configuration works perfectly on a local, non Azure dev machine.
All 4 of our Azure environments present this problem. The VPP files are on an Azure storage, but we have also tried with the VPP folder on a local drive with the same results.
Are there any issues with Azure that we should be aware of?
How is a Page Files folder differentiated from a Global Files folder?