BOARD LOGs in detail

Document created by mik1893 Employee on Aug 14, 2017Last modified by lscaburri on Jun 27, 2018
Version 16Show Document
  • View in full screen mode

 

1. User Logs

The file format used is tab-separated CSV.

This information should be used to track user / profiles modification and check if there were failed / unauthorized login attempts which require further investigation.

 

1.1 Login / Logout information

Filename: Login.log       

Updated every: User Login/Logout attempt from any Board client ( Windows, Mobile, Excel addin, Web)

Log Rotation: none

Header: No

 

Scope: It tracks all the login and logout of the users, it also include the address of the client machine from which the user connected. It tracks errors such as wrong password or user already logged from elsewhere

Accessibility: The log is active by default on the Board Server machine. The log file is located in the following path: ‘’Board_Path\Dataset\Log\Users\login.log’’.

Usability: The log is unique per each Board environment. The login.log file size could potentially increase.

Highlights: It contains a numeric column always set to 1 to facilitate counters.

 

File structure (example):

Action

 

 

Host

Username

Datetime

Dummy

WrongPassword

 

BPCCH05

User_1

2014-09-09 17:27:03

1

Login Succeeded

 

BPCCH05

User_1

2014-09-09 17:27:29

1

OfficeLicenseNotFound

..Logout Succeeded

 

BPCCH05

localhost

Administrator

Administrator

2014-09-09 17:28:25

2014-09-09 17:31:20

1

1

 

Fields Description:

Action: the attempted action from the user.
Host: the hostname on which the user is logged
Username: user performing the action
Datetime: time of the action
Dummy: always 1, need to quickly load data into Board Log Analysis database and retrieve count of actions

 

1.2 Provisioning logs

Scope: These logs track the provisioning of the users. It tracks users and profiles creation, deletion and modification

Accessibility: The log is active by default on the Board Server machine. The log file is located in the following path: ‘’Board_Path\Dataset\Log\Users\’’. The generated logs are: ProfilesCreated.log, ProfilesModified.log, ProfilesRemoved.log, UsersCreated.log, UsersModified.log, UsersRemoved.log

Usability: The log is unique per each Board environment. The logs file size could potentially increase.

Highlights: It contains the modified profile and the username of the admin that did this, Modification in tilde databases are not tracked here but on the tilde log itself.

 

1.2.1 Users maintenance logs

Filenames: UsersCreated.log , UsersModified.log, UsersRemoved.log

Updated every: User Creation / Modification / Removal from the security tab

Log Rotation: none

Header: No                                                 

 

File structure (example): 

Datetime

 

 

User

Administrator User

Dummy

2014-09-09 17:28:25

 

User1

Administrator

1

2014-09-09 17:29:25

 

User2

Administrator

1

2014-09-09 17:30:25

 

User3

Administrator

1


Fields Description
:

Datetime: time of the action
User: the user subject to creation/modification/removal
Administrator User: the admin user which is doing the modification
Dummy: always 1, need to quickly load data into Board Log Analysis database and retrieve count of actions

 

1.2.2 Security Profiles maintenance logs

Filenames: ProfilesCreated.log , ProfilesModified.log, ProfilesRemoved.log

Updated every: Profile Creation / Modification / Removal from the security tab

Log Rotation: none

Header: No

 

File structure (example):

Datetime

 

 

Profile

Administrator User

Dummy

2014-09-09 17:28:25

 

Profile1

Administrator

1

2014-09-09 17:29:25

 

Profile2

Administrator

1

2014-09-09 17:30:25

 

Profile2

Administrator

1

 

Fields Description:

Datetime: time of the action
Profile : the profile subject to creation/modification/removal
Administrator User: the admin user which is doing the modification
Dummy: always 1, need to quickly load data into Board Log Analysis database and retrieve count of actions

 

 

2. Server Logs

 

2.1 Configuration Options

Server logs should be configured through the “Configure Server Logging” options under the System tab, accessing with a Board administrator user.

The list of configuration options modifies the output of the Database logs and Capsule logs.

 

2.1.1 Database Log Events

This option enables the output of the “HBMP_*databasename*_YYYYMM.log” log files.

For every database present in your Board installation, an log file is generated. Every month a new file is generated.

The database standard log contains every action executed on the Database side, or from a Database procedure, except dataflow actions unless the Dataflow Log Events option is enabled (see below).

 

2.1.2 Capsule Log Events

This option enables the output of the “Cpsx_YYYYMM.log” log files.

