Landing Page not being displayed

We are not live yet in our cloudsuite but today in our DEV site when accessing the inbasket with get " page cannot be displayed" and this worked just fine last week with the correct landing page.

I don't even get a message, just a white screen.

This is often a browser compatibility mode issue.
Make sure the mingle, lsf, and landmark sites are all NOT running in compatibility mode.
Often IE settings are pushed out via group policy, and might include the option for compatibiliity mode for "all intranet" sites.

We don't use IE for Lawson 10, we use Chrome. INFOR recommends only to use Chrome starting with Version 10.

We have had this problem in the past and found that we had to clear out our temporary internet files. Have you tried that? Also, are you getting any type of error in chrome?

Where are you clearing out the temporary internet files? I go into Chrome and delete history from beginning of time. There is no error when the white page is displayed. It's just not displaying the landing page.

Hi pops - We sometimes see issues like this when the page can't find an image or other resource it is expecting to load.

You may want to try opening the browser debugger (F12) on this page to see if there is an error showing in the console. You may need to reload the page after you open debugger. You will likely see errors that don't cause any problems (it's amazing how many there are), but you may also see something that will help you track down the problem.

Just curious - is there a chance you are using customized HTML5 landing pages? If so, could someone have been fiddling with one of the global configuration files and made a change in DEV and promoted it to PROD the same day? Probably not, but I thought I'd mention it.

Hi Pops,
Is this happening to everybody or just some users? I know that we have a problem with Chrome in that it won't display content that is insecure (comes from http://...) on a https page. To get around that I had to go into the properties of the Chrome icon and add --allow-running-insecure-content at the end of the url in the target line. Usually though you will get a red shield show up that you can click on to see the error. See below for syntax.

"C:\Program Files\Google\Chrome\chrome.exe" --allow-running-insecure-content

This is happening to everyone on both Dev and Prod environments. Happened at the same time, same day. If you click on the white page in different areas, it takes you to different places. I put chrome into developer mode and here's what it displayed:

sso.js:1468 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.SSORequest @ sso.js:1468
https://gmhqsv-lwsn05.med...dmarkCombined.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
https://gmhqsv-lwsn05.med...lemodal.1.4.4.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
https://gmhqsv-lwsn05.med...dmarkCombined.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
https://gmhqsv-lwsn05.med...lemodal.1.4.4.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
ajax.sso.js:93 findSSOPre: An error occured while getting sso instance.
ajax.sso.js:94 [Error] : SecurityError: Blocked a frame with origin "https://gmhqsv-lwsn05.media.ad.gatehousemedia.com" from accessing a cross-origin frame.
ajax.sso.js:95 [object DOMException]
gmhqsv-lwsn05.media.ad.gatehousemedia.com/gdev/Lpa/html/Lpa?csk.PfiInbasketLandingPage=Infor&csk.hidetitlebar=true:164 Uncaught TypeError: $(...).smartresize is not a function
gmhqsv-lwsn05.media.ad.gatehousemedia.com/gdev/Lpa/html/Lpa?csk.PfiInbasketLandingPage=Infor&csk.hidetitlebar=true:161 Uncaught ReferenceError: landmark is not defined
https://gmhqsv-lwsn05.med...dmarkCombined.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
https://gmhqsv-lwsn05.med...lemodal.1.4.4.min.js Failed to load resource: the server responded with a status of 404 (Not Found)
ajax.sso.js:93 findSSOPre: An error occured while getting sso instance.
ajax.sso.js:94 [Error] : SecurityError: Blocked a frame with origin "https://gmhqsv-lwsn05.media.ad.gatehousemedia.com" from accessing a cross-origin frame.
ajax.sso.js:95 DOMException: Blocked a frame with origin "https://gmhqsv-lwsn05.media.ad.gatehousemedia.com" from accessing a cross-origin frame.(…)
PfiMetrics.MyActions?menu=ProcessFlowMenu.MyActions&csk.PfiInbasketLandingPage=Infor&csk.hidetitleb…:52 Uncaught TypeError: $(...).smartresize is not a function(…)
PfiMetrics.MyActions?menu=ProcessFlowMenu.MyActions&csk.PfiInbasketLandingPage=Infor&csk.hidetitleb…:49 Uncaught ReferenceError: landmark is not defined(…)

Looks like you have a couple of issues here. The first one is it can't find the following:
https://gmhqsv-lwsn05.med...dmarkCombined.min.js
Then it looks like your getting a security error blocking ajax.sso.js. Did someone in your organization make some changes to the anti virus software that could be blocking it?

Not to my knowledge. What do you suggest?

Not much other than if you have access to the Landmark server you could search for those scripts - jquery.simplemodal.1.4.4.min.js and landmarkCombined.min.js are in the folders that are being referenced. For instance on my system jquery.simplemodal.1.4.4.min.js is in the following folder:

D:\IBM\WebSphere85\AppServer\profiles\AppSrv01\installedApps\lawson-LSAtestCell02\lmtestenv-gen-law-env.ear\sso.war\scripts\lib
.

I've seen with a couple of client recently where antivirus/endpoint protection software from Symantec on the clients is blocking Infor javascript files.
What security software are you using on the client PCs?

OK, we think symantec removed one of the files. We put it back and made an exclusion in symantec. We still get the white screen after selecting the inbasket and prod. Didn't see any other files removed by symantec. Wondering if we need to reboot the entire environment as apposed to just the landmark server.

You might first try stopping and restarting WebSphere.

OK, the WebSphere was restarted and that did not fix the issue.