Microsoft Dynamics NAV (Archived)

Scary error message about dead and livings during Sync-NAVTenant. Upgrading from 2013R2 to 2018

(2) Share

Report

Posted on by Ghetz

2,997

So I wonder who had the idea to code this error message:

"A dead connection cannot be brought back to the livings" .. like seriously? wdf dude!

Anyway, I've restarted my NAV Services and SQL Server several times. Everytime I run this, it's working for about 1 hours, and then I get this error. Dunno if anyone has seen this before:

Sync-NAVTenant -ServerInstance  DynamicsNAV110 -Mode ForceSync

*This post is locked for comments

All responses (3)

Answers (0)

Community member 2 on at

Like (0)

Report

Scary error message about dead and livings during Sync-NAVTenant. Upgrading from 2013R2 to 2018

Hi @Ghetz,

Hope you are doing well.

I was wondering if you were able to resolve this by increasing the SQL command timeout?

I know it's a weird request but who knew that 6years later I would face the same error
Suggested answer

Alexander Ermakov 28,094 on at

Like (0)

Report

RE: Scary error message about dead and livings during Sync-NAVTenant. Upgrading from 2013R2 to 2018

Resurrection of zombies is a regular vendor practice :-).

Just for troubleshooting purposes, will you face the same issue using -CommitPerTable parameter?
Ghetz 2,997 on at

Like (0)

Report

RE: Scary error message about dead and livings during Sync-NAVTenant. Upgrading from 2013R2 to 2018

OK.. so digging into to event viewer, I found a NAV Service error about timeout. So I increased the "SQL command timeout" in the NAV service with the Administration Tool. Hope this brings us "back to the livings"!

Will confirm as soon as the Sync process finishes.