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

Unable to edit script in Visual Studio

Error message when I open a scriptI had Visual Studio running along, and then, one day, I opened a VB script in my SSIS package, and I got the following error: "Cannot show Visual Studio for Applications Editor.  The VSTA designer failed to load: "System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {7525139F-BB6B-447A-A81E-360B2197C3B2} failed due to the following error: 80040154 at Microsoft.SqlServer.VSTAHosting.VSTAScriptingEngine.EnsureDTEObject()"  (Microsoft.SqlServer.VSTAScriptingLib)."

The error is brand new, after I've created dozens of scripts and programmed in them using SSIS.  I've been reviewing a number of sites with those who have experienced similar difficulties, and several have reported that uninstalling and reinstalling Visual Studio does not solve the problem for them.  Some sites offer "FixIt" programs for a .Net Framework or another; and nothing I've tried has worked for me.  I get the sense that solving this should be methodical, and not haphazard.  

I would like some knowledgeable feedback on exactly which .Net Framework is responsible for this; and if I need to do an uninstall and reinstall, I'd like to know if the installs and/or uninstalls needs an ordered sequence.  Finally, I would like to have an inkling for how this happened, where one day it's working and the next not.  Knowing the cause as well as the effect may help me avoid this problem in the future.

Sincerely, ~Peter Ferber
0
PeterFrb
Asked:
PeterFrb
  • 4
  • 2
1 Solution
 
ValentinoVBI ConsultantCommented:
Have you tried doing a repair of SQL Server?  This can be done through the Maintenance page of the Installation Center.

More info: http://msdn.microsoft.com/en-us/library/cc646006.aspx

I've encountered a similar error before, but I'm not sure if it's exactly the same.  And I also don't remember anymore how I finally solved it, but I didn't need to reinstall anything.  Could be though that it needed some DLL manipulation.  But in any case, hopefully the repair proves to be successful!
0
 
PeterFrbAuthor Commented:
I would say the problem is with VS (Visual Studio), not SSMS (SQL Server Management Studio).  SSIS is a VS-related application, not SSMS.  I think now I should have put VS as the first reference of this post.  I'll see if I can get it added there.

~Peter
0
 
PeterFrbAuthor Commented:
Actually, Valentino, I just found a page that indicates you may be right!  See http://support.microsoft.com/kb/955645.  I will try your solution and see what happens!
Many thanks, ~Peter
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
PeterFrbAuthor Commented:
I'm still getting the same error, shown above, when I try to open a script.

I attempted to perform a repair on SQL Server, and the procedure ran with errors: see below.  In spite of these errors while attempting to do a repair, I am able to open the database engine, Analysis Services, Reporting Services, and Integration Services in SSMS.  I've downloaded the output from the log of what the procedure performed.  

Failed SQL Server Repair
I have a question about doing a repair.  I've tracked the error logs -- which, because they are nested, is a tricky business --, and I'm seeing errors of the following nature:

DEBUG: Error 2746:  Transform SP1.1 invalid for package C:\WINDOWS\Installer\324bc.msi. Expected product {754B9915-9E24-4167-9BB1-FF38F8C8D1CF}, found product {AA4A4B2C-0465-3CF8-BA76-27A027D8ACAB}.  

The error above suggests to me that the .Net Frameworks may be colliding and confusing the process of repair; and I need advisement on the question: Do I need to uninstall the .Net Frameworks before doing a repair?  

All the best, ~Peter
0
 
ValentinoVBI ConsultantCommented:
"I would say the problem is with VS (Visual Studio), not SSMS (SQL Server Management Studio).  SSIS is a VS-related application, not SSMS."

Absolutely, but SSIS/BIDS ships with SQL Server and the VSTA environment is also part of that install, hence the SQL repair suggestion.

I'm a bit worried about all those Failed lines in your screenshot.  To be honest, I'm not very convinced that the VSTA problem is the only one.

In any case, whatever you do, DO NOT uninstall a .NET framework because that might mess up way too much.  Other applications might need it as well.  Also, I don't think it's related to .NET in that way.

Have you already tried this: http://www.ssistalk.com/2010/05/28/ssis-2008-cannot-show-visual-studio-2008-tools-for-applications-error/

Also, do you have the latest SPs for both SQL Server (2008 R2?) and Visual Studio 2008 installed?
If you need info on the installation order of SQL, VS and the service packs, have a look here: http://blog.hoegaerden.be/2012/03/13/sql-vs-sps-installation-order/

Hopefully you can get your issue resolved without needing to do a full reinstall!
0
 
PeterFrbAuthor Commented:
Valentino, thank you.  To be honest, I haven't actually solved this problem yet, but I don't have to do so to pursue my current work effort.  I am going to get some professional help on this, as I don't want inadvertently to make things worse while trying to make them better.  I will forward the information you've given me to the support for which I will pay.  The situation qualifies as a "Discretion is the better part of valor" moment.

Best, ~Peter Ferber
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

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