I am working at a client site where they just migrated from Exchange 5.5 to Notes/Domino 6.5. Domino running on an AS/400.
Two users out of 100 cannot connect to the server today 11:14AM 1/6 but were able to at 10:40AM 1/6 and all day yesterday. I have uninstalled - deleted and reinstalled into a different directory - as soon as they launch Notes and enter their password - the client attempts to communicate with the server. The communication ‘lightening bolt’ flashes and never stops flashing. The client never finishes opening and, of course, is listed as not responding by the system. Any ideas? The two systems in question are different from each other. One is running XP with 128Megs of RAM the other is NT4 workstation with 128Megs of Ram.
Subject: RE: In a Quandry HELP… solid lightening bolt
Add these 2 lines to the client notes.ini file. That will tell you what is happening when it clocks. If you still can’t tell after seeing this, then post the results back here.
We are also running Notes on an AS/400. We had a similar problem with one user. The lightning bolt would remain solid on his PC and the server would show it was running at 80%. After determining the problem was not network related, we uninstalled Notes, deleted the lotus\notes folder and reinstalling to a totally new folder. This was successful. We then copied the user’s names.nsf database back. I reported this to IBM and the following is the technician’s response:
I’ve not seen this before but maybe something got left or fragmented in the desktop.ndk. But one other thing maybe the next time try renaming the Bookmark.nsf to see if that maybe where the corruption is.
Subject: RE: In a Quandry HELP… solid lightening bolt
We deleted the bookmark/headline.nsf and the NDKs to be sure. Didn’t help. I deleted the above files, renamed Names.nsf to names.old. Deleted the ~.lck files - deleted the cluster.ndf file. Reinstalled after doing an uninstall - same issue.
I also ran NSD in a cmd prompt to see what is what… then maybe have NSD kill the Notes client. NSD returned that nothing was running. I couldn’t use the NSD -kill to close Notes. The Notes.ini file entries didn’t work either, but I think that the client didn’t get a ‘chance to open’ the log file. The client hadn’t gotten there yet, kinda thing.
Subject: RE: In a Quandry HELP… solid lightening bolt
What fixed it was uninstall and reinstall of 6.03 on both machines. Worked like a champ. Since we don’t have a sametime server installed and the location document is set to manual for the connect, I think that may have been the issue.
We will use 603 from now on w/regards to the same issue or the constant NSD (another thread)