cancel
Showing results for 
Search instead for 
Did you mean: 

Javascript error on pop up/search help

Former Member
0 Kudos

Hi,

in the portal I have a transaction iView:

Type: SAP GUI for HTML

Transaction: CADO

When I want to use the search help, which should launch a pop up, nothing happens and I get a javascript error (please see attachment):

object doesn't support this property or method

URI: http://<server>:<port>/sap/public/icmandir/its/lsgui/js/sapItsMapi.js

invalid argument

URI: http://<server>:<port>/sap/public/icmandir/its/lsgui/js/sapItsMapi.js

This is what I have found out so far:

- it works perfectly in our development and test environment, which means I don't think it is caused by the browser.

- 3 weeks ago we didn't have this problem! In the meantime a full backup has been installed and the servers have been restarted.

- test of CADO from SICF (sap/bc/gui/sap/its/webgui) works fine - the pop up is shown

- I have republiced the services regarding SAP GUI for HTML

Do anybody have an idea of what is wrong?

Thanks in advance

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member194364
Active Contributor
0 Kudos

Hi Trine,

What Kernel version are you on? Version and Patch level?

I have seen "sapItsMapi.js" js error resolved with note 1736723

OR  else reapplying the Kernel again.

Regards,

Oisin

Former Member
0 Kudos

Hi Oisin

Thanks for your answer.

We are on version 7.01 patchlevel 113005.

It's seems strange that a note is required to make it work, because we actually didn't have this problem 3 weeks ago.

Do you think a restart or the full backup is the reason why this javascript error suddenly appear? and maybe we need to reactivate something to make search help work again.

Thanks in advance,

Trine

former_member194364
Active Contributor
0 Kudos

Hi Trine,

I agree re note; anyhow you are not on a Kernel version that note 1736723 fixes.

Full backup and the system restart could perhaps explain the change.

That is why I suggested reapplying the Kernel again. It perhaps did not extract correctly.

The ITS.SAR package comes whithin the disp+work.SAR package and it is up

to the ICM to extract it. This issue might have been caused by the

incorrect path to the ITS.SAR set by the icm/HTTP/file_access_0

parameter or even the disp+work files were not extracted in the correct

location? Compare against the Test and Development systems.

Regards,

Oisín