ERROR WHEN I TRY TO EDIT A SCRIPT TASK

Today, I must to re-install VS2005 and SQL Server 2005 desktop tools in my computer, because I install SQL Server 2005 SP2 desktop tool for an special features that I need.

This caused that the edition of the Script Task gives to me the following error:

Cannot show the editor for this task

Additional information:

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa.DT)

After the reinstalación, the error continues appearing, and I do not know that to do so that it works fine again.

Can any help me with this?

Thanks.

Alejandro

Are you on Vista?

http://blogs.msdn.com/mattm/archive/2007/03/09/sp2-vista-and-script-tasks.aspx|||No. I′m in XP SP2|||

Take a look at this thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1

sql

Error when creating new connection in DTS Designer

64b SQL2005 EE and all clent tools installed on the same server. Im trying to create a new connection in DTS Designer but after succesful test of the connection it errors out with

The new connection manager couldnt be created. Additional info : Exeption from HRESULT 0xC0010014

Any idea whats the problem here?

This might be caused by a problem described here:

http://support.microsoft.com/kb/913817

|||Im logged in with local admin account. Does that count? Still SSIS is running under Network Servise|||Usually the service does the component enumeration and caches the results, so this is performed without admin rights. You can check if this is an issue by temporary disabling the service, and trying this again (restart BIDS first). If this is caused by permission issue, you'll likely succeed because BIDS will do the component enumeration itself (this harms performance, but avoids Network Service restrictions).

Error upon creation of Integration Services

After I aborted my installation of the tools that come with Katmai, I could not create Integration Services project nor add package to an existing project. I get the following error

Constructor on type 'Microsoft.DataTransformationServices.Wizards.EtlProjectWizardInitializer' not found.

I've removed anything that had the word 'Katmai' in Add/REmove programs. I've also reinstalled the 2005 tools. Still no luck. I'm just wondering if anyone here has encountered this error.
I guess the abort did not rollback completely, but then its just my guess.
Did you try re-installing katmai tools and do a complete un-install after that?.|||Hi sir. I did a complete uninstall of Katmai db and tools. I'll try to reinstall it again, maybe it will help. I just repaired my VS2005Pro installation thinking it can solve the problem but still no luck.
|||

[Microsoft follow-up]

Possible katmai bug here guys.

|||

This sounds like one of the known bugs for Katmai.

If this is the same issue that I'm thinking of, it's because the component which handles our project creation is pointing to the Katmai files.

In the registry, the keys under (CLSID, CurVer):

HKEY_CLASSES_ROOT\Microsoft.SqlServer.Management.UI.WizardManager

Should be the same as:

HKEY_CLASSES_ROOT\Microsoft.SqlServer.Management.UI.WizardManager.9

The values should be:

CLSID = {4503861B-5694-45AE-94DD-BC6541316FB7}

CurVer = Microsoft.SqlServer.Management.UI.WizardManager.9

If CurVer is Microsoft.SqlServer.Management.UI.WizardManager.10, then this is the issue that we've seen.

Note, I can't recommend tweaking the registry by hand... but if uninstalling SQL Server and Visual Studio doesn't fix the issue, this might be an alternative.

It's odd that you're still hitting it after uninstalling everything, but I guess aborting the installation might have left you in a bad state. I know that a number of setup related issues have been resolved since the June CTP, and hopefully the issue that put you into this state was one of them. Make sure that when you reinstall, you have no instances of Visual Studio running.

~Matt

|||Moving to the Katmai SSIS forum.|||

There is a workaround to get the SQL Server 2005 tools working when it is installed with Katmai server.

You need to update this file "<drive>:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\Business Intelligence Projects\DataTransformationsProject.vsz".

Replace the "Microsoft.SqlServer.Management.UI.WizardManager" with "Microsoft.SqlServer.Management.UI.WizardManager.9". Save the change and restart the SQL Server 2005 tools. You should be able to create the new projects.

|||This weekend, I reinstalled both my VS2005Pro and SQL2005Dev as a final brute force solution. I was hoping that this would also erase in the registry the entry key that points to the non-existing or invalid dll. I noticed that even for the supposed "fresh" install, the layout of my IDE did not change and the problem was still there.

Thanks so much for the replies guys. Feng, I will apply your solution.

|||I applied both solutions here. I don't care which one did it but the important thing is my headache is over. Thank you so much again! More power to you guys!

Error upon creation of Integration Services

After I aborted my installation of the tools that come with Katmai, I could not create Integration Services project nor add package to an existing project. I get the following error

Constructor on type 'Microsoft.DataTransformationServices.Wizards.EtlProjectWizardInitializer' not found.

I've removed anything that had the word 'Katmai' in Add/REmove programs. I've also reinstalled the 2005 tools. Still no luck. I'm just wondering if anyone here has encountered this error.
I guess the abort did not rollback completely, but then its just my guess.
Did you try re-installing katmai tools and do a complete un-install after that?.|||Hi sir. I did a complete uninstall of Katmai db and tools. I'll try to reinstall it again, maybe it will help. I just repaired my VS2005Pro installation thinking it can solve the problem but still no luck.
|||