Scope: When enabled, the execution of every layout in any capsule screen will be logged.

Accessibility: The log has to be activated from the ‘System’ tab of the Board client under the ‘Configure Server Logging’ button. The statistics of all the layout executions are written in the log file: «Cpsx_YYYYMM.log» Also dataentry execution are tracked

Usability: The log is unique per each environment and splitted into monthly files. If there are many applications a clean action for those files is highly suggested.

Highlights: Version of the cubes used in a layout;
                    Multiple rows in each layout (one for each retrieved cube). The value of the dataentry is not tracked in this log, but in the dataentry log

 

The capsule log is unique and contains information on the usage of all the capsule in your Board installation. Every month a new file is generated.

The capsule standard log contains every action executed on a capsule, or capsule procedure, except dataflow actions unless the Dataflow Log Events option is enabled, and layout execution statistics unless the Layout Log Events option is enabled (see below).

 

2.1.3 Layout Capsule Log Events

When enabled, the execution of every layout in any capsule screen will be logged, with statistics on the query time of every block inside the layout. This information is very useful to debug slow screens and to understand system performance. Anyway, it is recommended not to enable this option in production environments with large number of users, as it may result in performance lacks.

 

2.1.4 Procedure Log Events

When enabled, allows logging of the name of the executed capsule procedure, in the capsule log. This information is very useful to track the execution of a capsule procedure from an user. Please note that this option doesn’t apply to database procedures

 

Scope: When enabled, it allows the logging of the server actions invoked during capsule procedures executions (dataflows, clear cube and select based on)

Accessibility: The log has to be activated from the ‘System’ tab of the Board client under the ‘Configure Server Logging’ button. The statistics are written in the log file: «Cpsx_YYYYMM.log»

Usability: The log is unique per each environment and splitted into monthly files.

Highlights: Statistics on the dataflow executions invoked on a capsule procedure
                    Which cube is used for a select based on calculation. This log contains the procedure name that invoked the step. It also contain a step number

 

2.1.5 Dataflow Log Events

When enabled, allows logging of the dataflows executions, with statistics on the execution time and the dataflow mode used.

 

2.2 Capsule Log

Filenames: Cpsx_YYYYMM.log

Updated every: User action on a Capsule screen

Log Rotation: every month – year and month appended in the file name

Header: Yes                                                      

 

Scope: The capsule log is unique and contains information on the usage of all the capsule in your Board installation

Accessibility: The log has to be activated from the ‘System’ tab of the Board client under the ‘Configure Server Logging’ button. The log file is located in the following path: ‘’Board_Path\Dataset\Log’’. The filename is «Cpsx_YYYYMM.log»

Usability: The log is unique per each environment and splitted into monthly files. If there are many applications a clean action for those files is highly suggested.

Highlights: Version of the cubes used in a layout
                  Multiple rows in each layout

 

File structure (example): 

NRUserNameDbNameDateTimeOperation

Capsule

Path

Screen

Title

[L]=Layout/

[P]=Procedure

Cube

Name

Cube

Version

[L]=Logical/

[P]=Physical View

[N]=Normal / [E]=DataEntry / [S]=SubmittedElapsedTime (FirstBlockOnly)

1=LayoutFirstBlock / 0=MoreLayout

Blocks

18AdministratorEcho20170920194307Multiple Layoutslogs.cpsxScreen 1[L]-UntitledGross Salesv001[L][N]00h00m00s1
18AdministratorEcho20170920194307Multiple Layoutslogs.cpsxScreen 1[L]-UntitledSales Packsv001[L][N]00h00m00s0
19AdministratorEcho20170920194307Multiple Layoutslogs.cpsxScreen 1[L]-Average PriceAverage Pricev002[L][N]00h00m00s1
19AdministratorEcho20170920194307Multiple Layoutslogs.cpsxScreen 2[L]-Average PriceBudget Salesv001[L][N]00h00m00s1
19AdministratorEcho20170920194307Multiple Layoutslogs.cpsxScreen 2[L]-Average PriceGross Salesv003[L][N]00h00m00s1

 

Fields Description:

NR: Action ID (auto-incremental)
UserName: User execution the action
DBName: Database on which action is executed
Date: Date (format YYYYMMDD)

Time: Time ( format hhmmss)

Operation: Action executed on the server

CapsulePath: Capsule in use by the user

ScreenTitle: Title of the screen in use

