on 06-04-2013 12:16 PM
Hi,
Strange problem. We are running BO4 SP5 patch 3. Users are visiting Launch Pad using a custom URL (like http://reports.companyname.com). This is done with a DNS record.
BO is also reachable with the original URL: http://bo4-servername-prod/BOE/BI.
Problem:
We open Launch Pad using http://reports.companyname.com. Then open a Webi report with a prompt. Refresh it and click export to PDF (using the print or export-button). A PDF-file is generated and opened in Adobe reader.
We close Adobe Reader, go back to BI Launch Pad and refresh the report with different prompt values. Again, we click 'export to pdf' and a pdf file is opened in Adobe Reader, but with still the old report data from previous refresh. Even when refreshing and exporting the report again, the PDF-file is still showing old data. When trying it again after a few hours the pdf is refreshed the first time, but again after refresh and exporting the report, it shows the older version.
When opening Launchpad using the original URL http://bo4-servername-prod/BOE/BI there is no problem and the PDF-file is always showing the same as in Webi. So I don't think this is a IE or Adobe caching problem.
It looks like the problem is related to this custom URL and cache. Does anyone else have this same problem with a custom URL? Is there a solution for this?
I think I found the cause of the problem. In the web browser there is a proxy configured. In the proxy settings of internet explorer I made an exception for reports.companyname.com and everytime the updated version of the pdf is shown now. Probably the proxy server caches pdf files from 'internet' URL's and not from local URL's.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In my case the solution was to disable the proxy. Maybe in your network there is a transparent proxy (http://en.wikipedia.org/wiki/Proxy_server#Transparent_proxy) or something like that? You could consult your network administrator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Hilbrads,
You may need to clear the cache at client side. Check if this could help you.
Regards,
Mani
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.