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 / Setup / October 2006

Tip: Looking for answers? Try searching our database.

Visual Studio 2005 hangs when trying to access the toolbox

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Kai - 01 Sep 2006 10:08 GMT
When I am trying to access the toolbox Visual Studio 2005 Professional I get
the message "Initializing toolbox... in the statusbar and the program stops
to respond. To exit Visual Studio I have to kill the process from the task
manager.

I are experiencing the same problem on almost every PC I have installed on.
Operating system is Windows 2000 and the PC's are not connected to the
internet.

Some of the PC's are "fixed" by leaving Visual Studio in it's hung state for
several hours. This seems to be a workaround, but it's not a very good
solution.

Your help is really appreciated.

--
Kai
Gary Chang[MSFT] - 04 Sep 2006 07:45 GMT
Hi Kai,

We experienced a similar case in Windows 2000 machine. By examining its
corresponding dump file, that issue is caused by checking some controls'
certificates. Some machines may have some problems while working through
certificates.

But without the hanging scenario's dump file, we cannot make sure what's
the root cause of your case.

Have you tried to export a different VS setting, you can test it via 'Tools
| Import and Export Settings...' .

By the way, if you have installed any third-party addins to your VS2005 or
any anti-virus/firewall software in your machines, I suggest you
uninstall/disable them for a test.

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Kai - 04 Sep 2006 08:12 GMT
Hi Gary.

> But without the hanging scenario's dump file, we cannot make sure what's
> the root cause of your case.

Where is this dumpfile and what is it called?

Yesterday we started Visual Studio, got the message toolbox initializing,
and Visual Studio went "dead". We left the machine with Visual Studio started
and the message toolbox initializing in the statusbar. Today we may close and
open the toolbox and everything works fine.

--
Kai
Gary Chang[MSFT] - 04 Sep 2006 09:25 GMT
Hi,

>Where is this dumpfile and what is it called?

Since there isn't a crash, the dump file would not be generated
automatically. You may need to start a debug (e.g. windbg) to attach that
VS2005 process while it hangs. But this would be a complicated work.

>Yesterday we started Visual Studio, got the message
>toolbox initializing, and Visual Studio went "dead".
>We left the machine with Visual Studio started and the
>message toolbox initializing in the statusbar. Today we
>may close and open the toolbox and everything works fine.

So the problem just disappears. That's great. It seems to be an environment
specific issue, I am afraid we are unable to repro the scenario in local
environment. If you have any additional information or need further
assistance, feel free to let me know at your earliest convenience.

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Kai - 11 Sep 2006 12:25 GMT
I have installed Visual Studio on another machine running Windows 2000. When
trying to open the toolbox the same error occured. I closed Visual Studio,
removed the network cable and restarted Visual Studio. This time the toolbox
was displayed almost instantly.

I have already turned off Visual Studio's startpage and online help. Is
there a way to make Visual Studio disregard our local network when trying to
open the toolbox without removing the network cable?

--
Kai
Gary Chang[MSFT] - 12 Sep 2006 04:18 GMT
Hi Kai,

Thanks for the update!

>Is there a way to make Visual Studio disregard our local
>network when trying to open the toolbox without removing
>the network cable?

I am afraid the VS2005 doesn't have such option. I suggest you can try to
use some Firewall system to block the VSIDE process on accessing the
internet.

Wish this works!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Graham Shaw - 19 Oct 2006 07:52 GMT
this is caused by visual studio looking for
internet homepage at microsoft the solution is to remove network connections.
Vs will then start, you ca then set tools options start page etc

Rate this thread:







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.