How can we help you today? How can we help you today?

Failed to Start SQL Prompt. Could not install CBT Hook.

I got the following message. Most likely the problem is I'm running both versions 2.0 and 3.0 beta.

'Failed to start SQL Prompt. Could not install CBT Hook. Error: System.Runtime.InteropServices.COMException(0xB3DA0001): Exception from HRESULT: 0xB3DA0001 at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at _1._1()'

Possible Cause:
1. Open Query Analyzer (QA).

2. Write a query that references a different database other than the one your currently connected to in the QA window. Example: You're connected to TempDB. You write "SELECT * FROM OtherDB.dbo.TableName". SQL Prompt gave me a brief message which I missed.

3. SQL Prompt's intellisense stops working. I noticed that both versions of SQL Prompt (2.0 and 3.0 beta) was running. I closed both versions. I restarted only the new version twice and then got the message above. Later I noticed that without restarting the old version, I couldn't get the intellisense to work.
dno75
0

Comments

2 comments

Sort by
  • Tilman
    Hi,

    You are not the first to encounter this message. See here

    http://www.red-gate.com/messageboard/vi ... hlight=cbt
    http://www.red-gate.com/messageboard/vi ... hlight=cbt

    However, it sounds you are getting it at different times. Do you still get the message? Or can you make it appear again? Everybody else only got it once and then it worked, and we would be very interested in reproducing it reliably.

    Regards,

    Tilman
    Tilman
    0
  • dno75
    Hi Tilman,

    I did get it at least one more time afterwards. This time with only the beta version installed. It occured when I exited SQL Prompt Beta. I think I was trying to exit SQL Prompt Beta because I couldn't get the candidate list to show up anymore (CTRL + space). I would begin writing a query using the Query Analyzer pointing to one server with the help of the candidate list (which worked great), then I'd connect to another server and try to write another query with the help of the candidate list, but this time the list would not show up. The candidate list would no longer pop up regardless of which server I was on so I tried to restart SQL Prompt. I believe this was when I got the error message. If I get it again, I'll try to find the steps to duplicate the error. Hope this helps.

    Thanks,
    David N.
    dno75
    0

Add comment

Please sign in to leave a comment.