[L]=Layout/[P]=Procedure: Layout or procedure (with name)

CubeName: Cube subject to the action

CubeVersion: Version of the subject cube

[L]=Logical/[P]=Physical View: If action is executed at cell level or on an aggregated level

[N]=Normal / [E]=DataEntry / [S]=Submitted: Normal means the block is displayed in read mode. DataEntry is when the block is open for data entry. Submitted means the server has executed a data entry submission, the blocks entered are logged after the refresh as submitted.

ElapsedTime (FirstBlockOnly): On the first block of the layout, shows the execution time for that layout.

1=LayoutFirstBlock / 0=MoreLayoutBlocks: 1 when it’s the first layout block, 0 for the others.

 

2.3 Database Log

Filenames: HBMP_*DataBaseName*_YYYYMM.log

Updated every: User action on a Database

Log Rotation: every month – year and month appended in the file name

Header: Yes      

Scope: The database standard log contains every action executed on the Database side, or from a Database procedure
Accessibility: The log can be deactivated from the ‘System’ tab of the Board client under the ‘Configure Server Logging’ button. The log file is located in the following path: ‘’Board_Path\Dataset\Log’’. The filename is «HBMP_*databasename*_YYYYMM.log»

Usability: The log is unique per each database and splitted into monthly files.

Highlights: Datareader executions and record counting, dataflow and datareader execution times, it does not contain procedure steps

 

Fields Description ( and example):

Action CodeDateTimeUserNameDbNameOperation-TitleD.Flow ModeTargetElapsedFileRecordNrValidatedRejectedRAM StatusErrCode
CD2017050215:21userEchoCube DefinedTARGET00h00m00s    
CD2017050215:21userEchoCube DefinedMIDDLE00h00m00s    
DF2017050215:26userEchoDataFlowHBMP+MIDDLE  [Ver:001]00h00m01s[1054/2168]Mb    
DF2017050215:26userEchoDataFlowHBMP+TARGET  [Ver:001]00h00m00s[1054/2168]Mb    
CD2017050315:23userEchoCube DefinedTARGET_200h00m00s    
CD2017050323:05userEchoCube DefinedSPARSE00h00m00s    
CD2017050323:05userEchoCube DefinedDENSE00h00m00s    
DF2017050323:06userEchoDataFlowLargeMatrix+DENSE  [Ver:001]00h00m02s[1043/2100]Mb    
DF2017050323:06userEchoDataFlowHBMP+DENSE  [Ver:001]00h00m00s[1046/2096]Mb    
DF2017050323:07userEchoDataFlowCellBased+SPARSE  [Ver:001]00h00m10s[1030/2117]Mb    
DF2017050323:07userEchoDataFlowHBMP+SPARSE  [Ver:001]00h00m00s[1031/2109]Mb    
FR2017050519:51userEchobubble00h00m00sbubbleChart.csv1241240[1118/1136]Mb
EM2017053118:34userEchoEntity ModifiedCity00h00m00s

 

Fields Description:

Action Code: Code of the action execute

Date: Date (format YYYYMMDD)

Time: Time ( format hh:mm)

UserName: Database on which action is executed

DbName: Database on which action is executed

Operation-Title: Action executed on the server. In case of FR (FileRead) action code, this is the title of the datareader protocol.

D.Flow Mode: Dataflow mode ( in case of dataflow operation)

Target: Target cube of the dataflow

Elapsed: Elapsed time for the action

File: File read in case of FR (FileRead) action. For SQL datareader is the code of the resultset obtained.

RecordNr: Number of records read (FileRead action)

Validated: Number of valid records loaded

Rejected: Number of records discarded

RAM Status: Ram usage at the end of the operation

ErrCode: Error code when operation is failed


3. Other LOGs

 

3.1 In-Memory Log

Filenames: HBMP_*DataBaseName*_InMemory.log

Updated every: Database loaded in-memory                                                   

Log Rotation: None

Header: Yes    

This log contains the information on the loading into RAM of a HBMP database.

It is a fixed-width log, which is outputted in a readable format to allow quick reading and use of the information contained in it. It displays the usage of RAM of the cubes, ram to disk ration, and loading time of the database.

 

Scope: Logs the size in memory of each cube, entity or sparsity of each db, it is generated at every in memory load of the db
Accessibility: The log is active by default on the Board Server machine. The log file is located in the following path: ‘’Board_Path\Dataset\Log\’HBMP_Inmemory.log’.

