Error Loading Xml Document From Saw.dll
Us Adventures in OBIEE Upgrade Land: Quirks and Workarounds — Episode I 17th December 2013 by Jeremy Harms ’Tis the season — what season you may ask? Why, the season filled with the joys of OBIEE 11g upgrades to the latest version, of course! Well, it’s that season for me anyway… Lately my brain has been inundated once again with all things pertaining to the fun minutiae that may or may not break when upgrading from one version to another in OBIEE. I figured I’d jot down some notes in a three part series just in case anyone else out there in upgrade land comes across some of the same quirks and needs to find a fix or workaround too. Some of these that I’ll post took longer than I’d initially hoped they would before I found some sort of resolution… So maybe this will be of benefit to someone. But first, a quick overview of the overall moving parts regarding my Oracle BI upgrade: Upgrading from OBIEE 11.1.1.6.5 to 11.1.1.7.131017 Underlying source: JD Edwards EnterpriseOne (JDE E1) OBIEE server OS: Windows Server 2008 R2 RCU DB and custom data warehouse running on Microsoft SQL Server 2012 Here in Episode I, we’ll cover two particular pesky issues I ran up against during this last upgrade: Strange “obips.UberBar.xml” browser pop up error Usage Tracking Not Working With SQL Server Native Client Issue 1: obips.UberBar.xml Error So first, let’s delve into the obips.UberBar.xml issue. Here’s what my users saw every time they clicked on a link (like "Catalog", or "Dashboards") in their new 11.1.1.7.131017 test system: Error loading XML Document from /analytics/saw.dll/uicomponents/obips.UberBar/obips.UberBar.xml?fmapId=QDCZJg. The response given was: At first, I thought for sure this must be related to some new "fantastic" 11.1.1.7.131017 bug, but upon further examination, there was a lot I had to learn about what can and cannot reside within the analyticsRes deployment directory. It was a custom skin/style problem due to how the client had built out their folder structure. Here’s what the new analyticsRes folder looked like initially in the new environment: Apparently when the skin/st
address from host name http://www.emerald-cube.com/2013/12/adventures-in-obiee-upgrade-land-quirks-and-workarounds-episode-i/ error.loading.xml.document.from.saw.dllanswerssaw.selections.xml.pcfixregistrycleaner.com The DNS server returned: Server Failure: The name server was unable to process http://error.loading.xml.document.from.saw.dllanswerssaw.selections.xml.pcfixregistrycleaner.com/ this query. This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct. Your cache administrator is webmaster. Generated Wed, 12 Oct 2016 13:40:51 GMT by s_ac4 (squid/3.5.20)
John Minkjan pointed out a while ago, the XSD (XML Schema) for the OBIEE configuration files can yield some interesting things. I've been looking at obipsconfigbase.xsd and found the following bits http://www.rittmanmead.com/blog/2012/08/advanced-presentation-services-settings-for-obiee-testing-development/ of information which I think could help certain testing and development work with OBIEE. First off, the standard disclaimer about undocumented functionality goes here. None of this is documented, therefore http://arjunonobiee.blogspot.com/2013/02/add-your-company-logo-to-login.html I would imagine completely unsupported, and I can't think of a valid reason for it to ever be used anywhere other than a sandbox/development installation. The options below (except error loading where indicated) come within the TestAutomation element of the Presentation Services instanceconfig.xml configuration. TestAutomation is nested within ServerInstance, thus:
In' message in the login screen. As you'll see below this is basic HTML code editing, so there is plenty of scope to show your logo wherever you want on the login screen. Start off by copying your logo image file to the following three directories: OBIEE_HOME\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\sk_blafp\b_mozilla_4 OBIEE_HOME\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\sk_blafp\login OBIEE_HOME \Oracle_BI1\bifoundation\web\app\res\sk_blafp\login Next we need to copy the some of the files used by OBIEE to display the web pages to a new area so that we can edit them. From theORACLE_HOME\Oracle_BI1\bifoundation\web\msgdbdirectory copy the pages subdirectory to: ORACLE_HOME\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\msgdb If the msgdb directory does not exist, create it first. Now go into the pages\common directory and you'll see one of the files - signin.html. This is the html page that displays the login screen. Take a backup copy of it first before starting. Edit login.html in a text editor. Locate the