xApmcs1wire Browser window won't open

Steve Q · #1 September 22nd, 2009, 12:53 PM

Michael,

For some unknown reason, the browser window will not open on xAPmcs1wire.exe version 2.4.0.13 The program is running and seems to be working Ok. The IO window works. The browser window hangs when it tries to open. I have restarted the computer and Homeseer; the problem persists. Everything seems to be working, but I cannot make any xAP changes.

Could this have something to do with mcsdatabase or access? I have been working with both quite a bit and I think I opened the xapdatabase (copy 5 or 6) with access to see if it would open (it did).

Any ideas?

Note: nothing new has been added to Homeseer (ver2.2.0.66). No hardware changes.

Steve Q

Michael McSharry · #2 September 22nd, 2009, 01:43 PM

I have version 2.11.0.1 and 2.11.0.3 running on two different computers without browser issues. 2.4.0.13 would seem to be quite old. Places to look is in the \Data and subfolders for a .txt file that may have some error log. Generally errorrs are reported using the homeseer.event schema so you can use xapmcsWritelog or the xAP Viewer to caputure error messages.

Steve Q · #3 September 22nd, 2009, 02:21 PM

Yes, it is an old version because about a year ago, I tried to go to a newer version but the newer version ( maybe it was the .net version) refused to work for more than a week; it seem to go deaf. Since I was not having any problems with version 2.4.0.13 I stuck with it.

I could not find a .txt file pertaining to xapmcs anywhere in the data folder. I will look elsewhere.

xAPViewer shows normal activity on the LAN. No error messages. No messages when I try to open the xAPmcs browser window.

I will try restatring everything again.

Thanks,
Steve Q

Steve Q · #4 September 22nd, 2009, 02:48 PM

Michael,

I restarted everything again. The browser window still refuses to load, no errors, it just hangs? Where is the HTML code page supposed to be located? I can't find anything that looks like the html page? The browser is looking for: http://localhost:8014/status

Unfortunately my Homeseer directory has a lot of xAP stuff because of all the different versions I was working with about a year ago. I also have a lot of xAP related files on my original Homeseer computer.

Steve Q

Michael McSharry · #5 September 22nd, 2009, 03:22 PM

8014 is the default port for xapmcs1wire. Each xAP application should be located in its own folder as common file names are used and they could interfere with each other if they are all thrown into the same sandbox. If you have multiple copies running then there will be a conflict with port 8014. You can change it manually from the xapmcs1wire.ini file before starting the application should you have a conflict with this port. You can also install it into a different folder, start it to confirm it is functional, exit, copy xapmcs1wire.ini from your prior location to the new one and start again.

Steve Q · #6 September 22nd, 2009, 04:04 PM

I changed the port in the .ini file to 8020 Restarted xapmcs1wire.exe It works fine on that port. I checked the folder structure; there are 2 folders: xapmcs1wire and xapmcs1wire2054. Everything looks fine in the subfolders. I renamed the .exe file for version 2054 to .exeno so now there is only one xapmcs1wire.exe on the computer.

Problem is still there, can't open the browser window.

Steve Q

Michael McSharry · #7 September 22nd, 2009, 04:21 PM

Are you indicating that you can open on port 8020, but not on 8014 or that you cannot open it on any port?

Steve Q · #8 September 22nd, 2009, 04:26 PM

I remembered that a few days ago I noticed that Homeseer was not displaying the ON.gif icon for the xapmcs1wire switch that I added on 9/20/2009. After investigating I discovered the \sensors directory was missing from the Homeseer2\html\images folder. So I copied it into the Homeseer2\html\images folder. This solved the problem with the Homeseer status page.

Perhaps something similar has happened with xapmcs1wire html page? An image file is missing?

Steve Q

Steve Q · #9 September 22nd, 2009, 04:28 PM

Quote:

Originally Posted by Michael McSharry

Are you indicating that you can open on port 8020, but not on 8014 or that you cannot open it on any port?

I can run xammcs1wire.exe on either 8014 or 8020 and it works OK on both but I can't open the browser page on either one.

Michael McSharry · #10 September 22nd, 2009, 04:36 PM

Then it seems like a firewall type issue. I know if you use Windows Firewall you need to explicity enable the port(s)

Steve Q · #11 September 22nd, 2009, 05:07 PM

Windows firewall is OFF. I opened the port 8020 in McAffee security center. And I included 8020 as a trusted site in Internet Explorer.

Still can't open the Browser. I also tried FireFox; still would not open the page.

Steve Q · #12 September 22nd, 2009, 05:33 PM

Upon further investigation, I found the xAP network is NOT responding to Homeseer commands. So the only activity I am seeing on the IO window and xAPviewer is inbound. Do you still have the installer for 2.4.0.13? I can try to reinstall it.

Steve Q

Steve Q · #13 September 22nd, 2009, 05:47 PM

