| Author |  | 
      
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 25 2015 at 17:13 | IP Logged |   |  
           | 
 |  
 
 working machine has
 cswskax6.ocx
 
 and non working has
 
 cswskax8.ocx
 
 I am going to copy the cswskax6.ocx and test
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Nick,
           | Posted: August 25 2015 at 17:44 | IP Logged |   |  
           | 
 |  
 Sounds good. cswskax6.ocx should be the one (I thought
 it was 7 but looks like its actually version 6).
 
 Let me know how it goes.
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          by using cswskax6.ocx cant even run
           | Posted: August 25 2015 at 17:51 | IP Logged |   |  
           | 
 |  
 A critical error occurred at 2015-08-25 17:50:49.004.
 
 PowerHome Version: 2.1.5d
 Critical Error Count: 1
 Error Number: 39
 Error Message: Error accessing external object
 property autoresolve at line 16 in constructor event
 of object uo_socketserver.
 Window: uo_socketserver
 Object: uo_socketserver
 Event: constructor
 Line: 16
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Nick,
           | Posted: August 25 2015 at 18:01 | IP Logged |   |  
           | 
 |  
 The error you got isnt related to the plugin and is
 coming from the Socket Server within PowerHome (which is
 using cswskax8.ocx). Is that file still in your syswow64
 directory? If so, try running regsvr32 against it to
 make sure its registered properly
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 25 2015 at 18:44 | IP Logged |   |  
           | 
 |  
 no mine is not 64 bit both are window 7 -32bit
 
 found only one file cswskax8.ocx  their is also one
 other file which is cswsvax8.ocx does it has to do any
 thing .
 
 Nick
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          cswsvax8.ocx is another Catalyst control that is used by
           | Posted: August 25 2015 at 18:59 | IP Logged |   |  
           | 
 |  PowerHome. All of the cs????ax8.ocx are Catalyst
 controls and would have been installed by PH (since
 you're 32 bit they'll be c:\windows\system32). I would
 go through and run regsvr32 (as an administrator) on
 each one and your problem should go away.
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 25 2015 at 19:16 | IP Logged |   |  
           | 
 |  if I unregister cswskax8.ocx and rename the file and
 reboot then run PH will get critical error, so does it
 mean it is still using it. in windows registry you will
 find entries for above file.
 
 Nick
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Nick,
           | Posted: August 25 2015 at 19:22 | IP Logged |   |  
           | 
 |  
 Im not sure I fully understand. cswskax8.ocx (as well
 as the other cs????ax8.ocx files) is used throughout
 PowerHome in multiple components (the ph_geturl
 functions, the webserver, the socket server, version
 1.9 and above of the raw socket plugin, etc). You
 can't unregister, rename, or delete these files
 and have PowerHome still work. They're required.
 
 You can have both cswskax8.ocx and cswskax6.ocx
 running and registered on the same machine. They're
 two different versions of the same product and because
 they have different file names and internal GUID's
 they can coexist without issue. The version 1.8 of the
 raw socket plugin needs the cswskax6.ocx to be present
 and registered in order to run that version of the
 plugin (you wouldnt change, unregister, or rename any
 of the cs????ax8.ocx).
 
 Maybe Im not understanding but when you unregister and
 rename cswskax8.ocx PowerHome will NOT work.
 
 Dave.
 
 
 Edited by dhoward - August 25 2015 at 20:41
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 25 2015 at 19:46 | IP Logged |   |  
           | 
 |  
 Ph 2.15d
 
 I have unregister cswskax8.ocx , regiser  cswskax6.ocx
 
 also unregister Ph_socket 2.1  and register  Ph_socket
 1.8
 
 checked in PH it shows the 1.8 plug in.
 
 and Lockup again -
 
 If I rename the cswskax8.ocx file the error so I left
 it alone just unregister with regsvr32.
 
 Nick
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Nick,
           | Posted: August 25 2015 at 19:57 | IP Logged |   |  
           | 
 |  
 To run the 1.8 socket plugin and PowerHome you
 MUST register BOTH cswskax8.ocx and
 cswskax6.ocx. None of the cs????8.ocx files should be
 unregistered or renamed.
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 25 2015 at 20:30 | IP Logged |   |  
           | 
 |  
 Okay register both and plugin 1.8 its up and pass 8
 command - will watch and see, meanwhile I have download
 2.15c on different computer still win 7 and will report
 get back on both.
 
 Thanks
 
 Nick
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 25 2015 at 22:33 | IP Logged |   |  
           | 
 |  
 no luck
 
 2.1.5d with 1.8 plugin - locks up
 
 different computer win7
 2.1.5c with 1.9 plugin - locks up
 
 only one which will take any beat up is
 win 7
 2.1.4 with plugin 1.8 - NO problem
 
 Thanks
 
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 26 2015 at 17:31 | IP Logged |   |  
           | 
 |  
 I can confirm (2 separate machine) that its works fine
 with 2.1.4 and plugin 1.8.
 
 I install 2.1.4 on 2nd machine where yesterday 2.1.5c
 would fail.
 
 Send and received many command without any problem.
 
 Please let me know if you want me to try something
 else.
 
 Thanks
 
 Nick
 
 
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Nick,
           | Posted: August 27 2015 at 11:17 | IP Logged |   |  
           | 
 |  
 Sorry to take so long getting back. I had a crash on
 my virtual development machine and had to restore from
 backup.
 
 Last thing I'd like you to try (if you can) is to try
 both version 2.0 and 2.1 of the Socket plugin on one
 of your 2.1.4 machines so I can rule out an issue with
 the new plugin.
 
 To do this, you'll have to copy the cswskax8.ocx from
 your 2.1.5 machine to your 2.1.4 machine and register
 it. Don't unregister or rename anything else though.
 
 If the 2.0 and 2.1 plugins run fine, then I can stop
 tweaking the plugin and start looking at what changed
 in the plugin frameword between PH 2.1.4 and 2.1.5.
 
 Thanks,
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 27 2015 at 12:50 | IP Logged |   |  
           | 
 |  
 I copied cswskax8.ocx registered same with plugin 2.0.
 So far it passed the 8 command test.
 
 I will update when I get back home.
 
 just FYI for last 30 hours 2.1.4 with 1.8 had no
 problem and I was passing information to my main PH
 thru Powerhome ph_ssrequest just to make sure trigger
 and my macro also works.
 
 Thanks
 
 Nick
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 27 2015 at 17:25 | IP Logged |   |  
           | 
 |  
 2.1.4 with plugin 2.0  - over 4 hrs and many commands
 like over 60 - NO problem.
 
 2.1.4 with Plugin 2.1  pass 8 command test and left it
 on on to check it more.
 
 so seems like no problem with plugin but something
 difference between the PH version.
 
 Thanks
 
 Nick
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 27 2015 at 22:03 | IP Logged |   |  
           | 
 |  
 both plugin 2.0 and 2.1 works with 2.1.4
 
 
 Thanks
 Nick
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Nick,
           | Posted: August 29 2015 at 00:58 | IP Logged |   |  
           | 
 |  
 Appreciate all the testing you've done. Its been a
 huge help. Based upon your test results, I started
 digging into the entire plugin framework and did find
 a change that occurred between 2.1.4 and 2.1.5. I
 created a special "torture test" plugin and can easily
 make 2.1.5 hang.
 
 The good news though is that I was able to make
 changes to the 2.1.5 plugin frameword to put it more
 in line with the way it was in 2.1.4 and I am no
 longer able to crash it. The bad news is that this fix
 won't be available until I release the next version of
 PowerHome.
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  | 
        | nick7920 Senior Member
 
  
 
 Joined: March 04 2008
 Location: United States
 Online Status: Offline
 Posts: 193
 | 
          Dave,
           | Posted: August 29 2015 at 11:12 | IP Logged |   |  
           | 
 |  
 Glad that we could isolate an error.
 Do you have an idea what is the time frame for next
 release, if it is few months then I can try writing my
 own bridge.
 
 for shot term I can leave my other laptop (2.1.4) ON
 to do the back and forth communication like I mention
 with ph_ssrequest
 
 I don't want to be pushy but just like to know my
 options.
 
 Thank you
 
 Nick
 
 | 
       
        | Back to Top |     | 
       
       
        |  | 
        | dhoward Admin Group
 
  
  
 Joined: June 29 2001
 Location: United States
 Online Status: Offline
 Posts: 4447
 | 
          Nick,
           | Posted: August 29 2015 at 23:00 | IP Logged |   |  
           | 
 |  
 I need to finish up the Z-Wave support and a few other
 bug fixes and improvements. This will be a full
 release so will require a new help file, new database
 upgrade utility, new install, etc. Its going to be
 probably a couple of months before I can pull all that
 together.
 
 I might be able to pull the changes into a "patch"
 2.1.5e version in a couple of weeks.
 
 Dave.
 
 | 
       
        | Back to Top |       | 
       
       
        |  |