After installing SP2, the script component editor will not edit script components created in pre SP2 releases. (I also have Visual Studio 2005 SP1 installed). The script TASK editor will start, but when attempting to open a script COMPONENT in the VSA editor, a script component created for pre-SP2 packages, the following error dialog occurs.
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
This same error dialog has occurred on multiple computers, none of them are running Vista (rather Windows XP SP2). All of the pre-existent pre-SP2 script components have Precompile set to true as well, since they are intended for 64 bit machines.
Now, certain posts say, register DLLs in the following directories via:
for %i in (*.dll) do RegSvr32 -s %i.
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa
One problem with these instruction is that the second directory doesn't even exist, however, a directory called "C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\VsaEnv" does exist, which is perhaps what was meant. Even after registering the DLLs there, the script component editor will not open (erroring out after clicking the "Design Script..." button).
Yes I have similar issue. I cant edit my script component. I am getting an following error message when I click on "Design Script".
Cannot Show Visual Studio for Applications Editor. Engine Returned Unknown Error
Anyone else?
Thanks
Sutha
|||I haven’t seen anything like this. From the look of it the VSA is installed properly (you mentioned that you can start designer for the script task but not for the script component). Can you design new script components on that machine?
Thanks
|||New SP2 script components and tasks can be created and edited.Script components created prior to SP2 (at least those created on 2153 and perhaps earlier) cannot be opened, at least on Windows XP. On Windows 2003 Server (32 or 64 bit) I have not observed any issue (the editor open's fine on the same .dtsx that fails to open on an XP machine).|||
I have the exact same issue and here is an interesting addition:
If I add a new script component (without attaching it to anything) and attempt to view the script it actually brings up the script editor with the code of the old script component that I was trying to open in the first place.
I guess I'll have to uninstall SP2 at this point.
Daryl
|||If you're on Vista, try the hotfix:http://support.microsoft.com/default.aspx/kb/931846|||
This uneditable script component problem is specifically noticed on Windows XP and is unsolved and without reasonable workaround(e.g. total replacement of OS with Win2k3).
The Vista script component create/edit issue is indeed solved with that 931846 hotfix (the receipt of which requires a call to Microsoft PSS as it is not regression tested).
|||I can definitely confirm this exact problem after an install of SS2005 SP2a. Exactlyas described. A little confused, the problem says it is with WinXP Pro - which I have -
but patch is for Vista? Anybody install the patch on XP or found another workaround.|||OK, there are 2 different patches for this. One for WinXP, one for Vista - they have
different patching systems. So if you call MS, make sure they know which one you want.
The patch number and KB article are the same. Welcome to Microsoft....|||Are you saying this is resolved? I don't believe it for one second, and I'll happily admit to being wrong. What is the URL, if you would be so kind?|||I'm having the same problem. Where can I find the XP patch?|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
KB928208|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I am working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
http://support.microsoft.com/default.aspx/kb/928208
You have to call MS to get this.
|||After two disconnects without being able to talk to anybody, a 90 minute wait time on the third try, and two more hours trying get this error solved, we got it to work. At least, some sort of temp solution until a KB / hotfix is available.
Keep in mind this is for a Win Server 2k3 environment and not exactly the most recommended solution.
Anyways, this was my fix.
Go to your pacakge code ( right click the package in the solution explorer and select view code ). Search for every "ReferencePath" and pretty much replace
""C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DTSRuntimeWrap\" with "C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.DTSRuntimeWrap\". (the rightmost reference)
Viola! That's it!
For now, I'll only do this for the packages I need to edit.
I hope this helps.
Thanks,
Alonso|||That's what I sent to Microsoft last night ( swap GAC_MSIL to GAC_32 on the reference path) and the 2153 script component starts working. Didn't post that advice on the forum because I wanted to hear back from Microsoft as to whether that was a legitimate solution, indicative of an underlying issue (perhaps with ngen.exe's queue), or both or neither. I understand that its not the most recommended solution, but its the only solution right now.