Usability: The log is unique per each Board Database. It contains information of the last db load in memory, if you want to keep track of the db loads in time you need to copy this log

Highlights: It contains also the time each object needed to load in memory, this time is more accurate if the «multicore on loading cube» option is not enabled

 

File structure (example):                        

Log

Echo---------------------------------Process-----Available-------Virtual---ElapsedTime---------Files-------RAM/DSK--------sec/Gb--------sec/Gb
[Gb]                                              RAM            RAM           MEM                 [sec]           DSK                Ratio              RAM             DSK

Starting Values {20/09/2017}          0,1                4,1       131072,0          {19:50}

----------------------------------------------------------------------------------------------------------------------------------------------

BeDD_Load                                     0,0                0,0             0,0                   0,1
Entities                                             0,0                0,0             0,0                   0,2
Relationships                                   0,0                0,0             0,0                   0,0
Sparsity                                            0,0                0,0             0,0                   0,0
Cube: Gross Sales                           0,0                0,0             0,0                   0,1          0,0                      2,8                95,5          267,4
Cube: Sales Packs                           0,0                0,0             0,0                   0,0          0,0                      0,1                0,0            0,0
Cube: Cost of Goods Sold               0,0                0,0             0,0                   0,0           0,0                      2,6                17,1          44,8

 

                  

3.2 Database Changes Detail Log

Filenames: DBChangesDetail.log                                                                            

Location: In every BoardPath\Database\*DatabaseName*.hbmp\Common folder

Updated every: Modification to the database structure.                                  

Log Rotation: None

Header: Yes    

This log contains the list of modifications executed on a database. The type of modification, datetime and the user which performs the modification are logged.
This log is very useful to understand eventual not-comparable errors when using the “Transporter” tool to migrate database structure from development to production.

