Jump to content

Errors, Busy Message, & Unable to Backup ISY


SteveSBE

Recommended Posts

Hi - 

I am running v.4.7.3 firmware and UI on an ISY 994i/IR PRO (1110). I use the Admin application on Windows 10 and run the Windows Defender firewall software. I've made additions to my Insteon hardware and made many program improvements in the past couple days. Although I've made backups of the programs that I've changed or added, my most recent ISY backup is from January 9th (as you'll see below).

 

My issue....

I had a problem with a long-lasting "System Busy" dialog box in the Admin application every time I updated and saved a program. The message has recently showed a message at the bottom of the window that "DB cannot load /CONF/1B2299.REC" (Figure 1). It usually took 15-30 seconds for the dialog box to go away. 

Figure 1    image.png.59408a1e744cded8c5e9097ad9de9251.png

Today I downloaded the Error Log and noticed the errors in Figure 2 below.  There were a very many more -170001 errors than the -110014 errors that mentioned "/CONF/1B2299.REC". 

Figure 2    image.png.e910e406cfcdf6fa9fa65a528bb2530f.png

So I read through the forum and saw an issue related to a long-lasting "System Busy" dialog box, in which it was advised to uncheck the UPnP box on the System Configuration. I did that and the change forced a re-boot of the ISY. The long-lasting "System Busy" dialog box (Figure 3) continued but the "DB cannot load /CONF/1B2299.REC" message did not appear. 

Figure 3    image.png.329bec2a86424030c25fb7cb952378ae.png

I also downloaded the Error Log again and showed the following messages.  There were over 57,000 of the "-170001 [UDSockets] PSub:41 error:6" error messages followed by the error code -5012 and the other error codes below it (Figure 4).  

Figure 4    image.png.7806d363245d8ff6819c472b4ec7f151.png

I thought I had made a recent backup but when I looked at the size of my most recent backup file taken on 1/24, it was only 1 KB. So I know that backup didn't work. I tried to take another backup today (1/31). I got a message that the backup zip file couldn't be created and also got the message below (Figure 5) that it "Could Not Retrieve file /CONF/1B2299.REC".  The size of the file was also only 1 KB.  I looked at the backup files I've stored and the most recent successful backup I have (based on the 196 KB size) was taken on January 9th. 

Figure 5   image.png.3468bc7c888dded7098cea3ab5978a09.png

I suspect these issues are related but can someone explain to me: 

      1. Why the "System Busy" dialog lasts so long and how can I fix that?

      2. What the "/CONF/1B2299.REC" file stores, what issue is with it, and if it can be fixed?

 

If I have to use the 1/9/18 restore to fix the problems, I would like to know how I can do that without losing the many added devices and many changes and additions to my programs that I've made in the past couple days. For example, are there options that just allow me to fix the "/CONF/1B2299.REC" file if that's the culprit? 

Thanks,

Steve

 

 

 

Link to comment

Techman - On Sunday I will clean the card contacts to see if that fixes the issue. (Too many commitments until Sunday.) 

Paul - Since I haven't see a lot of response, I'll be trying Techman's suggestion. Bue even if Techman's method works I feel that replacing the existing SD card is prudent for the long term. My question about using the method in your link is.... Will I loose any changes (added devices or programs) by following that method? 

Thanks,

Steve

 

Link to comment
5 hours ago, SteveSBE said:

Paul - Since I haven't see a lot of response, I'll be trying Techman's suggestion. Bue even if Techman's method works I feel that replacing the existing SD card is prudent for the long term. My question about using the method in your link is.... Will I loose any changes (added devices or programs) by following that method? 

Thanks,

Steve

 

Steve:

Unfortunately if there were changes between your last good backup and now, then yes... you would lose those changes.

