Troubleshooting and Support
Troubleshooting guide
If you encounter an error/issue not covered below, please contact Kumo support at [email protected].
-
During the setup, you see an error “Cannot enable event sharing as consumer account has no active event table”
This error happens because an event table has not been configured for your account. Follow the instructions on https://docs.snowflake.com/en/developer-guide/logging-tracing/event-table-setting-up to create an event table for your account. A user with
ACCOUNTADMIN
role can run the following to create an event table and set it at the account level:USE ROLE ACCOUNTADMIN; CREATE DATABASE IF NOT EXISTS <DB_NAME>; CREATE SCHEMA IF NOT EXISTS <DB_NAME>.<SCHEMA_NAME>; CREATE EVENT TABLE IF NOT EXISTS <DB_NAME>.<SCHEMA_NAME>.<EVENT_TABLE_NAME>; ALTER ACCOUNT SET EVENT_TABLE = <DB_NAME>.<SCHEMA_NAME>.<EVENT_TABLE_NAME>;
-
HTTP 403 error when accessing the Kumo endpoint.
Ensure that the default role of the user logging in has been granted theKUMO_USER_ROLE
created during installation. -
“Could not connect to the Kumo API server. Please double-check your internet connection and turn off any ad-blockers”
This error can happen when there’s a Snowflake network maintenance event and the Web UI is unable to reach Kumo running in your Snowflake account. Refresh the browser page, re-login using your Snowflake credentials and you’ll see Kumo again.
-
How do I get the URL for the Kumo application?
The
START_APP
command provides the URL to access Kumo. After Kumo is started, you can also get the URL to access the Kumo application using the following command. Navigate to the URL in your preferred browser. Login using your Snowflake credentials to use Kumo.----------------------------- --- USER INPUT REQUIRED --- ----------------------------- SET USER_WAREHOUSE = '<ADD WAREHOUSE TO USE>'; SET KUMOAPP_NAME = 'KUMO_APP'; SET KUMOAPP_ENDPOINT = CONCAT(($KUMOAPP_NAME),'.PROCEDURES.GET_END_POINT'); CALL IDENTIFIER($KUMOAPP_ENDPOINT)('USER_SCHEMA');
-
"Error accessing the specified database, schema or warehouse. Make sure USAGE privilege is granted on these objects to the Kumo application"
Make sure the required privileges are granted to the Kumo application before setting up the connector. Details of the privileges can be found here. -
"Database XYZ is a read-only secondary database and cannot be modified. Ensure that the database/schema used are writable and the appropriate permissions are granted to Kumo"
The database used to create a Snowflake connector must not be read-only. Ensure that a primary database is used for the connector creation and that the privileges here are granted to the Kumo native app.
Support
If you need assistance, you can reach out to your Kumo customer support representative or email us on [email protected]
Updated 7 days ago