BOOM! Failed to Start SQL Prompt immediately after install

• 
  Thanks Stephen,
  
  
  We're looking into this now.
  
  
  Thanks,

  Bart Read September 01, 2006 13:07

  - 0 +
• 
  After the above, I fired it off from the Programs list.
  
  It runs because the tray icon is showing.
  
  But, the only option on the icon is "Exit".
  
  Also, I tried typing a simple SELECT * FROM dbo. statement in the Management Studio editor, NOT having restarted the MS, and nothing happened - no list of objects, etc. MS restart required?

  PDinCA September 01, 2006 13:25

  - 0 +
• 
  I am getting the same problem, just to let you know it's not a "one-off"...
  
  Is there anything that you would like to know about my PC settings that might help resolve this?
  
  Chris

  Chris Palmer September 03, 2006 14:59

  - 0 +
• 
  • General information about my PC
  o CPU type and speed
  Pentium 4, 3Ghz
  o Amount of physical memory
  1G
  o Hard disk size and free space
  75G, 25G+ Free
  • Operating system, version, and any service packs installed
  XP Pro SP2
  • Publisher/version of any anti-virus software you have installed
  Trend Micro Office Scan Corporate Edition 5.58
  • SQL Server version and service pack information, and also
  N/A for this bug
  o Whether the server is a local or remote instance
  o Whether it is a default or named instance
  • Editor being used: either SSMS or QA, and the SQL Server service pack version if this differs from that on the server
  N/A for this bug
  • MDAC version
  MDAC 2.8 SP1 on Windows XP SP2
  • The SQL script you entered that caused the problem, and an indication of where the caret was in the script when the problem occurred.
  N/A for this bug.
  • A copy of the SQL Prompt 3 Beta log, which you can access via the SQL Prompt > Log menu option in either editor. You will need to grab this before you exit your editor since the log is recreated at the start of each editor session.
  As it didn't run, cannot supply the log.
  
  
  The program launches succesfully from the Program menu now though.
  
  Adrian

  achamp September 04, 2006 03:42

  - 0 +
• 
  OK thanks gents, sorry this is causing you so many problems.
  
  The tray app isn't actually SQL Prompt, it's a launcher app for launching SQL Prompt in Query Analyzer when the latter is started up. It's not needed at all for SQL Prompt to work in SQL Server Management Studio. As such the only option on its context menu is the Exit option.
  
  As for the CBT_Hook issue we're looking into this as a priority and I hope to be able to give you more information by the end of the week. We're trying to reproduce it here at the moment, thus far unsuccessfully. Would you be willing, if it became necessary, to install a patch version of SQL Prompt 3 that might give us more information back when the error occurs please?
  
  
  Thanks,
  Bart

  Bart Read September 04, 2006 07:20

  - 0 +
• 
  Could you all please let me know if you're able to run SQL Prompt 3 in SQL Server Management Studio regardless of whether or not the SQL Prompt 3 tray app is running? (The tray app is not needed to support SSMS so this shouldn't make any difference.)
  Thanks,
  Bart

  Bart Read September 04, 2006 07:25

  - 0 +
• 
  I can run SQL Prompt 3 in Managment Studio without tray app running.
  
  Adrian

  achamp September 04, 2006 07:48

  - 0 +
• 
  Thanks, that's a relief.

  Bart Read September 04, 2006 13:58

  - 0 +
• 
  I am only running SQL 2000, I cannot run SQL Prompt 3 in the Query Analyzer - that is - Ctrl+Spacebar does not "turn on" SQL Prompt.

  Chris Palmer September 04, 2006 18:55

  - 0 +
• 
  More on this - I re-tried running SQL Prompt from the Program Menu today, this time it loaded a tray icon without complaint. The only difference between today and the previous day is a Windows Update that was installed. However, even though the tray icon is there, double-clicking it does not bring up the SQL Prompt manager, and right-clicking it only offers me an Exit.
  
  Ctrl+spacebar did not initially activate SQL Prompt in Query Analyzer, but when I re-started Query Analyzer then SQL Prompt *did* load.
  
  I don't think its "behaving" very well though, as it only works in one window (the first one loaded) of the Query Analyzer, and it "ignores" the table I am working on when offering me fields to Select. However I guess that should be the topic of another Post.

  Chris Palmer September 04, 2006 19:01

  - 0 +

Add comment

Please sign in to leave a comment.