Application Error

There is a database that resides on our R509 server, Windows 2000 platform.
Two documents that have an "In Production" status cannot be opened but all others can.  Whenever we try to open these two documents, it gives us an error message of either:
1)  ASSERT(dbBox) failed at line 276 in file d\dmisc.c
OR 2)  The instruction at "0x005342d4" referenced memory at "0x00000008".  The memory could not be "read".

How can we resolve this? Thanks in advance for your help.
Who is Participating?
marilyngConnect With a Mentor Commented:

There are a number of references, including your above posted message on Notes.Net regarding the Assert Message and the other error you are receiving.

Is this database a specially constructed one or one thrown from a Notes Template?  Is it a mail-in database?  What's the difference between the databases that work fine and the one that doesn't?  For instance,

1. Have you checked to make sure that the database, and all its design elements are signed by the server.

2. Have you checked to make sure that any roles that exist are also applied to the server -- that the server has the correct access.

3. Is the server administering the database?  Or is the database set for the old server to administer it?

4. Have you run both fixup and compact on the database?

5. Have you tried to access these documents via Notes Peek? (To see what's different in the signatures that might be preventing the access)

6. Do these document have HTML in the RichTextFields?

7. Have you  cleared the replication history on the database?

8. Have you re-indexed the application (shift +F9 while it's open)?

9. Have you compacted the database?

10.  Generally, the best way to resolve corruption in a database is to throw a new replica on the server, clear the replication history, and then delete the old one.

Let me know how it turns out.. it may well be the bug that is not resolved in either 5 or Rnext.

This could be related to corruption in document.

Few of the causes/remedies

1. Check if you are using any special fonts especially in Richtext field (Look for $Fonts)
2. Check for any images which might be causing this problems (If possible delete the rich text fields)
3. Initialize or open event codes (try to Comment out the code and open)
4. Form properties (Design it to simple form by removing any headers or background images)

Let me know how it goes !


Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions


Really wild!! I've never run across this one before, good that you found the newsgroup discussion on it.  
zdimaAuthor Commented:
I have tried all that and it still does not work!
It turns out that it is not only one document in particular.  It is any document that you choose by random.  Sometimes you can view it and sometimes it gives you the error message below which results in Notes crashing.

Here's more background on this issue:

I have recently put up a second Domino server which now acts as the application server and our existing domino server is now only our mail server.  Both are on Windows 2000 platform running R5.0.9.

I have transferred all application databases to the application server (using replication) and deleted the original copies from the mail server.

All databases are working as expected except for one.  It works most of the time but once in a while, when you double-click a document (by random) to view its contents, it comes up with the following error message:

The instruction at "0x005342d4" referenced memory at "0x00000008".  The memory could not be "read".
Click on OK to terminate the program.
Click on CANCEL to debug the program.

You should be using some functionality/feature which is not properly embedded into the new release of notes. try upgrading or downgrading the version. New 5.0.10 is available, which says that it fixed most number of problems. Not sure though !!!

zdimaAuthor Commented:
Thanks for all the info.  We have moved the applications to a new server box separating mail from applications.  I think the replication and deletion of the old one fixed the problem.
Nope.  I get the same thing all too often in 5.0.11.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.