I'm wondering if someone can help me, I have just setup a new umbraco site (v4) and if I go to the web address www.mywebsite.com then all I get is a blank page, if I put in the URL of the homepage i.e. www.mywebsite.com/homepage.aspx then I can view the homepage but if I try and view any other pages that I have created such as www.mywebsite.com/test.aspx then I get the Umbraco page stating "No umbraco document matches the url ............."
The pages are published and even show up in an xslt menu but when I try and view them the Umbraco message says they do not exist. I have created many Umbraco sites before, is there something I have missed with this one that is causing the problem?
Sorry to jump in here...buuuut... I have the same problem, I have validated that the identity used by the app pool is Network Service. I have verified that Network service has Full control of every folder and file in the entire web site. I have ensured that all possible temp folders have full control for Network Service. I have tried Peter's delete umbraco.config, touch web.config, and republish, which worked and the file was added back, but then the problem resumed. I have used the SetACL solution suggested in another post and still no luck.
I have installed and configured more than 20 umbraco sites and have not run into this ever. Very annoying to say the least.
Go go Necro! (apologies for that but thought it might make sense to keep all of this in the same thread) ;-)
I also seem to be having a similar issue to this... all permissions seem to be set correctly, but published content (either new pages or changes to existing pages) aren't being displayed after performing a save and publish, even though I get the message from umbraco saying that it should be visible on the site.
Manually deleting the umbraco.config, touching the web.config and republishing the entire site does force the content to be displayed.
However, any changes made after the manual intervention aren't showing up until after another manual forced publish.
Any help greatly appreciated as we were due to go live next week, but content loaders aren't able to see any of the new content they're adding ;-(
MK: Yeah, I have this same problem when I publish ONE type of node in my site. It might be related to me copying it (and all of its children) from within the backend, but I can't be sure.
I noticed that when you right-click on the "Content" node and choose "Republish entire site", the umbraco.config gets regenerated and is immediately visible. It's a bit less intrusive than having to delete/recycle.
Hey Sebastiaan... thanks for the pointer, we have moved / copied a fair bit of content around so I'll see if I can narrow things down by looking at that, although the issue we're having is affecting publishing of any node - when you say backend, do you mean not within the umbraco CMS i.e. in the actual file system somewhere, as the moving / copying we've done has all been from within the Content section of the CMS?
I just tried making a change to a page and 'republishing entire site' from the content node, but that didn't seem to make the changes visible; even touching the web.config and then selecting 'republish entire site' doesn't make it visible - the only way to make any changes visible appears to be by removing the data\umbraco.config file... very strange >.<
We are trying to run this in a load balanced environment so I suspect our lack of understanding on how to configure that properly might potentially be responsible for some of the issues we're seeing. We've also just added AD integration in to the mix (we're trying to use this for our corporate intranet) so that might also be causing some conflicts too (never one for a simple life!) ;-)
My plan for now is to remove the second server and load balancing but keep the AD integration to see if we can get that playing nicely together, then work on load balancing in a test environment replicating the content from live, in parallel with a phased rollout of the intranet to staff using a single server. *crosses fingers*
Will post any updates (or more cries for help) as we find them ;-)
Should also add that the permissions on all folders (on both servers) are definitely set with sufficient rights - currently the 'Everyone' user has full access (as does Network Service)... the plan was to increase the security once we had everything working correctly....
Make sure that the IIS app pool is using Network Service, by default IIS7 is using another identity.
I think I see where your problem is now, the loadbalancing is probably doing you in. Have a look at the last few comments of this post to see why. I've never set up umbraco in a load balanced situation, but it's possible, you're going to have to Google a bit to find out how. I suppose everything should work immediately if you turn one server off.
Have had a quick read through and it does sound like a very similar issue... we are using DFS replication to synch the two servers but now even performing a recycle of config files isn't making changes display on the primary server, although they are appearing on the 'slave' server! *bangs head against a wall*
We do have a third server that we're using as a dev machine to test code changes pre-deployment to live, which is publishing fine so I might try and copy the config files across to the primary server and start again with the replication once we get publishing sorted out on there first...
Think it's possibly something to do with the way we set up the load balancing as setting <distributedCall
enable="false"> in the umbracoSettings.config seems to allow published changes to be visible on the primary server again.
The load balancing work was done by someone on the network team so I'm going to give that a try myself and see if we get a different result... we are also trying to integrate Active Directory authentication as well to view the site since it needs to be customised depending on the group that a person belongs to - both of these things (load balanced environment and AD integration) seemed to work in isolation, so I'm wondering if there's a conflict between the two somewhere, possibly the permissions of someone logged in to the site via AD doesn't then have the correct permissions set on their umbraco user account to enable them to publish? *clutches at more straws*
Will post again once I properly understand where the problem lies... ;-)
Ok, whilst I've still got a few hairs left on my head... ^^
The issue definitely seems to be down to the way we've got IIS configured to enable authentication via AD.
At present we've set IIS authentication for the default website on each of the servers to be Windows Integrated Authentication, and disabled Anonymous Authentication. If we reverse this setting, i.e. enable Anonymous Authentication, publishing across the two servers does work again, but this would then allow someone to bypass the AD authentication.
Do we need to only enable Windows Integrated Authentication on specific sub folders within the default website in IIS, if so which? Or vice-versa, i.e. simply setting the root to WIA and removing that from specific folders, if so which?
Any help greatly appreciated as I'm too young to be bald! ;-)
I think we've potentially resolved this, and I still have *some* hair left!
The guys configuring IIS on the servers for our site had kept the application pool identity set as the default NETWORK SERVICE (as per the majority of documentation / videos around here to be fair), which seemed to work fine across the load balanced servers initially.
However, once we added user authentication via AD into the mix, as far as I can tell, that meant the distributed call function couldn't access the servers cache refresher when pages were being published?
Consequently, assigning the default application pool a domain account with local admin rights to each of the servers in in the farm seems *fingers crossed* to have resolved the issue. We definitely need to tighten up the permissions we've applied so far and I've seen what seems like a good tutorial on that, but since we're deploying an intranet on our company network, it's perhaps not quite such an issue right now.
Cannot view published pages??
I'm wondering if someone can help me, I have just setup a new umbraco site (v4) and if I go to the web address www.mywebsite.com then all I get is a blank page, if I put in the URL of the homepage i.e. www.mywebsite.com/homepage.aspx then I can view the homepage but if I try and view any other pages that I have created such as www.mywebsite.com/test.aspx then I get the Umbraco page stating "No umbraco document matches the url ............."
The pages are published and even show up in an xslt menu but when I try and view them the Umbraco message says they do not exist. I have created many Umbraco sites before, is there something I have missed with this one that is causing the problem?
Very odd. Might be a problem somewhere in your web.config?
You could check the URL by going to the Content section and editing a page, on the properties tab there's the URL that is supposed to work.
That is the url I am using to try and access the page but it is not working.
And you do have a template linked to that page, right?
Anyway, check your web.config against another one, maybe the url rewriting config?
Try deleting the umbraco.config in the data-folder, touch the web.config and republish entire site.
Could be the cache isn't updated properly, above steps should fix that.
Peter
Thanks Peter,
That worked a treat.
If the problem keeps coming back, you might need to check the permissions of the data-folder.
Sorry to jump in here...buuuut... I have the same problem, I have validated that the identity used by the app pool is Network Service. I have verified that Network service has Full control of every folder and file in the entire web site. I have ensured that all possible temp folders have full control for Network Service. I have tried Peter's delete umbraco.config, touch web.config, and republish, which worked and the file was added back, but then the problem resumed. I have used the SetACL solution suggested in another post and still no luck.
I have installed and configured more than 20 umbraco sites and have not run into this ever. Very annoying to say the least.
Anyone got any suggestions?
Thanks.
Go go Necro! (apologies for that but thought it might make sense to keep all of this in the same thread) ;-)
I also seem to be having a similar issue to this... all permissions seem to be set correctly, but published content (either new pages or changes to existing pages) aren't being displayed after performing a save and publish, even though I get the message from umbraco saying that it should be visible on the site.
Manually deleting the umbraco.config, touching the web.config and republishing the entire site does force the content to be displayed.
However, any changes made after the manual intervention aren't showing up until after another manual forced publish.
Any help greatly appreciated as we were due to go live next week, but content loaders aren't able to see any of the new content they're adding ;-(
MK: Yeah, I have this same problem when I publish ONE type of node in my site. It might be related to me copying it (and all of its children) from within the backend, but I can't be sure.
I noticed that when you right-click on the "Content" node and choose "Republish entire site", the umbraco.config gets regenerated and is immediately visible. It's a bit less intrusive than having to delete/recycle.
Hope you can find a solution..
Hey Sebastiaan... thanks for the pointer, we have moved / copied a fair bit of content around so I'll see if I can narrow things down by looking at that, although the issue we're having is affecting publishing of any node - when you say backend, do you mean not within the umbraco CMS i.e. in the actual file system somewhere, as the moving / copying we've done has all been from within the Content section of the CMS?
I just tried making a change to a page and 'republishing entire site' from the content node, but that didn't seem to make the changes visible; even touching the web.config and then selecting 'republish entire site' doesn't make it visible - the only way to make any changes visible appears to be by removing the data\umbraco.config file... very strange >.<
We are trying to run this in a load balanced environment so I suspect our lack of understanding on how to configure that properly might potentially be responsible for some of the issues we're seeing. We've also just added AD integration in to the mix (we're trying to use this for our corporate intranet) so that might also be causing some conflicts too (never one for a simple life!) ;-)
My plan for now is to remove the second server and load balancing but keep the AD integration to see if we can get that playing nicely together, then work on load balancing in a test environment replicating the content from live, in parallel with a phased rollout of the intranet to staff using a single server. *crosses fingers*
Will post any updates (or more cries for help) as we find them ;-)
Should also add that the permissions on all folders (on both servers) are definitely set with sufficient rights - currently the 'Everyone' user has full access (as does Network Service)... the plan was to increase the security once we had everything working correctly....
With "backend" I do mean the CMS yes, sorry.
Make sure that the IIS app pool is using Network Service, by default IIS7 is using another identity.
I think I see where your problem is now, the loadbalancing is probably doing you in.
Have a look at the last few comments of this post to see why. I've never set up umbraco in a load balanced situation, but it's possible, you're going to have to Google a bit to find out how. I suppose everything should work immediately if you turn one server off.
Hi mate - any chance you could post that link again as it seems to have been chopped up? Was it one of these two?
Oh crap, not sure what happened there. This is the correct link!
lol - no worries ;-)
Have had a quick read through and it does sound like a very similar issue... we are using DFS replication to synch the two servers but now even performing a recycle of config files isn't making changes display on the primary server, although they are appearing on the 'slave' server! *bangs head against a wall*
We do have a third server that we're using as a dev machine to test code changes pre-deployment to live, which is publishing fine so I might try and copy the config files across to the primary server and start again with the replication once we get publishing sorted out on there first...
Thanks heaps for your help so far ;-)
Think it's possibly something to do with the way we set up the load balancing as setting <distributedCall enable="false"> in the umbracoSettings.config seems to allow published changes to be visible on the primary server again.
The load balancing work was done by someone on the network team so I'm going to give that a try myself and see if we get a different result... we are also trying to integrate Active Directory authentication as well to view the site since it needs to be customised depending on the group that a person belongs to - both of these things (load balanced environment and AD integration) seemed to work in isolation, so I'm wondering if there's a conflict between the two somewhere, possibly the permissions of someone logged in to the site via AD doesn't then have the correct permissions set on their umbraco user account to enable them to publish? *clutches at more straws*
Will post again once I properly understand where the problem lies... ;-)
Ok, whilst I've still got a few hairs left on my head... ^^
The issue definitely seems to be down to the way we've got IIS configured to enable authentication via AD.
At present we've set IIS authentication for the default website on each of the servers to be Windows Integrated Authentication, and disabled Anonymous Authentication. If we reverse this setting, i.e. enable Anonymous Authentication, publishing across the two servers does work again, but this would then allow someone to bypass the AD authentication.
Do we need to only enable Windows Integrated Authentication on specific sub folders within the default website in IIS, if so which? Or vice-versa, i.e. simply setting the root to WIA and removing that from specific folders, if so which?
Any help greatly appreciated as I'm too young to be bald! ;-)
I think we've potentially resolved this, and I still have *some* hair left!
The guys configuring IIS on the servers for our site had kept the application pool identity set as the default NETWORK SERVICE (as per the majority of documentation / videos around here to be fair), which seemed to work fine across the load balanced servers initially.
However, once we added user authentication via AD into the mix, as far as I can tell, that meant the distributed call function couldn't access the servers cache refresher when pages were being published?
Consequently, assigning the default application pool a domain account with local admin rights to each of the servers in in the farm seems *fingers crossed* to have resolved the issue. We definitely need to tighten up the permissions we've applied so far and I've seen what seems like a good tutorial on that, but since we're deploying an intranet on our company network, it's perhaps not quite such an issue right now.
;-)
is working on a reply...