Scope: It logs the changes made to a db (adding/removing/editing a cube a relation, an entity, a datareader or defining the time range.
Accessibility: The log is in the databasename.hbmp\common folder and it’s named dbchanges.log

Usability: The log can be used to determine which changes have been done on a database

 

File structure (example): 

Date

Time

User

Original Value 

20170623

15:16:54

Cubes

Administrator

20170623 

15:18:35

Enitites

Administrator

20170624 

12:50:00

DataReader

Administrator

20170624 

13:08:57

Expressions

Administrator

 

3.3 Dataentry Log

Filenames: Dataentry.log                                                                            

Location: In every Board_Path\Dataset\Log\ folder

Updated every: Modification to the cube cell element or value.                                  

Log Rotation: None

Header: Yes    

 

Scope: It logs the value of a dataentry, the value that the dataentry had before the edit, the layout on which the dataentry has been done and the coordinates (row, column) on which it has been performed

This log should be activated on demand, as it can be high resource-consuming.

How to activate the Dataentry Log :

  • Open the folder \\...Program Files\Board\Board Server
  • Edit the file Adulaparams.xml
  • Edit the following parameter/setting to "true"

  <DataEntryLogEvents>true</DataEntryLogEvents>

Accessibility: The dataentry.log file is located in the following path: ‘’Board_Path\Dataset\Log\dataEntry.log’’.
Usability: The log is unique per each Board environment. The Dataentry.log file size could potentially increase.

Highlights: It does not keep track of the selections and pagers

 

Current Limitation: it does not keep track of the active selections and pagers

File structure (example): 

Date

Time

User

Original Value 

New Value 

Cube

Coordinates

2017-09-20

17:28:25

Administrator

680579199, 226807

 700000000

Gross Sales (V001 - Gross Sales)

2011, France

2014-09-09 

17:29:25

Administrator

3143175, 60001147

 2800000

Sales Packs (V002 - Sales Packs)

2011, Italy

 

3.4 Entity Item Visualization Log

Filenames: DbTrace_yyyymmdd.log                                                                       

Location: In every BoardPath\Database\*DatabaseName*.hbmp\Common folder

Updated every: Visualization of a specific entity by an user, in a Capsule screen / drill / drill through.    

Log Rotation: Daily ( year, month, day in the filename)

Header: Yes    

The log reports the username, the timestamp and the list (tab separator) of the entity items plus the info-cube of layout and/or screen under investigation. This log should be activated on demand, as it can be high resource-consuming.

How to activate the Log Tracker :

  • Open the folder \\...Board\Database\db_name\Common
  • Create the file DbOptions.txt
  • Edit the file as following : Trace: entity_name
Since the Log file is in the Database Folder it is suggested to remove it regularly to avoid any impact on the Database Back-Up process (its size can become significant).

The Log is triggered under the following conditions:

  • The Entity “under” tracking must be in the Layout Axes (by row or column) or it must be in a Pager
  • All the active selected items are reported independently from Layout Filters or Hide Zero options
  • The Selector Object does not trigger the Tracker
  • If you need to track multiple Entities the DbOptions.txt file must edited like
    • Trace: entity_name_1
    • Trace: entity_name_2
    • Trace: entity_name_n   

 

3.5 SQL Error Log

Scope: It logs all the exceptions and error that odbc and ole-db drivers are throwing when using SQL datareader, Rolap cubes, Fast track, drill trough.

Accessibility: The log is active by default on the Board Server machine. The log file is located in the following path: ‘’Board_Path\Dataset\Log\SQLerror.log’’.

Usability: The log is unique per each Board environment. The SQLerror.log file size could potentially increase.

Highlights: You migh use this when a board connection is not workig throwing a generic «Database empty or unavailable», you will get the specific exception in this log.

 

File structure (example): 

Log

SELECT BOARD_TEST.ECHO_NEW_V001.PRODUCT, BOARD_TEST.ECHO_NEW_V001.NEW FROM BOARD_TEST.ECHO_NEW_V001
SELECT BOARD_TEST.ECHO_NEW_V001.PRODUCT, BOARD_TEST.ECHO_NEW_V001.NEW FROM BOARD_TEST.ECHO_NEW_V001
SELECT BOARD_TEST.ECHO_NEW_V001.PRODUCT, BOARD_TEST.ECHO_NEW_V001.NEW FROM BOARD_TEST.ECHO_NEW_V001
SELECT BOARD_TEST.ECHO_NEW_V001.PRODUCT, BOARD_TEST.ECHO_NEW_V001.NEW FROM BOARD_TEST.ECHO_NEW_V001
SELECT BOARD_TEST.ECHO_NEW_V001.PRODUCT, BOARD_TEST.ECHO_NEW_V001.NEW FROM BOARD_TEST.ECHO_NEW_V001
SELECT BOARD_TEST.ECHO_NEW_V001.PRODUCT, BOARD_TEST.ECHO_NEW_V001.NEW FROM BOARD_TEST.ECHO_NEW_V001
SELECT * FROM Order_Details
SELECT * FROM Orders
select Orders.[Order Date], Order_Details.ProductID, Orders.CustomerID, Orders.ShipVia, Order_Details.Quantity
FROM Orders, Order_Details
WHERE Order_Details.OrderID = Orders.OrderID

SELECT Orders.[Order Date], Order_Details.ProductID, Orders.CustomerID, Orders.ShipVia, Order_Details.Quantity FROM Orders, Order_Details WHERE Order_Details.OrderID = Orders.OrderID
SELECT * FROM Orders
SELECT * FROM Order_Details
select Orders.[Order Date], Order_Details.ProductID, Orders.CustomerID, Orders.ShipVia, Order_Details.Quantity
FROM Orders, Order_Details
WHERE Order_Details.OrderID = Orders.OrderID

SELECT Format(Order_Table.[Order Date],'YYYYMMDD'), Left(Order_Details.c_Product, 3), Order_Table.c_Branch, Left(Order_Table.c_Shipment, 2), Order_Details.Sales FROM Order_Table, Order_Details WHERE Order_Details.[Order No] = Order_Table.[Order No]
SELECT Format(Order_Table.[Order Date],'YYYYMMDD'), Left(Order_Details.c_Product, 3), Order_Table.c_Branch, Left(Order_Table.c_Shipment, 2), Order_Details.Sales FROM Order_Table, Order_Details WHERE Order_Details.[Order No] = Order_Table.[Order No] AND [Order Date] IN (40817,40818,40819,40820,40821,40822,40823,40824,40825,40826,40827,40828,40829,40830,40831,40832,40833,40834,40835,40836,40837,40838,40839,40840,40841,40842,40843,40844,40845,40846,40847)
=======================================================================================
ERROR [42S02] [Microsoft][ODBC Microsoft Access Driver] The Microsoft Access database engine cannot find the input table or query 'Product'. Make sure it exists and that its name is spelled correctly.
select Left(Product.c_Product, 3), Product.d_Product, Left(Product.c_Productgroup, 2), [Product Group].d_Productgroup_EN, [Product Group].c_Section, [Product Group].d_Section_EN
FROM Product, [Product Group]
WHERE Product.c_Productgroup = [Product Group].c_Productgroup
AND Product.c_Product IS NOT NULL
Order By Product.c_Product

DSN=NW
=======================================================================================
ERROR [07002] [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2.
SELECT Count(*) AS demo123987645 FROM (SELECT * FROM Order_Table, Order_Details WHERE Order_Details.[Order No] = Order_Table.[Order No]) t
DSN=ODBC_connection_1
=======================================================================================
ERROR [07002] [Microsoft][ODBC Microsoft Access Driver] Too few parameters. Expected 2.
SELECT Count(*) AS demo123987645 FROM (SELECT * FROM Order_Table, Order_Details WHERE Order_Table.[Order No] = Order_Details.[Order No]) t
DSN=ODBC_connection_1

3.6 Web Log

Scope: It logs all the events of the web HTML5 engine, by default it only tracks the exceptions. Usually when there is an exception on the webapi engine the user gets a red error message with a code, this code is a timestamp that you can use to find the exception in this log. The log can have also higher detail level, tracking all the actions of the web engine (recommended only in debug). The log level can be set into the following file: C:\Program Files (x86)\Board\Board WebApi Server\App_Data\config\diagnostic.config. The value can be set from 0 to 4: 0-Off 1-tracks the errors 2-tracks error and warnings (yellow messages) 3-tracks error warnings and informations (blu messages) 4 – tracks the full activity of the web engine in a verbose mode

Accessibility: The log is active by default on the Board web Server machine. The log file is located in the following path: «C:\Program Files (x86)\Board\Board WebApi Server\App_Data\logBoarWeb.log”

Usability: The log is unique per each Board environment. The BoardWeb.log file size could potentially increase.

Highlights: If you run the HTML5 engine under IIS ensure that the IIS has privileges to write this log in the IIS path. The log is in this case under a different location (according to your IIS settings)

 

File structure (example): 

Log

BoardWebAPIEngine.exe Warning: 0 : 09/21/2017 10:20:01, IDServer, , AuthorizationCodeStore not configured - falling back to InMemory
BoardWebAPIEngine.exe Warning: 0 : 09/21/2017 10:20:01, IDServer, , TokenHandleStore not configured - falling back to InMemory
BoardWebAPIEngine.exe Warning: 0 : 09/21/2017 10:20:01, IDServer, , ConsentStore not configured - falling back to InMemory
BoardWebAPIEngine.exe Warning: 0 : 09/21/2017 10:20:01, IDServer, , RefreshTokenStore not configured - falling back to InMemory
BoardWebAPIEngine.exe Warning: 0 : 09/21/2017 10:20:01, IDServer, , Using custom redirect URI validator - you are running with scissors.

BoardWebAPIEngine.exe Information: 0 : 09/21/2017 10:20:12, IDServer, , User is not authenticated. Redirecting to login.
BoardWebAPIEngine.exe Information: 0 : 09/21/2017 10:20:12, IDServer, , End authorize request
BoardWebAPIEngine.exe Information: 0 : 09/21/2017 10:20:12, IDServer, , Redirecting to login page
09/21/2017 10:20:12, IDServer, , Protecting message: "{\"ReturnUrl\":\"http://localhost/identity/connect/authorize?client_id=boardwebapplication&redirect_uri=http%3A%2F%2Flocalhost%2FCallback.html&response_type=id_token%20token&scope=openid&state=e4f9cb3464c84f7eac7d614a05aa2e85&nonce=

6dd5e51afeeb4cd2806d7a99b6e3f9ff\",\"ClientId\":\"boardwebapplication\",\"AcrValues\":[],\"Created\":636415788118968467}"
BoardWebAPIEngine.exe Information: 0 : 09/21/2017 10:20:12, IDServer, , Login page requested
09/21/2017 10:20:12, IDServer, , signin message passed to login: "{
\"ReturnUrl\": \"http://localhost/identity/connect/authorize?client_id=boardwebapplication&redirect_uri=http%3A%2F%2Flocalhost%2FCallback.html&response_type=id_token%20token&scope=openid&state=e4f9cb3464c84f7eac7d614a05aa2e85&nonce=

6dd5e51afeeb4cd2806d7a99b6e3f9ff\",
\"ClientId\": \"boardwebapplication\",
\"IdP\": null,
\"Tenant\": null,
\"LoginHint\": null,
\"DisplayMode\": null,
\"UiLocales\": null,
\"AcrValues\": [],
\"Created\": 636415788118968467
}"

 

3.7 Datareader Log

Scope: Logs the rejected rows of a datareader

Accessibility: The log must be activated next to every datareader (if the datareader is triggered manually), otherwise you need to specify it in the datareader procedure step. It will be placed in the dataset folder with the datareder serial number if we trigger a sql datareader, or in the file folder if we run an ascii datareader

Usability: The log Contains the rejected record and the erason why it has been rejected.

Highlights: It is calculated at every dr execution, so if you run a datareader you lose the previous log

 

File structure (example): 

 

 

 

 

 

3Chartreuse verte  

1Beverages           

1

Alltag     

[Rec.01] Error : RBT1825 New Item Found on column 1 [3]

2Chang 

1Beverages           

1

Alltag     

[Rec.02] Error : RBT1825 New Item Found on column 1 [2]

2Guaraná Fantástica

2Condiments  

2

Feinkost 

[Rec.03] Error : RBT1825 New Item Found on column 1 [2]

3Sasquatch Ale 

3Confections

1

Alltag

[Rec.04] Error : RBT1825 New Item Found on column 1 [3]

 

3.8 Transport Log

Scope: It logs the changes made to a db with the transporter tool

Accessibility: The log is in the databasename.hbmp\common folder and it’s named transport.log

Usability: The log can be used to determine which changes have been done on a database using the transporter tool

 

File structure (example): 

Log

DB_BACKUP Done Transporter
DREAD_NEW Done DataReader2
ENTCREATE Done Entity4
VERCREATE Done Cube1 - Version:2
VERCREATE Done Cube4 - Version:1
RULES_UPD Done Create rule2 [Entity4]
20170922 11:31:31 user1
-------------------------------------------------------
REL_RESET Done Entity1
CUBVALIGN Failed Cube1 [Version:2]
CUBVALIGN Failed Cube4 [Version:1]

 

3.9 Connector Log

Scope: It logs any action of connector type datareader, you can check it when the connector datareader is not working as expected or the connection itself does not work

Accessibility: The log is active by default on the Board Server machine. The log file is located in the following path: ‘’Board_Path\Dataset\’Connector.log’.

Usability: The log is unique per each Board environment. The Connector.log file size could potentially increase.

Highlights: It contains exceptions such as wrong username or password or expired token.

 

File structure (example): 

Log

4 22 Sep 2017 Fri 90 74 Thunderstorms 0 0 1 2017-09-21T08:17:51Z en-US 0 0 Yahoo! Weather - Austin, TX, US http://us.rd.yahoo.com/dailynews/rss/weather/Country__Country/*https://weather.yahoo.com/country/state/city-2357536/ Yahoo! Weather for Austin, TX, US en-us Thu, 21 Sep 2017 03:17 AM CDT 60 mi in mph F Austin United States TX 81 165 18 83 990.0 0 16.1 7:19 am 7:29 pm Yahoo! Weather 142 18 http://weather.yahoo.com http://l.yimg.com/a/i/brand/purplelogo//uh/us/news-wea.gif 30.30637 -97.752762 Thu, 21 Sep 2017 02:00 AM CDT <![CDATA[<img src="http://l.yimg.com/a/i/us/we/52/27.gif"/><BR /><b>Current Conditions:</b><BR />Mostly Cloudy<BR /><BR /><b>Forecast:</b><BR /> Thu - Thunderstorms. High: 91Low: 77<BR /> Fri - Thunderstorms. High: 90Low: 74<BR /> Sat - Partly Cloudy. High: 90Low: 73<BR /> Sun - Partly Cloudy. High: 89Low: 72<BR /> Mon - Scattered Thunderstorms. High: 89Low: 73<BR /><BR />
<a href="http://us.rd.yahoo.com/dailynews/rss/weather/Country__Country/*https://weather.yahoo.com/country/state/city-2357536/">Full Forecast at Yahoo! Weather</a><BR /><BR /><BR />]]> 27 Thu, 21 Sep 2017 02:00 AM CDT 80 Mostly Cloudy false[Rec.002] Error : RBT1825 New Item Found on column 1 [0]

 

