URGENT problem!

[Krissy-D]

I've moved my sugar install over to another domain (it was in development on another server and moving it to production) and its not allowing anyone to log in - the usernames and passwords are correct, but it seems to be ending the session as soon as its logged in. All the database defs etc are correct.

Can anyone help me as to why its seemingly logging me in and straight back out? Only message anywhere is "session has expired please log in again"

Many thanks

[Angel]

Take a look at the session_dir entry in your config.php file.

Chances are that it is pointing to a folder that existed on old server, but not the new one. The behavior that you describes matches what would happen if that were the case.

[Krissy-D]

I've checked the session_dir on both config files and they are both blank...

 'session_dir' => '', 
  

Any idea?

[Angel]

Check the config_override.php file for the same (if one exists).

Also check your PHP.INI file for the setting session.save_path. Verify that the directory referenced there is fully accessible to the user under which your web server is running.

[Krissy-D]

Check the config_override.php file for the same (if one exists).

Also check your PHP.INI file for the setting session.save_path. Verify that the directory referenced there is fully accessible to the user under which your web server is running.

config_override.php is empty...

Save path is right, and fully accessible - still no joy

I really don't want to have to rebuild on new server

[Angel]

You might want to consider this trick...

Edit you config.php file and change installer_locked => true to installer_locked => false. Save the changes.

Open your browser and go to http:///your_sugar_url/install.php

That should display the installation wizard. Proceed to the page that immediately follows the License page. That should perform a system check. Errors/problems it finds are usually more detailed here and should help track down the source of the problem.

DO NOT proceed with the rest of the wizard as you could overwrite your database. The idea is to simply get some more verbose errors/messages that might serve as further clues as to the source of the problem.

Once you are done, be sure to change the config.php file again so installer_locked is set to true.