<< FeedDemon helps you manage your feeds | Home | Lotusphere baby!! >>

Unable to redirect failover from SERVER!!web.nsf

Experiencing the strange error message from the subject in the log when running clustering on Domino 6.5.4 servers on Windows. Workaround is to create a web.nsf database. Hmmmm....

Tags :
Responses[5] RSS feed for responses to this blog entry
Posted by Mikkel Flindt Heisterberg on 11 August 2006 10:05:43 CEST #


Avatar: steve cannon
Reply

Re: Unable to redirect failover from SERVER!!web.nsf

Comment from steve cannon on 11 August 2006 20:20:39 CEST #
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.
Reply

Re: Unable to redirect failover from SERVER!!web.nsf

Comment from Mikkel Heisterberg on 13 August 2006 14:04:56 CEST #
Nice - thank you for sharing. I'll try that one out! ;-)
Avatar: Mark Dowling
Reply

Re: Unable to redirect failover from SERVER!!web.nsf

Comment from Mark Dowling on 08 September 2006 23:30:26 CEST #
not reproducible in 6.x? Oh yes it is - I just had to do it on 6.5.4FP1 server :)
Avatar: Anonymous
Reply

Re: Unable to redirect failover from SERVER!!web.nsf

Comment from Anonymous on 04 January 2007 23:03:05 CET #
Has anyone confirmed if this policy changed fixed the issue? Also, could this be contributing to performance issues if not addressed?
Avatar: Mikkel Heisterberg
Reply

Re: Unable to redirect failover from SERVER!!web.nsf

Comment from Mikkel Heisterberg on 05 January 2007 07:59:06 CET #
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.

Add a comment