Generating a HAR file for troubleshooting Sisense
When troubleshooting complex issues in Sisense such as PDF export, widget not loading etc., it is sometimes necessary for our support team to obtain additional information about the network requests that are generated in your browser while an issue occurs. A technical solutions engineer may request you to record a .HAR file, or a log of network requests, while that issue is occurring and then provide that to them for further analysis. Below are some instructions about how you can easily generate a HAR file using different browsers. Note: Keep in mind that HAR files contain sensitive data, including content of the pages you downloaded while recording and your cookies. This allows anyone with the HAR file to impersonate your account and all the information that you submitted while recording (personal details, passwords, credit card numbers, etc.). To generate the HAR file for Chrome Open Google Chrome and go to the page where the issue is occurring. Look for the Vertical ellipsis button and select More Tools > Developer Tools. From the panel opened, select the Network tab. Look for a round Record button in the upper left corner of the tab, and make sure it is red. If it is grey, click it once to start recording. Check the box Preserve log. Click the Clear button to clear out any existing logs from the Network tab. Reproduce the issue that you were experiencing before, while the network requests are being recorded. Once you have reproduced the issue, in Chrome, click Download. Then save the file to your computer: Save as HAR with Content Upload your HAR file to your ticket or attach it to your email so that our Support team can analyze it. The instructions are the same for a MAC computer or a Windows computer. Here is a brief animation showing this process: To generate the HAR file for Firefox Open Firefox and go to the page where you are experiencing trouble. Select the Firefox menu (three horizontal parallel lines) at the top-right of your browser window, then select Web Developer > Network. The Developer Network Tools opens as a docked panel at the side or bottom of Firefox. Click the Network tab. The recording autostarts when you start performing actions in the browser. Once you have reproduced the issue and you see that all of the actions have been generated in the Developer Network Panel (should just take a few seconds), right-click anywhere under the File column, and click on Save all as Har. Save the HAR file somewhere convenient. Upload your HAR file to your ticket or attach it to your email so that we may analyze it. The instructions are the same for a MAC computer or a Windows computer. To generate the HAR file for Edge Edge natively produces HAR files. For more instructions, see the instructions from the Microsoft website. Open the Network tool in F12 developer tools. Reproduce the issue. Export captured traffic as a HAR (CTRL + S). To generate the HAR file for Internet Explorer Open Internet Explorer and go to the page where the issue is occurring. Press F12 on your keyboard (or click the gear icon > F12 Developer Tools) Click the Network tab. Reproduce the issue that you were experiencing before, while the network requests are being recorded. Once done click the Save button. Give the trace a filename and click the Save button which will save it as a .har file or .xml file. Upload your HAR file to your ticket or attach it to your email so that we may analyze it. The instructions are the same for a MAC computer or a Windows computer. Please NOTE: You need to be aware that HAR files contain sensitive data, including the content of the pages you downloaded while recording and your cookies. Examples of information contained in the HAR file include personal details, user ID, passwords, and credit card numbers. You can always when the file is downloaded, replace the sensitive data.Build Errors Troubleshooting
When a build fails it's not always easy to identify the root cause of the failure. This post contains How-To troubleshoot your own build failure and popular build errors. You can search (Ctrl+F) this article for errors or search similar errors by build stages. Topics: How-To Troubleshoot your build failure Accumulative or Schema Changes builds introduction Troubleshooting Finalization stage time Troubleshooting ODBC driver Useful Articles Common errors in Importing data stage Common errors in Custom SQL stage Common errors in Initialization stage Common errors in Finalization stage Quick Troubleshooting and general introduction ElastiCube builds can be split into to three main stages: 1) Data Import 2) Custom SQL (Table\ Column) 3) Initializing/Finalizing a) Initializing - Creation of a proper structure for the data to be stored in the local environment. Something fundamental is failing → restart services b) Finalization - Arranging metadata and swapping the process with new data available for user's queries Accumulate build and Schema Changes are more fragile and disk consuming than Full build operations. If time allows, always go with Full build (‘Delete existing data’) as an immediate recovery. In Accumulative or Schema Changes builds, the Initializing and Finalizing stages contain the following operations: Initializing - Backup existing data folder to the _Alternative data folder to keep _Alternative available for querying during the Accumulative build of the main folder Finalizing - Copying all newly accumulated/imported data from the main folder to the _Alternative folder so they're both up to date Troubleshooting Finalization stage time: During finalizing stage Sisense removes the previous completed build and repoints the process to the new one. It requires additional resources of Disk Drive which can be longer then expected. Please ensure that Disk drive system works fine. Have disk defragmentation to the Disk Drive where cubes are located. Troubleshooting ODBC driver: Testing your ODBC driver with ODBCTest tool - Microsoft offers a connectivity test tool for ODBC connector. By running the ODBC Test tool you will be able to connect and query the underlying dataset. Download ODBCTest tool through Microsoft website Useful Articles A Tool To Help You Read an Compare ElastiCube Build Logs Clean Up Your C Drive Elasticube Plugins Server Console Preferences & Configuration Elasticube Manager Hangs When Trying To Add Amazon Redshift Data Turn Off Non-Blocking Accumulative Builds Important Note: When submitting a ticket to support, add as much information as possible, such as build stage, data source, screenshot of the error message, and attach relevant logs: Build Process logs: %ProgramData%\SiSense\PrismServer\ElastiCubeProcessLogs\<YourElastCubeName> ElastiCube Server Logs: %ProgramData%\Sisense\PrismServer\PrismServerLogs Importing data Error message: Naming issues "Invalid object name" Or "Could not find server '{S1}' in '{S2.S3}'. Verify that the correct server name was specified" Build stage: Importing data from a datasource Note: Schema name contains one or two dots (For example: Schema.Name.BP or Schema.Name) Troubleshooting: Edit the query in the ElastiCube and wrap the schema name in double-quotes (SELECT * FROM "Schema.Name".[table] Error message: 403:unauthorized error Build stage: Importing data from another ElastiCube Troubleshooting: This error happens if the user credentials used for logging to the server don't belong to an admin user, as only admin users are allowed through the Sisense ElastiCbue connector. Error message: Naming issues "Import failed - error 500 "Query could not be compiled" [field_name] is ambiguous between 'table_name.field_name' " Build stage: Importing data from another ElastiCube Troubleshooting: If both table name and field name are the same - change one of them in source cube rebuild the cube and retry to import data again Error message: "Exception while reading from stream" Build stage: Importing data from Redshift Troubleshooting: Go to "C:\Program Files\Sisense\DataConnectors\DotNetContainer\Connectors\Redshift\Sisense.Connectors.RedshiftConnector.dll.config" file and change the timeout value from "0" to "3000". After saving the change please restart the Sisense.CLRConnectirsContainer Service and try to run the build again. Error message: "There was no endpoint listening at net.pipe://localhost/CloudManagementService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details." Build Stage: In the build process or when interacting with ElastiCubes in the ElastiCube Manager Notes: Tends to be sporadic. Troubleshooting: Confirm that the ElastiCube Server is up and running If so, please try to restart services: ElastiCubeManagmentService (Sisense Version 7.1 and below) Sisense.ECMS (Version 7.2 and later) Sisense.ECMServer (Version 7.2 and later) Sisense.Repository Sisense.Oxygen Restart IIS by running 'iisreset' as an Administrator in the command prompt Error message: "Could not get connector for XXX database." Build stage: Importing data from a datasource Troubleshooting: Sisense.CLRConnectorContainer (For Sisense Connectors with Framework - JVM) or Sisense.JVMConnectorsContainer (For Sisense Connectors with Framework -.NET) Error message: "OutOfMemoryException" Build stage: Importing data from a datasource Note: The "Data-import chunk size" setting in the ElastiCube Server Preferences windows is set to a value larger than the available memory. Troubleshooting: Go to SiSense Server Console Click on server preferences Click on "More Settings..." Set "Data-import chunk size" to a value smaller than the max available memory. The default value of this setting is 100000. Error message: “Index is out of range” Or “Memory allocation has failed…” Build stage: Importing data from MongoDB Troubleshooting: A general approach to this issue would be to decrease/minimize the amount of columns generated for that table. There are a few ways to achieve this: If you did not select the virtual tables (containing _VT_ in their name), try selecting the virtual table instead If the error persists even while selecting a virtual table there are 2 options: In the ODBC driver configuration, hide columns that are not necessary for the reporting. Open up the ODBC Data Source Administrator from the windows start menu and configure the MongoDB driver Select Schema definition and then Edit Schema file Check the columns you want to hide, click save, tha lot or documentsen close the dialog Click on “Upload Metadata” to update the schema definition. In the Elasticube manager, delete the previously generated table and bring in the newly generated table, with the less columns. Alternatively, in the Elasticube manager, when you select the tables to bring in, instead of bringing in the table as is, edit the SQL query so that you bring in only those columns needed Instructions on how to do so can be found here. Rebuild Elasticube. Error message: "Import failed - Specified Cast is not valid" Build stage: Importing data from a datasource Note: Affects several connectors in Sisense Version 6.6 and later, including Redshift, PostgreSQL, and Oracle Troubleshooting: For Redshift and PostgreSQL: This issue manifests on Sisense 6.6 and was resolved on Sisense 6.7 For Oracle: This issue manifests on Sisense 6.6 and was resolved on Sisense 7.0. It occurs when importing data with more than 26 digits of precision. Apart from upgrading, the data can be cast/truncated/rounded in a manual query. Error message: “ERROR [HY000] [Simba][Support](50090) Conversion from … failed” Or you see a field in the MongoDB but that field does not exist in the table generated in the Elasticube Manager Build stage: Importing data from MongoDB Note: The MongoDB ODBC driver automatically generates the schema definition based on data sampling. Since the MongoDB schema is dynamic it is possible that documents that were not sampled had a different datatype or structure. Troubleshooting: Better sampling will resolve this issue. Open up the ODBC Data Source Administrator through the windows start menu Select the Mongo driver and click on “Advanced Options” In the documents to sample, increase the number of documents to sample. You can also set it to 0 and sample all documents to get the most accurate schema, however this may take some time, especially if there are a lot or documents: Click OK Click Schema Definition Click Generate All (this may take some time if you sample all documents!) Click Upload Metadata Bring in the new table generated into the Elasticube Rebuild the Elasticube Issue: New CSV files placed in a folder are not picked up in the build process Build stage: Importing data from a folder of CSV files Troubleshooting: Open C:\ProgramData\Sisense\PrismServer\ElastiCubeConfiguration.xml Add a new tag with the following text:<UseDotNetCsvConnector>true</UseDotNetCsvConnector> Restart the ElastiCubeManagement (Sisense Version 7.1 and earlier) or the Sisense.ECMS service and Sisense.ECMServer (Sisense Version 7.2 and later). Error message: "Memory allocation has failed for {ElastiCube name}. Please verify you have sufficient RAM and try to rebuild." Build stage: Importing data from data source tables Troubleshooting: Review the memory usage on the server at the build time. If it's nearly maxed out, try to reduce the number of rows or increase the machine hardware. If the memory is not heavily in use, review the number of columns in the source table. Uncheck 'Import' on unneeded fields, or use a custom import query to only import necessary fields. Error message: "ERROR [28000][Snowflake][ODBC](11570) Required credential settings are missing:{[PWD]}. ERROR [08001][Snowflake][ODBC](10380) Unable to establish a connection with data source. Missing settings:{[PWD]}" Build stage: Importing data from a datasource using an ODBC connector Note: If you are trying to setup a new Elasticube using the Snowflake ODBC connection functionality, but keep getting a password related connection error, there might be a need to hard code the credentials in the Windows Registry. According to the Snowflake documentation this is a safety precaution by Windows: "The Password field accepts a value, but does not store the value. This is a security precaution to ensure passwords are never stored directly in the driver." Troubleshooting: Hard code the credentials in the Windows Registry. To do so, please follow the steps below: Open the Registry Editor (Windows key + R and then type regedit). Once it's open, navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\{Snowflake driver name} In the right hand pane, right-click on the screen and select New > String value. Name this value uid. After adding, right-click on the newly created object and in the Edit String window, enter in the Value data cell the Snowflake login name. Repeat step 3. Name the new value pwd and repeat step 4) but enter the Snowflake password. Error message: "Import Failed ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified." Build stage: Importing data from a datasource using an ODBC connector Troubleshooting: Confirm you have set up the DSN with ODBC Data Sources (64-bit) (%windir%\system32\odbcad32.exe) Confirm you have set up the DSN as a System DSN rather than User DSN Test the DSN to confirm you can connect successfully before attempting to build Error message: "Import failed - Specified Cast is not valid" Build stage: Importing data from a datasource Note: Affects several connectors in Sisense Version 6.6 and later, including Redshift, PostgreSQL, and Oracle Troubleshooting: For Redshift and PostgreSQL: This issue manifests on Sisense 6.6 and was resolved on Sisense 6.7 For Oracle: This issue manifests on Sisense 6.6 and was resolved on Sisense 7.0. It occurs when importing data with more than 26 digits of precision. Apart from upgrading, the data can be cast/truncated/rounded in a manual query. Error message: "ORA-12504: TNS:listener Was Not Given The SERVICE_NAME In CONNECT_DATA" Build stage: Creating custom SQL expression table Note: The issue is that the connection string to the Oracle DB is expecting a SERVICE_NAME parameter instead of an SID. The difference between them is that SID is the unique name of the instance while the SERVICE_NAME is the alias to the instance Troubleshooting: Choose Add Data (or ElastiCube > Change connectivity > Change source provider if you're just updating an ElastiCube that started failing). In the Connect to Oracle Database window, uncheck the Use Direct Connection checkbox. In the Database server location textbox, enter the following: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=$your_ip)(PORT=$your_port))(CONNECT_DATA=(SERVICE_NAME=$service_name))) The variables you need to input are: $your_ip $your_port $service_name 4. Connect to the server and rebuild. If you need to find out the SERVICE_NAME, you can do so by connecting to the Oracle DB and running the following command: select * from global_name; For more information about the source of the issue visit the following: https://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams188.htm#REFRN10194 Error message: "Failed to load datasources" Build stage: Importing data from a datasource Troubleshooting: 1. Open the Control Panel > Administrative Tools > Services 2. Find each of the following services in the list and repeat steps 3&4. Do this in the following order of services: "ElastiCubeManagmentService" "Sisense.Repository" "SIsense.Oxygen" "Sisense.CLRConnectorsContainer" "Sisense.JVMConnectorsContainer" "SisenseWebExpress" - if you cannot find this service, see step 5. 3. Right-click on the service and select Stop (make sure the Status field becomes blank). 4. Right-click on the service again and select Start (make sure the Status field changes to ‘Running’). 5. In case SisenseWebExpress is not installed, restart the IIS web server: In your Start menu, type 'cmd'. Right-click the shortcut and select Run as Administrator. In the Command line, type: "iisreset", hit Enter and wait for the IIS server to restart. Close the Command prompt window. 6. Refresh your web browser page. 7. If refreshing the web browser didn’t help the issue, delete browsing data in your web browser. Error message: "Connection is not opened" Build stage: Importing data from a datasource Troubleshooting: 1. Open the Control Panel > Administrative Tools > Services 2. Find each of the following services in the list and repeat steps 3&4. Do this in the following order of services: "Sisense.ECMS" "Sisense.CLRConnectorsContainer" "Sisense.JVMConnectorsContainer" 3. Right-click on the service and select Stop (make sure the Status field becomes blank). 4. Right-click on the service again and select Start (make sure the Status field changes to ‘Running’). Custom SQL Error message: "The ElastiCube failed to complete query request (Connection lost)" Build Stage: Building a custom field or custom SQL expression table Note: Can occur on cubes that previously built successfully as the volume of data grows. Less common on later versions of Sisense. Troubleshooting: Review the build logs for the last mentioned column or table Review the SQL query for that field/table. The error indicates that Sisense is having trouble performing the SQL query used to create the field or column. Multiple date/time functions, complex operations, large joins, repeated use of UNION, nested CASE statements, and others are often the culprit. Try to rewrite or restructure the query in a simpler way to test Error message: Updating BBP for 'xxxx' failed. Capacity<Count (xxx < yyy). Build stage: Creating custom SQL expression tables/fields Troubleshooting: Upgrade to Sisense Version 6.6 or later Perform a full build, rather than a schema changes build Review and/or rewrite the custom SQL expression the build is failing on Error message: " Build Stage: During the build on a table/field Notes: May have multiple root causes Troubleshooting: Typically caused by a problematic join in the ElastiCube Manager. Review the last table/column mentioned in the build log for any incorrect joins (massive cross joins/not specifying a join ON clause, joining tables/fields incorrectly). Error message: Exception in DirectCommand.ExecuteReader(): DirectCommand.ExecuteReader failed: Query number 0: SQLException:int:conversion of string '...' failed Build stage: Creating custom SQL expression tables joined to existing tables Troubleshooting: Copy your new Custom SQL expression and save it off somewhere else (such as a Notepad document). Remove the custom table and all indexes on the existing table. Recreate the new table with your stored expression but don't join it to your existing table. Perform a Schema Changes build. Re-add the relationship between the new and the existing table. Perform a Schema Changes build. Initialization Error message: "Accumulative Changes Log Creation Failed Error Create Patch [The requested operation could not be completed due to a file system limitation ]" OR "Accumulative Changes Log Creation Failed Error Create Patch [There is bot enough space on the disk. ]" OR "Accumulative Changes Log Creation Failed" Build Stage: Initializing Build Note: Occurs only on accumulative builds. Can be caused by a Windows OS issue in some cases or there is not enough disk space on your Sisense machine. Troubleshooting: Check that there is adequate disk space Sisense saves temporary copies of the ElastiCube during the build in C:\ProgramData\Sisense\PrismServer\Patches. To move this location to another drive, modify C:\ProgramData\Sisense\PrismServer\ElastiCubeConfiguration.xml: Add on the second-to-last line (just before the </ElastiCubeConfiguration> closing tag), the following text: <DefaultPatchesDirectory>D:\</DefaultPatchesDirectory>, where D:\ is the new patches location Restart the ElastiCubeManagementService If that doesn't resolve the issue, navigate to the Sisense Server Console preferences and uncheck Compress on build (See: Server Console Preferences & Configuration article) Alternatively, defragment the affected drive (Search for Defragment and Optimize Drives on your server > select the driver that the cubes are saved on > click Optimize) Error message: "Connection Timeout: The request channel timed out while waiting for a reply after 00:02:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout." Build stage: Initializing Build Note: Error message comes up in a window in the ElastiCube Manager. This error may be coupled with other erratic or incorrect build behavior. This error is likely the result of Sisense files becoming corrupted. Troubleshooting: Record any ElastiCube Manager scheduled build settings set up to back them up Stop the ElastiCubeManagementService (on Sisense Version 7.1 and earlier) or Sisense.ECMS and Sisense.ECMServer (on Sisense Version 7.2 and later) Go to C:\ProgramData\Sisense\PrismServer Rename ElastiCubeCatalog to ElastiCubeCatalog0 Restart the ElastiCubeManagementService. The service restart may take longer than usual. Re-create your scheduled build settings in the ElastiCube Manager (they may be deleted in the troubleshooting process). Error message: "Elasticube xxxx is already being built" Or build is not starting Build Stage: Initializing Build Note: The ElastiCube server service is running on the system account. This issues can be caused by a Microsoft restriction, when the user running the ElasticubeManagement/Sisense.ECMS service doesn't have sufficient credentials (System account by default). Troubleshooting: Change the logon properties of the ElastiCube Management Service Steps: Go to Control Panel > Administrative Tools > Services Find (On Sisense V7.1 and below) ElastiCubeManagementService (on Sisense V7.2 and above) Sisense.ECMS, right-click and select Stop. Find (On Sisense V7.1 and below) ElastiCubeManagementService (on Sisense V7.2 and above) Sisense.ECMS, right-click and select Properties. Select the Log On tab, select This Account then click Browse. Click Locations. Choose your domain (e.g., Sisense.local in this example) and click OK. Click Advanced. Click Find Now, choose the user logged on to the machine and click OK. The selected user will be added to the names box, click OK. Enter and verify the user’s password, click OK. Restart the service. Error message: "Object reference not set to an instance of an object" Build Stage: Initializing Build (or prior to Initialization) Note: This error can result from a few different issues, most commonly for custom columns and custom tables. It is also helpful to think about what changed in the model before you encountered this error. Troubleshooting: Verify naming and references of each of the custom SQL expression tables and columns. Also try a full build of the cube. Steps: Start out with trying a full build of the Elasticube. If you see this error at the beginning of a build, open each custom SQL table and parse/preview the expression. Verify table and column names match what is in the model. Try a full build. If you still see issues, open each custom column and parse/preview the expression. Verify table and column names match what is in the model. Try another full build. Error message: "Unable to verify the first certificate" Build Stage: Initializing Build (or prior to Initialization) Note: This may indicate that the SSL certificate is not correctly configured (for example, the certificate only has one section, when it should have at least three) Troubleshooting: Please see this post on how to troubleshoot this error Finalization Error message: "ElastiCube XXX is having difficulties closing." Build Stage: Finalizing Build Note: This less likely to happen in Sisense V6.7 or later Troubleshooting: Modify C:\ProgramData\Sisense\PrismServer\ElastiCubeConfiguration.xml Increase <AbacusDbFarmGraceFulTimeoutInSeconds>30</AbacusDbFarmGraceFulTimeoutInSeconds> to 300 Increase <AbacusDbFarmForceFulTimeoutInSeconds>600</AbacusDbFarmForceFulTimeoutInSeconds> to 1200 After the updates, save the file and restart the ElastiCubeManagementService (on Sisense Version 7.1 and below) or Sisense.ECMS and Sisense.ECMServer (Sisense Version 7.2 and later)Troubleshooting Guide: General Website Loading Issues
This page is meant to provide an initial reference for website loading issues. Topics: 1. Page Doesn't Show Up 2. No Dashboard Panel on Left Side of Analytics Page/Bottom of Analytics Page 3. Queries are not Returning Data (Including Dashboards) 1. Page Doesn't Show Up Note: If you have just set up SSL on 7.2 refer to our SSL troubleshooting guide here. Sisense Version 7.2 and above On Sisense 7.2 and above, this error could look like the screenshot below: To resolve, follow steps below: On your Sisense webserver, open the Control Panel Click on 'Administrative Tools' Click on 'Services' For each of the services, please find them in the list and repeat steps 5&6, in the following order: Sisense.Gateway Sisense.Broker Sisense.Galaxy Right-click on it and select 'Stop' (make sure its status field becomes blank) Right-click on it and select 'Start' (make sure its status field changes to "Running") If this does not resolve the issue you are facing, please create a ticket with our support team that includes the application-logs directory on your Sisense webserver (located C:\ProgramData\Sisense\application-logs). Sisense Version 7.1 and below Sisense Verison 7.1 and below runs on the Microsoft program Internet Information Services (IIS). Sisense Version 7.2 runs on NodeJS and most of the site no longer runs on IIS which means you are not likely to run into this same issue on Sisense 7.2 and above. On Sisense 7.1 and below, this error could look like the screenshot below: To resolve, follow the steps below to restart IIS: On your Sisense webserver, go to the Start Menu and type 'cmd' Right-click the shortcut and choose 'Run as Administrator In the command line, type: 'iisreset' hit Enter, and wait for the IIS server to restart. Close the command prompt window. Try to reload the website, keep in mind it can take a few minutes for the site to come back up (longer when there are very large cubes or a large number of cubes). You'll know the site is back up when where are 7+ node.exe processes within Task Manager If this does not resolve the issue you are facing, please create a ticket with our support team that includes the iisnode directory on your Sisense webserver (located C:\Program Files\Sisense\PrismWeb\vnext\iisnode). 2. No Dashboard Panel on Left Side of Analytics Page/Bottom of Analytics Page This issue could look like the screenshot below where you are not able to see any of your dashboards in the left panel or in the section at the bottom of the Analytics page: Sisense Version 7.2 and above To resolve, follow the steps below to start services: On your Sisense webserver, open the Control Panel Click on 'Administrative Tools' Click on 'Services' For each of the services, please find them in the list and repeat steps 5&6, in the following order: Sisense.Galaxy Sisense.Gateway Sisense.Broker Right-click on it and select 'Stop' (make sure its status field becomes blank) Right-click on it and select 'Start' (make sure its status field changes to "Running") Open your Sisense website within a new browser window If this does not resolve the issue you are facing, navigate to the following URL: /app/test (for example http://localhost:8081/app/test) and see which services (if any) are failing. Please create a ticket with our Support Team that includes the application-logs directory on your Sisense webserver (located C:\ProgramData\Sisense\application-logs) and a screenshot of the results of the /app/test site. Please also mention if your organization uses AD within Sisense. Sisense Version 7.1 and below This is unlikely to happen on Sisense Version 7.1 and below. If you do run into this issue, please create a ticket with our support team that includes the iisnode directory on your Sisense webserver (located C:\Program Files\Sisense\PrismWeb\vnext\iisnode) and the DB directory on your Sisense webserver (located C:\ProgramData\Sisense\PrismWeb\Repository\DB). 3. Queries are not Returning Data (Including Dashboards) The primary symptom is that the dashboard returns yellow diamonds for every widget even through the ElastiCube exists and is running as shown in the screenshot below: The dashboard could also show the loading icon for a very long time, or 500 error Sisense Version 7.2 and above Disclaimer: If your organization is using Active Directory (AD) please open a ticket with our support team to assist in troubleshooting. To troubleshoot On your Sisense webserver, navigate to the following URL: http://localhost:14996/paths and see what the site responds with: If you see data returned, like shown in the screenshot below: Restart the ECMS service by following the steps below: On your Sisense webserver, open the Control Panel Click on 'Administrative Tools' Click on 'Services' For each of the services, please find them in the list and repeat steps 5&6, in the following order: Sisense.ECMS Right-click on it and select 'Stop' (make sure its status field becomes blank) Right-click on it and select 'Start' (make sure its status field changes to "Running") If you do not see data returned, like shown in the screenshot below: Restart IIS by following the steps below: On your Sisense webserver, go to the Start Menu and type 'cmd' Right click the shortcut and choose 'Run as Administrator' In the command line, type: 'iisreset' hit Enter and wait for the IIS server to restart. Close the command prompt window. Try to reload the dashboard. If the steps above did not resolve your issue, please do the following to create a new catalog folder which will most likely resolve the issue: Important note: Please be aware that your build-scheduling settings will be erased after the operation, so you will need to re-configure these on all your ElastiCubes. Open the start menu or Task Manager and search for 'Services' Find the following services and stop them 'Sisense.ECMS' 'Sisense.ECMServer' Open the following path - C:\ProgramData\Sisense\PrismServer and rename the 'ElastiCubeCatalog' to 'ElastiCubeCatalog1'. Open the 'Services' as previously done and start the 'Sisense.ECMS' and 'Sisense.ECMServer' service once again, this will take a bit longer than usual forcing Sisense to create a new catalog folder. Once the services are back up, try to reload the dashboards If this does not resolve the issue you are facing, please create a ticket with our support team that includes The ECS logs (located here: C:\ProgramData\Sisense\PrismServer\PrismServerLogs). Also inform the agent what you have tried to do to resolve the issue so far and whether your organization has integrated Active Directory (AD) with Sisense. Sisense Version 7.1 and below To troubleshoot, follow the steps to restart the ElastiCube Management Service: On your Sisense webserver, open the Control Panel Click on 'Administrative Tools' Click on 'Services' For each of the services, please find them in the list and repeat steps 5&6, in the following order: ElastiCubeManagementService Right-click on it and select 'Stop' (make sure its status field becomes blank) Right-click on it and select 'Start' (make sure its status field changes to "Running") If the steps above did not resolve your issue, please do the following to create a new catalog folder which will most likely resolve the issue: Important note: Please be aware that your build-scheduling settings will be erased after the operation, so you will need to re-configure these on all your ElastiCubes. Open the start menu or Task Manager and search for 'Services' Find the 'ElastiCubeManagementService' and stop it Open the following path - C:\ProgramData\Sisense\PrismServer and rename the 'ElastiCubeCatalog' to 'ElastiCubeCatalog1'. Open the 'Services' as previously done and start the 'ElastiCubeManagementService' service once again, this will take a bit longer than usual forcing Sisense to create a new catalog folder. Try to reload the dashboard. If this does not resolve the issue you are facing, please create a ticket with our support team that includes The ECS logs (located here: C:\ProgramData\Sisense\PrismServer\PrismServerLogs). Also inform the agent what you have tried to do to resolve the issue so far and whether your organization has integrated Active Directory (AD) with Sisense.Debug Script In Browser's Devtools
1. You can do that by adding the "debugger;" keyword anywhere in your widget or dashboard script, opening the developer console and refreshing. As the script is processed by the browser, it will stop execution at this point in the script and behave just like a manually added breakpoint. prism.on("beforemenu", function(){ debugger; }); 2. It should work in all plugins without issue. First of all, try placing a "console.log" at the exact location of your "debugger" statement and see if that does work - that is, if that line is really reached. Additionally, with plugins you can use Chrome's DevTools to place breakpoints anywhere in your code. You can find the plugin code in the location outlined in this screenshot below - find the code you're interested in, place a breakpoint and reload to see if that does stop.
