**** with Claymore's Dual Miner
2016-08-15 10:25:09 TRACE rpc Request: {"method": "eth_getWork", "params": [], "id":0}
2016-08-15 10:25:09 DEBUG rpc Response: Some("{\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32600,\"message\":\"Invalid request\",\"data\":null},\"id\":null}")
2016-08-15 10:25:10 TRACE rpc Request: {"method": "eth_getWork", "params": [], "id":0}
2016-08-15 10:25:10 DEBUG rpc Response: Some("{\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32600,\"message\":\"Invalid request\",\"data\":null},\"id\":null}")
**** with Ethminer
2016-08-15 10:25:30 TRACE rpc Request: {"id":1,"jsonrpc":"2.0","method":"eth_getWork"}
2016-08-15 10:25:30 DEBUG rpc Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[\"0xcc906703772e5e65d85abb672dc363bc91f866d7b01b61c0877c40d2edc92b49\",\"0x46862965466b5f8011ebefb35a0d1a0b7290c3ba38c11e916c74c347e00ed903\",\"0x00000000001c72ad64007a6db5d3515a0db95a130c9293553de655fde6328914\",\"0x1fa7e4\"],\"id\":1}")
2016-08-15 10:25:32 TRACE rpc Request: {"id":1,"jsonrpc":"2.0","method":"eth_getWork"}
2016-08-15 10:25:32 DEBUG rpc Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[\"0xcc906703772e5e65d85abb672dc363bc91f866d7b01b61c0877c40d2edc92b49\",\"0x46862965466b5f8011ebefb35a0d1a0b7290c3ba38c11e916c74c347e00ed903\",\"0x00000000001c72ad64007a6db5d3515a0db95a130c9293553de655fde6328914\",\"0x1fa7e4\"],\"id\":1}")
2016-08-15 10:25:33 TRACE rpc Request: {"id":1,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x62f2","0x0d2d291fe73cba1bfc69c5605a3d3e0af93a2f8c7d210d53cb4c1c263cd3d525"]}
Technically, RPC command in Claymore's Dual Miner is not an issue.
Actually, I have tested with RPC command windows in the parity UI, this command is working well.
but, with Miner, it shows as the error.
I feel as some kind of line termination code error ? or something, strange error has been happening,