Comments
10 comments
-
Seems to be identical problem to that of PDinCA -
I to am getting this error upon trying to load SQL Prompt 3 beta. So if anyone comes up with a solution I would love to get notified.
-
Well, I think this wins the award for the most pernicious bug found so far. We're going to be looking into this later this week when our QA guy is back. The problem is going to be reproducing it because we've never seen it... which leads me nicely on to my next question:
Andrew: are you still seeing this? The reason I ask is that unlike everyone else who's experienced it (who all seem to be about 5000 miles away) you're just up the road. Therefore would it be possible for us to come and have a play with your machine please assuming we draw a blank here?
Thanks,
Bart -
I've posted a reply on this over on the other thread headed by PDinCA, I found that the problem "went away" after I installed the latest Microsoft Update - that I found sitting ready to install when I got to work this morning - so it could be just differences in Windows installations that causes some people to get the problem. Note that I installed .NET 2 support just prior to installing SQL Prompt, so the update might have included a change in .NET 2.
-
Interesting. Thanks for letting us know Chris. I'll copy my colleagues on this. I wonder if Stephen (on the other thread) has tried this yet.
Thanks,
Bart -
Any ideas when i fix for this bug will be available, so far it wont do anything.
-
Sorry I'm afraid I can't be specific about that. For now you can use SQL Prompt 3 in SQL Server Management Studio. Chris's information indicates that you should make sure you have all the latest patches from Windows Update installed.
Thanks,
Bart -
This is strange. When I cranked up the same machine that had the problem, after rebooting and having many fewer applications, the damned thing worked perfectly. I'm wondering if the bug is due to an obscure problem with memory or resources. I do all my development work on a slow old machine without much memory specifically to check for performance problems and it happened on this one.
I'll do a bit more fiddling: Uninstall everything. Load up lots of applications and try it again, Uninstall everything. Load it up immediatley after reboot, but my money is on a resource thing -
Bart, Of course you and Lionel are welcome to prod the old workhorse here. I might be able to pin the problem down a bit further in the meantime
-
Thanks Andrew, that might be helpful. We're still trying to reproduce it here but with little success so far.
Cheers,
Bart
Add comment
Please sign in to leave a comment.
On installing...
"Failed to start SQL Prompt. Could not install CBT Hook: System.Runtime.InteropServices.COMException (0xE95B0F01) Exception from HRESULT: 0xE95b0F01 at system.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)"
Windows 2000 with SQL Server 2000 client stuff and .NET Framework 2. No issues with SQL Compare or SQL Data Compare etc etc. Completely patched up with all updates.