[Microsoft follow-up]

Possible katmai bug here guys.

|||

This sounds like one of the known bugs for Katmai.

If this is the same issue that I'm thinking of, it's because the component which handles our project creation is pointing to the Katmai files.

In the registry, the keys under (CLSID, CurVer):

HKEY_CLASSES_ROOT\Microsoft.SqlServer.Management.UI.WizardManager

Should be the same as:

HKEY_CLASSES_ROOT\Microsoft.SqlServer.Management.UI.WizardManager.9

The values should be:

CLSID = {4503861B-5694-45AE-94DD-BC6541316FB7}

CurVer = Microsoft.SqlServer.Management.UI.WizardManager.9

If CurVer is Microsoft.SqlServer.Management.UI.WizardManager.10, then this is the issue that we've seen.

Note, I can't recommend tweaking the registry by hand... but if uninstalling SQL Server and Visual Studio doesn't fix the issue, this might be an alternative.

It's odd that you're still hitting it after uninstalling everything, but I guess aborting the installation might have left you in a bad state. I know that a number of setup related issues have been resolved since the June CTP, and hopefully the issue that put you into this state was one of them. Make sure that when you reinstall, you have no instances of Visual Studio running.

~Matt

|||Moving to the Katmai SSIS forum.|||

There is a workaround to get the SQL Server 2005 tools working when it is installed with Katmai server.

You need to update this file "<drive>:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\Business Intelligence Projects\DataTransformationsProject.vsz".

Replace the "Microsoft.SqlServer.Management.UI.WizardManager" with "Microsoft.SqlServer.Management.UI.WizardManager.9". Save the change and restart the SQL Server 2005 tools. You should be able to create the new projects.

|||This weekend, I reinstalled both my VS2005Pro and SQL2005Dev as a final brute force solution. I was hoping that this would also erase in the registry the entry key that points to the non-existing or invalid dll. I noticed that even for the supposed "fresh" install, the layout of my IDE did not change and the problem was still there.

Thanks so much for the replies guys. Feng, I will apply your solution.

|||I applied both solutions here. I don't care which one did it but the important thing is my headache is over. Thank you so much again! More power to you guys!

Error to open SQL Profiler

I only Microsoft Clients Tools are installed in this Computer. Try to open
Profiler and Query Analyzer in Windows XP PRO SP2.
I get the following message:
"Program Files\Microsoft Sql Server\80\Tools\Binn\Profiler.exe is not a
valid Win32 application."
"Program Files\Microsoft Sql Server\80\Tools\Binn\isqlw.exe is not a valid
Win32 application."
How do I troubleshoot resolve this issue?
Thanks
Carlos Andrés Lozano G.
Solution Development
Try to reinstall Sql Server Client Tools.
Cristian Lefter, SQL Server MVP
"c@.rlos" <crlos@.discussions.microsoft.com> wrote in message
news:6266E3EB-6128-4E92-B640-E758ED1FB770@.microsoft.com...
>I only Microsoft Clients Tools are installed in this Computer. Try to open
> Profiler and Query Analyzer in Windows XP PRO SP2.
> I get the following message:
> "Program Files\Microsoft Sql Server\80\Tools\Binn\Profiler.exe is not a
> valid Win32 application."
> "Program Files\Microsoft Sql Server\80\Tools\Binn\isqlw.exe is not a valid
> Win32 application."
> How do I troubleshoot resolve this issue?
> --
> Thanks
> Carlos Andrs Lozano G.
> Solution Development
|||I have installed in 3 occasions and the same error leaves.
Will be able to be the computer?
"Cristian Lefter" wrote:

> Try to reinstall Sql Server Client Tools.
> Cristian Lefter, SQL Server MVP
|||c@.rlos wrote:[vbcol=seagreen]
> I have installed in 3 occasions and the same error leaves.
> Will be able to be the computer?
> "Cristian Lefter" wrote:
Try uninstalling the client tools, reinstalling from the SQL Server CD,
and then applying either the SP3a or SP4 (if you're already using SP4)
to the client. Make sure you install using an admin account.
Barring that option, you may have some unrelated corruption on the PC.
You could try reinstalling MDAC from http://www.microsoft.com/data.
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||The installers are found in a unit shared of the Servant. We have done the
installation in a Windows 2000 and functions without problems
"David Gugick" escribió:

> Try uninstalling the client tools, reinstalling from the SQL Server CD,
> and then applying either the SP3a or SP4 (if you're already using SP4)
> to the client. Make sure you install using an admin account.
> Barring that option, you may have some unrelated corruption on the PC.
> You could try reinstalling MDAC from http://www.microsoft.com/data.
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
|||isqlw is not a valid Win32 application
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
|||Are you sure?
"Durga Prasad Datta" wrote:

> isqlw is not a valid Win32 application
> ************************************************** ********************
> Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
> Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
|||Durga Prasad Datta wrote:
> isqlw is not a valid Win32 application
>
It's a valid Windows EXE as far as I know. If you open up the EXE you
can see the ubiquitous "The program cannot be run in DOS mode" message
in the EXE header.
David Gugick
Quest Software
www.imceda.com
www.quest.com