I have moved the site from my localhoat machine to live server,i am facing the below problem
warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'imce_access' was given in /home2/aspkcomt/public_html/testsite/includes/menu.inc on line 453.
please suggest......

Comments

mdupont’s picture

Priority: Critical » Normal

It seems the IMCE module in not enabled or that somes files are missing. Look for the function imce_access().

pooling55’s picture

I am having the same problem with many different module names in the error. Any help would be greatly appreciated

mdupont’s picture

Try to launch update.php and clear your caches, it may be an issue related to the path to modules in the DB.

agentgates’s picture

Title: warning:call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback,'views_acces' » Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'system_main_admin_page' not found or inval
Version: 6.22 » 7.9
Priority: Normal » Major

Hi all I'm having the same issue with 7.9 after upgrading from 6.19. The other problem is the site is offline and I'm unable to turn it back on as it gives blank white pages for the admin menus, including the direct link to the appropriate maintenace page and cache managment pages. (by the way the caches are turned off)

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'system_main_admin_page' not found or invalid function name in menu_execute_active_handler()

Could somebody please point me where to start lookin? The site runs on debian postgresql-8.4 though.

Many thanks for any help

Kind Regards
Tony

jenlampton’s picture

Title: Warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'system_main_admin_page' not found or inval » Warning: call_user_func_array() expects parameter 1 to be a valid callback, function XX not found or invalid
Priority: Major » Normal

@agentgates

You are having the same problem as others in the thread, and the solution(s) are also the same.

1) The problem is most likely your cache. You will need to clear Drupal's cache to rebuild the menu system. The menu system is what mapps the page you are on "/admin" to the function that needs to be called to generate that page "system_main_admin_page()". Even if you think that "caches are turned off" that does not mean that your cache does not need to be cleared. Drupal caches a lot of things including menu items and theme files - and the only part you can control through the UI is the caching of your content - which is not relevant here.

2) If clearing the cache doesn't make this particular error go away, then you are probably missing files on your server. In your case you need to confirm that the "system" module from Drupal core is there in it's entirety. (You can tell what module is missing because the name of the function starts with the name of the module) It could be that the process of FTPing flies terminated early, and some modules didn't make it up to your server.

Please clear your cache (you can do this using Drush if your admin pages aren't working) and if things don't start working immediately, check to make sure that all the files Drupal needs to run are actually present on your server.

agentgates’s picture

Hi Jen,

Thanks for the response, your help is highly appreciated. Although drush was also a bumpy ride but I've solved it.

[...] (removed by the user)

Regards
Tony

jenlampton’s picture

For @agentgates and anyone who should come after, please DO NOT run any SQL commands directly on your database unless you know exactly what you are doing - and why (especially on the menu table - you are messing with black magic there!!!!).

Manually running sql queries is an easy way to ruin your Drupal site

If you ever need to run a SQL command (and this will only be necessary extremely rarely) then please, PLEASE, make a back up first. You will soon realize that something is wrong - and that you will need to restore to the backup you made before you ran the command.

In the case of MySQL errors that appear during an update, you will see them until you run the update script. Drupal will handle all the necessary database updates for you. You should not need to touch the database yourself.

agentgates’s picture

Yeah, your right Jen. I forgot to mention I have 20 years in SQL so the backup, savepoints and that sort of things are default here.

So EVERYBODY please listen to her. If you don't know what you are doing don't even try the above I described!

Thanks for the correction Jen. BTW, do you want me to remove/edit the comment?

jenlampton’s picture

Yes, it would be good to remove any advice about running a SQL query manually. The problem you are describing (and the solution you offered) doesn't have anything to do with this issue. I don't want some poor person to come along, and read your comment thinking it will help them, try it, and get themselves in a heap of trouble.

Running update.php will let Drupal handle all the updates itself, that's all that was actually necessary.

kbthalla’s picture

Hi
The bug is solved,main problem is server spacing ,need to update space through php.ini file

windsurfitaly’s picture

tnx it works so after disabling IMCE

Pasqualle’s picture

Status: Active » Closed (fixed)