Has anyone experienced slowness or the Notes client being locked up when trying to open a doc link? When a salesman saves a quote, an email is sent to the District Mgr which contains a doc link to the quote. This usually works fine, however, every 6 months or so, a doc link will take 4 or 5 minutes to open and in many cases, causes the user’s Notes client to lock up! (No red box of death, just “Not Responding”) Because this is a such a rare occurrence, I’m thinking the issue is a corrupt document or corrupt data. I was just wondering if anybody has experienced this and might have an explanation.Thanks.
Subject: Doc link locks up Notes client
As with many problems I suppose there are a number of possible causes, but here are some ideas that may help you track the problem:
Clicking a doclink attempts to open any replica of the database to locate the target document. So if a user has a local replica there’s a good chance that this local db will be accessed to open the linked document. If the local replica’s view (that is referred to within the link) hasn’t been built before or hasn’t been updated for a while, then the indexing operation to build/update the view will make accessing the link slow and may seem to freeze their client.
Note that the link will contain a server “hint”. This isn’t used if the user has already accessed a replica of the db and has an icon on their workspace for the db. So, basically, if they have an icon to an old replica of the db on another server upon their workspace then this is what their client will try to use to open the link from (and, again, there’s the re-index delay as they access a replica that not many people use).
I suppose ultimately what I’m trying to say is that the Notes client will treat doclinks independently of the “hint” contained within the link, and the server to which the client connects is ultimately outside of the control of the sender of the link.
If, on the other hand, people are all accessing the same replica then could it be that sometimes a developer does some work on the view referred to in the links and the rebuild of this view is causing the delay?
One other idea that springs to mind is the form design of the document being opened. Could this cause the freezing/crashing? Also, does the form contain @DBLookup code that could be trying to access other views that need to be rebuilt? And does the form contain LS code or even JavaScript code that could be causing problems? It may be worth checking CPU activity of all tasks when the freeze occurs and see whether a particular EXE is doing any work during the freeze.
Finally, a question: when the Notes client goes to “Not Responding” can CTRL-BREAK bring it back to life or does this have no effect (or have the users not tried this)? Sorry this may seem like an obvious question to which you will probably say “of course they tried CTRL-BREAK!” but I thought I should ask just to make sure 