Posted by jgoodwill01 on September 16, 2009 at 6:14pm
| Project: | Reindex |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
I'm not sure how to correct this error.
I'm running IIS7 on Windows Server 2008.
Everytime I try to run Reindex I receive this error.
An HTTP error 0 occurred. /batch?id=3&op=do
Is there anything I can do to keep this from occurring?
Comments
#1
what browser is in use?
does the same occur in another browser or is it browser specific?
I ask because using "An HTTP error 0 occurred" as a search term reveals many threads with regards to it being a browser specific issue?
#2
I found out I was able to get the site to reindex if I hit the refresh button. I'm was using Firefox 3.5.3 when I received the error. I just checked it and I receive the same error in Internet Explorer. It seems really odd that the reindex works when I refresh the pages but fails on the initial attempt. If this is not a widespread problem then I'm probably just experiencing a conflict with one of my other modules.
If there happens to be a solution then that would be great but seeing as I have been able to get it to work no need on spending a lot of time trying to find a fix.
Thanks!
#3
Yeah, this happens at Drupal.org when I try to create an issue.
http://drupal.org/node/add/project-issue/gallery
It happens after I click "attach" in Firefox.
Let's see if it happens here, also?
.
.
.
Yep. It does. Happens at drupal.org.
#4
try to uninstall fckeditor.
#5
I'm no longer using the FCKeditor module and have switched to the WYSIWYG module with FCKeditor an am having a little more success with this.
#6
I have the same error (An HTTP error 0 occurred.) and refresh doesn't seem to work for me.
I have a very large number of nodes and comments and would love to use this to reindex my site.
I get the error in both Google Chrome 7 and Internet Explorer 8
#7
This problem is maybe caused by a wrong configuration of $base_url and should be prevented by inserting a warning message to the requirements system. Therefore I created a new issue #1046682: Install/Update process fails if $base_url is set to a wrong URL. Please close this bug as a duplicate, if this solves your issue. Thanks!
#8