Cannot run solman_setup & mopz after SPS30 (browser not supported)

[benoit-schmid]

Hello,

We have just applied the SPS 30.

Now we have the following error for the mopz or solman_setup.

What has happened? The call of URL http://xxx.uuu.ch:8000/sap/bc/webdynpro/sap/wd_sise_main_app has been terminated due to an error.

Note The following error occurred in system SSM : This browser is not supported The error occurred on application server xxx_SSM_00 and in work process 5 . The termination type was: ERROR_MESSAGE_STATE The ABAP call hierarchy was: Method: CLIENT_INSPECTOR_CREATE_CLIENT of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP Method: _HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME Module: %_HTTP_START of program SAPMHTTP

What can you do? In the case of termination type RABAX_STATE, you will find more information on the cause of termination in system SSM in transaction ST22. In the case of termination type ABORT_MESSAGE_STATE, you will find more information on the cause of termination on application server xxx_SSM_00 in transaction SM21. In the case of termination type ERROR_MESSAGE_STATE, you can search for more information in the trace file for the work process 5 in transaction ST11 on application server xxx_SSM_00 . An analysis of the trace files for other work processes may be necessary. If you do not yet have any user ID, contact your system administrator. Error Code: ICF-IE-http -c: 001 -u: J2EE_ADMIN -l: E -s: SSM -i: xxx_SSM_00 -w: 5 -d: 20130107 -t: 145854 -v: ERROR_MESSAGE_STATE -e: This browser is not supported -X:  -x: HTTP 500 - Internal Server Error Your SAP Internet Communication Framework Team

Would you know what I could do to solve this problem?

Thanks in advance for your answer.

[Former Member · Accepted solution]

Hi Benoit,

Below is an old note but the symptoms look quite same,You can try the steps described in the note,

Note 1724418 - WDA: Browser is not supported - User agent blocker

Thanks,

Jagadish.

[benoit-schmid · Accepted solution]

jagadish gudla wrote:
Hi Benoit,
Below is an old note but the symptoms look quite same,You can try the steps described in the note,
Note 1724418 - WDA: Browser is not supported - User agent blocker
Thanks,
Jagadish.

Hello,

Point 1 and 2 of Note 1724418 were ok.

But Point 3 and 4 have solved my problem.

Which search criteria have you used on the marketplace to find out this note? 

Thanks for your quick help.

[Former Member · Accepted solution]

Hi Benoit,

It was a indirect search in fact, I got the note 1788592 where there is a link to the above note.

Thanks,

Jagadish.

[kkypris · Accepted solution]

Hi,

The note you suggested solved the problem for me as well.

Thanks,

[Former Member]

1 Method:- Simple copy URL from IE and paste other browser.

2.Method:-

1. Call transaction SE11 and create the following domains:

• Domain: WDR_APP_PROP_ALLOW_USER_AGENTS

• Description: Allow User Agents

• Package: SWDP_RUNTIME_CORE

• Data Type: CHAR

• Length: 10

• Add the following value ranges:

• Fix.Val.: SUPPORTED

• Short Descript.: Supported

• Fix.Val.: TOLERATED

• Short Descript.: Tolerated

2. Call transaction SE11 and create the following data element:

• Data element: WDR_APP_PROP_ALLOW_USER_AGENTS

• Short Description: Allow User Agents

• Package: SWDP_RUNTIME_CORE

• Domain: WDR_APP_PROP_ALLOW_USER_AGENTS

• Add the following field labels:

• Short: User Agent

• Medium: Allow User Agents

• Long: Allow User Agents

• Heading: Allow User Agents

• Save and activate the changes.

3. Call transaction SE16 and open the database table WDY_APP_PROP_DEF. Maintain the following entry:

• SET NAME: STANDARD

• PROPERTY_NAME: WDALLOWEDUSERAGENTS

• ALIAS_NAME: wdAllowedUserAgents

• DEFAULT_VALUE: TOLERATED

• PROPERTY_KIND: 4

• MIN_LEVEL: 1

• MAX_LEVEL: 5

• ABAP_TYPE: WDR_APP_PROP_ALLOW_USER_AGENTS

• DESCRIPTION: Allow User Agents

• Save your changes.

• Display the new entry and select it.

• In the menu, choose "Table Entry" -> "Transport Entries".

• Select or add a transport request from the dialog box to transport the entry. Choose "OK".

4. Call transaction SHMM.

• Choose the instance CL_WDR_CONF_APPL_SHM.

• Choose the symbol for deletion from the table toolbar (garbage can to the right) to delete all instances from the shared memory.

[Former Member]

Hi,

  Can you please let us know the browser name and version you are using?

As well as please share the components version levels ?

Thanks and Regards,

Vimal

[benoit-schmid]

Hello,

It seems to be related to the 8 browsers testrd with user agent switcher 🙂

Therefore it is not a browser problem, as far as I guess.

Regards,

[Former Member]

Hi,

  You can also go through the below link for more information.

http://www.howtogeek.com/howto/18450/change-the-user-agent-string-in-internet-explorer-8/

Thanks and Regards,

VImal

[benoit-schmid]

Hello,

As said in my previous email testing with different user agent strings had already been performed.

Regards,