cancel
Showing results for 
Search instead for 
Did you mean: 

First WDA (Hello World) not working in IE but looks good in FireFox.

Former Member
0 Kudos

Hi,

My Hello World App in WD is not working in Browser IE. So I can't TEST it in SE80. It only shows a blank page and a javascipt error...

Taking the same URL in Firefox works just fine....

BSP apps is working just fine in both browsers.

sapr3d.korkow is inside a "single label domain"

http://sapr3d.korkow/sap/bc/webdynpro/sap/zwd_test2?sap-system-login-basic_auth=X&sap-client=300&sap...

I have looked at the Config Manuals for WDA. FQDN etc.

RZ10 now looks like this

icm/host_name_full sapr3d.korkow

rdisp/rfc_min_wait_dia_wp 5

rsdb/ntab/irbdsize 8000

rsdb/ntab/ftabsize 35000

rsdb/esm/buffersize_kb 6144

rsdb/cua/buffersize 5000

zcsa/installed_languages DEFKNOV

abap/buffersize 400000

DIR_EPS_ROOT F:\usr\sap\trans\EPS

DIR_TRANS
$(SAPTRANSHOST)\sapmnt\trans

SAPTRANSHOST sapr3d

SAPSYSTEMNAME U01

SAPGLOBALHOST sapr3d

SAPSYSTEM 00

INSTANCE_NAME DVEBMGS00

DIR_CT_RUN $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64

DIR_EXECUTABLE $(DIR_INSTANCE)\exe

PHYS_MEMSIZE 9059

rdisp/wp_no_dia 16

rdisp/wp_no_btc 4

rdisp/max_wprun_time 900

icm/keep_alive_timeout 180

icm/server_port_0 PROT=HTTP,PORT=80,TIMEOUT=0,PROCTIMEOUT=180

ms/server_port_0 PROT=HTTP,PORT=81$$

rdisp/wp_no_enq 1

rdisp/wp_no_vb 4

rdisp/wp_no_vb2 2

rdisp/wp_no_spo 1

In my hosts file I have:

.............

127.0.0.1 localhost

178.18.8.15 SAPR3D

..................

Any Pointers ?

Br,

Martin

Accepted Solutions (0)

Answers (1)

Answers (1)

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

Well that is a switch. Normally I see problem messages where things work fine in IE, but not in FireFox. You say that BSPs run fine in IE but not the WDA. I doubt then that there is a problem with the configuration on the server/FQDN since BSP and WDA share roughly the same checks in that regard.

What version of IE? What are the details of the JavaScript error you are receiving? I first guess is that you have a very locked down version of IE and some security setting is restricting the normal WD functionality. The exact JavaScript error might shed some light on that.

Former Member
0 Kudos

Hi,

I'm using IE 7.0.5730.13

I also "fixed" securtiy settings to be as Low as possible....

(Below message I could not cut and paste... so there may be some spelling misstakes.)

First javascript error:

Line: 10

Char: 13

Error: Invalid argument

code: 0

URL: http://sapr3d.korkow/sap/bc/webdynpro/sap/zwd_test2?sap-system.

second error (pushing Next button):

same as above but:

URL: http://sapr3d.korkow/sap/bc/webdynpro/ssr/domain_relax.html?000041-1

third error:

same as above but:

URL: http://sapr3d.korkow/sap/bc/webdynpro/sap/zwd_test2~ucfLOADING?sap-contextid=SID.....&sap-wd-clientW...

Any pointers ?

Br,

Martin

Edited by: Martin Andersson on Jun 29, 2008 5:36 AM

Former Member
0 Kudos

Hi,

your URLs don't contain the FQDN, you might remedy that. See also the [documentation|http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm]

Regards, Heidi

Former Member
0 Kudos

Hi,

sapr3d.korkow is a "single label domain"

This means that I do not have a ".ext".

BSP pages works just fine.

FireFox works as well...

//Martin

thomas_jung
Developer Advocate
Developer Advocate
0 Kudos

I'm afraid that the Invalid Argument error doesn't help much. It appears that this error can be produced by many differen situations.

Does this only happen in this one WDA application - or does the problem also occur for some of the standard SAP example applications? Also I don't see anything in the documentation about single label domains being supported. I've never tried them myself, but you might want to take Heidi's suggestion and try making it a Full domain ( <host>.<domain>.<extention>) just to make sure that isn't the cause of the problem.

Former Member
0 Kudos

Belive it or not...

Check for which of your applications security is critical and set the indicator in the Web

Dynpro application accordingly. To do this select the Web Dynpro application in SE80 and go

to the tab page Parameters. Using F4 help on the parameter you can select the entry

WDPROTECTEDAPPLICATION and set its value to X.

Setting this value to X solved my ´problem

//Martin

Former Member
0 Kudos

Hi,

Sorry, this was not the solution. It works anyway (without the parameter).

I don't know what the problem was...maybe some DNS stuff or something...

Anyway: Now it works

Thanks

Martin