30 23 Sep 2017 Sat 90 73 Partly Cloudy 0 0 1 2017-09-21T08:17:51Z en-US 0 0 Yahoo! Weather - Austin, TX, US http://us.rd.yahoo.com/dailynews/rss/weather/Country__Country/*https://weather.yahoo.com/country/state/city-2357536/ Yahoo! Weather for Austin, TX, US en-us Thu, 21 Sep 2017 03:17 AM CDT 60 mi in mph F Austin United States TX 81 165 18 83 990.0 0 16.1 7:19 am 7:29 pm Yahoo! Weather 142 18 http://weather.yahoo.com http://l.yimg.com/a/i/brand/purplelogo//uh/us/news-wea.gif 30.30637 -97.752762 Thu, 21 Sep 2017 02:00 AM CDT <![CDATA[<img src="http://l.yimg.com/a/i/us/we/52/27.gif"/><BR /><b>Current Conditions:</b><BR />Mostly Cloudy<BR /><BR /><b>Forecast:</b><BR /> Thu - Thunderstorms. High: 91Low: 77<BR /> Fri - Thunderstorms. High: 90Low: 74<BR /> Sat - Partly Cloudy. High: 90Low: 73<BR /> Sun - Partly Cloudy. High: 89Low: 72<BR /> Mon - Scattered Thunderstorms. High: 89Low: 73<BR /><BR /><a href="http://us.rd.yahoo.com/dailynews/rss/weather/Country__Country/*https://weather.yahoo.com/country/state/city-2357536/">Full Forecast at Yahoo! Weather</a><BR /><BR /><BR />]]> 27 Thu, 21 Sep 2017 02:00 AM CDT 80 Mostly Cloudy false[Rec.003] Error : RBT1825 New Item Found on column 1 [0]

 

