Forum LAMS for Tech-Heads - General Forum: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Manuals for LAMS 2.0

By: Greg Jones

[ Reply | Forward ]

Fiona,
Workstations do use a proxy server for outside addresses. On my workstation I stopped it using the proxy.
I also deleted any reference to LAMS in the Macromedia folder.
Restarted but unfortunately no change.
I am running both IE and firefox and did initially have trouble getting the latest flash version installed for IE. Don't know if that is significant.

The server in question is on our school network and is not accessible from outside.

Thanks for your efforts so far. I was the IT coordinator here for about 7 yrs and appreciate the frustations of diagnosing and solving issues.

Greg

Posted by Greg Jones

By: Greg Jones

[ Reply | Forward ]

Fiona,

Hadn't used my laptop version of LAMS for a while. Just started it up and everything seems to be OK - can preview a sequence.
Previously I had verified that the problem of previweing wasn't just on my workstation by connecting this laptop to the network. While connected I had the preview problem.
Tomorrow I will try it again just to double check - however am pretty certain that I will replicate the problem while on the network.

Summarising standalone version of LAMS on my laptop works OK however if I access the school server version via my laptop I have the preview problem. The problem is independent of the browser used.

Furthermore when I am at work tomorrow I will log on to the server console (win 2003) remove any proxy references - even pull the network cable and test.

Hope this is helpful

Greg

Posted by Greg Jones

By: Fiona Malikoff

[ Reply | Forward ]

Yes, these tests are helpful.

When you test tomorrow, can you set the laptop to have no cache in the browser and clear the current cache.

Then after you have finished testing, get the server logs and email them to me please? If the file is too big to post here, then email it directly to fmalikoff@melcoe.mq.edu.au.

The instructions for which files to send are on http://wiki.lamsfoundation.org/display/lamsdocs/Creating+DEBUG+Logs. You don't need to turn on the DEBUG level - I don't think it will help much in this case. It is mainly the access logs I'm after but I'll get the whole lot while I'm at it just in case!

Why clear the cache? I want to look at the access log and see what queries are being received by the server and clearing the cache and setting to no cache will ensure that all possible calls are sent.

The other thing you can try is to create the Flash log. When the preview window opens, put the cursor over the left hand pane and Press CTRL-ALT-? (which on my PC is CTRL-ALT-SHIFT-/). If it works a debug window will appear. You will need to drag the vertical frame bar to the right to see the debug window properly. Then highlight the log text, right mouse click to get up the little menu then do copy. Paste the text into a text file. Have a look at the attached screenshot to see what I mean.

Now this may not work - if Flash is busy trying to get stuff from the server then it won't bring up the debug window, and eventually Flash will time out and say that the movie is running slowly. If you get the movie running slowly message then give up trying to get the Flash log - you won't get it.

Fiona

Posted by Fiona Malikoff

By: Greg Jones

[ Reply | Forward ]

Fiona,

Finally cracked the problem. It all relates to the server name. If I use http://10.52.94.8:8080/lams the preview works

I have been using a DNS \ WINS entry to allow a slightly more friendly name to be use http://lams:8080/lams.
Using this causes the problem.
Verified on a number of workstations.

Does this relate to the setup where you specify the IP adress of the server? I remember at some stage typing in 10.52.94.8

Anyway thanks very much for you assistance

Greg

Posted by Greg Jones

By: Fiona Malikoff

[ Reply | Forward ]

Greg,

Good sleuthing there!

The server name used by the clients should be the same one that is configured on the server. Flash can be particularly fussy about calling across domains (its a Flash security thing) and although we try to avoid it, that may be why the problem is showing up in the Flash related bits.

You would have been asked for the URL when you first installed LAMS.

To update it (to make it http://lams:8080/lams/)
* log in as sysadmin
* select the Sys Admin link
* the System Administration menu should appear
* select "Edit Configuration Settings"
* change the entry ServerURL

Please put the "/" on the end of the address ie use http://lams:8080/lams/, not http://lams:8080/lams. LAMS should cope fine with either but having the '/' is more robust in case we do a have a bug somewhere.

If you are wondering what the other settings are on this screen, click on the little question mark icon and the help page (http://wiki.lamsfoundation.org/display/lamsdocs/LAMS+Configuration) will be opened. I've just added a warning to that page about potential Flash problems if this setting is not correct.

Fiona

Posted by Fiona Malikoff