CommitChanges() - Warning: Node d not committed or rolled back at start of commit - Are these warning permanent

09-15-04, 01:06 PM

Angus Logan

Hi All,

I had some strange JavaScript on my page that was breaking the second
postback (I think) from the authoring page when saving.

My event log has about 10-15 items with "CommitChanges() - Warning: Node d
not committed or rolled back at start of commit.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp."

I have now fixed the dodgy JS that was preventing the save to complete;

Do I need to clean my MCMS database as I am looking at exporting the channel
structure & content and moving it into test (i.e.. will this issue be
propagated by site deployment?)

Regards

09-15-04, 01:13 PM

Stefan [MSFT]

Hi Angus,

No. The cleanup is done using background processing.
Export will always only contain the commited and approved content.

Cheers,
Stefan.

09-15-04, 01:28 PM

Angus Logan

Thanks.

Similar Threads
CommitChanges() - Warning: Node d not committed or rolled back at start of commit. There is always an error in the event viewer after users approve or decline pages. CommitChanges() - Warning: Node d not committed or rolled back at start of commit. Any...
The server cache gets freed up with a possible warning from CommitChanges ... Greeting! We are using server Cache for our MCMS web application. We are refreshing the cache when it is required. But once in a while the cache gets freed up in the...
CommitChanges() warning In my event viewer, I am noticing a lot of warnings where it says: CommitChanges() - Warning: Node -<number> not synchronized at start of commit. This warning is duplicated...
CommitChanges() warning Hi, I am copying and updating pages using some VBScript. When I check the event log I get the error: CommitChanges() - Warning: Node 18166 not synchronized at start of...
NCompassResolution CommitChanges() - Warning: Node xxxx not synchronized at start of commit. I'm getting an odd warning appearing in the event log. It crops up so often it's filling up my event log every day! Strangely enough, it doesn't actually seem to be causing...