Hi, I think you should try one or more of the following things if you have not done so already.

• touching the web.config
• Republishing the entire site (from the context menu in "content")
• Recycled the application pool or restarted IIS?

If your content is still in the database one of the above "methods" should hopefully solve your problem.

Good luck

/Jan

None of the above things work.

So, more great solutions are deeply appreciated.

Someone had the same problem here: http://our.umbraco.org/forum/ourumb-dev-forum/bugs/4259-Unable-to-publish-content-into-umbracoconfig

Don't know if they solved the problem. Might be a umbraco bug?

//hundebol

Hi,

Please check, double-check and then triple-check permissions. 90% of all weird behaviour is related to permission issues.

If you are sure that all that is correct, I think you should check all nodes to see if there are any special characters in it. I've seen it happen before that 1 weird character is the cause of the xml-file not being created.

Perhaphs you can get some info about that from the umbracoLog table.

HTH,

Peter

Thanks for your help and replies, but none of the things are working.

Permissions should not change by themselves, now should they? The site has been running smoothly for half a year now. We are currently trying to restore a backup - it is of course a live site.

But what worries me is, that this thing can happen. How/why does this happen? Is it some bug in the umbraco core?

Our site runs on a virtual Windows server 2008 - might this has something do to with it?

# Peter Dijksterhuis: Where can I find the umbracoLog? In the database?

best regards/hundebol

What is the hosting environment. If you are hosting with a third party then permissions could definelty change "by themselves".

I would copy everything locally and see if I can get it working there - at least then you know if the problem is environment or application related.

Cheers

Paul

#Poul Blair: I see your point, but it's a company website, and our IT department controls our servers. It's as mentioned a virtual Microsoft Server 2008, and it pretty much takes care of itself. Why change a winning team, ay? So nobody has changed permissions or anything else on the server, that's definite.

We are working on copying a backup onto another server, to see it we can get i working again.

The real pain for me is, why this error comes. We have another Umbraco installation (same version, identical setup) running on another server. Hope this is not something that "just happens sometimes"...

is working on a reply...