Forum Problems Installing LAMS: Re: Re: Re: Re: problems integrating Moodle 1.83 and LAMS 2.04 on Windows 2003

By: David Lai

[ Reply | Forward ]

Hi Fiona,

Thanks for the reply.

The apache tomcat returned Http Status 400 - Cannot retrieve user information when i paste the url into the browser.

And as for the log, it's giving the error as below in Lams.log

15:42:33,859 [http-0.0.0.0-8080-1:] ERROR org.lamsfoundation.lams.web.session.SessionManager - Failed on finding current system session with null sessionId

The installation is carried out in 2 different machine. Since the installtion in windows 2003 failed so I tried it on my XP machine. And both machines are having the same language settings.

Both are using php 5.2 and using the same copy of module.

Posted by David Lai

By: Fiona Malikoff

[ Reply | Forward ]

The "Failed on finding current system session with null sessionId" error can be safely ignored.

If there aren't any errors on the LAMS logs then it points to an error on the Moodle side, or in the URL that calls Moodle to get the user details.

In LAMS, log in as sysadmin and go to the Sys Admin menu, the Maintain Integrated Servers screen and edit the Moodle configuration. Find the entry for the User Information URL and copy and paste that URL into your browser. That will try to call Moodle to get the user details. Does that work?

The url will be something like:

http://<moodle_server>/mod/lamstwo/userinfo.php?ts=%timestamp%&un=%username%&hs=%hash%

or

http://<moodle_server>/moodle/mod/lamstwo/userinfo.php?ts=%timestamp%&un=%username%&hs=%hash%

The extra "moodle/" is needed if you call access Moodle as http://<moodle_server>/moodle/ - it depends on how you installed Moodle.

If the url fails, and adding/removing the "/moodle" isn't the solution, then have a look at the Apache logs for any errors that Moodle might be writing out.

Fiona

Posted by Fiona Malikoff

By: David Lai

[ Reply | Forward ]

Hi Fiona,

Tried it out by still no luck with it. Checked Apache log and there is no error. Any other idea...?

Posted by David Lai

By: Fiona Malikoff

[ Reply | Forward ]

Well, no other sensible ideas.

I assume both Moodle and LAMS are on the same box?

Are you referring them as "localhost", via an IP address, via a name? If it is localhost, is localhost defined in the hosts file (I can't remember if Windows 2003 might need localhost defined or not).

This sounds like a silly question, because if you are referring to LAMS and Moodle using localhost, and localhost wasn't defined, then Moodle wouldn't be getting through to LAMS at all. But I'm clutching at straws here.

Fiona

Posted by Fiona Malikoff

By: Jun-Dir Liew

[ Reply | Forward ]

Try checking your browser's cookie policy - the HTTP 400 error might indicate that IE is rejecting third party cookies. You can override this by going to Tools menu -> Options, Privacy tab, Advanced button, and enable acceptance of third party cookies.

Of course this is for IE, by default Firefox doesn't block 3rd party cookies I think...

Posted by Jun-Dir Liew