Hi Kim,

Just saw Richard's tweet, and the error does look kind of familiar.

Is it possible that one of the data types on the page is build against Umbraco 4.7 and you are running a lower version of Umbraco?

Grtz

L

Hi Lennart,

No I checked that...The problem still remains.:s I also removed each package installed, but nothing improved...

grts,

Kim

Hmm though one, it does look like some kind of umbraco version mismatch.

Does the problem occur on every node you try to save or publish, or just when you try to save a specific node?

Which version of Umbraco are you running btw, and did you perform any upgrades?

Lennart,

It occurs on every node I try to save or publish.

It's an umbraco version 4.0. and the setting in IIS on the application pool is set on .NET Framework 2.0. When I took the sources on our their server and deployed them on our local server, I tried to save a node in the backend and everything worked...No errors...I have a usercontrol which is in a VS project, build on .NET Framework 3.5. I'm starting to think that the cause is this usercontrol...When I send the dll and .ascx to the client and they deployed it on their server, the problem started to occur...They also have .NET Framework 3.5 installed on their server...So I can't find a difference. :s

grts,

Kim

Sorry for the late reply.

I don't have much experience with running Umbraco on .NET framework 2, but I guess you could try and rebuild the usercontrol in .NET 2 (or at least the DLL).

It would probably be easier if you could replicate the issue on a staging/development server (same IIS version, IIS config, etc - not sure if that's feasable) because that would allow you to play around a little. 

Upgrading Umbraco might also fix the issue.

Does anyone else have an idea ?

is working on a reply...