This was working and then the http interface now does not show the cameras anymore.
using the console all seems fine. I have tried multiple browsers and well as rebooting the NVR
Any way to fix this?
Brand new NV4108E-A2
was working now "Config file error"
was working now "Config file error"
- Attachments
-
- live.jpg (59.18 KiB) Viewed 2234 times
Re: was working now "Config file error"
Hello and Welcome to the Forum
I would do a Factory Reset. Try that..
I would do a Factory Reset. Try that..
Be Safe.
Re: was working now "Config file error"
First I tried the "reset" that id not fix the "Config file error"
Next i did "factory defaults" and after redoing the install and adding cameras it still did not fix "Config file error"
I went to "search" and see that the old videos are still there so "factory defaults" does not reinitialize the disk.
My guess is the "config file" is on the hard drive. I don't see anyway to format it other than pulling it out.
I can't be the only person that has had this problem. Is there any software updates for this?
Next i did "factory defaults" and after redoing the install and adding cameras it still did not fix "Config file error"
I went to "search" and see that the old videos are still there so "factory defaults" does not reinitialize the disk.
My guess is the "config file" is on the hard drive. I don't see anyway to format it other than pulling it out.
I can't be the only person that has had this problem. Is there any software updates for this?
Re: was working now "Config file error"
Can you look in your NVR and see if there is a Reset button on the inside. If there is you will need to do a Factory Reset of the NVR over the Button. Not all NVRs have the Reset button, If it don't but a pad where one could be installed. Even then a button reset won't work because there is also missing things in the Circuit that wouldn't let it. But if it does have the button I would try to reset with button.
Firmware on the NVR is in ROM and not loaded on your HDD.. So while the HDD could be the issue I would maybe remove the power cable to the HDD while in there and boot back into the NVR and see if the error is away with out the HDD intalled. Both the Power and data cable should be un plugged from HDD.. Keep in mind it will beep if you have not disabled the alarm with no HDD installed that is how it comes factory..
Firmware on the NVR is in ROM and not loaded on your HDD.. So while the HDD could be the issue I would maybe remove the power cable to the HDD while in there and boot back into the NVR and see if the error is away with out the HDD intalled. Both the Power and data cable should be un plugged from HDD.. Keep in mind it will beep if you have not disabled the alarm with no HDD installed that is how it comes factory..
Be Safe.
Re: was working now "Config file error"
I found the format button. reformatted the drive, problem still exists. Weird, huh.
this post looks to have reported the same issue.
https://amcrest.com/forum/nvrs-dvrs-f19 ... 16634.html
I am now testing with only one POE camera, I changed to H.264 per your recommendation.
all works fine on the console but even "cameras" on http shows nothing, not even the POE camera.
this post looks to have reported the same issue.
https://amcrest.com/forum/nvrs-dvrs-f19 ... 16634.html
I am now testing with only one POE camera, I changed to H.264 per your recommendation.
all works fine on the console but even "cameras" on http shows nothing, not even the POE camera.
- Attachments
-
- cameras.jpg (70.12 KiB) Viewed 2218 times
Re: was working now "Config file error"
I there is a button on the circuit board. when pressed it does nothing. I also tried holding it down on powerup, again nothing.
The button is near the buzzer.
The button is near the buzzer.
- Attachments
-
- IMG_0029.JPG (1.74 MiB) Viewed 2217 times
Re: was working now "Config file error"
Here's how to use the button. It's not reset until you hear a beep.
Re: was working now "Config file error"
So not sure if the page mentions it, If following the steps and the system don't do a Beep normally within 20 seconds after you turn the power back on it more then likely failed. If it fails, I would try again. Steps outside of what I am sure is posted but something to try. If it loads back in without a Reset, wait 2min, then reboot the NVR. again wait 2 min. Then press and hold the button for 15seconds, then remove the power, *Seeing you don't have a power button this part can be tricky* Yet you need to keep the reset button pressed while you remove the power, Wait another 15seconds and plug the power cord back into the NVR, Once the cord is restored hold it until you hear a beep. Normally winin 20 seconds. If you don't hear a beep until the screen pops up then the reset failed.. You will know if the reset was good because it will be back to a Set up NVR screen and not the Grid
Next if it failed remove the power and data lines from the HDD and do it again. The HDD has nothing to do with the software in the NVR and isn't needed to restore the NVRs factory settings..
If you have tried to install another Firmware outside of the Amcrest family the NVR might be bricked. With a Device still in warranty I wouldn't ever try to install anything outside of Amcrest family. I am not saying that you did, I am just saying in case you did or if others that might get to your thread that has this issue becasue they did.. Either way the Reset should work if there is a Reset button following the link check6 sent.
Next if it failed remove the power and data lines from the HDD and do it again. The HDD has nothing to do with the software in the NVR and isn't needed to restore the NVRs factory settings..
If you have tried to install another Firmware outside of the Amcrest family the NVR might be bricked. With a Device still in warranty I wouldn't ever try to install anything outside of Amcrest family. I am not saying that you did, I am just saying in case you did or if others that might get to your thread that has this issue becasue they did.. Either way the Reset should work if there is a Reset button following the link check6 sent.
Be Safe.
Re: was working now "Config file error"
I have not done any hacking. Fresh out of the box. It came with the latest version.
Thanks for the reset sequence, it works like a champ I have booted/installed 4 times so far..
I am a retired software engineer. Debugging is in my blood. So I will continue digging.
since this only affects the web interface, is my Web version v3.2.7.83177 the current version?
Here is my config.
Thanks for the reset sequence, it works like a champ I have booted/installed 4 times so far..
I am a retired software engineer. Debugging is in my blood. So I will continue digging.
since this only affects the web interface, is my Web version v3.2.7.83177 the current version?
Here is my config.
- Attachments
-
- config.jpg (50.48 KiB) Viewed 2182 times
Re: was working now "Config file error"
I found what was causing the problem.
Since this only affects the web interface I consider it a bug. Since the latest version is 2022 I don't expect it will get fixed.
but there is a good-enough workaround.
when my sv3c d02poe-1080p-a camera gets added either by the web or console interface.
then the web interface breaks with the "x config file error".
removing the camera and rebooting does not fix this.
The workaround is:
have a good exported configuration maintain->manager->import/export Delete the offending camera.
if it is plugged into a POE port unplug it, POE cameras seem to auto add and you don't want that.
From maintain->manager->import/export "Import" a good configuration (assuming you "exported" when the system was healthy)
Now the web interface works, error is gone.
Raw testing notes.
To get the "x config file error" popup you toggle between "camera" and "live" on the http menu bar after logging in.
button press reset install, no hard drive or any POE cameras or anything plugged into the POE ports, it is on the LAN of course.
"camera/remote devices" finds all 6 cameras. None are added.
toggling and no config file error.
now adding the found cameras one at a time, and toggling for "x config file error" after each one.
starting with the non-POE cameras
all 6 worked, no error
next plugged in the POE camera.
I get the "x config file error" note that it was never added, just found with "search device"
now unplug POE camera and do another "search device" still get the "x config file error" "camera" is not responding just giving the popup error
http not working so on the console deleted all cameras. http still getting "x config file error"
http logged out and back in still getting " x config file error"
power down and reboot, POE camera still unplugged still getting error.
another button press reset install
Testing this time only plugging in the POE camera.
non POE cameras found again, not added, no error popup
plugged POE in it is not found yet.
now doing a "search device" and camera now found, "now getting the popup
unplugged POE and did another "search device" still getting error
Problem with even discovering just the POE camera.
the POE camera is a sv3c d02poe-1080p-a
I moved the camera from the POE port, now on the LAN now 12v powered.
another button press reset install
After adding the camera Now getting the problem
removed the camera and unplugged it.
I still get the error.
power cycling NVR and as expected the error is still there
the http interface is permanently unusable at this time.
Killed by a camera? still broken even after the camera is removed?
This is a bug, The HTTP software just work like the console app.
Interestingly the console is working fine and does not have a problem with the POE or LAN camera. T
he phone app is happy too. Only the http interface is broken.
another button press reset install
plugged a different camera, a sv3c b06poe-3mpl-a, with no problems
under maintain->manager->import/export I exported the configuration
then added the offending camera which as expected causes the "x config file error" problem.
from the console I deleted the offending camera, the problem still exists as expected.
Now from maintain->manager->import/export I import the recently saved configuration.
Eureka! the problem is gone.
so I now have a workaround.
Since this only affects the web interface I consider it a bug. Since the latest version is 2022 I don't expect it will get fixed.
but there is a good-enough workaround.
when my sv3c d02poe-1080p-a camera gets added either by the web or console interface.
then the web interface breaks with the "x config file error".
removing the camera and rebooting does not fix this.
The workaround is:
have a good exported configuration maintain->manager->import/export Delete the offending camera.
if it is plugged into a POE port unplug it, POE cameras seem to auto add and you don't want that.
From maintain->manager->import/export "Import" a good configuration (assuming you "exported" when the system was healthy)
Now the web interface works, error is gone.
Raw testing notes.
To get the "x config file error" popup you toggle between "camera" and "live" on the http menu bar after logging in.
button press reset install, no hard drive or any POE cameras or anything plugged into the POE ports, it is on the LAN of course.
"camera/remote devices" finds all 6 cameras. None are added.
toggling and no config file error.
now adding the found cameras one at a time, and toggling for "x config file error" after each one.
starting with the non-POE cameras
all 6 worked, no error
next plugged in the POE camera.
I get the "x config file error" note that it was never added, just found with "search device"
now unplug POE camera and do another "search device" still get the "x config file error" "camera" is not responding just giving the popup error
http not working so on the console deleted all cameras. http still getting "x config file error"
http logged out and back in still getting " x config file error"
power down and reboot, POE camera still unplugged still getting error.
another button press reset install
Testing this time only plugging in the POE camera.
non POE cameras found again, not added, no error popup
plugged POE in it is not found yet.
now doing a "search device" and camera now found, "now getting the popup
unplugged POE and did another "search device" still getting error
Problem with even discovering just the POE camera.
the POE camera is a sv3c d02poe-1080p-a
I moved the camera from the POE port, now on the LAN now 12v powered.
another button press reset install
After adding the camera Now getting the problem
removed the camera and unplugged it.
I still get the error.
power cycling NVR and as expected the error is still there
the http interface is permanently unusable at this time.
Killed by a camera? still broken even after the camera is removed?
This is a bug, The HTTP software just work like the console app.
Interestingly the console is working fine and does not have a problem with the POE or LAN camera. T
he phone app is happy too. Only the http interface is broken.
another button press reset install
plugged a different camera, a sv3c b06poe-3mpl-a, with no problems
under maintain->manager->import/export I exported the configuration
then added the offending camera which as expected causes the "x config file error" problem.
from the console I deleted the offending camera, the problem still exists as expected.
Now from maintain->manager->import/export I import the recently saved configuration.
Eureka! the problem is gone.
so I now have a workaround.