By dantw on

I have a Drupal 6.6 from fresh installation and now when I simply tried to upgrade a module I was getting the error:

"An unrecoverable error has occurred. You can find the error message below. It is advised to copy it to the clipboard for reference.
Please continue to the error page"

The detailed error message was actually the html source code of update.php and when I clicked on the error page link (which showed /update.php?id=4&op=finished) I was brought back to the previous Drupal database update overview page (/update.php?id=4&op=start). If the module upgrade required a database schema update, a message such as "Updating field type xyz with module abc" was logged in watchdog but the Status Report indicated the database update was out of date.

This is critical as it means I can't upgrade any module that requires database schema update. Any advice will be greatly appreciated!

⋅ Categories: Drupal 6.x

Comments

dantw’s picture

dantw commented

Two things came to my attention:

1. On the admin/theme/list, I switched the default theme to Garland before running update.php. But each time the error will unset the default theme selection - no theme was selected.
2. Running update.php incremented the id parameter in the query string (/update.php?id=5&op=start) and added a new record into the Batch table.

Any clue? Thanks again.

dantw’s picture

dantw commented

Apparently, I'm not the only one having this problem.

http://drupal.org/node/249799

http://drupal.org/node/320477

I have done several upgrades in Drupal 5 without any issues and this is the first time I've ever tried to upgrade a module in Drupal 6. If I can't even get a regular module's database update to work, how am I supposed to upgrade the core module?

ainigma32’s picture

ainigma32 commented

And from what version to what version?

- Arie

dantw’s picture

dantw commented

Arie, Thanks for the response.

I was trying to upgrade 4 modules -

Views 6.x-2.1 => 6.x-2.2
Calendar 6.x-2.0-rc4 => 6.x-2.0-rc6
FCKeditor 6.x-1.3-rc3 => 6.x-1.3-rc6
Date 6.x-2.0-rc4 => 6.x-2.0-rc6

Even though only the Date module required database schema update, I would got the error when I ran update.php on any of them. The only difference was Status Report won't show "Out of Date" for Database updates until update.php was run after replacing the Date module.

Thanks again.

mhopson’s picture

mhopson commented

I am upgrading the core from 6.4 to 6.9.

I have the exact same error message 'Unrecoverable error ...".

Has anyone figured this out yet.

pwhite’s picture

pwhite commented

I'm getting the same problem when trying to update from Drupal 6.8 to 6.9.

uberellis-dupe’s picture

uberellis-dupe commented

Me three.. Drupal 5.16 -> 5.17

I don't see anyone else having this issue in Drupal 5.x tho.
Modules being upgrades:
Image
ImageCache
FeedAPI

r3dw00d’s picture

r3dw00d commented

I'm having the exact same issue....

I had it before so I rebuilt my entire site in 6.8 thinking that the new version would help...

I ran it with Firebug for firefox installed but couldn't get any clues from that either.

This is a major problem for Drupal... I am really not understanding how I can run a production site with Drupal 6.... Maybe all the devs efforts are going into 7?

anyway.. if anyone has fixed this please let all of us poor saps know how....

thanks :)

dantw’s picture

dantw commented

I finally got my problem solved. In my case it seemed to me at some point during update Drupal was trying to show a different progress bar image file. I have Clean Url enabled (using IIRF on IIS) and in my rewrite rules all files were passed to index.php for processing. But for this particular file the rewrite rule was not able to find it. Instead of throwing a more specific 'file not found' error, the Batch API simply returned the 'An unrecoverable error has occurred' message (see http://drupal.org/node/363911). Once I added the following rewrite rule my update ran smoothly.

# Do not pass to drupal if the file or directory exists
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]

Hope this can help some people.

mhopson’s picture

mhopson commented

That is right ... I disabled clean URL and made it work.

After long hours of tracing update.php ... I figured this out.

jillefloridor’s picture

jillefloridor commented

Adding these lines to my IIRF did the trick!

