Has anyone seen this?
Unable to redirect failover from Mail/pap!!web.nsf
This message would make sense if web.nsf was on one of the cluster servers but not the other. Mail/pap is a clustered server but there is no such database on either of clustered servers (it is not on any of our servers, AFAIK). Periodically this message shows up in the log a few times or a few hundred times.
Subject: “Unable to redirect failover…” - IBM Technote
Hi,
Here’s an IBM Technote with a workaround for this problem:
Contrary to the Technote’s assertion, this problem exists in our 6.0.x/6.5.x environments. I created web.nsf on the clustered server (and a replica on the other clustered server) and within 5-10 mintues the “Unable to redirect failover from SERVER2!!web.nsf” entries stopped flooding the server console/log.
Prior to this, we tried ensuring that all Notes Client users had a local perweb.nsf and that the web browser Location preference was set to Internet Explorer (our organisation default). However, we still got the error messages - possibly we didn’t get all users. Whatever the reason, the R5 workaround works in ND6.
Regards,
Robert Fairhead
robertf@rocher.com.au
Subject: “Unable to redirect failover…”???
Doug, I’ve seen this caused by clients configured to browse using notes and an internotes server instead of IE. They click on a link in email and generate that error on the server. Check the location/browser settings in their local nab?:-jmw
Subject: I’ve seen this error triggered in an environment…
that had all locations set to “IE”. This was enforced by an event in the postopen of the personal address book, because IE was needed for the companies’ intranet. Still these errors pop up in the log.nsf - dozens of them!
Subject: Easy way to track who causes it
If you load the web task, you can see who is trying to use it in the logging:-jmw
Subject: will try, tnx
Subject: “Unable to redirect failover…”???
I think I have the reason, description, cause of this error. Need to confirm it with another domain. Is there someone who still face this issue?
Subject: RE: “Unable to redirect failover…”???
If you have the reasoning or a solution, please post. We have the same problem at my organization.
Subject: RE: “Unable to redirect failover…”???
This is my theory on the issue:
There is a Setup Settings document that sets Browser setting in Location document to “Microsoft Internet Explorer”
Because of this perweb.nsf is not created during the setup of client
When user receives a mail with HTML page and images the client tries to show it using perweb.nsf - which is not there on client
So client then tries to get it from the home/directory server web.nsf - but web retriever is not running so if u have a cluster it tries to failover to the next cluster server and gives a message on that server.
Solution - create perweb.nsf on clients where it is not there
The other possible solution that I have not tried yet is:
Dont set Internet Explorer as default browser in Setup policy - do it in desktop policy.
Pls. add your results here so that I am sure this is the case.
Best of Luck
Subject: RE: “Unable to redirect failover…”???
This is happening on my server(s) too. However, I don’t think that it is a user activated issue. The error messages appear every few minutes and it is the same set of databases that appear. Here is a cut of the data from the server’s log.nsf:
04/10/2005 19:07:18 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname1\Journal.nsf
04/10/2005 19:07:22 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname2\Journal.nsf
04/10/2005 19:07:35 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname3\names.nsf
04/10/2005 19:07:35 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname4\Journal.nsf
04/10/2005 19:07:40 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname1\Journal.nsf
04/10/2005 19:07:42 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname2\Journal.nsf
04/10/2005 19:08:06 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname1\Journal.nsf
04/10/2005 19:08:10 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname3\names.nsf
04/10/2005 19:08:10 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname3\Journal.nsf
04/10/2005 19:08:11 Admin Process: Searching Administration Requests database
04/10/2005 19:08:12 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname2\Journal.nsf
04/10/2005 19:08:37 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname3\names.nsf
04/10/2005 19:08:37 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname3\Journal.nsf
04/10/2005 19:08:40 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname1\Journal.nsf
04/10/2005 19:08:47 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname2\Journal.nsf
04/10/2005 19:09:09 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname1\Journal.nsf
04/10/2005 19:09:10 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname3\names.nsf
04/10/2005 19:09:10 Unable to redirect failover from Notes/Domain!!roaming\LastnameFirstname3\Journal.nsf
We have a 2 server cluster, but none of these files are on either server. Not even a stub. This message appears on the log throughout the day and night, so I don’t think it is user generated.
As you can see, we have implemented roaming use but we have plenty of people roaming in addition to the people who are firing up this error in the log. Any ideas anyone?
Jon
Subject: RE: “Unable to redirect failover…”???
better late than never, I had the same issues, it turned out to be the blackberry server pointing the the wrong roaming profile ie in the PIM sync section in the blackberry manager app. changed it to point to the correct roaming profile and the log errors disappeared from the Log.nsf !!
Subject: we see this a lot - not found an explanation yet.
Subject: Solution … we see this a lot - not found an explanation yet.
I solved the problem with “Unable to redirect failover” by adding ehe secondary server as the “Catalog/domain search server:” under the users location document and the “servers” tab.Still I am not fully happy with the solution as it feels like a “workaround”
Somebody have a better solution ?