Michel Kohanim Posted September 21, 2011 Share Posted September 21, 2011 Hello all, I am happy to announce the availability of our 3.1.9 release! For a list of changes, please take a look at this post. This is a minor release to address the inability to download logs in 3.1.8. IMPORTANT 1. Please note that Network Resource modules are now running in their own task. This might have some ramifications as calling network resources from programs no longer waits for the resource to complete. As such, a) you will experience quicker handling of network resources/programs and if you are using DSCLinc and WebLinc, your programs may behave a little differently. Please do test your network resources thoroughly 2. Please note that Safari does not support SSL session reuse and thus might take an exorbitant amount of time to communicate with ISY. As such, when using 2048 bit SSL, it's best not to use Safari. 3. If you are using the Irrigation Module and are upgrading from releases prior to 3.1.5, you must edit the programs using Irrigation variables and save the programs again. Irrigation module is no longer on promotion 4. Upgrading from 3.1.3 and below: If you are using WeatherBug Module's Rain Today in your programs, please note that the precision has changed from 1/10 to 1/100 and thus your programs might not run properly Things to test: - Battery/Batch buttons - If you have an ActionTec router with WeatherBug, please do make sure ISY can get to the outside world and especially to WB Server - Network performance and status - System instability and network issues especially system hang (even though the programs continue to run) - Network resources and programs For a discussion of variables, please look at our Program Variables forum. Notes: 1. ISY-26 is no longer included in the firmware builds 2. Due to the sensitive nature of supporting MorningLinc, users now must agree to terms and conditions upon Admin Console start up otherwise the dialog keeps popping up every time the Admin Console is started 3. IMPORTANT If you have already installed a self signed certificate and your current firmware is 2.7.10 and below, you must reinstall a new one before the upgrade. Instructions: 1. Please backup your ISY (File | Backup ISY). If you are backing up a 3.1.6 system, please note that the backups are corrupted. If you have a backup from prior releases, you should be OK 2. Please download the firmware for your platform - please do not unzip ISY 99i Series OR 994i Series 3. Important (If upgrading from 2.8.5 through 2.8.14) Due to invalid Java certificate chain, please make sure to remove all Universal Devices certificates from Java: a. Close all browser sessions b. Open Java Control Panel (Java Preferences on MAC) c. Click on the Security tab. Remove all Universal Devices certificates (on MAC, click on the '-' button at the bottom) e. Clear your Java Cache 4. Login to the Admin Console and choose Help | Manually Upgrade [the name of your system] 5. Choose the file saved in step 2 MAC users: if upgrade fails, please add https://your.isy.ip.address to ISY Finder (see 3f above) 6. After the upgrade, ISY reboots. Please do ensure to clear your Java Cache 7. IMPORTANT Once upgrade is completed and ISY reboots, use any of the following methods to access your ISY's Admin Console: a. 99/994i - http://isy/admin - applet (Windows only) b. 99/994i - http://isy/admin.jnlp - Java application (Windows only) c. http://your.isy.ip.address/admin - applet d. http://your.isy.ip.address/admin.jnlp - Java application e. http://www.universal-devices.com/99i/3.1.9 - applet f. http://www.universal-devices.com/99i/3.1.9/admin.jnlp - Java application Dashboard - not fully supported - http://www.universal-devices.com/99i/3. ... board.jnlp 8. Please backup your system again Thanks and with kind regards, Michel Quote Link to comment Share on other sites More sharing options...
LeeG Posted September 21, 2011 Share Posted September 21, 2011 Install of 3.1.9 was successful. Log file was not lost. It is now accessible under 3.1.9 Quote Link to comment Share on other sites More sharing options...
Brian H Posted September 21, 2011 Share Posted September 21, 2011 Same with me. No install issues and the logs where still there. Quote Link to comment Share on other sites More sharing options...
TJF1960 Posted September 21, 2011 Share Posted September 21, 2011 Hi Michel, Thanks very much for this newest beta. Everything went smoothly and it is very nice to have the logs back! Log file was not lost. It is now accessible under 3.1.9Hi Lee, Did your log contain a full day of info while you were running 3.1.8? My log shows reboot and query yesterday morning after upgrading to 3.1.8 then the log cuts right to reboot and query after upgrading today to 3.1.9, nothing in the middle from yesterday morning query to this afternoons query. Thanks, Tim Quote Link to comment Share on other sites More sharing options...
LeeG Posted September 21, 2011 Share Posted September 21, 2011 TJF1960 Looks like Log was not functional during time 3.1.8 was installed. I even tried a Clear Log to see if I could get rid of the errors on 3.1.8 and that did not clear the log. Looks like all Log activity of any kind was not functional on 3.1.8. Lee Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted September 21, 2011 Author Share Posted September 21, 2011 Hi Guys, Unfortunately the problem was that the loggers were not being registered in the log manager and thus the reason for not having any logs for the duration of 3.1.8. LeeG, are you saying that you cannot clear the logs? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
LeeG Posted September 21, 2011 Share Posted September 21, 2011 Michel Sorry for the confusion. I issued the Clear Log under 3.1.8 to see if that would resolve the errors being encountered when accessing the Log file. It did not. When I installed 3.1.9 and displayed the Log file I found it in tact (except for the missing entries from 3.1.8 that Tim noted) indicating the Clear Log issued under 3.1.8 had no effect. Everything under 3.1.9 is running fine. I add my thanks for such a quick resolution. Lee Quote Link to comment Share on other sites More sharing options...
Teken Posted September 22, 2011 Share Posted September 22, 2011 First attempt with 3.1.8 failed, upon second attempt the upgrade went fine. Tried the newest beta release of 3.1.9 tonight and the same *first* upgrade failed. Performing a second upgrade completed fine . . . The UI does appear to load much faster as one member had noted prior. All systems appear to be fully operational and was able to perform a full back up with out fault. One thing to note is that from work I can not make the ISY show the true status of the devices once I turn them on / off. If I didn't have 16 cameras running in the home I would not be able to confirm the status. I am not sure why this behavior exists to be honest. Normally when I log in from a public address the ISY will alert me of any of the appliance links which are not plugged in. So from there I have to close all of the pop up windows. When I am at work none of the 12 Appliance links which are unplugged show up as being a problem??? This is how I know the ISY has not loaded correctly, or perhaps not able to communicate fully to me on my end. PS The weather bug also does not populate either and this is also another indicator to me that the ISY will not show me the on / off status. Insight?? Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted September 22, 2011 Author Share Posted September 22, 2011 Hello LeeG, thanks so very much for the clarification! Teken, the reason you are not seeing the status of devices at work is probably because you either have corporate firewalls or a software firewall which blocks ISY from publishing events to your computer at work. Do you know what type of firewall you have? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
Baypointe Posted September 22, 2011 Share Posted September 22, 2011 I am having trouble adding items to wake on lan. It says "Invalid mac address format. Valid values are A-F, 0 to 9 seperated by a -" I used to be able to add them by copy/paste from router with the ":" but even when I try the - it will not let me add or adjust the ones I have. Jim Quote Link to comment Share on other sites More sharing options...
TomW Posted September 22, 2011 Share Posted September 22, 2011 Upgraded from 2.8.16 without any problems. Now I need to learn about variables. Thanks for all the new features and bug fixes. /Tom Quote Link to comment Share on other sites More sharing options...
TJF1960 Posted September 22, 2011 Share Posted September 22, 2011 I am having trouble adding items to wake on lan. It says "Invalid mac address format. Valid values are A-F, 0 to 9 seperated by a -" I used to be able to add them by copy/paste from router with the ":" but even when I try the - it will not let me add or adjust the ones I have. Jim Jim, I have the same problem. Found that the lower case letters were the problem. Changed to upper case letters then I could save. Tim Quote Link to comment Share on other sites More sharing options...
Teken Posted September 22, 2011 Share Posted September 22, 2011 Teken, the reason you are not seeing the status of devices at work is probably because you either have corporate firewalls or a software firewall which blocks ISY from publishing events to your computer at work. Do you know what type of firewall you have? With kind regards, Michel Yes, it must be the firewall at work. Strange thing is that once in a blue moon the ISY does pop up the devices not found and plugged in. This happens maybe once out of 30-40 attempts though . . . Quote Link to comment Share on other sites More sharing options...
Candide Posted September 22, 2011 Share Posted September 22, 2011 Updated from 3.1.7 - so far no problems. Quote Link to comment Share on other sites More sharing options...
TJF1960 Posted September 22, 2011 Share Posted September 22, 2011 Can anyone please verify wol is working and sending out the magic packets in 3.1.7. I can't seem to capture the packets leaving isy when tested. Thanks, tim Quote Link to comment Share on other sites More sharing options...
rlebel Posted September 23, 2011 Share Posted September 23, 2011 No idea if this is related to the release, (and this is actual 3.1.8 not 3.1.9) but I just replaced a 2441V (classy of Smarthome to send free updates with no hassle). I installed and then replaced the old one and it has now been updating for over 40 minutes. The thermostat is only used in one program and not linked to anything. Here is the start of the log, the GET-NEXT-LNK-RSP and LNK-DATA messages are going on and on: Thu 09/22/2011 16:50:11 : Linked: Linked 14.23.A0.00 type=05.03.FFFFFF92 Thu 09/22/2011 16:50:11 : [14.23.A0 - Main] Start : Adding device to ISY Thu 09/22/2011 16:50:12 : [14.23.A0 - Main] Finish : Adding device to ISY was Successful Thu 09/22/2011 16:50:12 : [14.23.A0 - Cool Control] Start : Adding device to ISY Thu 09/22/2011 16:50:12 : [14.23.A0 - Cool Control] Finish : Adding device to ISY was Successful Thu 09/22/2011 16:50:12 : [14.23.A0 - Heat Control] Start : Adding device to ISY Thu 09/22/2011 16:50:12 : [14.23.A0 - Heat Control] Finish : Adding device to ISY was Successful Thu 09/22/2011 16:50:12 : [14.23.A0 - Fan Control] Start : Adding device to ISY Thu 09/22/2011 16:50:12 : [14.23.A0 - Fan Control] Finish : Adding device to ISY was Successful Thu 09/22/2011 16:50:12 : [All ] Writing 0 bytes to devices Thu 09/22/2011 16:50:39 : Linked: Linked 14.23.A0.00 type=05.03.FFFFFF92 Thu 09/22/2011 16:50:39 : [All ] Writing 0 bytes to devices Thu 09/22/2011 16:50:49 : Linked: Linked 14.23.A0.00 type=05.03.FFFFFF92 Thu 09/22/2011 16:50:49 : [All ] Writing 0 bytes to devices Thu 09/22/2011 16:51:54 : [ 11 BE 3B 1] CLIMD 0 Thu 09/22/2011 16:51:54 : [ 11 C0 3D 1] CLIHUM 60 Thu 09/22/2011 16:51:54 : ---- Initializing the linked devices ---- Thu 09/22/2011 16:51:54 : [ 14 23 A0 1] Removing all links Thu 09/22/2011 16:52:04 : ---- All Linked Devices are now initialized ---- Thu 09/22/2011 16:52:07 : [All ] Writing 40 bytes to devices Thu 09/22/2011 16:52:07 : [14 23 A0 1 ] Link 0 : 0FF8 [A200129C44000000] Writing [A200129C44000000] Thu 09/22/2011 16:52:16 : [PLM ] Group 0 : Writing Controller Link matching [14 23 A0 1 ] Link 0 : 0FF8 [A200129C44000000] Thu 09/22/2011 16:52:16 : [14 23 A0 1 ] Link 1 : 0FF0 [E2EF129C44FF1FEF] Writing [E2EF129C44FF1FEF] Thu 09/22/2011 16:52:25 : [PLM ] Group 239 : Writing Responder Link matching [14 23 A0 1 ] Link 1 : 0FF0 [E2EF129C44FF1FEF] Thu 09/22/2011 16:52:25 : [14 23 A0 1 ] Link 2 : 0FE8 [E201129C44FF1F01] Writing [E201129C44FF1F01] Thu 09/22/2011 16:52:34 : [PLM ] Group 1 : Writing Responder Link matching [14 23 A0 1 ] Link 2 : 0FE8 [E201129C44FF1F01] Thu 09/22/2011 16:52:34 : [14 23 A0 1 ] Link 3 : 0FE0 [E202129C44FF1F02] Writing [E202129C44FF1F02] Thu 09/22/2011 16:52:44 : [PLM ] Group 2 : Writing Responder Link matching [14 23 A0 1 ] Link 3 : 0FE0 [E202129C44FF1F02] Thu 09/22/2011 16:52:44 : [14 23 A0 1 ] Link 4 : 0FD8 [E203129C44FF1F03] Writing [E203129C44FF1F03] Thu 09/22/2011 16:52:54 : [PLM ] Group 3 : Writing Responder Link matching [14 23 A0 1 ] Link 4 : 0FD8 [E203129C44FF1F03] Thu 09/22/2011 16:52:55 : ---- Initializing the linked devices ---- Thu 09/22/2011 16:52:55 : ---- All Linked Devices are now initialized ---- Thu 09/22/2011 16:52:55 : [All ] Writing 0 bytes to devices Thu 09/22/2011 16:52:55 : [ 14 23 A0 1] ST 152 Thu 09/22/2011 16:52:55 : [ 14 23 A0 1] CLIMD 0 Thu 09/22/2011 16:52:55 : [ 14 23 A0 1] UOM 2 Thu 09/22/2011 16:52:55 : [ 14 23 A0 1] CLIHUM 0 Thu 09/22/2011 16:53:21 : [All ] Writing 0 bytes to devices Thu 09/22/2011 16:53:22 : [All ] Writing 0 bytes to devices Thu 09/22/2011 16:53:23 : [ 11 C0 3D 1] CLIHUM 61 Thu 09/22/2011 16:53:24 : [All ] Writing 0 bytes to devices Thu 09/22/2011 16:53:25 : [14.23.A0 - Main] Start : Removing device from ISY Thu 09/22/2011 16:53:26 : [14.23.A0 - Main] Finish : Removing from ISY was Successful Thu 09/22/2011 16:53:26 : [All ] Writing 0 bytes to devices Thu 09/22/2011 16:53:27 : [11 C0 3D 1] Start : Replace device with '14 23 A0 1' type='5 3 92 0' Thu 09/22/2011 17:00:19 : [MNG-LNK-RSP ] 02 6F 80 A2 EF 11 C0 3D 00 00 00 15 Thu 09/22/2011 17:00:20 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:20 : [LNK-DATA ] 02 57 E2 11 12 D3 83 02 09 38 Thu 09/22/2011 17:00:20 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:20 : [LNK-DATA ] 02 57 E2 18 11 30 F3 01 00 37 Thu 09/22/2011 17:00:21 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:21 : [LNK-DATA ] 02 57 E2 14 12 D3 83 02 09 38 Thu 09/22/2011 17:00:21 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:21 : [LNK-DATA ] 02 57 A2 01 12 D3 83 02 09 38 Thu 09/22/2011 17:00:22 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:22 : [LNK-DATA ] 02 57 A2 02 12 D3 83 02 09 38 Thu 09/22/2011 17:00:22 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:22 : [LNK-DATA ] 02 57 A2 03 12 D3 83 02 09 38 Thu 09/22/2011 17:00:23 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:23 : [LNK-DATA ] 02 57 A2 04 12 D3 83 02 09 38 Thu 09/22/2011 17:00:23 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:23 : [LNK-DATA ] 02 57 A2 05 12 D3 83 02 09 38 Thu 09/22/2011 17:00:24 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:24 : [LNK-DATA ] 02 57 A2 06 12 D3 83 02 09 38 Thu 09/22/2011 17:00:24 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:24 : [LNK-DATA ] 02 57 A2 07 12 D3 83 02 09 38 Thu 09/22/2011 17:00:25 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:25 : [LNK-DATA ] 02 57 A2 08 12 D3 83 02 09 38 Thu 09/22/2011 17:00:25 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:25 : [LNK-DATA ] 02 57 E2 24 12 D4 0A 02 09 38 Thu 09/22/2011 17:00:26 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:00:26 : [LNK-DATA ] 02 57 E2 23 12 D4 0A 02 09 38 Thu 09/22/2011 17:00:26 : [GET-NEXT-LNK-RSP] 02 6A 06 And 40 minutes later: Thu 09/22/2011 17:43:20 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:43:20 : [LNK-DATA ] 02 57 E2 00 11 DD 98 01 03 37 Thu 09/22/2011 17:43:21 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:43:21 : [LNK-DATA ] 02 57 E2 14 11 DD 98 01 03 37 Thu 09/22/2011 17:43:21 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:43:21 : [LNK-DATA ] 02 57 A2 01 11 DD 98 01 03 37 Thu 09/22/2011 17:43:22 : [GET-NEXT-LNK-RSP] 02 6A 06 Thu 09/22/2011 17:43:22 : [LNK-DATA ] 02 57 A2 02 11 DD 98 01 03 37 Quote Link to comment Share on other sites More sharing options...
LeeG Posted September 23, 2011 Share Posted September 23, 2011 rlebel Those commands are reading through the PLM link database looking for entries that have the old device address. The first part of Replace with took some 7 minutes to get to the point where the PLM link database is being processed. Let it run to completion. Lee Quote Link to comment Share on other sites More sharing options...
ELA Posted September 23, 2011 Share Posted September 23, 2011 Just updated from 3.1.6 which appeared to have lots of issues. Now in 3.1.9. I never get any information the in the current state windows. If I do a query this still will not populate the current state window. I am still having the issue where changes I make to scenes or simple renaming will not show until I exit and re-enter? Is this some other issue? Things were fine until I upgraded to 3.1.6. The further upgrade to 3.1.9 does not appear to have helped my issues? Quote Link to comment Share on other sites More sharing options...
LeeG Posted September 23, 2011 Share Posted September 23, 2011 rlebel Be sure NO Insteon traffic other than that associated with the Replace reaches the PLM. The process of reading PLM link records will be disturbed possibly repeating large portions of the link database if Insteon messages are received because other Insteon devices are being turned On and Off. Lee Quote Link to comment Share on other sites More sharing options...
TJF1960 Posted September 23, 2011 Share Posted September 23, 2011 ELA, Out of curiosity what internet browser are you using? Michel, I am still getting a lot of errors in the log (typical log size about 24 KB a day) such as: Time User Code Message Thu 2011/09/22 08:29:37 AM System -170001 [Auth] 192.168.0.167:2664->80, Num=2 Thu 2011/09/22 08:36:23 AM System -170001 [Auth] 192.168.0.167:3490->80, Num=2 Thu 2011/09/22 08:39:27 AM System -170001 [Auth] 192.168.0.167:3962->80, Num=2 Thu 2011/09/22 08:42:23 AM System -170001 [Auth] 192.168.0.167:4358->80, Num=2 Thu 2011/09/22 08:46:23 AM System -170001 [Auth] 192.168.0.167:4989->80, Num=2 Thu 2011/09/22 08:47:38 AM System -170001 [Auth] 192.168.0.167:1184->80, Num=2 Thu 2011/09/22 08:48:53 AM System -170001 [Auth] 192.168.0.167:1326->80, Num=2 Thu 2011/09/22 08:54:09 AM System -170001 [Auth] 192.168.0.167:1944->80, Num=2 Thu 2011/09/22 09:04:07 AM System -170001 [Auth] 192.168.0.167:3155->80, Num=2 Thu 2011/09/22 09:07:38 AM System -170001 [Auth] 192.168.0.167:3576->80, Num=2 Thu 2011/09/22 09:12:21 AM System -140005 CLI-WBug Thu 2011/09/22 09:12:23 AM System -170001 [Auth] 192.168.0.167:4110->80, Num=2 Thu 2011/09/22 09:12:34 AM System -170001 [Auth] 192.168.0.167:4130->80, Num=2 Thu 2011/09/22 09:14:27 AM System -140005 Net Module Rule: 106 Thu 2011/09/22 09:25:45 AM System -140005 Net Module Rule: 106 Thu 2011/09/22 09:26:24 AM System -140005 Net Module Rule: 106 Thu 2011/09/22 09:26:31 AM System -140005 Net Module Rule: 106 Thu 2011/09/22 09:27:26 AM System -140005 CLI-WBug Thu 2011/09/22 09:39:00 AM System -170001 [Auth] 192.168.0.167:3337->80, Num=2 Thu 2011/09/22 09:41:40 AM System -170001 [Auth] 192.168.0.167:3672->80, Num=2 Thu 2011/09/22 09:45:25 AM System -170001 [Auth] 192.168.0.167:4160->80, Num=2 Thu 2011/09/22 09:47:21 AM System -140005 CLI-WBug Thu 2011/09/22 09:53:59 AM Even with the continued errors my system seems to be rock solid. In fact, everything seems to be running the very best it has ever been! DSCLink and 2 WCLinks are working very well with ISY. Many thanks for all of the hard work. Tim Quote Link to comment Share on other sites More sharing options...
polexian Posted September 23, 2011 Share Posted September 23, 2011 If I push Link Management->Start Linking. The red X doesn't close out the linking in progress. In order to stop the linking process I force closed the applet. When restarting the admin console the current state doesn't update. In order to fix this, Remove power cable from isy/99i and then you have to reinstall 3.1.9, then restore plm, then restore devices under the file menu. When you click these, you will not get feedback from the gui, but instead you have to open up the orchestrator console to see the feedback and the complete status of this command. Request the status feedbacks when deleting, adding, restoring plm, and restoring devices and any other commands that gives a pop up window be removed from the main html admin interface and have a secondary window to show the current status. Joe Quote Link to comment Share on other sites More sharing options...
rlebel Posted September 23, 2011 Share Posted September 23, 2011 Lee, thanks for your responses. It is of course very difficult to ensure a quiet network in an occupied home, even more so with thermostats reporting temperature and humidity changes. I went out for the evening and came back with the activity still continuing after about 5 hours so I rebooted. I then added the second updated 2441V and went to bed (of course, there was some insteon activity while going to bed). That PM activity did terminate. But I'm left with a few questions: (1) isn't the PLM read and written though the USB connection? Why should Insteon activity interfere with reading/writing it? (2) doesn't the ISY-99 know what should be in the PLM already? and (3) now that I have aborted at least one PLM checking process, is there something I should do to insure that my PLM and ISY are indeed in sync? I should note that my Insteon network is not 100% reliable, and I have somewhat given up fixing it after numerous attempts and filters. Thanks Moderator: sorry for this off topic discussion, please move it if you want. Quote Link to comment Share on other sites More sharing options...
LeeG Posted September 23, 2011 Share Posted September 23, 2011 rlebel The PLM commands to read the PLM link database do go through the serial interface. The Get Next PLM command is dependent on a NEXT record field internal to the PLM. Each Get Next command sets the NEXT field to the next available PLM link record. Unfortunately if the PLM receives an inbound Insteon message the link database is searched looking for a match. This search changes the NEXT field to point to the PLM link record following the matching link record to the inbound message. The Get Next issued to read the next record related to the Replace is no longer the correct record. This symptom is most often seen when running a Show PLM Links Table command. Any inbound Insteon traffic changes the NEXT field and leads to impossibly high link record counts because link records are being accessed multiple times or too low as link records are skipped. EDIT: the ISY does not access PLM link records directly. That would require tracking were each link record is located in the PLM. I don't know the implications of rebooting during the Replace operations. I would not expect it to cause intermittant powerline problems. Lee Quote Link to comment Share on other sites More sharing options...
brentrosales Posted September 23, 2011 Share Posted September 23, 2011 Is anyone else having an issue adding a new Scene with this update? I am getting "Subscriber didn't reply to event: 1 [26]" OR "Request Failed" Brent Quote Link to comment Share on other sites More sharing options...
ELA Posted September 23, 2011 Share Posted September 23, 2011 I am using Firefox browser. The strange thing is that I used a laptop also via Firefox and I do get status from there? Something to do with Firefox version or plug-ins??? I just had two programs fail to run as well???? Here is what I have in my error log: Time User Code Message Fri 2011/09/23 09:45:38 AM System -5012 27 Fri 2011/09/23 09:49:15 AM System -170001 [uDSockets] RSub:33 error:6 Any ideas would be appreciated. I am going to compare Firefox versions etc. I was not too concerned about missing status but two programs failing to run does concern me. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.