Microsoft Visual Studio is busy message BIDs IDE Constantly hanging

Question

Post reply

Microsoft Visual Studio is busy message BIDs IDE Constantly hanging

Welsh Corgi

SSC Guru

Points: 116520
More actions
October 31, 2011 at 12:58 pm

#390730

Since later Friday afternoon I have been having issues with the VS IDE constantly hanging on me.
I get the following message:
------------------------------------------------------------------
"Microsoft Visual Studio is busy
Microsoft visual studio is waiting for an internal operation to
complete. If you regularly encounter this delay during normal usage,
please report this problem to Microsoft"
-------------------------------------------------------------------
So far I have not been able to find a fix.
Any help would be greatly appreciated.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 1

Had that happen to me a lot too.

Unfortunately the only thing that "fixes" it is to close and reload the project.

That being said I can't remember if I went down the whole reinstall option.

Bids is up to date service pack wise.

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

Ninja,

Thanks for your feedback.

It is horrible, I never had this happen before.

I have SP2. I read that it appears to be a bug but I did not get anything definitive.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 3

I have seen it happen much more when "My Documents" was not on a local drive but instead of on a network or offline folder. The other times have been in lower memory conditions.

CEWII

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 4

Elliott Whitlow (10/31/2011)
I have seen it happen much more when "My Documents" was not on a local drive but instead of on a network or offline folder. The other times have been in lower memory conditions.
CEWII

Thanks Elliott,

My Documents is on a Network Drive.

I have the issue when I store the SSIS package on a local drive. Does that matter?

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 5

Welsh Corgi (10/31/2011)
Elliott Whitlow (10/31/2011)
I have seen it happen much more when "My Documents" was not on a local drive but instead of on a network or offline folder. The other times have been in lower memory conditions.
CEWII
Thanks Elliott,
My Documents is on a Network Drive.
I have the issue when I store the SSIS package on a local drive. Does that matter?

Well I think both BIDS and SSMS store some data like unsaved files and some other state data in My Documents so I could certainly see it happening. I've seen low memory conditions cause this as well. So both? Probably not going to be able to prevent it.

And yes sometimes a restart will help, but I think that is because memory is cleared.

CEWII

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 6

Thanks again Elliott.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 7

This morning I determined that the problem was the size of the Excel Destination.

It kept growing and when I finally realized what the problem was it was over 86MB.

I started with an empty Workbook with only Column Headers and it resolved the problem.

Go figure.:w00t:

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/