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

Visual Studio or Windows Server conflict

We have Visual Studio 2008, version 9.0.30729.4462 QFE installed on serveral
Windows Server 2008R2, Enterprise servers.  .NET Framework version 3.5 SP1

We have numerous SSIS packages on these boxes, all have been working beautifully for a year+.  As of Friday of last week, any attempt to open a package within Visual Studio fails with this message:

Microsoft Visual Studio is  unable to load this document:
Retrieving the COM class factory for component with CLSID {AA40D1D6-CAEF-4A56-B9BB-D0D3DC97SBA2} failed due to the following error: 8007007e.

The packages are running fine, it's just that they cannot be opened (or edited).
I am not sure which direction to go with this.  

Any tips?
0
dbaSQL
Asked:
dbaSQL
  • 4
  • 2
1 Solution
 
DcpKingCommented:
It sounds like you have some damage to one or more of the files needed to run VS. Does this happen on every single server, or have you got only one VS installation? If the latter, back up all your package sources, remove VS, and install it again.

BTW, why are you developing on your server machines?

hth

Mike
0
 
dbaSQLAuthor Commented:
Even further, I cannot open the SQL Server Configuration Mgr anymore on one of the servers that is having this problem.  Attempting to do so, fails with this:


MMC could not create the snap-in.  The snap-in might not have been installed correctly.
Name: SQL Server Configuration Manager
CLSID:  {D52E5F54-75D9-4A93-2215EA5CBED2}


I copy the icons to the task bar for all of my SQL - related components, and use this to open the apps, as needed.  Have been doing this forever.  Attempting to open the config mg fails with the above error.

Any ideas?
0
 
dbaSQLAuthor Commented:
I removed the previous icon and created a new one via MMC/Add-remove snap-in.  That works now, but I still can't get into the SSIS pkgs without the COM error posted above.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
dbaSQLAuthor Commented:
It happened once last Friday.  Yesterday it happened a few times.   Today it is happening on every attempt to open any package.  It's just one server.  The same attempt to open the package remotely, from another server, works without the COM error.
0
 
DcpKingCommented:
Your last post reinforces my suspicion that you have something (software) broken on your server.

Your packages are all under something like Users\username\My Documents\VS2010\Projects\ with each in its own folder below Projects. Take a copy of one of these folders and copy it to a machine with a working SSIS, park it in the same (relative) place, and open the .sln file. You will probably have to fix a few links but it should open ok. Doing that demonstrates that the problem is with the VS installation on the server.

As I said before, why are you developing on your server machine? You should develop either on the desktop or on a virtualised desktop and then deploy to the server. After successful deployment, shift a backup copy of the (now deployed) solution to the server and also back it up off the machine.

hth

Mike
0
 
dbaSQLAuthor Commented:
The problem is still unresolved.  I will work on the removal, and reinstallation.  Thank you for you input.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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