OK, so I went with the command line route which was simpler as even a new clean address was causing the error. When I entered the correct string (via your comment before) I got this window:
https://i.imgur.com/pJaIWHM.jpgFollowed by this one approx 15 seconds later
https://i.imgur.com/GSz8TG9.jpgC&P files from SGMiner to root of C:\ and then entered the string. Seems to be working now.
My card is a AMD HD7870
Will this still be pointing to the .conf file as I notice that the intensity is set to I: 8 and the intensity in the .conf file was at I: 13. To be honest it's better @ I: 8 as the PC is more usable as I mine. GPU is running @ 44c
Well, actually I don't know if it pulls from the conf. Because i've often had this problem, but I've set up a rig now to run bamt, which is a dedicated mining OS.
However. This site give basic expected kh. Although the script can affect what you actually get.
https://litecoin.info/Mining_hardware_comparison[7850 411 1200 1365 cgminer 2.11.3 -I 19 -g 1 -w 256 --thread-concurrency 16000
7870 GHz Edition, XFX 300 1000 1200 cgminer 3.6.0 -I 12 -g 2 -w 256 Windows 7 x64, 87C
7870, AX7870 2GBD5-2DHPPV3E 320 975 1500 cgminer -I 18 --thread-concurrency 16384 80C
7870 GHz Edition, 100354OC-2L 381 810 1450 Reaper v13 Beta sharethreads 20 thread_concurrency 15232 Windows 7 x64, Catalyst 13.3 Beta, 65C
7870 GHz Edition, GV-R787OC-2GD 385 1190 1500 cgminer 2.11.4 -I 12 -g 2 -w 256 --thread-concurrency 8192
I would test by adjusting the config and using that route. If it says accepting shares, then who knows what the json error is.
But check the thread concurrency in the config file.
In the command prompt console, you should be able to adjust your gpu engine clock and memory clock. The Intensity is debatable, too high and it will flake out the kh's too low and you won't get much of a return. I'm being honest, to be worthwhile you need to get your card up to providing 300-400 kh/s not near 20kh's.
But you've done pretty well up til now to deal with problems and get it running.