• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3073
  • Last Modified:

Microsoft Visual Studio is busy

I've done a lot of surfing on this, I'm at v2008 SR2, all the latest sp's, I cannot figure out what is causing this.

A very simple SSIS dtsx package, just a data flow task, ole db data source, csv flat file output, it reads from a view.  That's it.  I have been beating the heck out of it for a week, generated 100's of files successfully, and now suddenly it won't work.

I go into BIDS, open the package, in the bottom right it says 'Validating packagename', the cursor is an arrow with two ends, i cannot touch anything.  I cannot close BIDS normally, I have to terminate the exe via task manager, then i open it again.  I open the project, immediately get the '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."

I even tried creating a new project, new dtsx, it does the same thing.

I MUST get these files completed like yesterday.

Does anybody have any clue on how to get around this?
0
dbaSQL
Asked:
dbaSQL
  • 3
  • 2
1 Solution
 
Jim P.Commented:
Have you restarted the SQL Services lately? Or the server?

Have you looked at the activity monitor and seen if anything is blocking?

What kind of configuration -- Server, memory, server versions, SQL versions?

0
 
dbaSQLAuthor Commented:
Yes, the service has been restarted.  Nothing is blocking anything.

SQL v2008 R2, 24G ram, Windows Srv 2008 R2 Enterprise, 64bit
0
 
dbaSQLAuthor Commented:
I honestly don't know what the problem was, but I created the package on another instance successfully, and it is running.  The package is still unusable on the other instance, VS is busy, and I can't get any further than that.

but, it's running on another instance, so I'll just leave it at that.

thank you for looking this way, jimpen.
0
 
Jim P.Commented:
I've had it happen to me when I've loaded SQL on a workstation, had large databases to test and the SQL Agent was doing its stuff. I would take a quick look at the disk(s) and the disk channel on that instance.
0
 
dbaSQLAuthor Commented:
It's working on another instance, no reason to keep this open.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now