3.10 Client Error Log

Scope: Logs the exceptions that send the client in faulted state

Accessibility: The log is active by default on the Board client and it’s placed under the Board options tab, just click on open error log file

Usability: The Log is generated when there is an handled exception and the client goes in faulted state.

Highlights: It only tracks exception from the client, it’s useful to understand which action throws exception.

 

Log

******************************************************************
**********************EXCEPTION***********************************
******************************************************************

Date: 17/07/2017 15:48:11

Exception Source: BoardServerInterface

Assembly: BoardWinClient, Version=10.1.0.40310, Culture=neutral, PublicKeyToken=null

Exception type: BoardSharedStructures.BoardClientException

Exception Message: Cannot Save Capsule.

Exception stack: at BoardServerInterface.BoardServerInterface.SaveCapsule(Capsule cps)
at BoardCapsuleManager.CapsuleManager.SaveCps(Capsule cps)
at BoardCapsuleManager.CapsuleManager.SaveCapsule(Capsule cps)
at BoardWorkspaceControl.BoardWorkspace.OpenBlackBoardCapsule()
at BoardWorkspaceControl.BoardWorkspace.<.ctor>b__7(ServerConnectedMessage p)

Current Principal: System.Security.Principal.GenericPrincipal


Date: 20/09/2017 15:53:31

