- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We've configured and installed the WorkDay for Splunk TA and run into some issues.
I believe our Client ID, Client Secret, and Refresh Token have been correctly retrieved and entered from our WorkDay backend but we're consistently seeing this issue with no good connection:
HTTPError: HTTP 503 Service Unavailable -- KV Store initialization failed. Please contact your system administrator.
Has anyone seen this error in their experience? If my auth was bad I'd expect a HTTP 403. This seems to be saying our Workday endpoint isn't configured properly or our add-on client isn't registered.
Has anyone else experienced this problem?
Thanks!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not knowing much about the Workday Add-on... it may use Splunk's KVStore, and that message namely "KVStore Initialization Failed" sounds like there's something wrong with that component of your Splunk installation. You may want to peruse some of the kvstore tagged questions for some hints / things to look at.
Nadine Miller also gave a virtual .conf talk last April entitled "KVStore Hammer Time" that may also be helpful.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not knowing much about the Workday Add-on... it may use Splunk's KVStore, and that message namely "KVStore Initialization Failed" sounds like there's something wrong with that component of your Splunk installation. You may want to peruse some of the kvstore tagged questions for some hints / things to look at.
Nadine Miller also gave a virtual .conf talk last April entitled "KVStore Hammer Time" that may also be helpful.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you! Indeed This was my problem! Expired cert, even after upgrade.