I'm kind of in the same boat, in that my ISY is sneaking up on 5 years and I'm wanting to put a new SD card in it. I've wondered if the old card image could be drug across to the new... :

  • Insert the old card into the SD slot of a PC.
  • "Drag" a copy the contents off of the old card on to the PC in a folder
  • Following step 2 of the wiki, format the new card:
    • Turn off the ISY and put the new card in the ISY, restart it
    • Telnet in to the the ISY and issue an FS on the new card in the ISY
  • Replace the old card with new card in the reader on the PC and copy that image on to the new card
  • Insert that in the ISY, and see what happens

You could try that experiment, worst case you still have the old card.

Paul

 

 

Link to comment

Techman - The "eraser method" that you suggested didn't help. I still cannot backup the card. Thanks for the suggestion though. 

Paul - I'm going to try the copy method as you suggested. I'm not sure if you can help me with these questions but I'll ask anyways... The backup always stops at the 1B2299.REC file and I'd like to know what the consequences would be if the file cannot be copied either.  Is there a list of the specific function or purpose each file that might tell me if this file is updated frequently? Is it file a stable file that could be copied from an old backup without any issues? Would it be automatically created if I cannot get a current copy of it?   

Thanks for your replies, help, and suggestions. 

Steve

Link to comment
1 hour ago, SteveSBE said:

Techman - The "eraser method" that you suggested didn't help. I still cannot backup the card. Thanks for the suggestion though. 

Paul - I'm going to try the copy method as you suggested. I'm not sure if you can help me with these questions but I'll ask anyways... The backup always stops at the 1B2299.REC file and I'd like to know what the consequences would be if the file cannot be copied either.  Is there a list of the specific function or purpose each file that might tell me if this file is updated frequently? Is it file a stable file that could be copied from an old backup without any issues? Would it be automatically created if I cannot get a current copy of it?   

Thanks for your replies, help, and suggestions. 

Steve

Steve

I believe that’s the definition of the Insteon device with the address 1B2299. If the admin console still works, go to main, sort the colum by Insteon address to see what it is. If you can, see what scenes and programs it’s in and make a note. Try to delete it... maybe that gets you a back up, and you have to fix one device only.  Definitely move to a new card.

Try the copy if that won’t work, same downside, the ISY will forget the device at that address. Sometimes I’ve been able to reinstall a device that was deleted and scenes/programs come back

hopefully one of theses gets you going with minimal fixes..

Paul

Link to comment

I mentioned it in the 5.0.14 thread, but I've had good luck just copying the file from an old backup onto the SD card.  I couldn't back up my ISY because of a 0-length .REC file that had apparently become corrupt and copying a good version fixed it.  Once you do that and have a current backup, I'd switch to a new SD card and restore that backup.

Link to comment
7 hours ago, paulbates said:

Steve

I believe that’s the definition of the Insteon device with the address 1B2299. If the admin console still works, go to main, sort the colum by Insteon address to see what it is. If you can, see what scenes and programs it’s in and make a note. Try to delete it... maybe that gets you a back up, and you have to fix one device only.  Definitely move to a new card.

Try the copy if that won’t work, same downside, the ISY will forget the device at that address. Sometimes I’ve been able to reinstall a device that was deleted and scenes/programs come back

hopefully one of theses gets you going with minimal fixes..

Paul

 

Paul -

Thanks much for your help! It worked!

I did it as follows:

  1. Backed up the ISY to make sure that was the only bad file...the backup completed successfully.
  2. Identified all scenes that contained the switchlinc...there was only one.
  3. Identified all programs that used the switchlinc and/or scene.
  4. Deleted the device (a switchlinc).
  5. Removed the switchlinc from the one scene in which it was located.
  6. Removed two other switchlincs from the same scene (since all switchlincs contained errant links).
  7. Left the RemoteLinc in the scene.
  8. Added all three switchlincs back to the scene .
  9. Selected and updated every command that used the switchlinc or scene for each program identified in step 3.
  10. Backed up the ISY...successfully.
  11. Made a note to pick up a new micro SD card to replace the current one.

Thanks much for your recommendations and ideas.  Really appreciated...

Steve

Link to comment

Archived

This topic is now archived and is closed to further replies.


  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      36.9k
    • Total Posts
      370.2k
×
×
  • Create New...