October 1, 2007 at 6:56 am
I had several queries that I ran with Management Studio over the weekend die with the error message below. I've never seen this message before, does anyone know what causes is and/or how to prevent?
Thanks,
Jason
-----------------------
An error occurred while executing batch. Error message is: Error creating window handle.
The Redneck DBA
October 1, 2007 at 2:31 pm
that is definitely a client-side issue.
* Noel
October 1, 2007 at 3:07 pm
The more I think about it, the more I was coming to that conclusion also. I'm just not sure what to do about it, or is it just a fluke that I should ignore and not worry about?
The Redneck DBA
October 1, 2007 at 4:09 pm
Handles are Windows tools to manage limitted OS resources like bitmaps, brushes, Fonts, etc... It does happes that Handles are a limmited pool also and when you load many apps on your pc and one of them either have memory leaks of mis handle the handles 😀 you can run out of them. If this was on your local workstation a good old reboot will take you back to normal operating conditions. If you are a hard die guy and really want to know whos the responsible program in Task Manager and Display "Handle Count" 😉
Cheers,
* Noel
October 1, 2007 at 9:03 pm
I agree with Noeld that you should try a reboot and see what happens. Maybe shut down some processes and windows on your system. If it happens again, I'd run it from another client before worrying.
April 23, 2009 at 6:04 pm
yes, I have in fact, I am trying to resolve this. go to run >> dcomcnfg >> Look in your event viewer .
see dcom error 10010. I get this error running procedure from server1 calling procedure on server2. AFter almost an hour. It will give me this error. Then client ssms will dissappear. I believe it is a client issue on sql server 2008.
The server {7E477741-01A6-4C06-9DAC-55F6174C08A3} did not register with DCOM within the required timeout.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
this is a client side issue.
October 29, 2010 at 12:40 am
Large resultsets + query output to grid may end up to this error. Try setting output to text.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply