Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / May 2005

Tip: Looking for answers? Try searching our database.

System.InvalidOperationException: The object is currently in use elsewhere.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
news.microsoft.com - 05 May 2005 19:01 GMT
I have seen this problem posted repeatedly, but I have never seen the
question answered.

When I start VS.NET 2003 I get this error message:

System.InvalidOperationException: The object is currently in use elsewhere.
  at System.Drawing.Graphics.Dispose(Boolean disposing)
  at System.Drawing.Graphics.Dispose()
  at System.Drawing.Font.ToLogFont(Object logFont)
  at System.Drawing.Font.ToHfont()
  at System.Windows.Forms.FontHandleWrapper..ctor(Font font)
  at System.Windows.Forms.Control.get_FontHandle()
  at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
  at
System.Windows.Forms.PropertyGridInternal.GridToolTip.OnHandleCreated(EventArgs
e)
  at System.Windows.Forms.Control.WmCreate(Message& m)
  at System.Windows.Forms.Control.WndProc(Message& m)
  at System.Windows.Forms.PropertyGridInternal.GridToolTip.WndProc(Message&
msg)
  at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
  at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
  at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

The error does NOT show up if I close the Properties pane and start up
VS.NET. Another way I see the error if I go to Tools > Options > Windows
Forms Designer.

I am running VS.NET 2003 on Windows 2003 with all the latest updates on a
ProLiant ML370 G2. I have done everything I can think of: upgraded the
driver, found a work around to install the Dotnet Framework, run FileMon,
run RegMon, and reinstalled VS.NET 2003 a few time. The last thing to do is
reinstall Windows 2003.

Any useful advice?

Thanks,

Scott
news.microsoft.com - 08 May 2005 22:54 GMT
I have it (almost) fixed. I hacked at the registry and took out references
to "SharePoint", "Office", and some other misc keys. Obviously this is not
the recommended way to go. VS.NET wouldn't start after that. Then I ran
Registry Mechanic for Windows and everything works now accept now my system
is using Wingdings font for Dialog Titles.

The live lesson is to simply rebuild the OS. After all it is a development
server. A better lesson is to use Virtual Server.

Scott

> I have seen this problem posted repeatedly, but I have never seen the
> question answered.
[quoted text clipped - 38 lines]
>
> Scott

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.