5 thoughts on “Unable to redirect failover from SERVER!!web.nsf”

  1. We ran into the same problem. The issue was related to the policy documents. If your inital setup policy document specifies Internet Exlorer instead of Notes with Internet Explorer as the default browser, the client will never create the perweb.nsf. When you get an email with a link, the client will then try and find a web.nsf database on the server. If there is none, and if you’re clustered, it will failover to each of the databases. To fix, we changed the setup policy to Notes with Internet Explorer and then we later apply the desktop policy which sets the browser to IE.

  2. Has anyone confirmed if this policy changed fixed the issue? Also, could this be contributing to performance issues if not addressed?

  3. In my case it wasn’t due to policies as we are not using policies in that domain. As to being a source of performance problem I find it hard to rule out or say that it couldn’t be.

Comments are closed.