If it's gonna make you feel better, I had the same problem 2 weeks ago. Did some research and found a bug with a workaround to start TAPS from the command line (net start taps). This didn't help at all, so I opened a case with Cisco, who wasted my time and couldn't help me. In the meantime, I scanned all the phones and BATted them into the CallManager. So, either you try to start it from the command prompt or you better start scanning now. BTW, if enough people complain about TAPS and the lack of documentation for it, maybe someone from Cisco will do something about it.
By default TAPS service uses CCMServiceRW. As a workaround, start the service using administrator account. Change the logon information on Cisco TAPS service using windows services pane. Before starting the service, copy the .java.policy file from C:\Documents and Settings\CCMServiceRW\ to C:\Documents and Settings\administrator\. This is done on CM server where Cisco TAPS service is installed. Try starting the service again.
Check the system log to see the audit failures and verify that is the account having issues. Then reset the password of that account, reset all the services that use that account and try to start the service from a cmd.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.