Enterprise Reporting Script loading problems

The first step I'd take is to make sure that your MSXML files are downloaded and installed properly. If you have access to the support site, KB # 102044 deals with this error and gives you links to resolve.

Hi Bill. Make sure that IE recognizes all Lawson servers (apps, LBI, etc.) as either "Trusted Sites" or "Local Intranet". Then check a new IE7 security setting : "Access Data sources across domains". That should be all that is needed...

Also, make sure that your pop-up blocker is off. Could be what John is getting at with having them both in the "Trusted Sites"?

Didn't work. I have a new error now. It says this:

Object doesn't support this property or method [erload.init]

Oh by the way, I think my LDS guys thought that by going back to IE 6.0 would fix the problem so 6.0 loaded when I logged in today. Same problem though.

Greg - I don't know how to access those files you referenced.

Have your desktop support group:
- delete temporary files in IE
- Set IE for 'every visit to page'
- Make sure you have a Java JRE loaded (IE doesn't come with one any more)
- Check IE settings to make sure you can run scripts.

Here's a copy of most of the article and the links:

Portal login errors: "Error on page" --and-- "Object doesn't support this property or method" --and-- "The server returned an invalid XML response"


Description:
When I try to log into the Lawson Portal, I get the JavaScript error "Error on page" or "The server returned an invalid XML response," and the resulting JavaScript error details read "Object doesn't support his property or method" or

Line: 93
Char: 3
Error 'oHttp' is undefined
Code: 0

How do I resolve this error?


Resolution:
This Portal login issue usually occurs after a Microsoft Security Update has been applied. Microsoft has issued a patch for MSXML 4.0 SP2 to resolve this issue. You can download the fix from Microsoft's web site at http://support.microsoft....cid=kb;en-us;887606. Lawson recommends using the following patch process to resolve this issue:

Install MSXML 4.0 SP2 by launching the msxml.msi file at the bottom of the page (this step is only required if MSXML 4.0 SP2 is not installed):
http://www.microsoft.com/...f2b42&DisplayLang=en .

Install the Critical Update for MSXML 4.0 Service Pack 2 (887606): http://support.microsoft....scid=kb;en-us;887606

If you are still having the issue, follow the steps below to check the version of msxml4.dll to verify that it was updated by the Hotfix:
In Windows Explorer, navigate to C:\windows\system32.
Do a search for msxml4.dll.
Right-click on the msxml4.dll file and choose Properties.
Click the Version tab.
Verify the version of msxml4.dll using the table below:

Product Version of msxml4.dll
MSXML 4.0 SP2 (base) 4.20.9818.0
MSXML 4.0 SP2 plus Hotfix 832414 4.20.9821.0
MSXML 4.0 SP2 plus Hotfix 887606 4.20.9828.0


If you are still having the issue after verifying that the version was updated, reboot the PC.

If you are still having the issue after rebooting the PC, install the MS05-054 Cumulative security update for Internet Explorer: http://support.microsoft.com/kb/905915/en-us

If you are still having the issue after step 5, try adding http://*..com as a Trusted Site in Internet Explorer.


Notes:
There have been reports that this error may be caused by spyware/adware. Lawson recommends running a spyware/adware utility to remove any spyware on the PC in question.
There have also been reports that this error may be caused by McAfee software installed on the web server. Try uninstalling it and attempt to duplicate your issue again.
If you are using 3rd party software to 'push' updates to your users PC's and you believe this patch is installed on the PC but the user still has this error, go to the user's PC and install the patch manually.
In some cases with users receiving "Error retrieving form data: 500" on inquire into Portal forms, reinstalling msxml.msi and msxml4sp2-kp8876606 has resolved the issue.


Additional Information:
A note to Lawson clients: please review the following information with your IT/IS staff.

Microsoft Patch Deployment Considerations:
Upgrading Internet Explorer (IE) 5.5 clients to IE 6.x
This affectively reverts the client machine back to MSXML 3.x. When Internet Explorer security updates are applied they will re-introduce the problem corrected by the MSXML hotfix 887606.

Deploying third-party applications that include an MSXML Parser
This will revert the client machine back to whatever version of the MSXML parser is bundled with the respective application.

Solution:
Bundle MSXML 4.0 SP2 + MSXML Hotfix 887606 with the upgrade to IE 6.x and/or other third-party applications. This solution applies to any client that is deploying an application (through upgrades or otherwise) that include MSXML parsers.