Multiple Different Errors Upon Reserialization of Configured Items about unicorn

[demisx]

+1 Same issue.

[kamsar]

What Sitecore version is this on?

[demisx]

@kamsar 7.5

[kamsar]

Hmm, the first error might be caused by an antivirus or other filesystem-watching program locking files as Unicorn messes with them. I have not seen it before; but then I also have not tested it with 7.5 (I skipped directly to 8). Might try deleting the item tree in windows explorer, so that Unicorn doesn't have to clear them out before reserializing.

As to the second error, the stack trace jumps down into Sitecore's serialization API. The stack within Unicorn is pretty defensive (e.g. we're asserting that we're not passing any nulls to BuildSyncItem). Seems like it might be a bug in 7.5's serialization APIs not present in 8.x, or there might be something unique about the item you're trying to serialize. (That said I have a site where I keep the whole master and core stock DBs under Unicorn, so it sees a lot of unique things)

[BovineEnthusiast]

@kamsar Hi, we ended up fixing the issues and I think that they might have been initially caused by some problematic items in our database. We had initially tried serializing using the default <include /> paths. We had a massive database and, as I later realized, some items that were possibly corrupt. These items claimed to have children and if you were to try opening them it would say they didn't exist. Trying to package or serialize them caused errors. I think that upon trying to serialize these items, which were included in the default configuration we used, Unicorn started to stumble into issues. I think this also may have corrupted our database somehow as the errors started appearing after that.

We recently reset the database but this time limited the <include /> paths to only items that we were adding/modifying. It now works without issue.

Thanks.

[kamsar]

Good to hear.