Author Archives: henryallgood

About henryallgood

BI developer

Creating a 4.1 Webi doc from a personal file

Webi in a web browser:

  • In order to create a Webi report from an Excel file you need to be using the Java report builder, it is not available through the HTML report builder
  • The Excel file needs to be uploaded into BI4 before it can be selected – Webi can’t see your local drives or network shares
  • An Excel file uploaded into BI4 needs to be manually updated, you can’t select an Excel report instance yet

Using Webi Rich client:

  • You can select local or BI4 Excel files. It’s a pain selecting a spreadsheet from network shares as they dont appear in the  ‘Open a document’ window – need to type in full location and name e.g. \\server1\folder1\excel_doc.xlsx
  • Best to upload spreadsheet into BI4, then use ‘Replace File’ when you want to update the data in it
  • You can have both versions of the Webi Rich client (XI3.1 & BI4) installed on a PC without issue
  • You can also create a report from a text or CSV file using Rich client – avoid this and standardise on Excel as you have more options
Advertisements

SQL Server Native Client & OS Support

Useful link: https://msdn.microsoft.com/en-us/library/cc280356.aspx

Table from this site:

The following table lists which operating systems support SQL Server Native Client.

SQL Server Native Client version Supported operating systems
SQL Server Native Client (SQL Server 2005)
  • Microsoft Windows 2000 Service Pack 4 or later
  • Microsoft Windows Server 2003 or later
  • Microsoft Windows XP Service Pack 1 or later
  • Microsoft Windows Vista (requires SQL Server Service Pack 2, or later)
  • Microsoft Windows Server 2008 (requires SQL Server Service Pack 2, or later)
SQL Server Native Client 10.0 (SQL Server 2008)
  • Microsoft Windows Server 2003 Service Pack 2, or later
  • Microsoft Windows XP Service Pack 2, or later
  • Microsoft Windows Vista
  • Microsoft Windows Server 2008
SQL Server Native Client 10.5 (SQL Server 2008 R2)
  • Microsoft Windows Server 2003 Service Pack 2, or later
  • Microsoft Windows XP Service Pack 2 or later
  • Microsoft Windows Vista
  • Microsoft Windows Server 2008
  • Microsoft Windows 7
SQL Server Native Client 11.0 (SQL Server 2012 and SQL Server 2014)
  • Microsoft Windows Vista
  • Microsoft Windows Server 2008
  • Microsoft Windows 7
  • Microsoft Windows 8
  • Microsoft Windows Server 2012

 

 

BI4 Increase Time Outs

1 .BI Launchpad

Default session time out = 20 minutes.

Change session setting in web.xml file
Go to \SAP BusinessObjects\tomcat\webapps\BOE\WEB-INF
Open web.xml file and search for the following:<session-timeout>20</session-timeout>
Change the number to the number of minutes you require for BI Launchpad.

2. WebIntelligence
Default connection time out = 20 minutes.

Change ‘Idle Connection Timeout’ on all WebIntelligence Processing Servers to required value.
Note: The higher the value the longer connections will remain idle.

3. APS Specific Time Outs

Set these all to be the same as your Webi time out to reduce errors.

Web Intelligence Monitoring Service

Default Monitored Resource Cleanup Timeout (in seconds)

DSL Bridge Service

DSLBridge Engine Cleanup Timeout (in seconds)

Visualization Service

Visualization Engine Cleanup Timeout (in seconds)

 

Restart Tomcat & SIA services

Once ‘Idle Connection Timeout’ has been reached, a WebIntelligence user will see this error:
WebiError

Invalid setting in Excel key of the Engines section of the Windows Registry. (3433)

Situation

A Desktop Intelligence report using a personal data provider errors on refresh with the error “Invalid setting in Excel key of the Engines section of the Windows Registry. (3433)”

Error Message

Solution

In 64-bit Windows 7, a registry entry is created that Business Objects Desktop Intelligence uses. It is this entry that can become ‘corrupted’ with entries that are over 3 characters long.

To locate the entry press F3 and type Jet into the search box using these search settings to narrow the list to review:

jet

Review each one until you find an “Extensions” entry that has more than 4 characters in it:
“Extensions”=”txt,csv,tab,asc,xlsx”

In this case the “xlsx” is causing the problem. You can remove this entry so you are just left with:
“Extensions”=”txt,csv,tab,asc,xls”

The report then refreshes as normal.