Thanks a lot!

zjelev’s picture

zjelev commented

My configuration is Drupal 6.10 on IIS 6 with IIRF. But even when I turn off the Clean Urls the problem remains! The update runs smooth ONLY WHEN I remove the Ionic Isapi filter from IIS !
So I believe the problem is with the IIRF.
dantw, these rewrite rules don't work for me. Could you send me your IsapiRewrite4.ini configuration, because the one I have is apparently for Drupal 5?
Thanks a lot in advance.

mparker17’s picture

mparker17
he/him
Primary language English
Location UTC-5
commented

This solution worked for me!

I did have two problems though... I had the site already set up when I moved it to this server, so I had both the "Clean URLs" option and the "Global Redirect" module turned on with the "Non-clean to Clean" setting enabled. If you are also moving to a different server, I recommend turning off Clean URLs before moving, and turning it back on once everything is set up. Turn off "Non-clean to Clean" permanently... enabling it causes pages to redirect endlessly.

I am using "Ionic ISAPI Rewriting Filter (IIRF) 2.0.1.1013 RELEASE" on IIS v6.0. For the curious, here is my Iirf.ini file:

# Do not pass to drupal if the file or directory exists
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]

# Handle query strings on the end
RewriteRule /(.*)\?(.*)$ /index.php\?q=$1&$2 [I,L]
 
# now pass through to the generic handler
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^/(.*)$ /index.php?q=$1 [I,L]

See http://serverfault.com/questions/13176 for more information

commuterzombie’s picture

commuterzombie commented

I was having the same problem with Drupal 6.x on Windows 2003/IIS 6 using the Ionic Isapi Rewrite Filter. The problem occurred in Firefox and IE, with or without clean URLs disabled.

I added those lines to my C:\WINDOWS\system32\inetsrv\IIRF\IsapiRewrite4.ini file, restarted IIS and the problem was solved.

This was driving me mad, thank you very much for posting the solution!

fiddlededee’s picture

fiddlededee commented

I was having the exact same issue upgrading Drupal 6.8->6.9, on IIS 6 and using IIRF for clean urls.

I ended up disabling IIRF so no URL rewriting was happening (stopped IIS, renamed the config file, restarted IIS), edited settings.php and changed update_free_access (or whatever) to TRUE.

Then I used IE 6 to view /update.php. No error and everything went smoothly. I suspect this is a problem with Firefox, but i changed two things at once so IIRF, or URL rewriting generally, could also be factors. I only was inspired to use IE 6 by this thread, which mentioned issues with Firefox: http://drupal.org/node/84603

Hope that helps someone.

addisono’s picture

addisono commented

Disbling Clean URL's and commenting the following in my .htaccess worked like a charm:

# RewriteCond %{HTTP_HOST} ^www\.example\.com$ [NC]
# RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

Used Firefox 3 and it worked fine.

druper’s picture

druper commented

I had to disable clean URLs, and revert all URL rewriting in /root/.htaccess, /apps/drupal/.htaccess, and settings.php. I had also forgotten that I had to set write permission on settings.php (and, of course, remember to disable write permissions after the fact).

