The obvious thing I can think about it that scheduled tasks run every minute, did you check umbracoSettings.config to see if there's enabled scheduled tasks.

Hi Sebastiaan...

Hmmm, is it possible to disable scheduled tasks in general?

The only scheduled task which is enabled is the CMSImporter - i have commented this one out now but the warning is still beeing logged.

Commenting out is enough, make sure to recycle the app pool after that.

All scheduled tasks are commented out - app pool recycled and site restartet - unfortunately no luck there, the warning is still all over the place :(

Same issue here. On 6.1.6 no scheduled tasks. 

CMSImport is probably running it's own scheduled tasks that might be giving you this warning.

Hi Sebastiaan, we're not using cmsimport on our website :-)

I'm seeing the same thing in a 6.1.6 site, too - the Trace Log is full of warnings:

"Couldn't find any page with nodeId=0. This is most likely caused by the page not being published" logged by Umbraco.Web.Routing.DefaultUrlProvider

I don't have any scheduled tasks, either, nor is CmsImport installed.

I had this issue on a site just now.
Dunno if it's related to you guys' problems, but it was due to an orphaned internal link in an RTE field.
It pointed to a deleted document, but actually had empty content and a correct link before it, so it was a bit hard to spot. :)

For instance:

<p>RTE field with <a href="#">Orphaned link</a></p>

would log an entry that it can't find the URL to nodeId=1234.

I found it by querying for the node ID in the cmsPropertyData table

select * from cmspropertydata where datantext like '%1234%'

And of course, the reason it appears at regular intervals, and different intervals for each of us is that it's logged every time somebody opens a page where it's used. In our case, it was in the main layout of the site. :)

Have you guys figured this out? I am too seeing quite a number of entries in TraceLog with same error message on a 6.2.1 installation.

I have a LOT of ids so I didnt really try Lars' approach to search for orphaned node ids, and hoping there is a more straightforward fix.

No schedulers, no CMSimport etc, Plain Vanilla install.

Would appreciate if you can share your findings!

Me too! v6.2.2

Also getting 99% cpu utilization periodically on the app_pool! arrggh!

Just a note - even if you don't have any scheduled tasks, Umbraco will run the scheduled publish "cron job" exactly every minute (this is what checks if you have any pages that have set the future publish date GetContentForRelease() on ContentService and publishes them). So if you have any log items that occur every minute it is likely to do with this.

Hi Dan

Thanks for the pointer. It does make sense to have that running for scheduled publish.

However none of the users use that, and judging by the number of ids listed its unlikely thats causing that many entries in trace log with the nodeid not found err.

I am also experiencing hundreds of these logs

2014-10-18 04:36:41,126 [9] WARN  Umbraco.Web.Routing.DefaultUrlProvider - [Thread 96] Couldn't find any page with nodeId=-1. This is most likely caused by the page not being published.

Our site is periodically experiencing 100% CPU utilization and taking down the site. When the site goes down, we see this error:

2014-10-23 21:31:52,843 [10] ERROR umbraco.presentation.publishingService - [Thread 12] Error executing scheduled publishing
System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.) ---> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean& marsCapable)
   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
   at System.Data.SqlClient.SqlConnection.Open()
   at Umbraco.Core.Persistence.FaultHandling.RetryPolicy.<>c__DisplayClass1.<ExecuteAction>b__0()
   at Umbraco.Core.Persistence.FaultHandling.RetryPolicy.ExecuteAction[TResult](Func`1 func)
   at Umbraco.Core.Persistence.Database.OpenSharedConnection()
   at Umbraco.Core.Persistence.Database.<Query>d__1c`1.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Umbraco.Core.Persistence.Repositories.ContentRepository.<PerformGetByQuery>d__24.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
   at umbraco.presentation.publishingService.CheckPublishing(Object sender)
ClientConnectionId:16446269-6db8-4852-b58d-911242821f3b

I'm not certain that the 100% CPU utilization is a related to the mass warning logs, but the fact that martin griffiths posted previously that he had seen the logs and 99% CPU utilization, I thought that maybe there was a relationship. Does anyone have any insight?

This is an umbraco 7.1.4 site. Recycling the app pool solves the problem.

Thanks

Not sure if it is related, but there was a fix oin 7.1.6 and 6.2.3 for Umbraco using loads of memory - http://umbraco.com/follow-us/blog-archive/2014/10/2/umbraco-717-and-623-saving-you-loads-of-memory - maybe related?

A bit late here maybe, but I found a deleted and unpublished node in the recycle bin with a contentNodeID corresponding to my logged error.

is working on a reply...