Resizing System Volume Information (SVI) Windows only
Question: Sometimes your server might run out of space on because the SVI (System Volume Information) is eating up all memory. The system volume information is used in windows in order to save information related to system restore which is used when a restoration of the system is performed. The problem is that if there is no size limit to this feature, it might take a significant amount of the system memory, without ability to directly delete it. Answer: There are two ways to resize the SVI: Through the system properties - follow these instructions: http://www.pcadvisor.co.uk/how-to/windows/how-make-system-volume-information-folder-smaller-3613911/ Through the command line - if you don't see the system protection tab according to the above method, you can resize it through the command line: https://indrajitc.wordpress.com/2008/03/25/reclaiming-disk-space-from-system-volume-information/Troubleshooting Export to Excel Issues
Introduction In version 6.7, Sisense introduced support for exporting pivot table widgets to Microsoft Excel. For general information about the feature and how to use it, please review https://docs.sisense.com/win/SisenseWin/downloading-pivot-tables-to-excel.htm. We strongly recommend using version 6.7.1.15016 or later to successfully export widgets to Excel. Please see our release notes for more information about issues on earlier versions. Issues and Troubleshooting Issue: Export fails with the error "The file could not be generated" Root Cause: Multiple Resolution: For customers using a reverse proxy, load balancer, or bound host name in IIS, please follow Step 6 on in our SSL documentation page (https://documentation.sisense.com/setting-up-ssl/) and try again In your web browserNavigate to http{s}://{host:port}/engine/test and confirm the Excel engine is working. Expected result: {"test":"engine works properly"} Review for operating system processes that occupy the same port as your Sisense site by running "netsh http show urlacl" in the Command Prompt (cmd.exe). If a conflict is identified, run "netsh http delete urlacl url=http://*:{port}/". For example, "netsh http delete urlacl url=http://*:{8081}/". Afterwards, restart IIS by running 'iisreset' in the Command Prompt as an administrator. For further assistance, please contact Sisense support and include your logs (see information below) --- Issue: Excel export is generated but content contains garbled HTML Root Cause: Multiple Resolution: Same steps as above --- Issue: Excel exports are generally successful but fail on widgets that utilize the metadata plugin (https://docs.sisense.com/main/SisenseLinux/translating-sisense-metadata-on-linux.htm) Root cause: Conflicts between the Metadata plugin and Sisense's Excel export generation Resolution: Please contact Sisense Support --- Issue: Excel export is successful but contains incorrect formatting or styling Root cause: Limitation in Sisense version 6.7-7.0 Resolution: Upgrade to Sisense 7.0.1 or later --- Issue: Export export is successful but column sorting is incorrect Root cause: Limitation in Sisense version 6.7-7.0 Resolution: When available, upgrade to Sisense 7.1 or later --- Issue: Excel export contents do not match the pivot table contents Root cause: Issues with Sisense's Excel export engine Resolution: Our developers are aware and currently working to resolve these uncommon issues. For more information, please contact Sisense Support. Exporting Programmatically (including embedded analytics/OEM scenarios) For customers embedding Sisense who want to replicate the export to Excel functionality, please see the information available in the 1.0 version of our REST API documentation for a sample script: https://sisense.dev/guides/restApi/. To generally export widgets to Excel via the REST API, use the api/v1/engine/excelExport endpoint. The response is binary content; catch and write it to a .xlsx file in your script. Export Logs Excel export logs are located by default at C:\ProgramData\Sisense\PrismWeb\Logs\engineLogs.log. Disabling Exports Customers who wish to disable Excel exports can disable CSV and Excel exports through the Sisense REST API. The endpoint is api/roles. For more information, see https://docs.sisense.com/main/SisenseLinux/customizing-user-roles.htm. Run a PUT call to set the value for the export_csv property under Widgets to false. This change will need to be run for each role you want to affect.Resolving the ODBC_Wrapper.dll Error When Connecting Via ODBC
Scenario: A common error when trying to connect via ODBC to a data source is: "Could not load file or assembly 'ODBC_Wrapper.dll' or one of its dependencies..." This error can occur after successfully setting up the ODBC connection in the Windows ODBC Data Source Administrator, when trying to use the ODBC connection in the ElasticubeManager. This error happens due to a missing component in the Windows OS Installation. Solution: Please download and install the following update on your Elasticube server: Microsoft Visual C++ 2015 Redistributable Package (x64). After the installation is complete, restart the Elasticube Manager (and server, if prompted to do so) and try connecting again with your connection string / DSN for the ODBC.Error exporting to PDF
Sisense allows you to generate a PDF report of your dashboard when you need to take copies of your dashboards with you for meetings or sharing them with others. This article gives detailed troubleshooting steps on how to handle PDF export failures on all Sisense versions. How Does It Work? When you click Download PDF or the PDF icon in the menu bar , a preview of your report is opened. After you have defined the appearance of your report, you can save the layout of the dashboard by clicking Save. The next step is to click Download PDF, your saved layout will be downloaded into a PDF file. Disable All Plugins One of the most common causes of a PDF export failure is due to a faulty plugin. If you cannot export any report to PDF, then the issue is most likely due to plugins. Firstly, disable all the plugins. To do so, go to Admin → Plugins under System Configuration and toggle the switch to disable each plug-in. To disable all plugins at once, select each Plug-in and toggle the Disable Selected switch: If the report is exported to PDF successfully, then you can switch on the plug-ins one-by-one to find the problematic one. When you find a problematic plug-in, make sure you have the latest version of the plug-in installed. If disabling all plugins does not work we recommend going to the actual "plugins" folder on the Sisense server and removing all the plugin folders manually. For versions 7.2 and higher the "plugins" folder can be found in C:\Program Files\Sisense\app\plugins For versions 7.1 and lower the "plugins" folder can be found in C:\Program Files\Sisense\PrismWeb\plugins Disable All Scripts An easy way to determine where the issue is, is to create a new simple widget and try to export it. If the dashboard is exported successfully, it means that the issue is local, and you need to check the scripts applied to your widgets and dashboards. Try to disable your scripts to understand if it affects your PDF exports. Once you find the broken script, you will need to fix it. To disable a script, you need to open the Script Editor and disable your script by commenting it out. It can be commented out by adding ‘//’ to the beginning of each row. For dashboard scripts, for the dashboard, in your dashboard, click Edit Script For a specific widget, click on the widget in Edit mode. 7.2 And Later Further Troubleshooting If you are using Sisense installation which is on V7.2 and above and still experiencing errors with PDF exports, it is possible that it is related to a Configuration Manager setting. To troubleshoot this, on a Sisense webserver take the following steps: (please note that this could make your site unavailable for a short period of time so take care to do this off-hours if in a production environment) In a web browser (Chrome is preferred but any of the supported web browsers are OK), navigate to http://localhost:3030 You will see the Configuration Manager appear Scroll down to the "Domain Binding" section. If this field is populated, remove the entry. There are only a few specific reasons to have this set. If your Sisense domain is attached to the server via a DNS entry you typically do not need to set this. Click the 'Save' button at the top right-hand corner 7.1 And Earlier Further Troubleshooting If you are using Sisense installation which is below V7.2 and still experiencing errors with PDF exports, it is possible that it is related to a local configuration file issue. To verify the configuration is correct, please follow the below: If you have an domain defined on your server, make sure the setting in 'Admin'-->'system configuration' does not include "http://" Make sure that you have access to the domain URL from the local server (ie. http://bi.my.company.com/) If you have SSL configured - please make sure you can browse to the secure site locally as well (ie. https://bi.my.company.com/) Check bindings: Open the Windows IIS Manager -> Navigate to each of the websites -> "Bindings" and make sure that no two websites bind to same port (double bindings) Go to "Add or Remove Programs" -> Right click on Sisense and choose "Change..." -> In installation window "Continue" -> "Change Settings" and verify that the port configured matches the port specified in the IIS Manager for Sisense Web If these troubleshooting steps do not fix the issue, you may need to edit the exporting section of the default.yaml file. Find the file here: C:\Program Files\Sisense\PrismWeb\vnext\config The exporting section is located at the end of the file, and there are 3 variables you may have to change- host, port, and protocol. Please set these variables to the values that are used to access Sisense Web on the server. For example, if you access Sisense Web by going to http://test.dashboards.com, you would set the variables tohost: "test.dashboards.com" port: 80 protocol: "http" After making the changes, save the file, and restart IIS. Log Files For further investigation detailed logs on the any PDF related errors can be found below For Sisense V7.1.3 and earlier: C:\Program Files\Sisense\PrismWeb\vnext\iisnode For Sisense V7.2 and later: C:\ProgramData\Sisense\application-logs If you are still seeing issues after following this guide please feel free to contact Sisense Support for further assistanceJWT Token Not Working After Upgrade to Version 6.7 (and Up)
If you are using JWT SSO in Sisense, the SSO might stop working after upgrading to version 6.7 and up. The reason for that could be a missing "typ": "JWT" attribute in the JWT token's header. To check if the header attribute is missing, retrieve the JWT token generated by your system and plug it into a JWT online debugger such as jwt.io. Check the decoded header of the token to see whether the "typ": "JWT" exists or not. For example: Solution Modify your SSO script to explicitly include the "typ": "JWT" in the generated JWT token. How to Extract Your JWT Token Open your web berowser. Open the browser's developer tools panel, and click on the Network tab. Navigate to your Sisense web. Make sure you are longing in via SSO.| In the Developer tool Network panel, look for the jwt call and highlight it. Highlight the Request URL in the Headers tab, copy, and paste it into a text editor. The string between the "jwt=..." and "&return..." is your JWT token.