Michael, I swapped the .ini file with an older one (backup). Now the browser loads but it shows only the bare table. No images (gifs), no device names, no further information. Somehow the links to the data are messed up.

I have to do some work now; be back around 11PM.

Steve Q

Michael McSharry · #14 September 23rd, 2009, 12:27 AM

If you unzip the xapmcs1wire download and maintain the folder structure then you will have all the supporting files needed for the browser display.

Steve Q · #15 September 23rd, 2009, 09:34 AM

Thanks Michael, I can't find the zip file, but I did find the error file; don't know why I couldn't find it before? Below are the entries for Sept 2009:

9/20/2009 7:57:05 PM | xapmcs1Wire Using xAP port 32770 0
9/20/2009 9:44:11 PM | xapmcs1Wire Using xAP port 32770 0
9/22/2009 11:14:57 AM | xapmcs1Wire Using xAP port 32770 0
9/22/2009 1:29:00 PM | xapmcs1Wire Using xAP port 32770 0
9/22/2009 2:02:35 PM | xapmcs1Wire TCPServer Unable to send TextFile C:\Program files\Homeseer 2\xapmcs1Wire\HTML\xapmcs1wire\stylenobody.css to socket 2 because State is 9 0
9/22/2009 2:02:35 PM | xapmcs1Wire TCPServer_SendBinaryFile C:\Program files\Homeseer 2\xapmcs1Wire\HTML\xapmcs1wire\clock.gif 300
9/22/2009 2:02:35 PM | xapmcs1Wire TCPSever_SendTextString 300
9/22/2009 2:02:35 PM | xapmcs1Wire TCPSever_SendTextString 300
9/22/2009 2:02:35 PM | xapmcs1Wire TCPSever_SendTextString 300
9/22/2009 2:39:32 PM | xapmcs1Wire Using xAP port 32770 0
9/22/2009 2:43:38 PM | xapmcs1Wire Using xAP port 32770 0
9/22/2009 2:46:07 PM | xapmcs1Wire Using xAP port 32770 0
9/22/2009 2:55:13 PM | xapmcs1Wire Using xAP port 32770 0
9/22/2009 11:37:32 PM | xapmcs1Wire Using xAP port 32770 0
9/22/2009 11:44:31 PM | xapmcs1Wire TCPServer Unable to send TextFile C:\Program files\Homeseer 2\xapmcs1Wire\HTML\xapmcs1wire\stylenobody.css to socket 2 because State is 9 0
9/22/2009 11:44:31 PM | xapmcs1Wire TCPServer_SendBinaryFile C:\Program files\Homeseer 2\xapmcs1Wire\HTML\xapmcs1wire\clock.gif 300
9/22/2009 11:57:09 PM | xapmcs1Wire TCPServer Unable to send TextFile C:\Program files\Homeseer 2\xapmcs1Wire\HTML\xapmcs1wire\stylenobody.css to socket 5 because State is 9 0
9/22/2009 11:57:09 PM | xapmcs1Wire TCPServer_SendBinaryFile C:\Program files\Homeseer 2\xapmcs1Wire\HTML\xapmcs1wire\sunrise.gif 300

Looks like it can't find the style sheet? It's in the directory where it is supposed to be!

Steve Q

Steve Q · #16 September 23rd, 2009, 11:43 AM

I found the zip file containing xapmcs1wire ver 2.4.0.13

Michael, rather than reinstall this old version, maybe I should install your latest version 2.11.0.3. What do you think? Have the "going deaf" problems been resolved?

Steve Q

Michael McSharry · #17 September 23rd, 2009, 01:44 PM

"Going Deaf" was a characteristic of the .NET version of the mcsXap plugin. It has been experienced by some, but not by all. It has no relationship to xapmcs1wire. The latest xapmcs1wire is the one that should be used.

I'm finishing up the migration of mcsSprinklers to a service and rewriting the .NET socket implementation. When I have success with that then I expect to implement xapmcs1wire using the same software. This will remove the MSJVM restriction. It could also have implications for changes to mcsXap.

Steve Q · #18 September 23rd, 2009, 02:24 PM

Thanks for the clarification. I will go with 2.11.0.3.

Steve Q

Steve Q · #19 September 23rd, 2009, 02:49 PM

Michael, I installed 2.11.0.3 and copied my .ini file to the xapmcs1wire directory. Upon startup it loaded my devices and started working properly. IO window traffic looks fine. However, the Browser window will still not open! So I changed the name of xapmcs1wire.ini to xapmcs1wire.old and restarted xapmcs1wire.exe which allowed xapmcs1wire.exe to create a new .ini file. Now I can open the browser and see all my devices; however, their names, device codes, and poll times are gone. I guess I can manually reenter that info (lots of stuff!).

Is there anyway to repair the original .ini file?

Steve Q

Michael McSharry · #20 September 23rd, 2009, 03:49 PM

You should be able to copy entire groups from your old to new .ini file. This will help to isolate which specific setting is causing a problem.