Why am I getting error "Eventtype...does not exist or is disabled" using a user defined eventtype in a REST API call?

[kmugglet]

Is there anything I should do before using user defined eventtype in a rest api call?

my username is svc_user_bob (real name changed to protect the innocent)

as svc_user_bob I created the following eventtype
Name:

sam_service.CombinedQueueGroupEgressLogRecord

Description:

ds=service.CombinedQueueGroupEgressLogRecord

All well and good, I can return events of that eventtype.

When I do a rest call via curl

curl -k -u svc_user_bob:myFakePassword https://localhost:8089/services/search/jobs -d search="search eventtype=sam_service.CombinedQueueGroupEgressLogRecord"    

I get a SID which in job inspector shows as failed. On looking in the search log I get the following error

12-01-2014 18:00:08.615 WARN  StringSearchExpander - sid:1417417038.14 Eventtype 'sam_service.CombinedQueueGroupEgressLogRecord' does not exist or is disabled.

Why?

Other queries run via rest work OK but not this eventtype. I've deleted and created in several times just to make sure it's not a hanging config issue from some old eventtype with the same name.

[kmugglet · Accepted solution]

Quotes it is, placing the eventtype name in quotes and making sure it is readable by just about everyone on the planet seems to have worked. Just need to dial back the permissions until it fails

[kmugglet]

Sorry, should add Splunk 6.2 running on RHEL 6

[kmugglet]

I have managed to get one eventtype through a REST call : splunkd-log
It's set as global permissions with no user associated