cancel
Showing results for 
Search instead for 
Did you mean: 

RELEASE_DATA_PROVIDER problem - 'page cannot be displayed'

Former Member
0 Kudos

We are having trouble using the 'RELEASE_DATA_PROVIDER'

command URL. The problem appears to be workstation

related, though we've not been able to figure out the

cause or a solution. On some machines, the command URL

works fine; on others, it results in a 'The page cannot be

displayed' error; the same error that shows up when you

attempt to navigate to a web site that doesn't exist (HTTP

404, I think).

<b>

var layoutURL = '<SAP_BW_URL>' +

'&DATA_PROVIDER=DATAPROVIDER_1' +

'&CMD=RELEASE_DATA_PROVIDER' +

'&TEMPLATE_ID=ZTEMPLATE_WIZARD' +

'&APPLY_CMD_ON_TARGET=X' +

'&CMD_1=ITEM%3DCHECKBOXES_1%26IOBJNM%3D' + struct1 +

'&CMD_2=ITEM%3DCHECKBOXES_2%26IOBJNM%3D' + struct2;

window.open (layoutURL);

</b>

One thing that we have noticed is that the URL in the

address bar of the new window is different on the machines

that work vs. those that don't.

Broken Machine:<b>

http://db1as1.rohmhaas.com:8080/sap/bw/BEx?

SAP-LANGUAGE=E&PAGENO=2&REQUEST_NO=2

&DATA_PROVIDER=DATAPROVIDER_1

&CMD=RELEASE_DATA_PROVIDER

&TEMPLATE_ID=ZTEMPLATE_WIZARD

&APPLY_CMD_ON_TARGET=X

&CMD_1=ITEM%3DCHECKBOXES_1%26IOBJNM%3D3X6WWZYC072PVLI4PMEJCF6EJ

&CMD_2=ITEM%3DCHECKBOXES_2%26IOBJNM%3D3X75WFS9UUDUKNEN6CYLQW9IJ

</b>

Working Machine:

<b>

http://db1as1.rohmhaas.com:8080/sap/bw/BEx?

SAP-LANGUAGE=E&PAGENO=1

&ACCEPT=image%2fgif%2cimage%2fx-xbitmap%2cimage%2fjpeg%2cimage%2fpjpeg%2capplication%2fx-shockwave-flash%2capplication%2fvnd%2ems-excel%2capplication%2fvnd%2ems-powerpoint%2capplication%2fmsword%2c%2a%2f%2a

&CMD=LDOC

&CMD_1=ITEM%3dCHECKBOXES_1%26IOBJNM%3d3X6WWZYC072PVLI4PMEJCF6EJ

&CMD_2=ITEM%3dCHECKBOXES_2%26IOBJNM%3d3X75WFS9UUDUKNEN6CYLQW9IJ

&DATA_PROVIDER_ID=3YQFBKMZ6WQ01UAAQHQAW4WMJ

&RELEASED_DATA_PROVIDER=X

&REQUEST_NO=2

&SAP-CONTEXTID=SID%3aANON%3arhux29_DB1_15%3a_SNjrb3O4NuXD3yYgIzyt84X6voSsUHEOwCJ4oPb-ATT

&SAP-LANGUAGE=E

&SAP-SSOLIST=O3I9cmh1eDI5X0RCMV8xNV8xMRUY1MzlGQjlCRTlERjEzMDM5MDhFNjUxMDE0Nzg1QTQyMTcyMg%3d%3d

&SAP-USERCONTEXT=sap-language%3dEN

&SESSION_ID=SID%3aANON%3arhux29_DB1_15%3a_SNjrb3O4NuXD3yYgIzyt84X6voSsUJ4oPb-ATT

&TEMPLATE_ID=ZREPORT_WIZARD

&URL_PREFIX=%2fsap%2fbw%2fBEx%3fSAP-LANGUAGE%3dE%26

&URL_PREFIX_NO_COOKIE=%2fsap(cz1TSUQlM2FBTk9OJTNhcmh1eDI5X0RCMV8xNSUzYV9TTmpyYjNPNE51WEQzeVlnSXp5dDg0WDZ2b1N3dDSjRvUGItQVRU)%2fbw%2fBEx%3fSAP-LANGUAGE%3dE%26

&USER-AGENT=Mozilla%2f4%2e0(compatible%3bMSIE6%2e0%3bWindowsNT5%2e1%3bSV1%3bIE_DTPXP%3b%2eNETCLR+1%2e1%2e4322)

&REQUEST_NO=2

</b>

Any help you can provide would be greatly appreciated;

this issue is driving us nuts. I've tried to set a

breakpoint in the CL_RSR_WWW_VIEW class where the

'RELEASE_DATA_PROVIDER' command is processed, but I cannot

figure out how to get the code to stop there; it seems to

only execute that code when opening in a new window, so I

can't get it to run from RSRT2.

Thanks!

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

What version of IE do you have on the broken machines?

Former Member
0 Kudos

Both the broken and the working machines appear to

be running the same version of IE...

6.0.2900.2180.xpsp_sp2_gdr.050301-1519

Update Versions: SP2

Former Member
0 Kudos

OK. So, we've fixed the problem, without really

understanding why it is happening. After deleting the

cookies on the broken machines, the Command URL now works.

Any suggestion on why this might have caused the problem?

Or what we can do (code-wise) to prevent it in the future?

Thanks.