06-20-2005 08:13 AM - edited 03-18-2019 04:43 PM
Unity 4.0.5. Clean install with DIRT restore. DBwalker was run before the restore with 0 errors, now it is reporting the following:
*** Starting General System Checks ***
Checking LastModifiedTime column for all entries in the Configuration table
0:(error) Date/Time format problem in Configuration table:-2147467259 ([Microsoft][ODBC SQL Server Driver]Invalid time format). Check the LastTimeModified column for all entries in the Configuration table for correct format.
***********
Solved! Go to Solution.
06-20-2005 09:48 AM
You'll see other reports of that out here - the Configuration table date/time stamp is used only for failover (i.e. so the systems can keep those settings in sync across boxes). If you are using failsafe and are getting this, then there's a problem. If you aren't using failsafe, then there's nothing to worry about here.
You can manually update the LastModifiedTime column for the rows in that table if you want the error to go away regardless. Check out the release notes for this bug for more details:
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef60341&Submit=Search
06-20-2005 09:48 AM
You'll see other reports of that out here - the Configuration table date/time stamp is used only for failover (i.e. so the systems can keep those settings in sync across boxes). If you are using failsafe and are getting this, then there's a problem. If you aren't using failsafe, then there's nothing to worry about here.
You can manually update the LastModifiedTime column for the rows in that table if you want the error to go away regardless. Check out the release notes for this bug for more details:
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef60341&Submit=Search
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide