Error 22946???

Getting a 22946 error when I try and run Toolkit. It happened when I was running 1.2 which was fine for what I am doing. Updated to 1.5 (full version) and I get exactly the same thing. It reports that C-Gate "A required component of Toolkit, C-Gate failed to start.

I have killed ZoneAlarm which was running in the background with no problems for nearly a year just in case.

Scratching my head at the moment! Any thoughts....thanks.

Cheers,

Fleetz

 

Starting C-Gate from the command line helps diagnose this issue.. this thread may help:

http://www.cbusforums.com/forums/showthread.php?t=827

 

I have looked at tried what this post was suggesting but to no avail. I can run C-Gate first then Toolkit and no problems. If I launch Toolkit first Toolkit doesn't launch C-Gate first. It use to do this everytime now for whatever reason it is disconnected and not able to find the C-Gate path.

Any ideas?

Thanks,

Fleetz

 

Same problem with version 1.12.5 and Windows 8 x64

I am having exactly the same problem described in this thread but with the latest release of C bus Toolkit on Windows 8 x64. I have tried manually stopping and restarting C-Gate to no effect. I'm only a self-taught end user, and I had a previous version I downloaded about six months ago working fine (stupidly didn't keep a copy of the install files) on Windows 7. Can anyone point me at a previous release that might work?

On another matter – I feel embarrassed to ask, but when I try to connect to my Ethernet interface module on my local network, do I use "remote" or "local" connection? Also, what is the system name?

Further information: I uninstalled and reinstalled, this time leaving "install as Windows servers" unticked. I then ran the cgate.exe in an elevated window and got the following messages:

C:\Clipsal\C-Gate2>cgate.exe
Starting C-Gate in console mode since C-Gate is not installed as service
Starting the C-Gate Java process as a console application
CGate is starting with java environment: C:\Clipsal\C-Gate2\jre6\bin\java.exe - jar -Xms32M -Xmx256M cgate.jar (using embedded JRE in cgate directory)
Successfully started a C-Gate Java process

I then tried running CBus Toolkit, and another command window appeared with the following:

Clipsal C-Gate(TM) v2.9.5 (build 2460)
Logging to file: event.log
C-Gate is running.
20130314-164424 803 cmd3 - Host:/127.0.0.1 opened command interface from port: 49966
20130314-164424 804 cmd3 - Host:/127.0.0.1 closed command interface from port: 49966
20130314-164426 803 cmd5 - Host:/127.0.0.1 opened command interface from port: 49970
20130314-164426 804 cmd5 - Host:/127.0.0.1 closed command interface from port: 49970
20130314-164427 803 cmd7 - Host:/127.0.0.1 opened command interface from port: 49971
20130314-164427 804 cmd7 - Host:/127.0.0.1 closed command interface from port: 49971
20130314-164428 803 cmd9 - Host:/127.0.0.1 opened command interface from port: 49972
20130314-164428 804 cmd9 - Host:/127.0.0.1 closed command interface from port: 49972
20130314-164429 803 cmd11 - Host:/127.0.0.1 opened command interface from port:49973
20130314-164429 804 cmd11 - Host:/127.0.0.1 closed command interface from port:49973
20130314-164431 803 cmd13 - Host:/127.0.0.1 opened command interface from port:49974
20130314-164431 804 cmd13 - Host:/127.0.0.1 closed command interface from port:49974
20130314-164432 803 cmd15 - Host:/127.0.0.1 opened command interface from port:49975
20130314-164432 804 cmd15 - Host:/127.0.0.1 closed command interface from port:49975
20130314-164433 803 cmd17 - Host:/127.0.0.1 opened command interface from port:49976
20130314-164433 804 cmd17 - Host:/127.0.0.1 closed command interface from port:49976
20130314-164434 803 cmd19 - Host:/127.0.0.1 opened command interface from port:49977
20130314-164434 804 cmd19 - Host:/127.0.0.1 closed command interface from port:49977
20130314-164435 803 cmd21 - Host:/127.0.0.1 opened command interface from port:49978
20130314-164435 804 cmd21 - Host:/127.0.0.1 closed command interface from port:49978
20130314-164437 803 cmd23 - Host:/127.0.0.1 opened command interface from port:49979
20130314-164437 804 cmd23 - Host:/127.0.0.1 closed command interface from port:49979
20130314-164438 803 cmd25 - Host:/127.0.0.1 opened command interface from port:49980
20130314-164438 804 cmd25 - Host:/127.0.0.1 closed command interface from port:49980
20130314-164439 803 cmd27 - Host:/127.0.0.1 opened command interface from port:49981
20130314-164439 804 cmd27 - Host:/127.0.0.1 closed command interface from port:49981
20130314-164440 803 cmd29 - Host:/127.0.0.1 opened command interface from port:49982
20130314-164440 804 cmd29 - Host:/127.0.0.1 closed command interface from port:49982

But then I got the same error again (22946). In desperation I installed the software on another computer on my network (also Windows 8), and it worked! This is a stopgap solution, but I really need to get this running on the computer I use all the time.

 

C-Gate connection choices

Hello mbagshaw.

Can't comment on your W8 problem, but without knowing any details of your setup I would have to say use 'connect to local c-gate'. If you had c-gate running on another (ie: remote PC) then use the 'connect to remote c-gate'.

System name relates to the remote PC running c-gate that you want to set up a connection for and is there as a description. For example, on my work laptop I have:
MediaPC - my home theatre PC;
OrangeBoy - my old work laptop (retired);
RPi_11 - Raspberry Pi at IP address xxx.xxx.xxx.11;
RPi_12 - Raspberry Pi at IP address xxx.xxx.xxx.12

 

hello,

ive had my old laptop lost and i have bought a new one. now it has w8 on it and i get this same msg and i cant get it in any way to connect to c gate or my network. it keeps coming up with a windows firewall msg, i let it through but still same msg appears!!

has anyone got this working on w8?

any feedback would be good as im a little frustrated over it now!!

cheers paul