Everything went well going from 1.5.2+ to 1.7.2 No errors were reported and the brief checks I did seemed to indicate everything was fine. I migrated the database without any problems.
I then upgraded to 1.8.1+(2007021510). I set it to unattended mode but watched anyway. Most of it went OK but I saw a database upgrade error appear but then disappear before I could properly read it. The next screen was a blank page.
I shut my browser down and then restarted it. I logged on as admin OK and the site seems to be working without any problems except that if I choose "notifications" from the 'Site Administration' I get a blank page again.
Is there an installation log somewhere that might tell me what has gone wrong?
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
Hi John,
server (error) logs might tell something but you could also try to turn debugging on from
Administration -> Server -> Debugging
Debug messages: ALL
and go to Notifications.
Did you have anything installed outside "normal" 1.5 package? I could guess something "old from 1.5" is missing/not upgraded or lack of memory could be one explanation...
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
authorize plugin needs upgrading
Thanks Anthony.
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
I have the same error.
I have recently upgraded Moodle from 1.6 to 1.8. Everything had worked fine. I installed numerous blocks and they all worked. At first when I went to the administration page and clicked on notifications, there was a completely blank white page. Later it fixed itself. I am not sure how.
But now it is doing the same thing. I cannot install modules because the notifications page is always blank.
If any of you know the answer to this, please respond.
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
My problem was that in Moodle 1.5 there is a folder moodle/enrol/internal
In Moodle 1.8 this is no longer present but the upgrade process can add new files and overwrite old files but cannot (or does not) delete files so you have to remove this folder manually.
This cured my problem.
Hope this helps.
John
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
I have the same problem. By clicking on notifications as an admin I get an empty page. Only when I delete the line upgrade_RPC_functions in admin/index.php I get a correct notification page. Can somebody help me?
Thanks,
Katarzyna Potocka
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
KP (&PB),
In his last post in this thread, JR indicated that his problem happened because he put the upgraded Moodle files into the same folder as the old version (see http://docs.moodle.org/en/Installation_FAQ#How_do_I_upgrade_Moodle.3F_Do_I_just_overwrite_the_files.3F). You didn't do that, did you?
RLE
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
it has something to do with a new impleneted enrolment possibility. When I change the moodle code in admin/mnet/adminlib.php so that he dowsn't look for this special enrolment type it works fine. Can somebody tell me, what for the upgrade_RPC_functions() in admin/index.php are.
Thanks, KP
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
KP,
Vaguely. According to the (very terse) comments in admin/index.php, the function upgrade_RPC_functions, which is defined in admin/mnet/adminlib, checks for changes in RPC functions. Mnet stands for Moodle Network (see http://docs.moodle.org/en/Moodle_Network) and RPC stands for Remote Procedure Calls. Moodle Network is new with 1.8, and it allows multiple computers all running Moodle to communicate with each other. RPC is a protocol that allows computers, possibly running different operating systems (Linux, Windows, etc.) to communicate to the extent that they can remotely call basic operating system procedures in each other (sounds potentially dangerous; watch out for hackers!). It is used by Moodle Network.
The function upgrade_RPC_functions keeps track of RPC functions in modules, authentication routines and enrollment routines by recording the ones it finds in the Moodle database, in tables whose names (after the Moodle table prefix, mdl_ by default) begin "mnet".
That's about all I know from a cursory review of the code and Googling a couple of terms. I hope it is detailed enough for you! 
RLE
Re: upgrade problem from version 1.5.2+ to 1.8.1+ (via 1.7.2)
Specially the part about checking the server logs.
Saludos. Iñaki.