Home AMXForums Archive Threads AMX Applications and Solutions

G4 web interface problems

Hi everybody,
a problem with G4 modero web interface appeared in a project with no software or hardware changes. For some reasons, when I try to open the modero web interface from a PC, I see the mesasge "Please wait-Initial screen loading....", then a white screen and the message "please push spacebar or enter to use this". When I push one of them nothing happens and the PC get stuck !!!! Since the last months everything were going perfectly.
I use G3 and G4 web interface on this controller. G3 one goes fine. G4 not!!!
I use the Java environment that AMX suggests.

Any idea?
George

Comments

  • FrankieFrankie Junior Member Posts: 71
    Could it be some sort of pop-up blocker?
  • Thomas HayesThomas Hayes Junior Member Posts: 1,164
    I had this happen yesterday too, first time I've ever seen it.
  • Danny CampbellDanny Campbell Senior Member Posts: 311
    I have heard that a Microsoft security patch #KB916281 is what has broken this. The only solution that I have heard at this point is to uninstall that patch.
  • ClingpeachClingpeach Junior Member Posts: 156
    Danny Campbell is right. I called AMX tech support. Its the cumulative patch. How does one uninstall this. I cant find it in the add/remove programs. AMX is trying to find a fix
  • Stephen BoltonStephen Bolton Junior Member Posts: 345
    G4 web interface problems

    Hi all,

    This artical is worth a read

    http://support.microsoft.com/kb/916281

    There are a couple of supposed fixes by third parties out there for this problem, but there appears to be serious issues associated with at least a couple of them - like the pc won't restart etc. That was enough for me!

    Perhaps rollback xp?

    ..George, be wary of the notes about upgrading java - in my experience you can't use java rev over v1.4.x or your G3 web instances will stop working..

    Steve
  • ClingpeachClingpeach Junior Member Posts: 156
    I used Go Back to get rid of this update. I have NOW since turned off Automatic Updates.
  • gary_cumminsgary_cummins Junior Member Posts: 52
    I use ultravnc viewer for touchpanels. It seems to connect better and it gives you plenty of display options. I know the web interface is cool, but this really is a great alternative.

    http://ultravnc.sourceforge.net/

    Look for "[email protected] 1.0.1 Standalone Viewer" on the right.

    TIP: If you right click on the shortcut after you install and go to properties. Add the touch panel's IP address at the very end and the link like this:
    "C:\Program Files\UltraVNC\vncviewer.exe" 192.168.1.63
    Now the shortcut goes directly to that touchpanel.
  • George KrietsepisGeorge Krietsepis Member Posts: 180
    Thank you all guys... Any idea of when AMX is going to fix the problem?
  • DHawthorneDHawthorne Junior Member Posts: 4,584
    I prefer VNC as well, but that won't help you if there is no physical Modero panel on the job. Older panels don't support it, and when NetLinx first came out, I sold several projects with no panel at all, just a web control page. For jobs like that, you need a working web control java applet, and sadly, it's always been hit-or-miss, and this patch just added to the misses. The falling off of support for it at AMX has been steady, which is very unfortunate. It ostracizes customers to be left dangling with an unsupported product; they don't sqay, "oh, I guess I'll just upgrade to the new opffering," they say, "screw that, I don't want to buy anything from a company that will do that to me."
  • veraviewveraview Junior Member Posts: 44
    Another Windows Update Problem

    I just got back, from an unfortunately long drive, to solve a problem for a customer. This system has run perfectly since my last visit 8 months ago, until very recently, when they called to say their MVP8400 was hanging, the AXT-CV4 was hanging as well, and the system would go unresponsive, then come back up a minute or so later. I spent 3 hours updating firmware on everything I could think of, including the projector, double-checking my code, and running through the system. I finally found that when I called up a G4 computer control window on the MVP, everything would go south. The PC's desktop background (on its monitor) would disappear, come back, disappear, the mouse would flicker, and the both panels would become unresponsive. The master's network ports were going crazy! I had msgs on in a telnet session, and only saw the MVP drop offline for a few seconds. I put in the latest G4CC.exe patch to no avail. Since this was by no means a critical part of the system, I just pulled the USB stick out and like magic I couldn't reproduce the problem by bringing up the computer control window. The ONLY variable here was that windows update was recently run on their PC. Running out of time, I figured it would be best to see what y'all think before I start pulling my hair out.
    Has anyone seen this take on the Windows Security problem before? Here is all that netlinx logged. Watch device 10001 go on and offline. Most curious is line 10.

    Anyone thinking I may have missed something more obvious?

    Entry Date/Time Object Text
    1: 06-28-2006 WED 12:19:52 ConnectionManager Memory Available = 25730804 <15580>
    2: 06-28-2006 WED 12:15:53 Interpreter CIpEvent::OnLine 10001:1:1
    3: 06-28-2006 WED 12:15:46 Interpreter CIpEvent::OffLine 10001:1:1
    4: 06-28-2006 WED 12:09:29 ConnectionManager Memory Available = 25746384 <82804>
    5: 06-28-2006 WED 12:05:09 Interpreter CIpEvent::OnLine 10001:1:1
    6: 06-28-2006 WED 12:05:09 ConnectionManager Memory Available = 25829188 <16112>
    7: 06-28-2006 WED 12:05:02 Interpreter CIpEvent::OffLine 10001:1:1
    8: 06-28-2006 WED 11:55:14 ConnectionManager Memory Available = 25845300 <39616>
    9: 06-28-2006 WED 11:46:25 ConnectionManager Memory Available = 25884916 <10112>
    10: 06-28-2006 WED 11:46:25 Unknown (Reader=tInterpreter writer=tDeviceMgr)- CMessagePipe::Max = 25
    11: 06-28-2006 WED 11:46:25 ConnectionManager Memory Available = 25895028 <10664>
    12: 06-28-2006 WED 11:31:02 ConnectionManager Memory Available = 25905692 <10800>
    13: 06-28-2006 WED 11:30:21 ConnectionManager Memory Available = 25916492 <10992>
    14: 06-28-2006 WED 11:29:16 ConnectionManager Memory Available = 25927484 <69680>
    15: 06-28-2006 WED 11:28:54 ConnectionManager Memory Available = 25997164 <16808>
    16: 06-28-2006 WED 11:28:54 TelnetSvr Accepted Telnet connection:socket=15 addr=10.128.101.144 port=1300
    17: 06-28-2006 WED 11:28:19 Interpreter CIpEvent::OnLine 10001:1:1
    18: 06-28-2006 WED 11:28:19 ConnectionManager Memory Available = 26013972 <30280>
    19: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:17:1
    20: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:16:1
    21: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:15:1
    22: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:14:1
    23: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:13:1
    24: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:12:1
    25: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:11:1
    26: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:10:1
    27: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:9:1
    28: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:8:1
    29: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:7:1
    30: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:6:1
    31: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:5:1
    32: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:4:1
    33: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:3:1
    34: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:2:1
    35: 06-28-2006 WED 11:28:02 Interpreter CIpEvent::OnLine 5001:1:1
    36: 06-28-2006 WED 11:28:02 ConnectionManager Memory Available = 26044252 <20840>
    37: 06-28-2006 WED 11:27:57 ConnectionManager Memory Available = 26065092 <11100>
    38: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 0:5:1
    39: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 13:2:1
    40: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 13:1:1
    41: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OffLine 13:2:1
    42: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OffLine 13:1:1
    43: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 128:1:1
    44: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 129:1:1
    45: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 32768:1:1
    46: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 32769:1:1
    47: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 32770:1:1
    48: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 13:2:1
    49: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 13:1:1
    50: 06-28-2006 WED 11:27:55 Interpreter CIpEvent::OnLine 0:1:1
    51: 06-28-2006 WED 11:27:55 ConnectionManager Memory Available = 26076192 <45940>
    52: 06-28-2006 WED 11:27:55 ConnectionManager Memory Available = 26122132 <11064>
    53: 06-28-2006 WED 11:27:55 ConnectionManager Memory Available = 26133196 <26472>
    54: 06-28-2006 WED 11:27:55 Interpreter CIpInterpreter::Run - Execute Startup Code
    55: 06-28-2006 WED 11:27:48 ConnectionManager Memory Available = 26159668 <101896>
    56: 06-28-2006 WED 11:27:47 WebServer Web Server is ready
    57: 06-28-2006 WED 11:27:47 WebServer Completed SSL Initialization
    58: 06-28-2006 WED 11:27:47 WebServer SSL Is Configured To Be Enabled
    59: 06-28-2006 WED 11:27:47 WebServer Try to Initialize SSL...
    60: 06-28-2006 WED 11:27:47 WebServer Web Server Start Initialization...
    61: 06-28-2006 WED 11:27:47 Interpreter CIpUffHandler::Load - NV Ram Used 25640
    62: 06-28-2006 WED 11:27:47 Interpreter CIpUffHandler::Load - NV Ram Total 1047536
    63: 06-28-2006 WED 11:27:47 Interpreter CIpListMan::LoadDone - Set New Guid
    64: 06-28-2006 WED 11:27:47 Interpreter CIpPersistent::RestoreNewVariable
    65: 06-28-2006 WED 11:27:47 Interpreter CIpNvMemory::SetGuid L=40 S= j ? D
    66: 06-28-2006 WED 11:27:47 Interpreter CIpUffHandler::Load Good Incoming was 29% of Actual Size 127KB
    67: 06-28-2006 WED 11:27:47 Interpreter CIpSymbol::LoadModuleInfo 44 1
    68: 06-28-2006 WED 11:27:47 Interpreter CIpSymbol::LoadGlobalLocalInfo 2300 58
    69: 06-28-2006 WED 11:27:47 Interpreter CIpSymbol::LoadStructureInfo 974 10
    70: 06-28-2006 WED 11:27:47 Interpreter CIpSymbol::LoadFileInfo 196 3
    71: 06-28-2006 WED 11:27:47 Interpreter CIpTempMan::LoadTemplate 4260 2
    72: 06-28-2006 WED 11:27:47 Interpreter CIpDeviceList::LoadDeviceList 6 2
    73: 06-28-2006 WED 11:27:47 ConnectionManager Memory Available = 26261564 <12516>
    74: 06-28-2006 WED 11:27:47 Interpreter CIpCodeMan::LoadTable 14 2
    75: 06-28-2006 WED 11:27:47 Interpreter CIpDirect::LoadDirect 60 2
    76: 06-28-2006 WED 11:27:47 Interpreter CIpListMan::LoadNonVolatile Load 130 2
    77: 06-28-2006 WED 11:27:47 Interpreter CIpListMan::LoadVolatile 566 2
    78: 06-28-2006 WED 11:27:47 Interpreter CIpCodeMan::LoadCode 4724 2
    79: 06-28-2006 WED 11:27:47 Interpreter CIpUffHandler::Module Header
    80: 06-28-2006 WED 11:27:47 Interpreter CIpSymbol::LoadGlobalLocalInfo 10398 260
    81: 06-28-2006 WED 11:27:47 ConnectionManager Memory Available = 26274080 <448300>
    82: 06-28-2006 WED 11:27:47 Interpreter CIpSymbol::LoadStructureInfo 1166 11
    83: 06-28-2006 WED 11:27:47 Interpreter CIpSymbol::LoadFileInfo 540 8
    84: 06-28-2006 WED 11:27:47 Interpreter CIpTempMan::LoadTemplate 8776 1
    85: 06-28-2006 WED 11:27:47 Interpreter CIpDeviceList::LoadDeviceList 1374 1
    86: 06-28-2006 WED 11:27:47 Interpreter CIpCodeMan::LoadTable 22 1
    87: 06-28-2006 WED 11:27:47 Interpreter CIpDirect::LoadDirect 5814 1
    88: 06-28-2006 WED 11:27:47 Interpreter CIpListMan::LoadNonVolatile Load 25270 1
    89: 06-28-2006 WED 11:27:47 LontalkIF Neuron ID=00A207775201
    90: 06-28-2006 WED 11:27:47 Interpreter CIpNvMemory::DisplayFree Used=24 Available=1047512
    91: 06-28-2006 WED 11:27:47 Interpreter CIpNvMemory::NvClearMemory Complete Nv Memory Reset
    92: 06-28-2006 WED 11:27:47 Interpreter CIpPersistent::SaveOldVariable
    93: 06-28-2006 WED 11:27:47 Interpreter CIpListMan::LoadVolatile 4696 1
    94: 06-28-2006 WED 11:27:47 Interpreter CIpCodeMan::LoadCode 56352 1
    95: 06-28-2006 WED 11:27:47 Interpreter CIpUffHandler::Module Header
    96: 06-28-2006 WED 11:27:47 Interpreter CIpUffHandler::Project Name=CbCONFr7
    97: 06-28-2006 WED 11:27:47 Interpreter CIpUffHandler::Root
    98: 06-28-2006 WED 11:27:47 Interpreter CIpUffHandler::Load - Begin...doc:PROG.TKN
    99: 06-28-2006 WED 11:27:47 Interpreter CIpNvMemory::NvInitalize NvRam Tested OK Used=25704 Available=1021832
    100: 06-28-2006 WED 11:27:47 ConnectionManager Memory Available = 26555680
    101: 06-28-2006 WED 11:27:46 ConfigurationManager UDP Blink Message Time = 5 seconds (0=off)
    102: 06-28-2006 WED 11:27:46 ConfigurationManager Log Entry Count = 1000
    103: 06-28-2006 WED 11:27:46 ConfigurationManager TCP Timeout = 45000mS
    104: 06-28-2006 WED 11:27:46 ConfigurationManager NetLinx Sockets Message Queue Size = 50
    105: 06-28-2006 WED 11:27:46 ConfigurationManager PhastLink Receive Message Queue Size = 500
    106: 06-28-2006 WED 11:27:46 ConfigurationManager ICSNet Receive Message Queue Size = 200
    107: 06-28-2006 WED 11:27:46 ConfigurationManager LontalkHost Message Queue Size = 500
    108: 06-28-2006 WED 11:27:46 ConfigurationManager Lontalk Message Queue Size = 500
    109: 06-28-2006 WED 11:27:46 ConfigurationManager UDP Transmit Message Queue Size = 500
    110: 06-28-2006 WED 11:27:46 ConfigurationManager ICSP 232 Transmit Message Queue Size = 500
    111: 06-28-2006 WED 11:27:46 ConfigurationManager ICSNet Transmit Message Queue Size = 500
    112: 06-28-2006 WED 11:27:46 ConfigurationManager PhastLink Transmit Message Queue Size = 500
    113: 06-28-2006 WED 11:27:46 ConfigurationManager Axlink Transmit Message Queue Size = 200
    114: 06-28-2006 WED 11:27:46 ConfigurationManager Message Dispatcher Message Queue Size = 500
    115: 06-28-2006 WED 11:27:46 ConfigurationManager IP Connection Manager Message Queue Size = 500
    116: 06-28-2006 WED 11:27:46 ConfigurationManager TCP Transmit Threads Message Queue Size = 200
    117: 06-28-2006 WED 11:27:46 ConfigurationManager Diagnostic Manager Message Queue Size = 500
    118: 06-28-2006 WED 11:27:46 ConfigurationManager Device Manager Message Queue Size = 500
    119: 06-28-2006 WED 11:27:46 ConfigurationManager Route Manager Message Queue Size = 200
    120: 06-28-2006 WED 11:27:46 ConfigurationManager Connection Manager Message Queue Size = 500
    121: 06-28-2006 WED 11:27:46 ConfigurationManager Notification Manager Message Queue Size = 200
    122: 06-28-2006 WED 11:27:46 ConfigurationManager Interpreter Message Queue Size = 600
    123: 06-28-2006 WED 11:27:46 ConfigurationManager Routing Flags = $0
    124: 06-28-2006 WED 11:27:46 ConfigurationManager Timeline Loopcnt = 10
    125: 06-28-2006 WED 11:27:46 ConfigurationManager IP Threshold = 200
    126: 06-28-2006 WED 11:27:46 ConfigurationManager Lontalk Threshold = 50
    127: 06-28-2006 WED 11:27:46 ConfigurationManager Interpreter Threshold = 10
    128: 06-28-2006 WED 11:27:46 ConfigurationManager Device Holdoff = 0
    129: 06-28-2006 WED 11:27:46 ConfigurationManager URL Entry Count = 0
    130: 06-28-2006 WED 11:27:46 ConfigurationManager DNS Entry Count = 0
    131: 06-28-2006 WED 11:27:46 ConfigurationManager Domain Name =
    132: 06-28-2006 WED 11:27:46 ConfigurationManager Serial Number = '2105x1240250',0
    133: 06-28-2006 WED 11:27:46 ConfigurationManager System = 1
    134: 06-28-2006 WED 11:27:46 ConfigurationManager LoadConfiguration Complete (26620).
  • pdabrowskipdabrowski Aussie Guy Posts: 184
    I don't know if it has something to do with this, but MS06-025 (KB911280) was just re-released, the known issues with v1 of this patch had much to do with breaking legacy terminal scripting and serial control: http://support.microsoft.com/kb/911280

    This particular fix was supposed to plug a hole in RASMAN and this may have also contributed to breaking of G4 computer control (I don't know enough about G4CC, so perhaps one of the AMX guys may be able to shed some light).
  • Temporary solution
    I have heard that a Microsoft security patch #KB916281 is what has broken this. The only solution that I have heard at this point is to uninstall that patch.

    I also heard patch KB916281 is the problem. G4 web control should work again once the patch is removed.
  • sethollesetholle Junior Member Posts: 66
    G4 WEb interface problems

    After talking to AMX this is definetly a problem. TECH NOTE number 804 gives ways to fix it. For now I just removed the patch. However this is not a permanent solution. AMX told me they should have a firmware update ready by monday to address this completely.
  • George KrietsepisGeorge Krietsepis Member Posts: 180
    Hello everybody,
    have you anyone of you found a permanent solution for this problem? Any news from AMX investigation?
  • sethollesetholle Junior Member Posts: 66
    G4 web problem

    I am still waiting for a permanent fix to this problem. I have uninstalled the patch. However this is only temporary as our network guys demand all the latest patches on our computers. Amx still has not released any new firmware.
  • wgreenwgreen Junior Member Posts: 15
    A firmware patch from AMX is out and available on the website. I used it this morning and it worked fine.
  • shr00m-dewshr00m-dew Junior Member Posts: 394
    So did they pull it or is it a special area or something??? Can't find it nor anything released today.

    Kevin D.
  • Harald FrickHarald Frick Junior Member Posts: 20
    shr00m-dew wrote:
    So did they pull it or is it a special area or something??? Can't find it nor anything released today.

    Kevin D.

    There is a Tech-Note 804 which describes the problem with "G4 Web Control Stops Working After Microsoft Cumulative Security Update". The Tech-Note is updated now and at the end you will find 2 Firmware Patch Files (for Duet and Non-Duet Masters).

    Here is the direct link:
    http://www.amx.com/techsupport/techNote.asp?id=804
  • sethollesetholle Junior Member Posts: 66
    G4 web interface problems

    There is no permanent solution as of yet. Two weeks ago, AMX said they were developing a fix. HOwever, I have just installed the very latest xp upgrades, actually they automatically install on our corporate network. It seems that whatever mess microsoft made in their bad patch, has been rectified in the new patch.
    That old patch with a 21 ending definetly does kill the web control. As soon as you uninstall it, the problem goes right away.
  • shr00m-dewshr00m-dew Junior Member Posts: 394
    So are you saying the above posted fix from AMX does not work for you?

    Kevin D.
  • sethollesetholle Junior Member Posts: 66
    Solution to g4 web control problem

    There is a patch that amx created. It is a firmware file update for the master controlling the g4 panel. It is under tech note number 804. Just go the tech note. Download the file. Either for a duet or non duet master. Upload the firmware file and you should be good to go. I don't know why amx has not posted this a new firmware right when you go to training. You would think they would considering, this is a pretty big problem.
    I tried to include the .kit file here, but the uploading sofware for extensions, does not let you.
    Seth C. Olle
  • sethollesetholle Junior Member Posts: 66
    G4 patch

    Has anyone heard why amx has not officially released this patch to fix this g4 web control on their web site. I have installed the patch from tech note 804 and it works great. I don't now why they have not added it to firmware. I talked to them after the initial problem and they said they would be loading it up monday, that was like a month ago. Has anyone heard anything?
  • terrmulterrmul Junior Member Posts: 18
    Anyone....

    Anyone have any news on this. I still can't connect and have uploaded the firmware patch. Is there somehting I'm missing?
  • wgreenwgreen Junior Member Posts: 15
    There are two different versions of the patch. One for systems running Duet and one for systems not running Duet. I have used this patch without any problems. You may want to consider reloading whatever firmware version you are using and then loading the patch again.
  • dunnpdunnp Junior Member Posts: 12
    G4 Web Control Patch

    Read Tech Note 804. The problem is caused by the MS security patch and is solved IF you can remove it. Unfortunately it's bundled into SP2 & can't be removed. The fix is to download the relevant patch in the Tech Note into each Netlinx master.
    ...Phil
Sign In or Register to comment.