Received the following error. Subscribers say their accounts are working fine, but Unity says to delete and re-add the accounts...
0:(error) Internal dbWalker error:-2147467259 ([Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x00000000a44000 in file 'e:\MSSQL\data\UnityDb.mdf'.) in procedure checkSubscribers of Form frmMain
1435:(error) No notificaiton devices found for this subscriber. This is an unusual error to encounter on a production system.
You will need to delete and recreate this subscriber. If you cannot delete the subscriber in the SA directly you can remove this subscriber's row from the Subscriber table in the UnityDB database in SQL.
If you are uncomfortable editng SQL directly, please contact TAC. Be sure to get a backup of your system using DiRT before editing anything in SQL on your own.
Well, the error means what it says - no notification devices were found for the user in quesiton (or all the users in question I guess) - this wont make their accounts stop working other than notificaitons wont be going out if that's expected. It does, however, indicate your system is potentially in a very bad way. The error coming back is being issued from the SQL Server - dbWalker is doing a very generic query for all notificaiton devices for a user and SQL is coming back and saying there's corruption of some kind and nothing is returned.
That's bad. You need to make sure you have a backup in place sooner rather than later.
Lots of reasons for corruption are possible, hard to say what but it could be a hard drive sector bit the dust is could be a drive going south in a hurry - no way to know but corruption is never a good thing.
If you're users don't have notification devices configured for dialout (i.e. delivering a note to a page on new urgent messages or calling them at home etc...) then they probably wont notice anything wrong. I'm curious what shows up in the SA when you open one of these users and try and access their notificaiton devices - I'm guessing some sort of error or empty page comes up.
Either way - dbWalker can't fix that kind of corruption - hence the indication that to get the user back into shape will require a delete/recreate. But as noted, please be sure to get a backup of your system in place if you haven't already.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...