User manual TANDBERG ANALYTICS EXTENSION ADMINISTRATOR GUIDE

[. . . ] TANDBERG Analytics Extension Administrator guide D14668. 01 September 2010 Introduction Contents Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Document Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 New feature overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] A workaround to the problem is appending the connection string manually: 1. In Excel, go to Data > Existing Connection. Select the relevant connection, and click Open. In the Import Data window that follows, click Properties. . . Go to the "Definition" tab (Figure 6). Append the text string in the "connection string" field with ";password=<your password>". Note the semicolon in front. TANDBERG Analytics Extension Admin guide 16 Troubleshooting Example: If the user account is named "peter. jones", the connection string might look like this: Provider=MSOLAP. 3;Persist Security Info=True;User ID=REPORTING\peter. jones;Initial Catalog=tmsng_dwhAsDb;Data Source=analytics. reporting. tms. lab;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error If the password of the account is "ENGLAND66", the modified string should look like this: Provider=MSOLAP. 3;Persist Security Info=True;User ID=REPORTING\peter. jones;Initial Catalog=tmsng_dwhAsDb;Data Source=analytics. reporting. tms. lab;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error;password=ENGLAND66 Checking the "Save password" box will make the changes to the connection string persistent. However, note that the connection string is stored unencrypted in an XML file on the local disk. Figure 6: Manually appending the connection string The LocaleIdentifier property XML for Analysis parser: The LocaleIdentifier property is not overwritable and cannot be assigned a new value After creating a connection, the error message XML for Analysis parser: The LocaleIdentifier property is not overwritable and cannot be assigned a new value may appear when you try to utilize the connection in a pivot table or chart. This issue only TANDBERG Analytics Extension Admin guide 17 Troubleshooting applies to certain combinations of old versions of Excel and SSAS. The following Microsoft Connect page describes a workaround Error when creating an Excel Pivot Table from a SSAS project. Right click the connection in the Select Data Source window and select Open with > Notepad (Figure 7) to edit the connection file as described in the Microsoft Connect page, . Locate the <odc:ConnectionString> element, and append ";Locale Identifier=1033" (note the semicolon) to the end of the elements content (Figure 8). The connection is now updated and ready for use. Figure 7: Opening the connection for editing TANDBERG Analytics Extension Admin guide 18 Troubleshooting Figure 8: Appending the connection string TANDBERG Analytics Extension Admin guide 19 Logs Logs If you experience difficulties with the TANDBERG Analytics Extension, technical support may ask you to supply log files along with a description of your issue. The follow sections outline the types of logs available. For information on installer logs see TANDBERG Analytics Extension Installation Guide Application Logs Problems with the Analytics Extension web interface or the Windows Service that initiates the update jobs are logged in files located on the web server where the Analytics Extension was installed. Logged events from the Analytics Extension web interface and the Analytics Extension Service are stored in the following locations: <Installation Dir>\TANDBERG\Analytics Extension\ReportingService\Logs <Installation Dir>\TANDBERG\Analytics Extension \AdminWeb\App_Data\Logs These files are plain text but are low level and intended for debugging purposes by TANDBERG personal. Database Logs The data warehouse itself also keeps logs useful for troubleshooting; these entries are stored in the database itself in the tables orc. ExecutionEventLog. dwh. AppliedPatch, and dwh. InstallerEventLog. These logs may be browsed using any SQL tool. To save all the entries in these logs to a file: 1. Open Management Studio and connect to the database engine instance 2. Expand Databases, find your data warehouse database (tmsng_dwh by default) 3. Right-click on the database and select "New Query". [. . . ] The provisions of any order document used by Licensee shall be of no effect (notwithstanding any provisions in such order document to the contrary), except for the number of users, pricing and ship-to information. Any terms in Licensees order document which are inconsistent with the terms of this License are not accepted by TANDBERG and the terms of this License will prevail. This License is governed by, and is to be interpreted in accordance with the laws of the State of New York, excluding its conflict of law rules to the contrary. The United Nations Convention on Contracts for the International Sale of Goods is expressly disclaimed. [. . . ]