The TvDB links are not being shown and long delays in using JMM Desktop with error messages popping.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Update to JMM Desktop 3.1.32.0
2. Go to the Collection tab
3. Select any filter then click on it

What is the expected output? What do you see instead?
To just to be able to navigate and use JMM Desktop normally.

Basically, the errors get displayed after selecting any filter from the 
Collection tab. The first and second error messages provided in the additional 
info below are what keeps on appearing each time I navigate my collections list.

After going inside a filter and closing the error messages, the anime group 
list is shown but each time I choose a group/series, the first and second error 
messages are shown again. Sometimes, even multiple instances of the second 
error message is shown.

I then tried adding re-linking some TvDB links to see if anything will change. 
Unfortunately, it gives off a different error and doesn't appear to do anything.

What version of the product are you using? On what operating system?
JMM Desktop 3.1.32.0

Please provide any additional information below.

First error:
Dispatcher processing has been suspended, but messages are still being 
processed.

Second error:
The message with Action 'http://tempuri.org/IJMMServer/GetTVDBCrossRefV2' 
cannot be processed at the receiver, due to a ContractFilter mismatch at the 
EndpointDispatcher. This may be because of either a contract mismatch 
(mismatched Actions between sender and receiver) or a binding/security mismatch 
between the sender and the receiver.  Check that sender and receiver have the 
same contract and the same binding (including security requirements, e.g. 
Message, Transport, None).

The TvDB linking error:
The message with Action 
'http://tempuri.org/IJMMServer/GetAniDBEpisodesForAnime' cannot be processed at 
the receiver, due to a ContractFilter mismatch at the EndpointDispatcher. This 
may be because of either a contract mismatch (mismatched Actions between sender 
and receiver) or a binding/security mismatch between the sender and the 
receiver.  Check that sender and receiver have the same contract and the same 
binding (including security requirements, e.g. Message, Transport, None).

Original issue reported on code.google.com by windfury...@yahoo.com on 4 Jun 2013 at 12:10

[GoogleCodeExporter]

My mistake, this is embarassing.
As it turns out, it was because I failed to update JMM Server to 3.1.32.0.

Original comment by windfury...@yahoo.com on 4 Jun 2013 at 12:15

[GoogleCodeExporter]

All good, you are not the first and won't be the last :)

Please keep reporting any bugs you find.

Original comment by werndly...@gmail.com on 4 Jun 2013 at 10:01

• Changed state: Invalid

[GoogleCodeExporter]

Alright, will do. :)

Original comment by windfury...@yahoo.com on 5 Jun 2013 at 1:19