Exception Source: PresentationCore

Assembly: BoardWinClient, Version=10.1.2.40810, Culture=neutral, PublicKeyToken=null

Exception type: System.OutOfMemoryException

Exception Message: Insufficient memory to continue the execution of the program.

Exception stack: at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Current Principal: System.Security.Principal.GenericPrincipal

******************************************************************
**********************EXCEPTION***********************************
******************************************************************

 

4 Log Encryption

The following logs can be encrypted:
User logs
Capsule log
Database log
 
To activate encryption of the log files, open the Board Server Configuration program, go in the Security tab and enable the check-box and type your encryption pass-phrase as shown in the picture below

 


 
Notes!
The pass-phrase is also necessary to de-crypt the files, make sure you keep a safe copy of your pass-phrase accessible only to authorized personnel.
Once the encryption is enabled, the prefix "encrypted" is added to the file name: for example the log file Login.log becomes encryptedLogin.log
The encryption pass-phrase is saved locally on the server using DPAPI encryption.
 
To de-crypt the log files you may use the utility program BoardLogDecrypter.exe which is found in the folder
c:\Program Files\Board\Board Server\Tools\BoardLogDecrypter
 
The syntax of the command to de-crypt a log file is the following:
 
BoardLogDecrypter EncFile="[Encrypted File]" DestFile="[Destnation File]" Password="[Password]"
 
EncFile: the encrypted log that you want to decrypt
DestFile: The destination file that will contain the Decrypted Log
Password: the password you set up in the step before.
Note that the de-crypter generates a new file in clear text without altering the original encrypted file.

27 people found this helpful

Attachments

    Outcomes