BusinessObjects Extended Analytics
Administration guide
BusinessObjects Extended Analytics 4.1
Copyright
Copyright © 2007 Business Objects. All rights reserved. Business Objects owns the following
U.S. patents, which may cover products that are offered and licensed by Business Objects:
5,555,403; 6,247,008; 6,289,352; 6,490,593; 6,578,027; 6,768,986; 6,772,409; 6,831,668;
6,882,998; 7,139,766; 7,181,435; 7,181,440 and 7,194,465. Business Objects and the
Business Objects logo, BusinessObjects, Crystal Reports, Crystal Xcelsius, Crystal
Decisions, Intelligent Question, Desktop Intelligence, Crystal Enterprise, Crystal Analysis,
Web Intelligence, RapidMarts, and BusinessQuery are trademarks or registered trademarks
of Business Objects in the United States and/or other countries. All other names mentioned
herein may be trademarks of their respective owners.
Third-party
contributors
Business Objects products in this release may contain redistributions of software licensed
from third-party contributors. Some of these individual components may also be available
under alternative licenses. A partial listing of third-party contributors that have requested or
permitted acknowledgments, as well as required notices, can be found at:
http://www.businessobjects.com/thirdparty
Contents
Chapter 1 Administrating the databases 3
SSAS 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
SSAS database security configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 4
SSAS database backup / restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Cubes optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
SSRS 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 2 Securing the BusinessObjects Extended Analytics platform 17
Securing the Deployer component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing X.509 certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing a private key and a public key on the Reporter server . . . . . 19
1. Obtaining a certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2. Installing the certificate in the personal store . . . . . . . . . . . . . . 19
3. Configuring security of the private key with WSE 3.0 . . . . . . . . 20
4. Declare the certificate name in the Configuration Manager . . . 25
Configuring BusinessObjects Extended Analytics with firewalls . . . . . 25
Chapter 3 Platforms administration 29
Configuration Manager settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Importing / exporting platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Importing a platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Creating a platform for Star Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Chapter 4 Log/monitoring 41
Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Log configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Accessing / using the EntLibConfig.exe tool . . . . . . . . . . . . . . . . . . . . 42
File configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Log categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Administration guide 1
Contents
Specific configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
UDF for Security component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Chapter 5 Appendix 49
Configuration file details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 0
Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Default session timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Analyzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Web sites properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Chapter 6 Troubleshooting 55
2 Administration guide
Administrating the databases
chapter
Administrating the databases
1
SSAS 2005
SSAS 2005
SSAS database security configuration
When BusinessObjects Extended Analytics Deployer creates the database,
the security options are configured properly. However, if you restore a
database or if you encounter any problems, you may want to check the
security options.
1. Open the database properties.
The following window will appear:
2. Click on ImpersonateServiceAccount.
4 Administration guide
The following dialog box will appear:
3. Check that the Use the service account or Default is selected. If other
options are selected, the database will not function.
SSAS database backup / restore
Y ou cannot save or restore individual cubes; the Backup/Restore functionality
applies at the database level. You can access this functionality through SQL
Server Management Studio.
Since the cubes generated by BusinessObjects Extended Analytics are
MOLAP cubes (data is stored in SSAS), the backup of the SSAS database
contains a complete image (structure and data) of this database. During the
restore process, the data saved in the backup will be stored in the cube: there
is no resynchronization with the relational database:
• If proactive caching/live access is not activated, this backup can be
restored independently of the relational database (BusinessObjects
Finance database).
• If proactive caching/live access is activated, the cubes and their related
dimensions will resynchronize when modifications are made in the
BusinessObjects Finance database. In this case, the cubes would not be
up to date: they would be synchronized with dimensions and partitions
that have been modified in BusinessObjects Finance since the last
restore of the SSAS database, but not with other dimensions and
partitions. It is therefore strongly recommended that you resynchronize
the SSAS database with the BusinessObjects Finance database if it uses
proactive caching.
Administrating the databases
SSAS 2005
1
Administration guide 5
Administrating the databases
1
SSRS 2005
To resynchronize a restored SSAS database with a re lational database (i.e. to
update the data, the structure itself does not change), it must be reprocessed:
the process command is accessible in SQL Server Management Studio. The
process command must be executed on the complete database using the
process full option.
Once the database is restored, you must check that the security options of
the database are correctly configured as explained in the section “SSAS
database security configuration” on page 4.
Cubes optimization
Designer has no functionality for optimizing cubes: all BusinessObjects
Extended Analytics cubes have the same settings (dimensions and MOLAP
partitions, no aggregation). The SSAS administrator can manually modify
these settings using Microsoft tools (Visual Studio and Management Studio).
However, BusinessObjects Extended Analytics does not recognize these
modifications and thus will overwrite them when the cube is redeployed.
Nevertheless, the Microsoft recommendation is increase the memory as
much as possible to enhance performance.
SSRS 2005
SSRS 2005 is made up of the following components:
• A SQL Server Reporting Services service
• A web site Report Server
• A web site Report Manager
• A reports database
• A database used to store the temporary work tables
• An SMTP server
• A set of Windows accounts that run all of the previous components
In order to plug and manage all these components, you can use the
Reporting Services Configuration Manager. This graphic assistant is
especially useful for the following cases:
• When SQL Server is installed on a separate machine
• When you did not use the configuration assistant during setup and
consequently you have to manually configure SQL
• When the application does not function correctly and you need to run a
diagnostic
6 Administration guide
Administrating the databases
SSRS 2005
The Reporting Services Configuration Manager should not display any red
icons. If this occurs, you will have to fix the problem in the relevant component
and then restart the Configuration Manager to ensure that the component is
now running properly.
The following screen shots present each page of the Configuration Manager
and its functionality.
Tip: To find out more about the Configuration Manager, you can consult the
corresponding Microsoft Online Help.
Report Server Status
1
The Report Server Status page provides information about the report server
instance you are configuring and shows the status of the Reporting Services
service.
Administration guide 7
Administrating the databases
1
SSRS 2005
Report Server Virtual Directory
The Report Server Virtual Directory page provides information about the
virtual directory configuration for the report server and allows you to deploy
the Reporting services web service to IIS.
8 Administration guide
Report Server Manager Directory
Administrating the databases
SSRS 2005
1
The Report Server Manager Directory page provides information about the
virtual directory configuration used to access Report Manager and allows you
to deploy the Reporting services administration web site to IIS.
Administration guide 9
Administrating the databases
1
SSRS 2005
Windows Service Identity
The Windows Service Identity page provides information about the Report
Server Windows service settings and allows you to define the windows
account used to run the Reporting Services service.
10 Administration guide
Web Service Identity
Administrating the databases
SSRS 2005
1
The Web Service Identity page provides information about the Report Server
Web service settings for Internet Information Services and allows you to
define the windows account used to run the Reporting Services web sites.
Administration guide 11
Administrating the databases
1
SSRS 2005
Database Setup
The Database Connection page provides information about the report server
databases that store reports, report models, and server metadata. You can
use this page to define or modify the SQL Server Report database name,
login and location.
It also allows you to migrate previous Report databases, and to install the
SQL Server engine on a machine other than the Reporter server.
12 Administration guide
Encryption Keys
Administrating the databases
SSRS 2005
1
The Encryption Key page provides information about the encryption keys
used by Reporting Services.
Warning: We strongly recommend that you do not change these
parameters.
Administration guide 13
Administrating the databases
1
SSRS 2005
Initialization
The Initialization page provides information about the initialization status for
report server instances.
If the corresponding icon is red, click on the Initialize button to initialize the
instance status.
14 Administration guide
Email Settings
Administrating the databases
SSRS 2005
1
The E-mail Settings page provides information about the report server email
delivery extension settings.
To find out more about the email configuration, see the Configuring settings
for sending email via SSRS chapter of the Installation guide.
Administration guide 15
Administrating the databases
1
SSRS 2005
Execution Account
The Execution Account page provides information about unattended
execution account configurations.
This is not used by BusinessObjects Extended Analytics.
Tip: To find out more about the Reporting Services Configuration Manager,
you can consult the corresponding Microsoft Online Help.
16 Administration guide
Securing the BusinessObjects Extended Analytics platform
chapter
Securing the BusinessObjects Extended Analytics platform
2
Securing the Deployer component
Securing the Deployer component
It is possible to secure the Deployer component by installing it on two different
servers. One server will be used as the main Deployer server, the other one
will be used as a backup server. You can automatically switch from one server
to the other with a load balancing mechanism.
If you want users to connect to Deployer using one URL only , you can specify
this using a load balancer in fail-over mode.
Y ou ne ed to install Deployer on two different machines with the same settings
and the same URL. The load balancing can be handled with either Microsoft
NLB or a load balancer device. On a two-node NLB cluster, install Deployer
on each node with the same settings.
Warning: The load balancing device must be configured in fail-over mode,
not in load balancing mode. Only one Deployer server can be used at a time.
Installing X.509 certificates
BusinessObjects Extended Analytics uses standard public key encryption to
support authentication. This is a reliable way to establish a disconnected trust
relationship between different modules in order to provide federated
authentication.
In this respect, BusinessObjects Extended Analytics Reporter plays the role
of a Security T oken Se rver . Thus, Reporter will generate and sign the security
token. In order to do so, Reporter uses the private key of an X.509 certificate
installed on the Reporter machine. The corresponding certificate could be
either a corporate certificate or a generated self-signed one.
Reporter needs to access the "private" certificate (containing the private key)
whereas Reporting Services and Analysis Services only need to access the
"public" one.
To install X.509 certificates, the following steps are required:
1. Install a private key and a public key on the Reporter server.
2. Assign the correct access rights to the account that will run
BusinessObjects Extended Analytics.
3. Set up the relevant configuration files.
4. Install a public key on the SSAS server and configure the relevant
configuration files.
18 Administration guide
Securing the BusinessObjects Extended Analytics platform
Installing X.509 certificates
Note: The BusinessObjects Extended Analytics setup installs and uses a
default X.509 certificate. With this default X.509 certificate, you can use
BusinessObjects Extended Analytics in a test or a development configuration.
Installing a private key and a public key on the Reporter server
1. Obtaining a certificate
You can buy a certificate from a commercial or a free certification authority , or
you can create a self-signed certificate. To create a self-signed certificate, you
can use the following tool available in the \Redist\Makecert directory of the
BusinessObjects Extended Analytics installation CD. To find out more about
the procedure, see the Microsoft documentation:
http://msdn.microsoft.com/library/default.asp?url=/workshop/security/
authcode/signing.asp.
2. Installing the certificate in the personal store
You must then add the X.509 certificate containing the private key and the
public key in the personal store of the local machine. To do so:
1. Select Start > Run and enter mmc.
A console will appear.
2. Select File > Add/Remove Snap-in.
3. In the Add/Remove Snap-in dialog box, click on the Add button.
4. Select Certificates snap-in and click on Add.
5. Select Computer account and click on Next and then on Finish.
6. Go to the Personal folder and right-click on Certificates.
7. Select All Tasks > Import.
8. Follow the steps required by the Certificate Import Wizard.
2
Administration guide 19
Securing the BusinessObjects Extended Analytics platform
2
Installing X.509 certificates
Note: To install a certificate, you can also use the Makecert executable or
follow the procedure delivered with your certificate.
3. Configuring security of the private key with WSE 3.0
As an ASP .NET application, Reporter runs on either the ASPNET (IIS 5.1) or
NETWORK SERVICES (IIS 6.0) accounts which have limited rights and thus
cannot access the machine store private keys.
Therefore, you must either configure the Reporter application to run on an
identity with enough privileges or grant those accounts access to the specific
key which will be used for signing. You can do this with the WSE X.509
Certificate Tool.
To install Microsoft WSE 3.0, follow this procedure:
1. Double-click on Setup.exe located in the BusinessObjects Extended
Analytics\Redist\WSE3.0 folder of the installation CD.
The following dialog box will appear.
20 Administration guide
Securing the BusinessObjects Extended Analytics platform
Installing X.509 certificates
2. Click on Next.
The following dialog box appears.
3. Check the I accept the terms in the license agreement box and click
on Next.
The following dialog box appears.
2
4. Check the Administrator box and click on Next.
Administration guide 21
Securing the BusinessObjects Extended Analytics platform
2
Installing X.509 certificates
The following dialog box appears.
5. Click on Install and on Finish.
6. Once the setup is completed, select Start > All Programs > Microsoft
WSE 3.0 > Certificates Tool.
The following dialog box appears.
7. In the Certificate Location dropdown list, select Local Computer and in
the Store Name dropdown list select Personal.
8. Click on Open Certificate.
22 Administration guide
Securing the BusinessObjects Extended Analytics platform
Installing X.509 certificates
The following dialog box appears.
9. Select the certificate you want to edit and click on OK.
Once the certificate is selected, the Key identifiers appears.
2
10. Click on View Private Key File Properties.
Administration guide 23
Securing the BusinessObjects Extended Analytics platform
2
Installing X.509 certificates
The following dialog box appears.
11. Select the Security tab.
12. Grant Read permissions to the account on which BusinessObjects
Extended Analytics Reporter runs (by default it is ASPNET on Windows
XP and NETWORK SERVICE on Windows 2003).
13. If you are using the Windows authentication, add the Anonymous user of
the Reporter web site by granting Read permissions to the Internet Guest
Account (by default named IUSR_Myservername) Windows user
account.
24 Administration guide
Securing the BusinessObjects Extended Analytics platform
Installing X.509 certificates
14. Click on Apply and OK.
4. Declare the certificate name in the Configuration Manager
1. Open the Configuration Manager (for instance: http://vm-dtdeployer/
ConfigurationManager/).
2. Edit the BusinessObjects Extended Analytics platform you want to
modify.
3. In the General Settings page, enter the certificate name you just
installed.
4. Click Save and Deploy Changes.
Configuring BusinessObjects Extended Analytics with firewalls
BusinessObjects Extended Analytics is made up of many components that
comunicate with each others. If you want to use firewalls, see below a
diagram of the architecture and the list of ports to open.
2
Administration guide 25
Securing the BusinessObjects Extended Analytics platform
2
Installing X.509 certificates
Configuration of Finance database in CtAdmin
Protocol Source Machine Target Machine
Microsoft SQL TCP (1433 by default) Finance and Webservices SQL
Microsoft SQL UDP (1434) Finance and Webservices SQL
Configuration of Reporting services database
Protocol Source Machine Target Machine
Microsoft SQL TCP (1433 by default) Reporter SQL
Microsoft SQL UDP (1434) Reporter SQL
Microsoft CIFS TCP (445) Reporter SQL
Connection to Configuration Manager
Protocol Source Machine Target Machine
HTTP (80 or 443) User Configuration Manager
Platform configuration with Configuration Manager
Protocol Source Machine Target Machine
HTTP (80 or 443) User Configuration Manager
HTTP (80 or 443) Configuration Manager SSAS
MS-OLAP (TCP 2383) Datapump SSAS
Microsoft SQL TCP (1433 by default) Reporter SQL
Microsoft SQL UDP (1434) Reporter SQL
Connection to Reporter
Protocol Source Machine Target Machine
HTTP (80 or 443) User Configuration Manager
26 Administration guide
Securing the BusinessObjects Extended Analytics platform
Installing X.509 certificates
Cube creation
Protocol Source Machine Target Machine
MS-OLAP (TCP 2383) Deployer SSAS
Microsoft SQL TCP (1433 by default) Deployer SQL
Microsoft SQL UDP (1434) Deployer SQL
Browse a cube with Analyzer
Protocol Source Machine Target Machine
HTTP (80 or 443) User Datapump
MS-OLAP (TCP 2383) Datapump SSAS
Publish a report from Analyzer
Protocol Source Machine Target Machine
HTTP (80 or 443) User Datapump
MS-OLAP(TCP 2383) Datapump SSAS
HTTP (80 or 443) User Reporter
Microsoft SQL TCP (1433 by default) Reporter SQL
2
Administration guide 27
Securing the BusinessObjects Extended Analytics platform
2
Installing X.509 certificates
Report execution (RDL report) on Reporter (Datapump
connection)
Protocol Source Machine Target Machine
HTTP (80 or 443) User Reporter
Microsoft SQL TCP (1433 by default) Reporter SQL
HTTP (80 or 443) Reporter Datapump
MS-OLAP (TCP 2383) Datapump SSAS
Report execution (RDL report) on Reporter (TCP/IP connection)
Protocol Source Machine Target Machine
HTTP (80 or 443) User Reporter
Microsoft SQL TCP (1433 by default) Reporter SQL
Microsoft SQL UDP (1434) Reporter SQL
MS-OLAP (TCP 2383) Reporter SSAS
28 Administration guide
Platforms administration
chapter
Platforms administration
3
Configuration Manager settings
Configuration Manager settings
All settings managed in the Configuration Manager are stored into an XML
file, located in the folder where the Configuration Manager has been installed.
This file is named Configuration.xml. As all settings are stored into this file, it
is highly recommended that you store this file into a secure directory.
The web.xml file allows you to set the name and location of the
Configuration.xml file.
1. Open the web.config file and modify the following lines.
<?xml version="1.0"?>
<configuration>
<configSections>
...
<appSettings>
<add key="ConfigurationFilePath" value="Configuration.xml"/>
<add key="AnalyticsReporterAdminServiceSiteName"
value="CartesisReporterAdminService"/>
<add key="AnalyticsUdfAdminServiceSiteName"
value="CartesisAnalyticsUdfAdminService"/>
<add key="AdminWebServiceTimeout" value="120000"/>
</appSettings>
<connectionStrings/>
<loggingConfiguration name="Logg
2. Add the path to the new location file and modify the name and location of
the Configuration.xml file and save the file.
3. You can modify the AdminWebServiceTimeout parameter to set the
number of minutes after the Configuration Manager will be automatically
disconnected. By default, this parameter is set to 120000 milliseconds (2
minutes).
30 Administration guide
Importing / exporting platforms
Importing a platform
The Configuration Manager Home page allows you to save the configuration
of an existing platform. The Import from XML file allows you to create a new
platform from an existing XML configuration file.
T o import a plat form :
1. Log on to the following URL: http://<deployer_server>/
ConfigurationManager to connect to the Configuration Manager Home
page.
The following window appears.
Platforms administration
Importing / exporting platforms
3
2. Click Import from XML File.
Administration guide 31
Platforms administration
3
Importing / exporting platforms
The following window appears.
3. Click on Browse to select the XML file containing the platforms you want
to import.
4. Select the platforms you want to import and click OK.
32 Administration guide
Platforms administration
Importing / exporting platforms
The platforms you have just imported appear in the platform list.
3
5. Click on Edit to open and deploy the platform you have imported.
Exporting a platform
To export a platform:
1. Log on to the following URL: http://<deployer_server>/
ConfigurationManager to connect to the Configuration Manager Home
page.
Administration guide 33
Platforms administration
3
Importing / exporting platforms
The following window appears.
2. Click Export to XML File.
The following window appears.
34 Administration guide
Platforms administration
Importing / exporting platforms
3. Select the platforms you want to export and click OK.
Save the file into the appropriate folder and close the Configuration
Manager.
3
Administration guide 35
Platforms administration
3
Creating a platform for Star Schema
Creating a platform for Star Schema
To create a platform for Star Schema:
1. Log on to the following URL: http://<deployer_server>/
ConfigurationManager to connect to the Configuration Manager Home
page.
The following window appears.
2. Enter a Platform name.
3. Enter a Master security URL: the URL to the main BusinessObjects
Finance web services.
4. Select the Authentication mode of the login below: Forms or Windows.
The authentication mode depends on the Business Objects data source
security used: Forms (Business Objects authentication) or Windows.
5. Enter a Domain name if you selected the Windows authentication.
6. Enter a Login to the BusinessObjects Finance application.
Note: This login must have administration rights on the BusinessObjects
Finance database.
7. Click OK.
36 Administration guide
The following window appears.
Platforms administration
Creating a platform for Star Schema
3
Note: The parameters you have modified appear in green, but are not
applied until you click Save and Deploy Changes.
You can modify the following parameters by clicking the Change button.
8. Analytics Platform name: you can modify the platform name you
entered in step 3.
9. Administration IP port: This parameter is not used for a Star Schema
platform.
10. Protocol: This parameter is not used for a Star Schema platform.
11. X509 certificate: name of the X509 certificate used to secure
communications between Analytics servers.
12. Password: you can define a password to secure the platform
configuration. Once a password is set, it will be mandatory to change any
platform settings.
Administration guide 37
Platforms administration
3
Creating a platform for Star Schema
13. Click Save and Deploy All to deploy all parameters, even those you did
not modify.
Note: As you are using BusinessObjects Extended Analytics with a Star
Schema database, the General Settings page is the only one you need
to fill in.
38 Administration guide
The platform is now deployed.
Platforms administration
Creating a platform for Star Schema
3
Administration guide 39
Platforms administration
3
Creating a platform for Star Schema
40 Administration guide
Log/monitoring
chapter
Log/monitoring
4
Concepts
Concepts
Because BusinessObjects Extended Analytics is a complex distributed
environment involving different components running across different layers, it
is helpful to enable logging so that problems that occur can be located. The
technical log enables you to trace the events and problems generated by
application processes.
In BusinessObjects Extended Analytics, the component used to log the
application is the Microsoft Enterprise Library Logging Block. All
BusinessObjects Extended Analytics components use it, except the UDF and
Analyzer components.
The EntLibConfig.exe tool is available in the Tools folder of the installation
CD. This tool allows you to configure different elements such as the type of
event logged (also called category sources), the log level or the output
destination (tracelistener) and how the log messages can be filtered
depending on their category or their severity.
Specific category sources are available with BusinessObjects Extended
Analytics, but there are also several default category sources provided with
the EntLibConfig.exe tool:
• All events: all events are taken into account
• Logging Errors and Warnings: all Error or Warning events
• Unprocessed Category: all events not mentioned in the Category
Sources
Log configuration
Accessing / using the EntLibConfig.exe tool
To access the EntLibConfig.exe tool:
1. Navigate to the Redist\EntLibConfig folder of the installation CD and
unzip the contents of this folder onto your hard drive (no specific location
is required).
2. Double-click on EntLibConfig.exe.
3. Open the configuration file you want to edit by clicking on File > Open
Application.
42 Administration guide
Log/monitoring
Log configuration
The Enterprise Library Configuration window appears:
• In the TraceListener view, you can define the destination output of the
BusinessObjects Extended Analytics logs.
• In the SpecialSources view, you can define the specific category
sources you want to use for BusinessObjects Extended Analytics.
• In the Category sources view, you can add the categories for which you
want a specific log. To find out more about the different categories
available, “Log categories” on page 45.
Warning: Do not forget to specify the TraceListener on each
SpecialSource or Category source you want to configure.
4
File configuration
SSRS Security Extension
(The BusinessObjects Extended Analytics components plugged into SSRS
for Security management)
• File name: ReportingServicesService.exe.config
• File name location: C:\Program Files\Microsoft SQL
Server\MSSQL.2\Reporting Services\ReportServer\bin
• Log default location: C:\Program Files\Microsoft SQL
Server\MSSQL.2\Reporting Services\LogFiles
Deployer
• File name: web.config
Administration guide 43
Log/monitoring
4
Log configuration
• File name location: C:\Program Files\Business Objects\Extended
Analytics\Deployer
• Log default location: C:\Program Files\C:\Program Files\Business
Objects\Extended Analytics\Deployer\Log
Reporter
• File name: Site\web.config
• File name location: C:\Program Files\Business Objects\Extended
Analytics\Reporter\Site
• Log default location: C:\Program Files\Business Objects\Extended
Analytics\Reporter\Site\Log
• File name: WS\web.config
• File name location: C:\Program Files\Business Objects\Extended
Analytics\Reporter\WS
• Log default location: C:\Program Files\Business Objects\Extended
Analytics\Reporter\WS\Log
Configuration Manager
• File name: web.config
• File name location: C:\Program Files\Business Objects\Extended
Analytics\ConfigurationManager
• Log default location: C:\Program Files\Business Objects\Extended
Analytics\ConfigurationManager\Log
Designer
• File name: Cartesis.InformationDelivery.Workbench.exe.config
• File name location: C:\Program Files\Business Objects\Extended
Analytics\Designer
• Log default location: C:\Program Files\Business Objects\Extended
Analytics\Designer\Log
44 Administration guide
Log categories
Log/monitoring
Log configuration
4
Category name Application /
Process
Security All All messages related to security
SoapMessage Deployer
Reporter
SSRS
Deployer.WebService Deployer All communication messages
Deployer.ServiceContext Deployer Messages related to Deployer
Deployer.CommandOptimization Deployer All messages related to Deployer
Deployer.Scheduling Deployer All messages related to scheduling
Deployer.SSASConnectionManagement Deployer All messages related to connection
Deployer.StarSchemaDeployment Deployer All messages related to the Star
Note: There are no hierarchies between categories. This means that if you
select the Deployer category, the Deployer.WebService will not also be
selected.
Comment
All SOAP messages between a
Web service and its clients
related to Deployer
security context
message queue optimization
with SSAS
Schema deployment process
Specific configurations
UDF for Security component
The UDF component logs are handled by the default .NET log mechanism,
configured in the Microsoft SSAS 2005 configuration file (UDF runs as part of
SSAS).
This mechanism is different from the one used for other BusinessObjects
Extended Analytics components, and EntLibConfig.exe can’t be used to
define the log level.
The UDF log settings are defined in the default SSAS 2005 log settings file as
a <configuration> node child node.
This file, msmdsrv.exe.config, is located into the C:\Program Files\Microsoft
SQL Server\MSSQL.xxx\ OLAP\bin directory.
Administration guide 45
Log/monitoring
4
Log configuration
There are 2 possible sources:
• default: All UDF logs are taken into account
• [MyDatabase]: Only UDF logs for the mentioned database are taken into
account
There are 2 possible listeners:
• System.Diagnostics.EventLogTraceListener: Log in the Windows event
log
• System.Diagnostics.TextWriterTraceListener: Log in a text file
There are 5 different log levels:
• Critical
• Error
• Warning
• Information
• Verbose
46 Administration guide
Log/monitoring
Log configuration
Following is an log configuration file example:
<system.diagnostics>
<sources>
<!-- Defines the default behaviour for the Security UDF logging -->
<!-- Possible Log levels are
Critical, Error, Warning, Information, Verbose -->
<source name ="default" switchValue="Information">
<listeners>
<add name="FileLog"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="../log/Cartesis.Analytics.AnalysisServices.log"
traceOutputOptions="DateTime,ThreadId"
/>
</listeners>
</source>
<!-- Overloads the behaviour for MyDatabase1
to redirect trace output to a different file -->
<source name ="[MyDatabase1]" switchValue="Error">
<listeners>
<add name="FileLog1"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="../log/Cartesis/MyDatabase1.log"
traceOutputOptions="DateTime,ThreadId"
/>
</listeners>
</source>
<!-- Overloads the behaviour for MyDatabase2
to redirect trace output to a different file
and change the Log level -->
<source name ="[MyDatabase2]" switchValue="Verbose">
<listeners>
<add name="FileLog2"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="../log/Cartesis/MyDatabase2.log"
traceOutputOptions="DateTime,ThreadId"
/>
</listeners>
</source>
</sources>
<trace autoflush="true">
</trace>
</system.diagnostics>
…
4
In this example, UDF will log all Information level messages in the
Cartesis.Analytics.Analysis Services.log file.
All Error messages for MyDatabase1 will also be logged in the
MyDatabase1.log file.
All Verbose logs for MyDatabase2 will also be logged into the
MyDatabase2.log file.
Administration guide 47
Log/monitoring
4
Log configuration
Analyzer
The Security UDF monitors the configuration file. Therefore if its content is
changed the file is reloaded and the changes to the log configuration take
effect at once.
More information can be found here: http://msdn2.microsoft.com/en-us/
library/1txedc80.aspx.
Default logs are generated on the Analyzer computer to the AnalyzerPrj.log
file in the default user temporary folder.
In order to measure performances, you can customize this log by adding the
following registry key: LogPerformances with 1 as the value. In this log file
each performance measure begins with "PERF - ". The key must be created
in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Excel\Addins\ID
Prj.AnalyzerAddIn\LogPerformances
48 Administration guide
Appendix
chapter
Appendix
5
Configuration file details
Configuration file details
Designer
If the Deployer URL has been modified, you will have to apply these
modifications in the Cartesis.InformationDelivery.Workbench.exe.config
file.
1. In the Designer client, navigate to the C:\Program Files\Business
Objects\Extended Analytics\Designer directory.
2. Open the Cartesis.InformationDelivery.Workbench.exe.config file
and modify the following rows:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<appSettings>
<appSettings>
<add key="WebClientTimeout" value="100000"/>
<add key="DuplicateElementsAllowed" value="true"/>
<add key="iAnalysisStarSchemaTableNames"
value="true"/>
<add key="StarSchemaAggregation" value="true"/>
<add key="IsAccountDimensionAggregatable"
value="false"/>
<add key="DeployerUrl" value="http://localhost/
DeployerForFinance/DeploymentService.asmx"/>
<add key="MergeMemberMaxDisplay" value="5000"/>
<add key="AnalyticsConfigurationManagerWSUrl"
value="http://localhost/ConfigurationManager/
ConfigurationManagerService.asmx"/>
<add key="MultiMeasureGroupAnalysis" value="true"/>
<add key="DeployerPollingTimer" value="5000"/>
</appSettings>
<add key="DeployerUrl" value=""/> tag corresponds to the
3.
Deployer URL.
4. The
the timeout value for all web service requests, this includes calls to the
deployer service, the new BusinessObjects Extended Analytics
Configuration Manager service and also the calls to the Finance web
services. The unit of measure is milliseconds.
5. The
to the refresh timeout used during cube deployments. The unit of
measure is milliseconds.
50 Administration guide
<add key="WebClientTimeout" value=""/> tag corresponds to
<Add key="DeployerPollingTimer" value=""/> corresponds
Reporter
Default session timeout
By default, the Reporter timeout session is set to 20mn. You can however
change this setting by editing the Web.config file and modifying the following
line:
• <sessionState cookieless="UseCookies" mode="InProc"/>
In order to customize the timeout, just add [space]timeout=”[minutes]” af ter
the existing settings, as shown in the following example:
• <sessionState cookieless="UseCookies" mode="InProc" timeout="60"/>
Analyzer
There is no specific configuration file for Analyzer. However, in order to avoid
the creation of huge useless reports, you can limit the number of cells
requested from the server.
To do this, there are two DWORD registry entries:
• QueryCellLimit: you must create this entry in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office
\Excel\Addins\IDPrj.AnalyzerAddIn\QueryCellLimit
This key controls the number of cells that would activate the warning
dialog. The value must be a positive integer.
A value of 0 means no limit (same as registry entry not existing). This will
provide an error message informing the user that the request has more
cells than allowed and the query will not be executed.
• QueryCellLimitWarnOnly: you must create this entry in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Office\Excel\Addins\IDPrj.AnalyzerAddIn\QueryCellLimitWa
rnOnly
This key controls whether the query is still executed after the message
about QueryCellLimit is displayed. A value of 0 (same as registry entry
not existing) means that the query will not be executed.
Any value greater than 0 means it's only a warning. This will provide a
warning message and the query will be executed.
You can also deactivate the Anayzer cache by creating the following key.
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Office\Excel\Addins\IDPrj.AnalyzerAddIn\UseMetaDataCache
A value of 0 means that the cache mechanism will not be used.
Appendix
Configuration file details
5
Administration guide 51
Appendix
5
Web sites properties
Web sites properties
Reporter
Once the setups are done, the recommended settings are the following. You
should verify that identify where the Windows account has been specified in
the following two locations: in the data pool and in the website properties.
1. Check the Windows account specified in the Reporter data pool
properties.
2. Check the security settings of the Reporter web site properties.
52 Administration guide
Deployer
Appendix
Web sites properties
Note: This procedure applies to BusinessObjects Finance Deployer
installation.
Once the setup is done, the recommended settings are the following. You
should verify that the Windows account has been specified in the following
two locations: in the data pool and in the website properties.
1. Check the Windows account specified in the Deployer data pool
properties.
5
2. Check the security settings of the Deployer web site properties
Administration guide 53
Appendix
5
Web sites properties
54 Administration guide
Troubleshooting
chapter
Troubleshooting
6
Object: Unable to open solution
Knowledge base article number: 14842
Problem encountered
This problem occurs when you try to open an existing and previously saved
solution. The progress bar moves but the solution does not open.
Resolution
A possible cause is that the connection to the DB server was interrupted
when you were saving the solution or deploying a cube within this solution.
You need to restart the Finance data source in CtAdmin and this will normally
solve the problem.
Object: Analyzer: Unable to start C:\Program Files\Business
Objects\Extended Analytics Analyzer
Knowledge base article number: 15154
Problem encountered
When you try to start Analyzer, the following error message appears: "Excel
cannot be launched".
Resolution
There are four areas to be checked:
Check ActiveX settings in Internet Explorer
Proceed as follows:
1. Open Internet Explorer.
2. Select the Tools > Internet Options menu command.
3. Select the Security tab.
4. In the Local intranet area, click on the Custom Level button.
5. In the Initialize and script ActiveX controls not marked as safe
setting, check the Enable option and click on OK.
6. In the Security tab, click on the "Custom Level" button for "Trusted sites".
7. In the Initialize and script ActiveX controls not marked as safe
setting, check the Enable option and click on OK.
8. Click on OK and close Internet Explorer.
56 Administration guide
Troubleshooting
Check the following keys in the registry
• HKEY_LOCAL_MACHINE\SOFTWARE\Microsof t\Of f ice\Excel\Add ins\Repo
rtPublishing.ReportPublisherAddIn]
• "FriendlyName"="Cartesis ES Report Publisher Add-In"
• "Description"="Report Publishing for Information Delivery Add-In"
• "LoadBehavior"=dword:00000003
The 'loadBehavior' must be set at 3.
• [HKEY_LOCAL_MACHINE\SOFTWARE\Microsof t\Of fi ce\Exce l\Addi ns\IDPrj
.AnalyzerAddIn]
• "Standalone"="1"
• "LoadBehavior"=dword:00000003
• "CommandLineSafe"=dword:00000000
• "FriendlyName"="Cartesis ES ID Add-In"
• "Description"="Cartesis ES ID Add-In"
• "Toolbar"=hex:01,00,01,01,00,00,4c,00
Reactivate the Analyzer add-in
1. Click on About in the Help menu in Microsoft Office Excel.
2. Then click on Disabled Items.
6
For installation in Citrix and Excel 2000 or XP
Check that the
HKEY_LOCAL_MACHINE\Software\Classes\Interface\{000C0601-00000000-C000-000000000046 key exists. Otherwise, you should create it.
Object: Deleted view still appears in Analyzer
Knowledge base article number: 14824
Problem encountered
Although the view has been deleted, it still appears in Analyzer.
Resolution
This problem occurs because the view is a separate object from the cube.
When you deploy a view, a cube is created in MS Analysis Server. Note: the
name of the cube is by default the same as the deployment name created. If
you use Analyzer, you connect the (excel) sheet to a cube and not to a view.
Administration guide 57
Troubleshooting
6
So, when deleting a view, you are in fact just doing that - you delete the view,
but not the cube. In order to delete the cube, you will need access to Designer
or SSAS.
Object: DBError in Analyzer report cell
Knowledge base article number: 14844
Problem encountered
I succesfully created and deployed a cube. In the Analyzer report, I get the
following message in all the cells: "#DBError".
Resolution
The issue is due to the fact that you have deployed a cube with "pro-active
caching" enabled ("Activate Live Access" option in the deployment of the
cube) and that insufficient privileges are granted to the SQL Server user
defined in Finance data source.
In order for proactive caching (live access) to work, the SQL Server used to
connect SSAS to SQL Server (which is the user defined in the Finance data
source) should have System Administrator privileges on SQL Server.
Object: No Analytics in functional profiles
Knowledge base article number: 15707
Problem encountered
This Finance SP1 and SP2 setup problem was referenced by the R&D team
as bug report no. 20725. This bug will be corrected in the next Finance sales
version.
Resolution
You should register the relevant DLL again. To do this, open an MS-DOS
window in the Windows Start menu and go to the Finance directory for the
required version.
You should then run the following command line:
regsvr32
Cartesis.InformationDelivery.Security.MagnitudeRightExtensio
n-win32.dll
58 Administration guide
Troubleshooting
Object: Designer client unable to connect to Finance platform in a different
Windows Domain
Knowledge base article number: 15740
Problem encountered
When a new solution is created using Designer in the Finance database, an
error message appears. The Designer then appears as per normal and you
can create and deploy a view.
The error message is as follows: "Exception getting data sources".
The Event Log indicates that "GetDataSources...error has been returned from
a call to the COM".
Resolution
To correct this problem, you should change one of the DCOM settings on the
server.
1. Ask for the dcomcnfg.reg file from Business Objects Support.
2. Run Designer and the dcomcnfg.reg file on the machine where
Designer is installed.
3. Restart Designer.
6
Object: Windows Installer 3.1 required for installation of BusinessObjects
Extended Analytics
Knowledge base article number: 14971
Problem encountered
Windows Installer 3.1 required for installation of BusinessObjects Extended
Analytics.
Resolution
In order to install BusinessObjects Extended Analytics, one of the
prerequisites is that Windows Installer 3.1 is available on the system. This is
not mentioned in the Installation Guide.
Note: For some OS versions (e.g. Windows 2003) this is a standard
component, and you will not encounter this issue.
For the following OS, this component is not a standard available:
• Microsoft Windows 2000 Service Pack 3 (SP3)
Administration guide 59
Troubleshooting
6
• Microsoft Windows 2000 Service Pack 4 (SP4)
• Microsoft Windows XP
• Microsoft Windows XP Service Pack 1 (SP1)
• Microsoft Windows XP Service Pack 2 (SP2)
• Microsoft Windows Server 2003
Y ou can downlo ad this component from the Microsoft site at the following link:
http://support.microsoft.com/?kbid=893803
Object: Formatting lost when publishing reports
Knowledge base article number: 14741
Problem encountered
When I publish my report, its formatting is lost.
Resolution
This is a known issue. The format applied to all rows is determined by the first
cell of the first row. This applies to all format settings, i.e. font, style, size,
colour etc. This is actually a limitation in RDL (Report Definition Language),
the language used for converting the Excel sheet to web documents.
Some other known limitations are:
• Not all graphs are supported.
• On graphs, the legend should be positionned above or under the graph,
not on the sides.
• The format of all rows is the one applied to the first row of the report.
• Blank columns are supported.
• Blank rows are not supported unless directly under the column header.
• Titles and comment must be inserted inside a text box; only one format of
font can be applied per text box.
• Text boxes must not overlap.
The release note describes the known RDL publishing limitations in greater
detail.
60 Administration guide
Troubleshooting
Object: Regional settings must be in the same language as the OS and
Excel application
Knowledge base article number: 14977
Problem encountered
Regional settings must be in the same language as the OS and Excel
application
Resolution
In order to function correctly, RDL publishing requires regional settings to be
in the same language as the Windows OS and MS Excel application. This
means that if you have US Windows and Excel, you need to ensure that the
language specified in the "Your locale (location)" field is also "English (United
States)". You can access this field by selecting Control Panel > Regional
Settings > General tab in the Windows Start menu.
Object: Modification of suffix/prefix used by tables leads to their deletion
6
Knowledge base article number: 15398
Problem encountered
Open Designer and deploy the star schema. Go to the Star schema options
tab. Select the T able suffix or Table prefix field. When you make changes to
the suffix or prefix used for the tables which were created during the previous
deployment, the tables are deleted.
Resolution
This problem was referenced by the R&D team as bug report no. 1205.
If you encounter this issue, please register so that you will be notified of the
update made to this article when the problem is corrected in a future version.
Object: Filtering and searching for element names
Knowledge base article number: 14980
Problem encountered
Can I use wildcards such as * and ? in the "searching for member values"
function when selecting elements?
Administration guide 61
Troubleshooting
6
Resolution
Yes, you can. The filtering uses .NET regular expresssions for searching with
wildcards. Here follows a very brief overview:
1. Literals like abc will match any element name containing at least one
occurrence of 'abc'. This is case sensitive.
2. * means zero or more, + means one or more. So a+bc will match any
string containing a followed by one or more b followed by a c.
3. You can group literals using [] so [ae] will match any string containing a
single a or e. Hence gr[ae]y will match 'gray' or 'grey' (but not 'greay').
4. You can use a hyphen to indicate ranges. E.g. [0-9] will match any
number. [0-9]* will match a sequence of zero or more numbers. [A-Za-z]
will match any single upper or lower case letter.
5. Y ou can connect multiples of these together to form more complex filte rs.
E.g [A-Za-z]+[0-9]+ will match any element name that starts with 1 or
more letters and followed by 1 or more numbers.
6. A caret will negate a match set so a[^b] matches an a followed by a
character other than b. [^0-9] therefore matches any non-numeric
character.
7. You can do case insensitive matches using /i -- so /iABC will match
'AccountABC', 'AccountAbC' , 'Accountabc', "CompanyABC", "abcDEF",
etc.
8. ^ means the start of the element name and $ the end of the name. E.g.
^A matches names starting with A, [0-9]$ matches names ending in a
number.
9. As well as * and +, you can search for repetition occurring between n and
m times using {n,m}. E.g. A[0-9]{1,3} will match elements containing an A
followed by between 1 and 3 numbers.
10. The vertical bar | means or. So to match any element containing ABC,
XYZ or 123 use ABC|XYZ|123.
11. A (?) is used to match any single character. For example, to search for
period 2000.12, you should type 2000?12.
Here are some examples:
ABC simply matches elements which contain ABC.
^ABC matches elements starting with ABC.
^ABC[0-9]* - Matches element names in ABCxxx format where xxx is a
sequence of numbers.
[A-Za-z_][A-Za-z0-9_]* - Matches element names that start with a letter or
underscore followed by zero or more letters, numbers or underscores.
62 Administration guide
Object: Unable to see analyzed amounts in cube
Knowledge base article number: 14845
Problem encountered
I selected and successfully deployed the "Activity" dimension (client
dimension) in my cube.
However, I do not see any analyzed amounts in my report in Analyzer. What
should I do?
Resolution
In order to view analyzed amounts, you cannot specify the client dimension
alone in the cube. You should include 2 items.
1. In Designer, you need to select the required dimension in "Dimensional
Analysis". This tab is available when you click on the View.
2. In Analyzer, you need to select the correct "measure".
When you deploy a cube with "Dimensional Analysis" selected, the cube will
have multiple measures. The "Amount type" measure represents the nonanalyzed amounts. The other measure, called "Amount type- "<Dim>", will
display the analyzed amounts.
Troubleshooting
6
Object: Time required to open an existing solution is long due to messages
Knowledge base article number: 14859
Problem encountered
When I open an existing solution, it takes a very long time because all
messages (sometimes more than 5000) are displayed.
Resolution
There are 2 ways to prevent this problem from occurring:
• You can delete the messages by clicking on the "clear list" button in the
Information Display.
• You can choose not to display messages by selecting View (ALT-V) and
unchecking the "Information Display" option.
Object: Cache settings
Knowledge base article number: 15158
Administration guide 63
Troubleshooting
6
Problem encountered
I do not understand how the settings in "Cache settings" work. These can be
found in the Refresh tab for each dimension or in the Option tab for cube
deployment.
What are each of the intervals for?
Resolution
• The Query Poll Interval setting specifies the time interval between
checks performed by MSAS to ensure that tables in the Finance
database are updated.
• The Silence interval and Silence override interval settings are both
related to the updating of the cube.
• Silence interval: the cube is synchronized if the Finance server
detects inactivity for an x amount of time.
• Silence override interval: the cube is synchronized at every x
interval regardless of whether or not the Finance server detects
activity.
For example, if Silence interval = 10 minutes and Silence override
interval = 20 minutes:
The system will wait for a pause in activity of 10 minutes before
synchronizing data. Even though there may be no pause in activity, the
system will synchronize data after an interval of 20 minutes.
• The Rebuild Interval setting is calculated using the first processing date
of the cube. A rebuild corresponds to a redeployment.
The refresh options work in the same way as for dimensions but only if these
are based on a characteristic.
Object: Filtering access using UDF For Security
Knowledge base article number: 15903
Problem encountered
The UDF component filters connections when authenticating but does not
apply the security filters. Users therefore have access to all data. Is this
normal?
64 Administration guide
Troubleshooting
Resolution
BusinessObjects Extended Analytics does not apply the same security
configured in Finance. Users can view data in BusinessObjects Extended
Analytics depending on their analysis restriction for the default category
together with the rest of the categories available.
For example, if you have no analysis restriction for the default category, then
no restriction will be applied to the other categories and all of the data can be
viewed.
To apply security, you should configure a restriction for the default category
and authorize the categories that are required.
Furthermore, the Windows account of the BusinessObjects Extended
Analytics user should not be declared administrator on the SSAS machine. If
this is the case, then the UDF For Security component will not function and no
security can be managed between BusinessObjects Finance and
BusinessObjects Extended Analytics.
Object: Active: Error message when publishing Excel sheets containing
charts
Knowledge base article number: 14981
6
Problem encountered
When publishing an Excel sheet that contains a chart, the following error
message appears: "Error HRESULT E_FAIL has been returned from a call to
a COM component".
Resolution
This is a known product defect.
This problem occurs when the list separator is NOT a semicolon. By default,
the Windows US and UK versions have a comma as list separator.
To change the list separator:
1. In the Windows Control Panel, open the Regional and Language
Options.
2. Click on the Customize button and set the list separator to ';' instead of
','.
Object: Unable to create a new solution
Knowledge base article number: 15744
Administration guide 65
Troubleshooting
6
Problem encountered
When you try to create a new solution, the following error message appears:
"unknown error when opening existing solution".
The problem occurs when an Oracle database is used as the Finance
relational database, and the Oracle client has not been customized properly
on the Designer client.
Resolution
To correct this, you should:
• Create an Oracle alias on the client that communicates with the Oracle
database (or add the appropriate settings to the tnsnames.ora file).
• Add a total access control for the Windows Everyone user in the "ora92"
directory.
Object: Brackets []
Knowledge base article number: 14843
Problem encountered
Sometimes, some members appear as [ ] in Analyser and no description is
displayed.
Why is this so?
Resolution
This happens when some of the elements do not exist in the hierarchy you
want to display.
For example, you choose to display RUs with a hierarchy on division
(characteristic of RU). If the value of the characteristic division is not entered
for some of the RUs, the [ ] symbol will appear instead of the value.
Object: Ambiguous names
Knowledge base article number: 14850
Problem encountered
Why does the "Analyzer - Resolve Ambiguous Member Names" box appear?
Resolution
"Ambiguous names" are found when two members of a hierarchy that do not
belong to the same parent have the same description.
66 Administration guide
Troubleshooting
As Analyzer does not know which one you want to display, the box appears.
For each cell with an ambiguous name (on the left), you should select the
corresponding unique name (on the right).
Please see article 14849 on deployment names in the customer knowledge
base.
Object: Active: Unable to deploy a cube containing an analysis dimension
whose name is too long
Knowledge base article number: 15724
Problem encountered
You cannot deploy the cube and the following error message appears: "The
maximum number of characters is 100".
Resolution
You cannot deploy a cube because the names of analysis dimensions
selected for the cube cannot exceed the maximum number of characters.
This problem was referenced by the R&D team as bug report no. 1074.
If you encounter this issue, please register so that you will be notified of the
update made to this article when the problem is corrected in a future version.
6
Object: Are periods automatically updated in the cube?
Knowledge base article number: 14918
Problem encountered
How will the Period dimension be updated in the cube?
Resolution
By default, Designer allows the selection of periods from 1990 to 2010. Note:
these default values can be modified in a configuration file
(Cartesis.InformationDelivery.Workbench_V9.exe.config or
Cartesis.InformationDelivery.Workbench.exe.config) stored in the Designer
installation folder. The settings to be customized are "MinDisplayDate" and
"MaxDisplayDate".
You can select the periods you want to see in the cube. Once created in the
cube, the periods will be automatically updated from Finance if proactive
caching is enabled.
Administration guide 67
Troubleshooting
6
If you have changed the values of periods and you (re)open an existing
solution, an error message will appear. You should ignore this error message
as the system will work correctly.
Object: "Display selected members" option selected is not kept
Knowledge base article number: 14975
Problem encountered
"Display selected members" option selected is not kept.
Resolution
After saving a solution or opening another window, the "Display selected
members" option is not kept even though it was selected. The option appears
unselected.
Object: Publication error with hidden columns
Knowledge base article number: 14976
Problem encountered
A publication error will occur when you publish an Excel sheet with at least 2
hidden columns, each of them containing a dimension.
Resolution
If at least two columns (each of them containing one dimension) in "page/
document header" are hidden in an Excel file, an error will occur when
publishing: "An entry with the same key already exists".
For hidden rows, this issue does not occur.
Object: Amounts not displayed in hierarchy nodes for Account dimension
Knowledge base article number: 14858
Problem encountered
I selected a (self-referencing) characteristic for Account for the hierarchy . The
aggregation is enabled, but in Analyzer I do not see amounts.
Is this a bug?
68 Administration guide
Resolution
No. In the Account dimension, if you select a hierarchy based on a selfreferencing characteristic (where the nodes of the hierarchy themselves are
accounts), there is no aggregation.
This is because if you store amounts from these accounts directly in Finance,
this would cause a conflict. Regarding accounts, the rule is that the amounts
are always taken from the database directly and are not aggregated.
For more information on generic aggregation rules for dimensions, please see
KB article 14857.
Object: Error when publishing
Knowledge base article number: 14847
Problem encountered
I created a report in Analyzer, but when I try to publish it, the following error
message appears:
"Unable to get the Orientation property of the PageSetup class".
What is the problem?
Resolution
This message appears because you have no printer setup.
You can check this by selecting the page setup in Excel. The following
message appears: "Current printer is unavailable...".
You should then configure a printer and publish the report again.
Troubleshooting
6
Object: Access right not applied when publishing report
Knowledge base article number: 16059
Problem encountered
Wen I open a report in Excel format using Reporter, the report is empty. I
need to perform a Read data before the data appears. Is this normal?
Resolution
Excel reports are empty when opened because access restrictions are
applied only when you connect to the cube. Existing data is not filtered.
Users who are authorized to consult reports should do so in RDL format. This
enables them to set variables and run reports directly in Reporter.
Administration guide 69
Troubleshooting
6
If the page setup configured for reports is not applied when publishing in RDL
(see Answer Link article), you should change the page setup so that it is
compatible with RDL format.
Object: ORA-955: Error message when deploying solution
Knowledge base article number: 15738
Problem encountered
During the deployment of a solution, an error message appears when I insert
data in one of the tables e.g. RGSFH_Default_CODATA :"é
ORA-955: name is already used by an existing object.
This is because an attempt was made to create a database object (such as a
table, view , cluster , index, or synonym) that already existed. Database objects
must have unique names.
Resolution
You can enter a unique name for the database object, modify or drop the
existing object so that it can be reused.
Object: Unable to start Analyzer on the Reporter site
Knowledge base article number: 16130
Problem encountered
When I start Analyzer using Reporter, the following error message appears:
"BusinessObjects Extended Analytics Analyzer could not be enabled.
The Analyzer Excel additional module could not be initialized.
Check that the Analyzer Excel additional module is installed and correctly
registered on the machine".
Resolution
This problem occurs because in version 3.5 SP1, you must configure a data
source in Reporter.
To do so, you should:
- go to "Site settings".
- click on "Data sources".
70 Administration guide
- configure a data source (see the installation document for information on
specifying fields).
Once this is done, Analyzer will open correctly in Reporter.
Object: Users with access restrictions can access all data
Knowledge base article number: 15156
Problem encountered
ES ID does not apply the same security configured in Finance. Users can
view data in ID depending on their analysis restriction for the default category
together with the rest of the categories available.
For example, if you have no analysis restriction for the default category, then
no restriction will be applied to the other categories and all of the data can be
viewed.
Resolution
To apply security, you should configure a restriction for the default category
and authorize the categories that are required.
Troubleshooting
6
Object: Error message when installing SQL Server 2005 SP2
Knowledge base article number: 16291
Problem encountered
When I install hotfix KB927109 or SQL 2005 SP2, the installation fails with
error MSP 1685.
Resolution
The installation requires files from version SQL RTM.
Run the installation using the original CD.
Object: SQL Server error message when installing Deployer
Knowledge base article number: 16292
Problem encountered
If you are running the Deployer for Finance setup on the same machine as
the SSAS server and if you have installed SSAS in a folder other than the
default folder, the following error message may appear:
Administration guide 71
Troubleshooting
6
The installation of SQLServerManagementObjects2005 appears to have
failed. Do you want to continue the installation?
Resolution
1. Click on Yes.
You can continue the setup, this will not affect the installation process.
Object: Analyzer: Data is not filtered according to security configuration
Knowledge base article number: 16004 –16293
Problem encountered
In Analyzer, data is not filtered according to the security configured.
Resolution
The user name entered here MUST be a user known and authenticated by
the SSAS Server (in the same domain or a known domain). This user must
NOT have local administration rights on the SSAS Server, SSAS instance or
SSAS database. Otherwise, the UDF For Security component will not
function.
Object: Datapump not working
Knowledge base article number: 16294
Problem encountered
The datapump is not working anymore.
Resolution
Check that the password is not expired.
During the datapump installation, you entered a login. This login MUST have
a password that never expires. For security reasons, SSAS does not allow
blank passwords.
Object: Reporter: RDL reports do not open correctly
Knowledge base article number: 16295
Problem encountered
RDL reports do not open correctly when they are being run.
72 Administration guide
Resolution
Check that the password is not expired.
During the Reporter installation, you entered a login. This login MUST have a
password that never expires. For security reasons, SSAS does not allow
blank passwords.
Object: Reporter: Security not applied correctly in RDL reports
Knowledge base article number: 16296
Problem encountered
Security in RDL reports is not applied correctly when they are being run.
Resolution
During the Reporter installation, you entered a Windows login and a domain
name known to the SSAS Server (DomainName\Login) in the Windows
account used for Reporter Execution field.
This is not a BusinessObjects Finance login. The login entered here MUST be
a login known and authenticated by the SSAS Server (in the same domain or
a known domain). This login must NOT have local administration rights on the
SSAS Server, SSAS instance or SSAS database. Otherwise, the UDF For
Security component will not function.
Troubleshooting
6
Administration guide 73
Troubleshooting
6
74 Administration guide
Loading...