Then I had to wait for it all to take effect (not used to Apache, this is weird, having to wait, and I never know how long it's going to be).

All that to update Views from 6.x-2.3 to 6.x-2.4.

Yeesh, seems like this is a bug that needs fixing.

I'm a drupal newbie, so it took about a day to run this down and get it straightened out.

bohz’s picture

bohz commented

I had the same problem upgrading 6.13->6.14
plus:
webform
filefield
imagefield
(all to the latest release)

The rewrite rule did not work for me.
But completely disabling the IIRF ISAPI filter did work.
I did not try with IE...maybe next time.

It took me only 5 minutes to find this thread (and the solution) after the error popped out.
This community is great!

Thank you all

nielt’s picture

nielt commented

Apache version: 1.3.41 (Unix)
PHP version: 5.2.6
MySQL version: 5.0.67-community
Operating system: Linux
Drupal 6.10

When running update.php, I get the same error as described in the original post. I tried some of the fixes, and a whole range of different browsers (I don't see how this can be browser-specific anyway), but cannot seem to get my database to update.

Fixes tried:
Disabling clean URLs
Disabling all rewrite rules in .htaccess
Changing base URL in settings.php
Adding 

# Do not pass to drupal if the file or directory exists
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]

to .htaccess

I first experienced this problem when trying to update the database schema after upgrading the Webform module, but have since tried different modules that require update.php to run and get the same error. I can provide more details if necessary.

This is a production site, and I would really appreciate any help!

mhopson’s picture

mhopson commented

And also turn off apached url rewrite during upgrade.

chadj’s picture

chadj commented

I've tried all the above on one of my sites. Same curious problem. Did you ever find a solution Neil?

nielt’s picture

nielt commented

I'm terribly sorry Chad, but I can't even remember which one of my sites this was affecting. I want to kick myself in the backside for not writing down the solution here when I got it right.

I doubt that all the issues mentioned in this thread are exactly the same. The error message isn't very helpful.

My suggestion: disable clean URL's and clear the Drupal cache before updating.

Sorry again, I hope you find a solution!

Reuter-1’s picture

Reuter-1 commented

This is definitely a Firefox issue. I had the same problem and almost tore my hair out trying solutions. Luckily, I found this thread before doing anything desperate.

I had been trying the update in Firefox, but after reading one of the comments above I switched to Internet Explorer (8, in my case) and the update went through as smoothly as ever.

syndicateStorm’s picture

syndicateStorm commented

Very useful forum. However, I tried all of the above and nothing worked. For me the database seemed to be getting updated just fine but I still had the disconcerting message: unrecoverable... Made me a little nervous even though update.php seemed to be doing it's job. I returned to my ways of using clean URLs and my original .htaccess file.

I recently noticed I had two modules installed but not enabled: apache solr and organic groups. These were on my local machine so in the process of prepping to go live I decided to clean house and "uninstalled" both modules. I tried running update.php afterward for kicks and it worked like a charm, problem fixed.

Anyways, I'm not sure what the exact source of the problem was but perhaps this is useful information if changing .htaccess or disabling clean URLs didn't work for you. Perhaps the database for one of these modules was corrupted or perhaps there was some obscure bug regarding updating when you have disabled modules (fyi these modules had been formerly enabled).

Good luck.

nachenko’s picture

nachenko commented

As weird as it sounds. None of what you suggested here worked. Some dude said "it's a FF issue, IE8 did the trick".

I said to myself: "Naaaah!". Tried Chrome, and it didn't work. Of course.

Then, a bit of desperate, I tried the only IE that i have currently installed (virtual machines don't count): IE6.

Guess what? It worked.

Holy cow!

span’s picture

span commented

A truly remarkable error. I had the same issue as everyone else with too little information about the actual error.

Read that Firefox would be the problem so I tried Safari which also didn't work. Of course IE wouldn't work then either so I kept on looking for an answer for another hour before trying with IE8 and everything worked smoothly.

Someone with enough brains really should try to figure this one out. Perhaps some JS error that returns something faulty which throws the page not found error?

amirtaiar’s picture

amirtaiar commented

Had the same issue solved using IE8 (the first time I see a good thing about IE...).
Though, Since the problem accured I can't access the website using FF / Chrome...
Why is that?
I have clean cache, cookies,,,

Managing Partner at Reasonat

kenorb’s picture

kenorb commented

#249799: An unrecoverable error has occurred

dreadfulcode’s picture

dreadfulcode commented

Got the same problem after migrating my site from my local server to this so-called economy hosting @ Godaddy. Who'd think clean url config problems would create such cryptic messages? Anyhow, if I give Godaddy their lousy six bucks for this so-called deluxe hosting, I will get clean Url writing capabilities.

I pay godaddy = problem solved.