My BI system has been humming along perfectly for months. I've made no changes, but with Windows 10 auto updating periodically - and auto updates with BI turned on (I know, I know)... Suddenly I'm faced with the inability to open BI.
It has always been run as a service. I have BI Tools set to restart if it goes down. I've had to disable that, as it would try to re-open endlessly.
The BI server is headless (no montior). When I was unable to log in via my phone's app, I teamviewered into the server to find over 100 copies of this error up:
I'm guessing that's because BIT had been trying to restart over and over again. After clearing all of those, restarting the server, and disabling BIT, I get the subject error.
I cannot get the console to open.
Things I've tried so far:
1) Uninstalled BI from programs/features of win 10 (declined to delete registry settings)
2) reinstalled the latest full version
3) Was prompted for key, and when it opened, there were NO cameras.
4) I imported the oldest of the 3 registry backups (from several days ago)
5) Upon restarting, same error.
I don't know if Windows is borked because of a system update, or if something got hosed from a BI update. But either way, I'm dead in the water.
Any ideas?
It has always been run as a service. I have BI Tools set to restart if it goes down. I've had to disable that, as it would try to re-open endlessly.
The BI server is headless (no montior). When I was unable to log in via my phone's app, I teamviewered into the server to find over 100 copies of this error up:
I'm guessing that's because BIT had been trying to restart over and over again. After clearing all of those, restarting the server, and disabling BIT, I get the subject error.
I cannot get the console to open.
Things I've tried so far:
1) Uninstalled BI from programs/features of win 10 (declined to delete registry settings)
2) reinstalled the latest full version
3) Was prompted for key, and when it opened, there were NO cameras.
4) I imported the oldest of the 3 registry backups (from several days ago)
5) Upon restarting, same error.
I don't know if Windows is borked because of a system update, or if something got hosed from a BI update. But either way, I'm dead in the water.
Any ideas?