- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2024 01:46 AM
Hello community,
We have noticed an issue with the import set for Consumer data.
There are various fails in the last few days, we’ve checked ServiceNow - snowflake is not locked and I’ve test loaded 20 records from the Data Sources (Snowflake JDBC Consumers) which worked fine.
The import sets are showing errors:
java.sql.SQLException: net.snowflake.client.jdbc.SnowflakeSQLException: Your user account has been temporarily locked due to too many failed attempts. Try again after 15 minutes or contact your account administrator for assistance. For more information about this error, go to https://community.snowflake.com/s/error-your-user-login-has-been-locked.
Would you know what might cause this error message?
I googled everywhere but did not find anything.
Thanks a lot for any help.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2024 03:53 AM
Hello Nicholas,
you were right.
Import setting was cloned to the lower instances and everything was imported every night to PROD, Test and DEV. Specifically, the tables scheduled_import_set, sys_import_set_run, and sys_data_source were likely involved. As a result, all three instances were attempting to fetch data simultaneously, leading to multiple failed login attempts and subsequently locking the user account.
Resolution:
To resolve this, I deactivated the JDBC Scheduled Data Imports on the TEST and DEV instances
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2024 02:00 AM
From the message it seems the service account is only temporarily being locked out and when you manually attempt a load it's working fine because the account is no longer locked out.
Have you validated all instances are using the correct password by manually attempting the load using the same method the scheduled jobs would use? Clone-backs could be causing issues with the credentials you have stored in sub-prod environments. It might also be due to other activities using this same credential but this is less likely.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2024 03:53 AM
Hello Nicholas,
you were right.
Import setting was cloned to the lower instances and everything was imported every night to PROD, Test and DEV. Specifically, the tables scheduled_import_set, sys_import_set_run, and sys_data_source were likely involved. As a result, all three instances were attempting to fetch data simultaneously, leading to multiple failed login attempts and subsequently locking the user account.
Resolution:
To resolve this, I deactivated the JDBC Scheduled Data Imports on the TEST and DEV instances