Make a copy of the umbraco.config file (in your data folder) and delete it or just rename it. Then do the 'Republish Entire Site', it will recreate the 'cache' or XML file of all the nodes. Sometimes the file can just go weird.

Thanks Seth,

I have removed it and tried 'republishing entire site' many times, but it didn't work. When i pulish the folder, it displays number of published documents and at 400+, restarts counting from 1 again

The display number doesn´t always work. If you look at the size of you umbraco.config file does it still get bigger if the count restart from 1 again? If it is the nodes are still being published and you should probably just wait.

Publishing problems are often caused by lucene indexing, so perhaps disabling that will help

Also, in your web.config you could try to increase the

executionTimeout = "number" 

(http://msdn.microsoft.com/en-us/library/e1f13641.aspx)

Inside the httpRuntime tag.

Dan

Did you check the umbracoLog-table? There might be a clue. 

Could be corrupt data in some node/document.

Error updating item: umbraco.DataLayer.SqlHelperException: Umbraco Exception (DataLayer): SQL helper exception in ExecuteNonQuery ---> System.Data.SqlClient.SqlException: Arithmetic overflow error converting expression to data type datetime.
The statement has been terminated.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at umbraco.DataLayer.SqlHelpers.SqlServer.SqlServerHelper.ExecuteNonQuery(String commandText, SqlParameter[] parameters)
   at umbraco.DataLayer.SqlHelper`1.ExecuteNonQuery(String commandText, IParameter[] parameters)
   --- End of inner exception stack trace ---
   at umbraco.DataLayer.SqlHelper`1.ExecuteNonQuery(String commandText, IParameter[] parameters)
   at umbraco.cms.businesslogic.datatype.DefaultData.set_Value(Object value)

Looks like breaking at converting data to DateTime

Umbraco 4.0.3 has had a problem with datepicker datatypes, caused by a bug in the datalayer code.

There was a fix released that might help you out. 

Some relevant links in this post (also link to a build containing the fix):

http://our.umbraco.org/forum/templating/templates-and-document-types/5934-Date-Picker-doesn't-work

Does this problem also occur if you only publish a few nodes or maybe just the second lowest level - or only when doing a complete (re)publish?

I'm wondering if the exception can be traced to a single node, document type or data type.

- Morten

If i publish even a single page, publishing is ok but in audit trial, following message is recorded

Error removing node from umbraco index: 
'System.IO.FileNotFoundException: Could not find file 'C:\PROJECTS\XYZ\trunk\wwwroot\data\_systemUmbracoIndexDontDelete\_ze.fnm'. File name: 'C:\PROJECTS\XYZ\trunk\wwwroot\data\_systemUmbracoIndexDontDelete\_ze.fnm' at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at Lucene.Net.Store.FSIndexInput.Descriptor..ctor(FSIndexInput enclosingInstance, FileInfo file, FileAccess mode) at Lucene.Net.Store.FSIndexInput..ctor(FileInfo path) at Lucene.Net.Store.FSDirectory.OpenInput(String name) at Lucene.Net.Index.FieldInfos..ctor(Directory d, String name) at Lucene.Net.Index.SegmentReader.Initialize(SegmentInfo si) at Lucene.Net.Index.SegmentReader.Get(Directory dir, SegmentInfo si, SegmentInfos sis, Boolean closeDir, Boolean ownDir) at Lucene.Net.Index.IndexReader.AnonymousClassWith.DoBody() at Lucene.Net.Store.Lock.With.Run() at Lucene.Net.Index.IndexReader.Open(Directory directory, Boolean closeDirectory) at Lucene.Net.Index.IndexReader.Open(String path) at umbraco.cms.businesslogic.index.Indexer.RemoveNode(Int32 Id)' 

Hi Masood,

Sounds like a lucene issue, or maybe a permissions error?

Have you tried the solutions on

1. http://our.umbraco.org/forum/using/ui-questions/4030-Exception-in-audit-trail
2. http://our.umbraco.org/forum/ourumb-dev-forum/bugs/4707-Reindex-kills-my-site
3. http://our.umbraco.org/forum/ourumb-dev-forum/bugs/4259-Unable-to-publish-content-into-umbracoconfig

If I were you I'd back up the site, check the permissions, remove everything in the /data directory and republish everything.

Cheers,

Chris

Have you tried right-clicking "Content" at the top and choosing "Republish entire site" (just to get the site back up)?

When the site is running again, you can concentrate on writing an AfterPublish eventhandler that will log whether a node was published, that way, you can more easily find the node at fault.

Thanks evey one, this issue has been solved now.

Fantastic new, Masood!

Can you explain how you solved it for the next person who has a similar issue?

cheers,
doug.

hi Doug,

I have tried solutions as noted by Chris , Sebastiaan and others but not worked for me. I have unpublished & republish entire site programatically, and all looks ok but i am still concerned about speed, and umbraco.config file is also over 40MB.

thanks

Masood

is working on a reply...