Skip to main content

Irritating Domino Error

I found this in a log file today while looking for something else:

01/20/2011 09:35:27 AM  Database collection open error: e:LotusDominoDatanames.nsf: View is damaged.  Please rebuild it (by pressing shift-F9 or running UPDALL -r).
01/20/2011 09:35:27 AM  Error updating view '#445806' in names.nsf: View is damaged.  Please rebuild it (by pressing shift-F9 or running UPDALL -r).

#1.  I love that they told me how to fix it.
#2.  I wish I knew which view that actually is.  I don't have an numbered views in my address book.

Once I find out how to translate the view number to a view name, I'll let you know here.


  1. That number is probably the NotesID of the view note. You can check that using Ytria ScanEZ or similar tool (Free if used readonly)

  2. You don't have to know the view name for this case. Updall -r names.nsf rebuilds all views.

  3. The issue with that is not being able to rebuild all views during production hours.

  4. Yes, it's the NoteID.

    First, open calculator in Windows then switch to View > Programmer. Put in 445806 and then change the number from Dec to Hex and this gives you 6CD6E.

    Then open admin client, go to files and find that db. Then expand Tools on the right and then Database and then click Find Note. Put in the hex value from above and you'll be able to see what view it is by clicking on the $TITLE field. Then go to Manage Views and purge that view. Though it could be related to a design error and you might need to delete the view and refresh the design to create it again.

  5. Found it, it turns out it was a ($Policy) view in the names.nsf.

    Unfortunately I had to do a rip and replace with the names.nsf from another server. Couldn't fix the view in that DB.


Post a Comment

Popular posts from this blog

Policies and Controls are King in the IT Security world

I came across an article by Roger Grimes over at Infoworld on how security policies and controls are the real power when it comes to IT security. Roger mentions the SANS 20 Critical Security Controls for Effective Cyber Defence , which are a great read for anyone looking at updating or auditing your policies for completeness. The SANS top 20 controls are a must for any organization: Inventory of Authorized and Unauthorized Devices Inventory of Authorized and Unauthorized Software Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Boundary Defense Maintenance, Monitoring, and Analysis of Security Audit Logs Application Software Security Controlled Use of Administrative Privileges Controlled Access Based on the Need to Know Continuous Vulnerability Assessment and Remediation Account Monitoring and Control Malware Defenses Limitation and Control

Error 217 - Error creating product object on Domino 64 bit

I'd like to share something with you.   An error that you'll get if you are trying to use ODBC with Domino 8.5.1 64bit. It starts out with an agent error of Error 217.  The text of the error is "Error creating product object" You can read about it here on the Notes/Domino forum . You can find the solution here as well . I guess I'm now waiting for Domino 8.5.2 for a solution for this.   It would have been nice to have had this in the release notes.  It would have help me greatly.

Reminder: Increase the maximum available memory on your Lotus Notes client JVM today!

Yup, that's right.  Public Service Announcement time. If you haven't increased the maximum memory available to your Lotus Notes JVM yet, what are you waiting for? By default, the Notes JVM only has 256mb of memory available to it.  On a system with 4GB+ of memory, you should be easily able to increase it to 1/4 to 1/3 of the system memory and improve the end user performance. Here's how: Shut down Lotus Notes. In order to make sure that all processes are stopped, run this command:  Start -> Run Type: C:\Program Files (x86)\IBM\Lotus\Notes\nsd.exe -kill Open: C:\Program Files (x86)\IBM\Lotus\Notes\framework\rcp\deploy\ Open the "" file in a text editor like notepad.  You will possibly require Administrator permissions. At the beginning of the file, you will see text surrounded by a lot of pound signs ####. The first ‘property’ after the last # sign is: vmarg.Xmx=-Xmx256m Change 256m to 1024m so that the line reads: vmarg.X