No Document exists with Version '722ccdc5-5a4d-45bb-a67e-de5ea13bf212'
I have a process which imports data from Sales Force and creates nodes in Umbraco. Just recently the import process keeps failing with the exception "No Document exists with Version '722ccdc5-5a4d-45bb-a67e-de5ea13bf212'.
The point at which this fails is when I try to instatiate a new document as follows:
var doc = new Document(e.NodeId);
I've checked the database and the there is a record with that version id for the node I am trying to instatiate so any ideas as to why the error may be thrown and how to overcome it would be appreciated.
I've been down that route, and in actual fact have to use that method on more occasions than I like but what it doesn't explain is how the nodes came ot be orphaned in the first place. They were dynamically created as part of the same process which later tries to instatiate them again later on. It makes very little sense.
Oh and in case it's of relevance if I skip over the exception the node listed by running the orphaned nodes query then subsequently disappears from the query result and is no longer an orphan. It's a strange one for sure.
No Document exists with Version '722ccdc5-5a4d-45bb-a67e-de5ea13bf212'
I have a process which imports data from Sales Force and creates nodes in Umbraco. Just recently the import process keeps failing with the exception "No Document exists with Version '722ccdc5-5a4d-45bb-a67e-de5ea13bf212'.
The point at which this fails is when I try to instatiate a new document as follows:
I've checked the database and the there is a record with that version id for the node I am trying to instatiate so any ideas as to why the error may be thrown and how to overcome it would be appreciated.
Thanks
Umbraco version 4.11.4
Does this this help?
http://www.simonantony.net/knowledge-base/articles/no-document-exists-with-version-umbraco-error/
I've been down that route, and in actual fact have to use that method on more occasions than I like but what it doesn't explain is how the nodes came ot be orphaned in the first place. They were dynamically created as part of the same process which later tries to instatiate them again later on. It makes very little sense.
Oh and in case it's of relevance if I skip over the exception the node listed by running the orphaned nodes query then subsequently disappears from the query result and is no longer an orphan. It's a strange one for sure.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.