Lotus Nut

I first posted this to my Blogspot blog. The most recent update is for a specific DWA 7 error - and I'm planning on adding some stuff from DWA 8. This post generally ranks high on my search engine hits, so I like to keep it updated from time to time. Hopefully it's helping people get these issues resolved. If you know of a resolution that's not listed, please let me know! This first entry is one that happens pretty frequently. An alternate title could be "iNotes Warning" from previous versions. This document contains two sections. One is a general information section and the other is a section on steps to correct the error(hopefully). Please see the bottom for a change log.

General Information:

The full error message is:
"Microsoft Internet Explorer Domino Web Access Warning. Sorry, we were unable to process your request at this time. If you are unable to continue working in your mail file, please dismiss this warning and then select View, Refresh from your browser's menu."

In Domino Web Access (DWA) 7.0 and higher, there is a new error message that reads "The installation of Domino Web Access 7 Control has been blocked or declined by the user. Do you want to use this on subsequent Domino Web Access pages?" A specific correction for this can be to ensure that the user has at least Power-User authority. Another possible correction is to simply add the DWA server to Internet Explorer's Trusted sites zone.

IBM has two technotes regarding this:

Prompt: 'Installation of Domino Web Access 7 Control has been blocked by the user. Do you want to use Subsequent Domino Web Access Pages?'. This alludes to the DWA7w.cab file being moved or corrupted on the DWA server or even that the default HTML directory has been changed from domino\html. I have notified them that in my experience, this may come up when the DWA server isn't in the trusted sites zone for IE.

Can the Domino Web Access ActiveX Upload Control (iNotes Class) be manually placed on a workstation? While not directly related to the error message, this contains a table of the behaviour of DWA with and without the ActiveX control installed.

Corrective Actions:

Recently, the top two on the following list have been what we have seen to cause more issues. If the computers are external (employees' home PC), then I would definitely bank on them having spyware.

- Disable Pop-Up blocker
- Clean up spyware (use application such as Spybot and/or AdAware)
- Add DWA server to Internet Explorer's Trusted Sites zone (this may be a good idea for any other intranet servers or via an Active Directory policy)
- Clear out Java Cache by running C:\Program Files\Java\jre1.5.0_0X\bin\javacpl.exe
---Click “Delete Files” then click “OK”.
---*if there are different versions, do this for each version or uninstall older versions and leave only the newest copy.
- Clear out Windows temp folders.
--- C:\Temp--- C:\Documents and Settings\USER PROFILE\Local Settings\Temp
--- C:\Documents and Settings\USER PROFILE\Local Settings\Temporary Internet Files
--- C:\Winnt\Temp
--- *Clear out the Temp/Temp. Internet Files for each user listed in the Documents and Settings folder.
- Reset IE to default settings.
--- Right Click on the Internet Explorer icon on the desktop or go to Control Panel and open Internet Options.
--- Click on the Programs Tab. Then click the Reset Web Settings button. Uncheck
“Also reset my home page” then click “OK”.
- Tools > Internet Options > Advanced > Disable "Use HTTP 1.1" (you may need to enable it because sometimes IE just doesn't like the setting. I have actually seen it start working by enabling this option.)
- Tools > Internet Options > Advanced > Disable "Do not save encrypted pages to disk"
- Download the MSXML 4.0 SP2. This link will get you to the download. I selected the msxml.msi.
- Clear Browser Cache
- Delete iNotes or Domino Web Access class file
- If one is currently installed, upgrade to the latest Sun JVM
- Windows Update (also verify that a recent Windows Update has not broken this!)
- Load Convert, Fixup, Updall, and Compact against the mailfile
- Reboot
- Defrag
- Run a tool such as Symantec/Norton WinDoctor

Change Log:
08/14/2006: Added information regarding Java Cache, Temp Folders, and Resetting IE defaults.
04/14/2006: Added information regarding technotes 1228480 and 1161877.
Added comment to Windows Update line to state that a recent update may be causing the problem. I have personally seen this in 2004 and the link in the text above is from April 2006.