Loading ...

How to count lines--Configuration file warning: Invalid value on line X | UPS Management Devices & PowerChute Software

Home » Spaces » UPS Management Devices & PowerChute Software » discussion » General » How to count lines--Configuration file warning: Invalid value on line X

How to count lines--Configuration file warning: Invalid value on line X

Discussion in UPS Management Devices & PowerChute Software started by Jeff , 9/13/2019 4:06 PM
Login to follow, share, and participate in this space.
Not a member?Join now
Announcement 

Please review Schneider Electric Knowledge Base articles for assistance with most technical support questions.  http://www.apc.com/us/en/faqs

Posted in: General

How to count lines--Configuration file warning: Invalid value on line X

Subscribe to RSS
  • JohnsIsland

    Good Friday morning!

    When I see the error, Configuration file warning:: Invalid value on line X, I am not sure which lines to count in the INI file to determine where the problem is.  Do I count lines which are commented out (with a ;), blank lines or head lines (where the line begins with a [ and ends with a ])?

    Thanks,

     

    Jeff

  • JohnsIsland

    Another variable, do I count the lines in the INI file I uploaded or should I download the INI file after receiving the error message and count the lines in the downloaded file?

  • JohnsIsland

    I cut the file I was uploading so I could whittle away and figure out which line was bad.  I received the same error messages including invalid value on line 23.  Given the file below, I think the error message is reporting what's bad in the file running on the NMC.  Will downloading the INI file and counting lines (which lines) give me the error lines?  Or is the invalid value on line X not related to a line in the INI file?

     

    One way to fix the problem is to download from a different NMC, upload it to make sure it doesn't generate invalid values, modify it if nessecary, and upload it to the NMC that is returning invalid values after uploading.  Yes, I did make more than one change at a time and didn't keep a copy of the file before I made multiple changes.  Hopefully I will remember to keep a copy of the INI and/or make one change at a time.

    Jeff

    ; Schneider Electric
    ; Network Management Card AOS v6.6.4
    ; Smart-UPS & Matrix-UPS APP v6.6.4
    ; (c) Copyright 2003 - 2018 All Rights Reserved
    ; Configuration file, generated on 11/07/2018 at 21:13:03 by Administrator apc

    [NetworkTCP/IP]

    IPv4=enabled
    BootMode=DHCP Only
    DomainName=bmain.bsf
    PortSpeed=Auto
    DHCPBootpVendorClass=APC
    DHCPBootpClientID=MAC
    DHCPBootpUserClass=SUMX
    DHCPRequireCookie=disabled
    PingResponse=enabled
    IPv6=disabled
    IPv6DefaultGateway=::
    IPv6IP=::/64
    IPv6Manual=disabled
    IPv6AutoConfig=enabled
    DHCPv6Mode=Router Controlled

     

  • JohnsIsland

    I have been testing to see if I can clear the errors by formatting and uploading firmware. Testing with a SUA750XL and a AP9630.  I have formatted by pressing the reset button until I see the right NIC LED flashing orange.  After formatting I have uploaded the same F/W (6.6.4).  I then download and upload the config.ini using the ini utility.  After the upload is complete, I open the device log file and find the errors listed below.

    How do I resolve the errors I am finding? 

     

     09/16/2019 12:22:47 apc Web user 'apc' logged in from 172.26.106.66.
     09/16/2019 12:22:46 System Configuration file upload complete, with 895 valid values.
     09/16/2019 12:21:42 System Configuration file warning: Invalid value on line 369.
     09/16/2019 12:21:42 System Configuration file warning: Invalid value on line 367.
     09/16/2019 12:21:42 System Configuration file warning: Invalid value on line 366.
     09/16/2019 12:21:42 System Configuration file warning: Invalid value on line 365.
     09/16/2019 12:21:41 System Configuration file warning: Invalid value on line 364.
     09/16/2019 12:21:41 System Configuration file warning: Invalid value on line 363.
     09/16/2019 12:21:41 System Configuration file warning: Invalid value on line 362.
     09/16/2019 12:21:41 System Configuration file warning: Invalid value on line 361.
     09/16/2019 12:21:41 System Configuration file warning: Invalid value on line 360.
     09/16/2019 12:21:41 System Configuration file warning: Invalid value on line 359.
     09/16/2019 12:21:41 System Configuration file warning: Invalid value on line 358.
     09/16/2019 12:21:41 System Configuration change. Event log web display filter category.
     09/16/2019 12:21:40 System Configuration change. Event log web display filter severity.
     09/16/2019 12:21:37 System Configuration change. System name.
     09/16/2019 12:21:32 System Configuration change. Host name.
     09/16/2019 12:21:31 apc FTP user 'apc' logged out from 172.26.106.66.
     09/16/2019 12:21:28 apc FTP user 'apc' logged in from 172.26.106.66.
     09/16/2019 12:21:28 apc FTP user 'apc' logged out from 172.26.106.66.
     09/16/2019 12:21:28 apc FTP user 'apc' logged in from 172.26.106.66.
     09/16/2019 12:20:45 apc FTP user 'apc' logged out from 172.26.106.66.
     09/16/2019 12:20:28 apc FTP user 'apc' logged in from 172.26.106.66.
     09/16/2019 12:20:28 apc FTP user 'apc' logged out from 172.26.106.66.
     09/16/2019 12:20:28 apc FTP user 'apc' logged in from 172.26.106.66.
     09/16/2019 12:19:42 apc FTP user 'apc' logged out from 172.26.106.66.
     09/16/2019 12:19:23 apc FTP user 'apc' logged in from 172.26.106.66.
     09/16/2019 12:19:23 apc FTP user 'apc' logged out from 172.26.106.66.
     09/16/2019 12:19:23 apc FTP user 'apc' logged in from 172.26.106.66.
     09/16/2019 12:17:41 Device UPS: Restored the local network management interface-to-UPS communication.
     09/16/2019 12:17:37 System Network service started. System IP is 172.26.222.84 from DHCP server 172.26.106.62 with 604790 second lease.
     09/16/2019 12:17:24 System Network service started. IPv6 address FE80::2C0:B7FF:FED7:2CF2 assigned by link-local autoconfiguration.
  • JohnsIsland

    I forgot to mention, when downloading the file it takes about 20-22 seconds.  When uploading it takes 3-4 seconds.  Is the upload process terminating early due to corruption?

  • JohnsIsland

    I found the 6.8 F/W upgrade today.  I formatted a AP9630, then to 6.8, and found only one invalid value after using the ini utility.  I need to test a bit more, as I am working on a different AP9630 card today.  Hopefully the F/W update is the cause for the reducing the invalid values.

    It would be nice if someone from APC would weigh in on the problems I have/am seeing.

    Kind of curious why the 6.8 is in a different section of the AP9630 download page.

    Jeff

  • JohnsIsland

    After updating a AP9631 to v6.8.0/v6.8.2/v1.0.9 in a SMX2000LV with UPS 07.4 (ID1003), I downloaded the user config file and uploaded the same user config file and found only one error: SystemConfiguration file warning: Invalid value on line 239.  That is quite an improvement.

    Just for fun, I copied the aforementioned user config file into Excel, and found line 239: DeviceCommCtrl="", which is in the NetworkBACnet section.  I don't have a clue if that is the problem line or if the problem line is elsewhere.  I did see a possible error in the BACnet/IP GUI, the check box is on the line above Enable foreign device registration. 

    I just enabled BACnet, and had to enter a password.  I downloaded the config file and uploaded the same config file.  Amazing, the Invalid value on line 239 error did not appear.  I then disabled BACnet, downloaded and uploaded the file and the error did not appear.  I think this means the NIC doesn't like an empty value in DeviceCommCtrl="".  

    I would ask APC to fix this itty bitty error.  Until APC fixes the error, I will add a valid password to the user config file so the APC Events log is clean, in order to satisfy my A/R desire to ensure I don't have any errors which could cause problems with mission critical equipment. 

    Jeff

     

  • JohnsIsland

    If someone from APC would submit a request to fix the bug I think I found, and so notes this thread, I will mark it as answered/closed.

Page 1 of 1 (8 items)
Choose your language:  
powered by Communifire
Version 6.0.7207.29305