VS2010 VB.Net Macro IDE Crashes VS
-
Tuesday, August 31, 2010 10:45 PM
VS2010 VB.Net
When I try to access the Macro IDE or open MyMacros I get the error: Vsaenv: Cannot find one or more components. Please reinstall the application. I have reinstalled (rebuild in place) VS2010 Pro - didn't help.
After the error the IDE goes away for a while and sometimes crashes and sometimes it returns to the code IDE. If I try again as often as not VS crashes hard. On reload it looks like it is going through rebuilding settings.
I've searched around and haven't found a similar problem /solution. Ideas?
All Replies
-
Thursday, September 02, 2010 1:38 AMI am having the exact same issue after installing Visual Studio Ultimate 2010 on a clean machine. I did read something that there is not a new Macro IDE with 2010, which would seem to indicate a requirement to also have Visual Studio 2008 installed. I'm going to try that out (since I need it anyway). I'll report back if that is the resolution.
-
Thursday, September 02, 2010 1:53 PMModerator
Hi, Bob
Please try uninstalling the VS2010, and installing it again to see whether this could resolve your issue, the exception may be caused by some components missing.
The location for the Macro IDE is in
C:\Program Files\Common Files\microsoft shared\VSA\9.0\VsaEnv\
You could try to use Process Monitor to monitor the Process when you start your Macro IDE.
If this still does not help to resolve the odd issue, please try to use some dump tools to get the dump file. And submit the dump file to connect.microsoft.com
For how to get the dump file, please see this link and note the reply from YiChun Chen.
http://social.msdn.microsoft.com/Forums/en/vssetup/thread/196ee627-b180-4e9c-a28e-81625d0c5cae
Hope this helps.
Thanks
Chao
Please unmark it if it does not help, and mark it if it helps. -
Thursday, September 02, 2010 3:17 PM
I had initially tried a repair of VS 2010 Ultimate, and that did not correct the problem. The solution that worked for me was to install Visual Studio 2008 + SP1 and other VS hotfixes. Everything works fine now.
-
Thursday, September 02, 2010 7:26 PM
Uninstall/reinstall is easy to say but takes hours...
C:\Program Files\Common Files\microsoft shared\VSA\9.0\VsaEnv\ has files in it and if I try to run the .exe it reports the components missing message same as from the VS2010 IDE.
If I try and run REGSVR32 on msdis170.dll and it complains that then entry-point DllRegisterServer was not found and that it is not a valid dll
Is there a way for you determine what the dependences are? Does the macro IDE work for you an a PC that does not have VS2008 as mentioned in the other posts?
I think it was working when I had the beta installed bujt it stopped working after I installed the release version.
-
Thursday, September 02, 2010 9:28 PMHey Bob, may ask what OS you are running?
-
Thursday, September 02, 2010 11:25 PMVista Business 32bit
-
Saturday, September 04, 2010 2:57 PM
I'm having the exact same problem with Windows 7 Ultimate, running Visual Studio 2010 Premium. When trying to view the list of Macros that I have, I get the error:
Vsaenv
Cannot find one or more components. Please reinstall the application.
When I click 'OK', Visual Studio freezes for a while, then I get this error:
Cannot load the recording macro project 'MyMacros' for the following reason:
Server execution failed
Would you like to create it?
Selecting either 'Yes' or 'No' to this error message doesn't do anything.
I'll try uninstalling and installing Visual Studio, but like others have said, this is quite a time consuming process, so it'll have to wait for another day.
If anyone has any other suggestions, it would be very helpful.
Thanks,
Johnny
-
Sunday, September 05, 2010 5:07 AM
A quick follow up on this. I uninstalled and reinstalled Visual Studio, but I'm getting the same error. I also copied over all the files in
C:\Program Files\Common Files\microsoft shared\VSA\9.0\VsaEnv\
from another computer (with a proper working Visual Studio), but it still didn't fix the macro issue.
Johnny
-
Thursday, September 09, 2010 2:38 AM
Johnnyo5,
I saw exactly the symptoms you described above (and selecting 'Yes' from the error message box crashed the IDE).
To fix this isse, run VS 2010 setup again and select ‘Add/Remove features’. On the next screen, make sure the checkbox for the ‘Visual Basic’ feature is checked - if it is unchecked then check it and proceed with setup to install missing VB. After setup is finished, just launch VS (no system reboot is required). This fixed this issue for me (VB wasn't originally installed with VS 2010 on my machine).
Zopuh
- Proposed As Answer by mkmurray Tuesday, November 01, 2011 10:13 PM
-
Thursday, September 09, 2010 10:18 PM
I was banging my head against this for a week. I found a solution in Microsoft's documentation:
http://download.microsoft.com/download/8/C/E/8CE18AE7-CAA8-4A4C-87CF-0C3DF772322D/VS2010RTM.htm
Check out section 2.1.7. Worked for the developer I was supporting when nothing else did. Not sure what exactly caused the problem, but by following the procedure outlined in the document, the update action forced an installation of the macros IDE.
Good luck!
- Marked As Answer by Chao KuoModerator Friday, September 10, 2010 8:32 AM
- Unmarked As Answer by Bob Heitzman Wednesday, February 16, 2011 10:17 PM
- Proposed As Answer by Shawn Eary Friday, April 15, 2011 2:04 AM
-
Friday, September 10, 2010 3:58 AMThanks Matt. That worked like a charm.
-
Monday, September 27, 2010 10:09 PM
Hello,
I tried exactly what's written in http://download.microsoft.com/download/8/C/E/8CE18AE7-CAA8-4A4C-87CF-0C3DF772322D/VS2010RTM.htm but unfortunately it did not work for me.
I'm running Windows XP SP-3 with all latest updates. I have VS 2003 still installed (for legacy purpose), I also installed VS-2008 Standard edition and, in order to take less space, uninstalled it and then MS-installed VS2010 Professional upgrade edition. MS-SQL Server 2008 Express was being installed at the same time as VS 2010 was installed.
Does anybody have an idea on this problem?
Regards,
Pierre, Montreal
-
Sunday, February 06, 2011 8:11 PM
I followed the workaround on this page:
And it fixed the problem. Remember to delete the VSDesignerUI file out of the visual studio 9.0 folder (even though vs2010 is 10.0)
-
Monday, February 14, 2011 7:12 PM
Orion, that link doesn't work for me. Just wondering if its working for you or if you can point me to another spot.
Thanks
-
Monday, February 14, 2011 7:13 PM
Matt,
That link isn't working for me. Is it working for you still?
Thanks,
Mike
-
Wednesday, February 16, 2011 10:24 PM
Matt's suggested link didn't work for me - VS still crashes.
I can open the Macro explorer but as soon as I try to open MyMacros I get the error "Cannot find one or more comonents. Please reinstall the application."
I suspect I would have to wipe my disk and reinstall Vista AND VS to get this to work. I give up.
-
Friday, April 15, 2011 2:04 AM
I was banging my head against this for a week. I found a solution in Microsoft's documentation:
http://download.microsoft.com/download/8/C/E/8CE18AE7-CAA8-4A4C-87CF-0C3DF772322D/VS2010RTM.htm
Check out section 2.1.7.
I don’t know what I did to VS2010, but at some undetermined time I messed the VS2010 Macro Editor up[1]. Every time I tried to open one of my macros, I was getting a “Error Loading Type Library/DLL” error. So I uninstalled “Microsoft Visual Studio Macro Tools” and tried again hoping VS2010 would be smart enough to reinstall the Macro Tools for me; unfortunately, VS2010 didn’t offer to do such. Instead I got the error that Mr. Heitzman mentions, so I tried repairing VS2010 and but still got the annoying error mentioned in this thread (If I remember correctly).
Finally, I stumbled across this thread and the idea first suggested by Mr. Pollard that appears on paragraph 2.1.6 of the RTM documentation. Much to my happiness, changing the components of VS2010 caused it to go into the “update state” and reinstall the “Microsoft Visual Studio Macro Tools” and solve my issue.
Kudos to Mr. Pollard!!!
[1] – We all know that VS2010 uses elements of VS2008 for macro development.
-
Friday, May 27, 2011 8:32 AMWorked for me too Matt. Thanks, I was searching high and low!
-
Tuesday, June 14, 2011 1:03 AMThank you Matt, your advice worked perfectly. You are a life saver.
- Proposed As Answer by Eric Ouellet Thursday, December 08, 2011 4:19 PM
- Unproposed As Answer by Eric Ouellet Thursday, December 08, 2011 4:19 PM
-
Thursday, December 08, 2011 4:21 PM
For VS 2010 SP1. The proposed solution work fine for me only and only if I unsintall the Visual Studio Macro package first (just under Visual Studio uninstall line in "Programs and Features" list)
Eric Ouellet -
Monday, March 26, 2012 7:40 PM
Matt's 2.1.7 solution worked for me
This probably happened when I [foolishly] un-installed Visual Studio 2008 within the last few weeks.
Wayne Erfling (aka Cornan The Iowan)

