Problem capturing from D&D Insider
Submitted by nmorales2 on Fri, 2010-01-29 03:34.
I have installed Mozilla and the VCC Plugin. I bring up the view of the monster in D&D insider and hit capture on the toolbar. At that point a message comes up saying:
"Virtual Combat Cards replied: You sent something that VCC cannot capture."
The server is running. In the mozilla toolbar, the remote url is http://127.0.0.1:4143/capture
Is this correct? Any idea on what the problem is? I've tried it with a bunch of different monsters and keep getting the same results.






Moving to Bug
On Firefox 3.6 the way XML is serialized changed. This is causing the trouble. Created an issue for this, and I'm investigation a solution: #154: Fail all capture on Firefox 3.6
Fixed!
For all those facing this problem, please update your VCC (patch 1.1.2).
Same capture problem
I too am getting the same error message -- none of the monsters I've tried to capture have worked.
I tried searching for Goblin and tried all of the lvl 1 goblins then tried all 15 of the lvl 1 creatures from the MM1. Every single one generated the error that read "[JavaScript Application] Virtual Combat Cards replied: You sent something that VCC cannot capture."
In the FireFox plugin it reads "http://127.0.0.1:4143/capture"
I am using the latest version of the Mac OS, 10.6.2 and Firefox, 3.6
Something odd
Lucas, I tried to capture using my windows VCC and all of them worked correctly. There should be a vcc.log your disk (HOME/vcc probably). Can you open an issue and attack these logs?
I cloud be something with the Mac version, or maybe Firefox (in on 3.5.7). Either way we need to investigate this to figure out what is wrong. I'll see if it works on Windows with Firefox 3.6.
What monster is causing the problem?
The remote URL is correct. There are some monsters that are still causing problems (probably something wrong in handling of the HTML).
Could you give me the name of the monsters?
Problem capturing from D&D Insider
I am also haveing this same exact issue, when I copy and past the monster URL into the capture I get a different error.