on 02-10-2012 11:57 PM
Hello,
I like to train myself in ABAP webdynpro, so I have installed NW 7.02 SP6 EhP2 on a virtual machine (VMware) with Win2008R2.
I have applied with SICF all services as mentioned in OSS note 1088717 describing a list of /default_host/sap/bc/webdynpro/... etc.. as well as some services specificly around view designer.
Furthermore, the file "hosts" is set as follows:
192.168.8.128 dummy.com
192.168.8.128 PALATINVIRT1 PALATINVIRT1.dummy.com
10.10.0.10 PALATINVIRT1 PALATINVIRT1.dummy.com
whereas PALATINVIRT1 is the name of my host installed with Win2008R2 and NW 7.02..
Finally, ping tests are successfully for:
palatinvirt1
palatinvirt1.dummy.com
dummy.com
All of them are replying with 192.168.8.128.
Instance parameter icm/host_name_full is set to "palatinvirt1.dummy.com" (checked via transaction RZ10).
If I launch SE80, select "Web dynpro components" in order to check my view , I can open the view and click on tab "Layout" but I'm not able to see the generated HTML page as well as I don't see any UI element toolbar if I'm switching in edit mode. Instead, I will get a script error "The value of property " wdp_edit_on" is Null" and then "URL: res://iframe.dll/dnserrordiagoff_web_OC.htm".
If I check some activated services, especially the tutorial webdynpro applications (I have activated them in SICF), I will get a typical error "Web page cannot be displayed". So, it looks like a generic error I have.
Does anyone know which setting I have to check?
Hi Stephen,
Not sure what exactly the issue is but i would suggest you update to the latest available basis support pack.
Thanks,
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello to All,
I have found the reason for the error: resolution of my URL was not possible.
If you get such errors, this does not have anything to do with service pack updates or so or ICF services.
If you are driving a scenario virtual machine VMware with NW02 installed as well as SAPGUI installed on your physical PC (host PC) and you have no DNS server running on your host, then you have to define a mapping of your VM IP address to the FQDN.
I also have installed the Microsoft Loopback adapter, assigned to IP address 10.10.0.10 on my VM.
In my case, palatinvirt1.dummy.com is the FQDN.
Therefore, on VM the file HOSTS in directory c:\windows\system32\drivers\etc should contain:
192.168.8.128 dummy.com
192.168.8.128 palatinvirt1 palatinvirt1.dummy.com
10.10.0.10 dummy.com
This will enable each kind of requests via WAS.
On your host PC, it is also required to define a correct mapping for the palatinvirt1.dummy.com address, otherwise your host does not know where to look at.
So, modify on your host PC the file HOSTS in directory c:\windows\system32\drivers\etc:
192.168.8.128 palatinvirt1.dummy.com
This solved my problem.
I also recommend to fix the IP address on your VM and not to use DHCP service on top, otherwise you are risking of getting different IP addresses next time you are starting new your VM.
Yours
Stephan
User | Count |
---|---|
94 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.