Today, I had the unfortunate event of dealing with a failed Ektron eSync job. Also unfortunate was the fact that there did not appear to be any sort of error message to even figure out something had gone wrong. The blank "Synchronization Status" just sat there, trying to figure out what it should do next, indefinitely.
After waiting around a few minutes, I killed the Ektron Windows Service on the source CMS instance (my developer box), restarted IIS, and re-ran the esync process. This time I made certain to pay attention. The error did not say much, nor did it stay on screen longer than a few seconds before returning to the "Synchronization Status" waiting screen. Here is what it looks like.
Something apparently failed in the .NET System.ServiceModel.Channels.ServiceChannel class and had left eSync (Ektron?) in a faulted state.
What the hell does that mean?
After troubleshooting every Ektron log, database table, and esync system I could think of, I resorted to the nefarious Ektron forums and found an article in the Ektron forums regarding a similar situation in which I found myself.
The answer came from Andrew, "check your license."
Now forgive me, but having a communication channel in a faulted state does NOT sound like a license issue. But what the heck, I decided to give it a shot.
It worked. Apparently our recently updated server license keys had omitted the (S) flag, thus discontinuing the production server's support of esync.
Boy, I am glad that error message helped me figure that out after two hours of spinning my wheels on completely unrelated tangents.
</rant>