error when trying to browse SSRS on a remote machine

Hi,

I deployed SSRS reports to my local report server and set the connection string to access a server on the network with Analysis Server.

Result:
I can access and use the reports from my computer. But when I use any other computer on the network I can't use the reports. I can access them but they don't find the database ant therefor they don't present any data.

Error message as folows: "An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Cannot create a connection to data source 'dsAnalys'. (rsErrorOpeningConnection) Get Online Help
Database 'Analys' does not exist. "

This works fine on my local machine, the error comes only when i try to browse on a remote machine. I am using SQL Server 2005

Any help would be appriciated!!!

Thanks in advance,

Chanduu

Can you access the database from a different PC using SQL Server Management Studio?

Possibly the server is not accessible from those PCs? Is it on a different domain?

|||yes, i am able to access|||

Chandu I am just trying to see what is causing this error.

1.) Do you have Shared Datasource in SSRS.

2.) While deploying to the remote server, make sure to include the right TargetServerUrl.

3.) On the Remote Server, go the Home folder and check for the DataSources if it has

a.) Enable this Data Source CheckBox checked.

b.) Connection string

c.) In the Connect Using: Check if the Credentials stored securely in the report server is Checked and the UserName and Password is given.

4.) Check for the permissions.

Hope this helps...

|||

Thanks a lot !!! friends .. I got answer for this error

Steps i followed to reslove this error

1. Goto http://<report server>/reports

2. Select the datasource folder

3. Check "Credentials stored in that report" and give valid user id and password

4. Check the check box"Use as windows credentials when connecting to datasource"

error when trying to browse SSRS on a remote machine

Hi,

I deployed SSRS reports to my local report server and set the connection string to access a server on the network with Analysis Server.

Result:
I can access and use the reports from my computer. But when I use any other computer on the network I can't use the reports. I can access them but they don't find the database ant therefor they don't present any data.

Error message as folows: "An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Cannot create a connection to data source 'dsAnalys'. (rsErrorOpeningConnection) Get Online Help
Database 'Analys' does not exist. "

This works fine on my local machine, the error comes only when i try to browse on a remote machine. I am using SQL Server 2005

Any help would be appriciated!!!

Thanks in advance,

Chanduu

Can you access the database from a different PC using SQL Server Management Studio?

Possibly the server is not accessible from those PCs? Is it on a different domain?

|||yes, i am able to access|||

Chandu I am just trying to see what is causing this error.

1.) Do you have Shared Datasource in SSRS.

2.) While deploying to the remote server, make sure to include the right TargetServerUrl.

3.) On the Remote Server, go the Home folder and check for the DataSources if it has

a.) Enable this Data Source CheckBox checked.

b.) Connection string

c.) In the Connect Using: Check if the Credentials stored securely in the report server is Checked and the UserName and Password is given.

4.) Check for the permissions.

Hope this helps...

|||

Thanks a lot !!! friends .. I got answer for this error

Steps i followed to reslove this error

1. Goto http://<report server>/reports

2. Select the datasource folder

3. Check "Credentials stored in that report" and give valid user id and password

4. Check the check box"Use as windows credentials when connecting to datasource"

sql

error when trying to browse SSRS on a remote machine

Hi,

I deployed SSRS reports to my local report server and set the connection string to access a server on the network with Analysis Server.

Result:
I can access and use the reports from my computer. But when I use any other computer on the network I can't use the reports. I can access them but they don't find the database ant therefor they don't present any data.

Error message as folows: "An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Cannot create a connection to data source 'dsAnalys'. (rsErrorOpeningConnection) Get Online Help
Database 'Analys' does not exist. "

This works fine on my local machine, the error comes only when i try to browse on a remote machine. I am using SQL Server 2005

Any help would be appriciated!!!

Thanks in advance,

Chanduu

Can you access the database from a different PC using SQL Server Management Studio?

Possibly the server is not accessible from those PCs? Is it on a different domain?

|||yes, i am able to access|||

Chandu I am just trying to see what is causing this error.

1.) Do you have Shared Datasource in SSRS.

2.) While deploying to the remote server, make sure to include the right TargetServerUrl.

3.) On the Remote Server, go the Home folder and check for the DataSources if it has

a.) Enable this Data Source CheckBox checked.

b.) Connection string

c.) In the Connect Using: Check if the Credentials stored securely in the report server is Checked and the UserName and Password is given.

4.) Check for the permissions.

Hope this helps...

|||

Thanks a lot !!! friends .. I got answer for this error

Steps i followed to reslove this error

1. Goto http://<report server>/reports

2. Select the datasource folder

3. Check "Credentials stored in that report" and give valid user id and password

4. Check the check box"Use as windows credentials when connecting to datasource"

Error when transferring data from local database to hosted database

Hi,

I tried to tranfers some database tables from my local SQL Server 2000 database to a hosted database (SQL Server 2005) MSSQL Management Studio 2005. I did the same job successfully before also from my local MSSQL2000 to another hosted MSSQL2005 database. However, this time I encounter the following problem (in red below).

I opened a ticket for support from my service provider but they seemed to have no idea. Therefore, I must seek for help on this forum. Could anyone please give me some advice? Thank you very much in advance.

Regards,
Kenny

Messages
* ERROR : errorCode=-1073548784 description=Executing the query "CREATE TABLE [islandwidecatering.com.sg].[dbo].[Affiliates] (
[AffiliateId] int NOT NULL,
[VendorId] int,
[StartDate] datetime,
[EndDate] datetime,
[CPC] float NOT NULL,
[Clicks] int NOT NULL,
[CPA] float NOT NULL,
[Acquisitions] int NOT NULL
)
" failed with the following error: "Could not allocate space for object 'sys.syscolpars'.'clst' in database 'islandwidecatering.com.sg' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
helpFile= helpContext=0 idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC} (Microsoft.SqlServer.DtsTransferProvider)

It seems there is no available space for the new table. You can try to configure the databse to auto growth, or delete useless data to free space.

Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
Message posted via http://www.droptable.com
The MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.

Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
--
Message posted via http://www.sqlmonster.comThe MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.

Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
Message posted via http://www.droptable.comThe MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.sql

error when attempting to configure a local distributor

i'm getting the following error message when i attempt to configure my server as a local distributor:

TITLE: Connect to Server

Cannot connect to 9A6375C3046246B.

ADDITIONAL INFORMATION:

Failed to connect to server 9A6375C3046246B. (Microsoft.SqlServer.ConnectionInfo)

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

this error is occuring despite the fact that i have the server configured to allow remote connections. can someone please help me troubleshoot this error? thanks.

Try after enabling named pipes by default it is only TCP/IP...

Is it default instance or named instance? if it is named instance try to use portnumber along with server name.

ex: servername\instancename,portnumber

|||

MohammedU wrote:

Try after enabling named pipes by default it is only TCP/IP...

Is it default instance or named instance? if it is named instance try to use portnumber along with server name.

ex: servername\instancename,portnumber

i enabled remote connections to be named pipes only and i'm still getting the same error. i'm using a default instance.|||

check whether the server is Firewall enabled. You need to create exception on port

refer

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

Madhu

|||

Madhu K Nair wrote:

check whether the server is Firewall enabled. You need to create exception on port

refer

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

Madhu

the windows firewall is already disabled. do i still need to create an exception?

|||does anyone from microsoft care to chime in? anyone else?|||

Please check if "select @.@.servername" is returning back you the right ServerName (Boxname)?

If not use

-- sp_dropserver 'incorrect servername','droplogins'--

and

-- sp_addserver 'correctservername','local'--

Even if the select @.@.servername is showing the right servername , Query select srvid from sysservers where srvname=’9A6375C3046246B’

If srvid is not = 0 use sp_dropserver and sp_addserver mentioned above (but this time the incorrect servername will be = correctservername )

Note you need to restart service once for changes to be in effect.

Regards

Rishi Maini

|||

Rishi Maini SQL DBA wrote:

Please check if "select @.@.servername" is returning back you the right ServerName (Boxname)?

If not use

-- sp_dropserver 'incorrect servername','droplogins'--

and

-- sp_addserver 'correctservername','local'--

Even if the select @.@.servername is showing the right servername , Query select srvid from sysservers where srvname=’9A6375C3046246B’

If srvid is not = 0 use sp_dropserver and sp_addserver mentioned above (but this time the incorrect servername will be = correctservername )

Note you need to restart service once for changes to be in effect.

Regards

Rishi Maini

thanks for replying. the correct query is the following:

use msdb

go

select srvid

from sys.sysservers

where srvname = '9A6375C3046246B'

the query result is: 0

any other ideas? anyone else care to chime in?

|||i still need help with this issue.

thanks in advance|||i'm going to keep bumping this thread until i get a response from someone with microsoft.|||

Duane Douglas wrote:

i'm going to keep bumping this thread until i get a response from someone with microsoft.

|||

Are you trying to setup through UI or sp?

Have you tried to use "sp_adddistributor"?

If this is an urgent matter, please contact customer support, this is a forum.

Gary

error when attempting to configure a local distributor

i'm getting the following error message when i attempt to configure my server as a local distributor:

TITLE: Connect to Server

Cannot connect to 9A6375C3046246B.

ADDITIONAL INFORMATION:

Failed to connect to server 9A6375C3046246B. (Microsoft.SqlServer.ConnectionInfo)

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

this error is occuring despite the fact that i have the server configured to allow remote connections. can someone please help me troubleshoot this error? thanks.

Try after enabling named pipes by default it is only TCP/IP...

Is it default instance or named instance? if it is named instance try to use portnumber along with server name.

ex: servername\instancename,portnumber

|||

MohammedU wrote:

Try after enabling named pipes by default it is only TCP/IP...

Is it default instance or named instance? if it is named instance try to use portnumber along with server name.

ex: servername\instancename,portnumber

i enabled remote connections to be named pipes only and i'm still getting the same error. i'm using a default instance.|||

check whether the server is Firewall enabled. You need to create exception on port

refer

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

Madhu

|||

Madhu K Nair wrote:

check whether the server is Firewall enabled. You need to create exception on port

refer

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

Madhu

the windows firewall is already disabled. do i still need to create an exception?

|||does anyone from microsoft care to chime in? anyone else?|||

Please check if "select @.@.servername" is returning back you the right ServerName (Boxname)?

If not use

-- sp_dropserver 'incorrect servername','droplogins'--

and

-- sp_addserver 'correctservername','local'--

Even if the select @.@.servername is showing the right servername , Query select srvid from sysservers where srvname=’9A6375C3046246B’

If srvid is not = 0 use sp_dropserver and sp_addserver mentioned above (but this time the incorrect servername will be = correctservername )

Note you need to restart service once for changes to be in effect.

Regards

Rishi Maini

|||

Rishi Maini SQL DBA wrote:

Please check if "select @.@.servername" is returning back you the right ServerName (Boxname)?

If not use

-- sp_dropserver 'incorrect servername','droplogins'--

and

-- sp_addserver 'correctservername','local'--

Even if the select @.@.servername is showing the right servername , Query select srvid from sysservers where srvname=’9A6375C3046246B’

If srvid is not = 0 use sp_dropserver and sp_addserver mentioned above (but this time the incorrect servername will be = correctservername )

Note you need to restart service once for changes to be in effect.

Regards

Rishi Maini

thanks for replying. the correct query is the following:

use msdb

go

select srvid

from sys.sysservers

where srvname = '9A6375C3046246B'

the query result is: 0

any other ideas? anyone else care to chime in?

|||i still need help with this issue.

thanks in advance|||i'm going to keep bumping this thread until i get a response from someone with microsoft.|||

Duane Douglas wrote:

i'm going to keep bumping this thread until i get a response from someone with microsoft.

|||

Are you trying to setup through UI or sp?

Have you tried to use "sp_adddistributor"?

If this is an urgent matter, please contact customer support, this is a forum.

Gary

error when attempting to configure a local distributor

i'm getting the following error message when i attempt to configure my server as a local distributor:

TITLE: Connect to Server

Cannot connect to 9A6375C3046246B.

ADDITIONAL INFORMATION:

Failed to connect to server 9A6375C3046246B. (Microsoft.SqlServer.ConnectionInfo)

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

this error is occuring despite the fact that i have the server configured to allow remote connections. can someone please help me troubleshoot this error? thanks.

Try after enabling named pipes by default it is only TCP/IP...

Is it default instance or named instance? if it is named instance try to use portnumber along with server name.

ex: servername\instancename,portnumber

|||

MohammedU wrote:

Try after enabling named pipes by default it is only TCP/IP...

Is it default instance or named instance? if it is named instance try to use portnumber along with server name.

ex: servername\instancename,portnumber

i enabled remote connections to be named pipes only and i'm still getting the same error. i'm using a default instance.|||

check whether the server is Firewall enabled. You need to create exception on port

refer

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

Madhu

|||

Madhu K Nair wrote:

check whether the server is Firewall enabled. You need to create exception on port

refer

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

Madhu

the windows firewall is already disabled. do i still need to create an exception?

|||does anyone from microsoft care to chime in? anyone else?|||

Please check if "select @.@.servername" is returning back you the right ServerName (Boxname)?

If not use

-- sp_dropserver 'incorrect servername','droplogins'--

and

-- sp_addserver 'correctservername','local'--

Even if the select @.@.servername is showing the right servername , Query select srvid from sysservers where srvname=’9A6375C3046246B’

If srvid is not = 0 use sp_dropserver and sp_addserver mentioned above (but this time the incorrect servername will be = correctservername )

Note you need to restart service once for changes to be in effect.

Regards

Rishi Maini

|||

Rishi Maini SQL DBA wrote:

Please check if "select @.@.servername" is returning back you the right ServerName (Boxname)?

If not use

-- sp_dropserver 'incorrect servername','droplogins'--

and

-- sp_addserver 'correctservername','local'--

Even if the select @.@.servername is showing the right servername , Query select srvid from sysservers where srvname=’9A6375C3046246B’

If srvid is not = 0 use sp_dropserver and sp_addserver mentioned above (but this time the incorrect servername will be = correctservername )

Note you need to restart service once for changes to be in effect.

Regards

Rishi Maini

thanks for replying. the correct query is the following:

use msdb

go

select srvid

from sys.sysservers

where srvname = '9A6375C3046246B'

the query result is: 0

any other ideas? anyone else care to chime in?

|||i still need help with this issue.

thanks in advance|||i'm going to keep bumping this thread until i get a response from someone with microsoft.|||

Duane Douglas wrote:

i'm going to keep bumping this thread until i get a response from someone with microsoft.

|||

Are you trying to setup through UI or sp?

Have you tried to use "sp_adddistributor"?

If this is an urgent matter, please contact customer support, this is a forum.

Gary

Error trying to design script (Script Component)

Hi everybody:
Maybe somebody around here can help me out with this one.
I applied SQL Server 2005 SP 2 to my local environment (win 2003 server) about two weeks ago week and last week I noticed an error when I tried to edit the script components of some previously created packages.
I am not 100% sure that SP 2 is the cause but that's the only thing that has changed recently.

Well, this is my error:
I click on the "design script" button of any package that was built before patching my sql server and I get an error message telling me that the "Visual Studio for Applications editor cannot be shown" and, of course, Visual Studio won't open.
I've tried creating new test packages with script components and they seem to work fine so this is only happening with older pacakges.

I'm appending below the error message that I get when I click on the technical details button of the error dialog box that I get.

I can see that the something is going on when generating/retriveing the GUID for the script. I tried cutting and pasting the component and that didn't work. If I delete the script component and create a new one, I am able to open VSA and I notice on the project explorer tab of VS that my old ScriptComponent project is there. So, the project explorer shows two projects: one with the default ScriptMain class and one with the previously worked ScriptMain that was never lost. When I close VSA, I get the error dialog box. If I try to design the script again, it won't open.

Well, I hope anybody here has a clue if this is a bug with SP 2 or if there is workaround without having to re-install either SQL server 2005 or VS .NET 2005 to see if the error is gone.

Thanks,
Alonso

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)
at Microsoft.SqlServer.VSAHosting.DesignTime.LoadEngineSource(String engineMoniker, String project)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

===================================

A project with the name 'ScriptComponent_56e278ce61c7453580a57df39d4765bf' already exists.

Program Location:

at Microsoft.Vsa.IVsaEngine.LoadSourceState(IVsaPersistSite site)
at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)

You're not the only one with un-editable script components (here is the thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1) . Quite a few others are experiencing this issue (uneditable script component on SP2 for components created prior to SP2). Now, what's interesting, if I may term it that, is that your local environment is win2k3, whereas I've seen it on XP x86. Personally been in contact with Microsoft for over two weeks trying to get this resolved. If you want to call up PSS as well and send them sample packages, perhaps that would help add more data points to the investigation, and get this resolved.
|||Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.
|||

Alonso Villanueva wrote:

Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.

What operating system are you on?

There is already a hotfix for Vista, if that's your situation.|||This is my local environment configuration:

Visual Studio 2005 Professional Edition SP1
Windows Server 2003 Standard Edition SP1
SQL Server 2005 SP2
Microsoft .NET Framework v2.0.50727

Unfortunately it's not Vista :(

Like I said before. I'll try to have Microsoft PSS contacted today.

Thanks,
Alonso
|||After reading the http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1 thread, I tried opening my Script Component from a Windows 2003 server and I was able to edit it there, but not from my XP workstation. Both have SQL Server SP2 installed.|||

Windows XP, MS SQL Server 2005 SP2. I got this one after clicking 'Design Script...' in Script Transformation. Script Task swallows an error and does nothing at all. Tried to apply all solutions mentioned on this forum, however nothing helped. Could MS Guys eventually fix this?

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Retrieving the COM class factory for component with CLSID {3089D50C-DDAC-4743-9FBF-C15743A32161} failed due to the following error: 800736b1. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaEngine.CreateEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value)
at Microsoft.SqlServer.VSAHosting.DTEngines.Create(String moniker, String language, IDTEngineEvents engineEventsHandler)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

|||

Could this be the issue you are facing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1855810&SiteID=1 ?

Have you installed any .NET update recently?

Thanks,

Bob

|||The solution described there is to install SP2. As I mentioned I already have SP2 installed.|||

I am sorry -- I missed that. I will ask around if anybody has an idea.

Thanks,

Bob

|||

Hi Alonso,

Can you take a look at the scripts in that offending package and make sure there are no 2 script components with that same name (ScriptComponent_56e278ce61c7453580a57df39d4765bf). You can open the .dtsx file in notepad or any other text viewer and search for that text. If that is the case you can either remove one of those script components and re-add it which will generate it with an unique name. Pre SP2 we had some problems with using copy/paste operation on script tasks or script components that will cause problems at run time by generating scripts with the same name for both the source and the destination of the copy/paste operation.

As an workaround you can try doing a copy/paste on the offending component and then remove the source component of the copy/paste operation on a machine with SQL Server SP2 installed. That should change it's name with an unique one but make sure to rebuild the new component by opening it in the designer and closing it.

Let me know if that worked for you.

Thanks,

Silviu Guea [MSFT], SQL Server Integration Services

|||

I'm having the exact same problem as Alonso. I have SQL Server 2005 SP2 installed (in part as an attempt to fix this problem) and I've searched the code to ensure that there are no script components with the same ID (there were no duplicates). I do have two packages in the same project, and I checked the other package to see if it used the same ID (it didn't).

Please Help!

|||

We are having similar issues with the "Design Script" button in a Script Task. We get an error when clicked and it leads to an "Interface not registered" error in the detail text.

So far we have followed a number of dead end fixes (registering DLLs, tracking registry/file activity with regmon and file mon, looking for duplicate entries in the GAC, etc...).

One of our developers is dead in the water until this is resolved.

Anyone else get further?

Halvo

|||

To add more details to my specific problem: the problem also occurs with packages that have been created with both pre SP2 and post SP2 SQL Server 2005. Steps to create the problem are:

1. Create a new package, and create a data flow task

2. Add a new flat file connection manager and flat file source

3. Add Transformation type Script Component

4. Make connection between flat file source and Script Component

5. Edit Script Component node; check a couple of fields to reference as read only fields in the script

6. Click Design Script button. I end up in "Module1", but select the actual ScriptComponent_xxxxxxx ScriptMain from the Project Explorer

7. Save, and exit. A popup appears that says "Cannot show Visual Studio for Applications editor. Additional Information: A project with the name 'ScriptComponent_xxxxxxx' already exists" (same GUID as seen in the project explorer in step 6 - but it already exists because it was created as a result of designing the script! It's not a duplicate)

8. Subsequent attempts to click the Design Script button will now fail with the message:

Cannot show Visual Studio for Applications editor. Additional Information: The operation could not be completed (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.set_Name(String value)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

Incidently, you can create a new Script Task and access the VSA GUI as in step 6 above, but again you can only do this once before the same error occurs.

I really wanted to use the script component for my application but I'm running short on time for my project and will have to use an ugly workaround if I can't solve this soon.

Any help is much appreciated - I'm running out of ideas here!

Scottie

|||

Hi - I'm wondering if this problem has been resolved as I ran into it and have been unable to resolve.

I've tried everything posted on this board - more than once and am still getting the dreaded

error "Cannot Show Visual Studio for Applications Editor"

Running the following...

XP sp2

SQL 2005 Service Pack 2

Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU Service Pack 1 (KB926601)

Thanks

Error trying to design script (Script Component)

Hi everybody:
Maybe somebody around here can help me out with this one.
I applied SQL Server 2005 SP 2 to my local environment (win 2003 server) about two weeks ago week and last week I noticed an error when I tried to edit the script components of some previously created packages.
I am not 100% sure that SP 2 is the cause but that's the only thing that has changed recently.

Well, this is my error:
I click on the "design script" button of any package that was built before patching my sql server and I get an error message telling me that the "Visual Studio for Applications editor cannot be shown" and, of course, Visual Studio won't open.
I've tried creating new test packages with script components and they seem to work fine so this is only happening with older pacakges.

I'm appending below the error message that I get when I click on the technical details button of the error dialog box that I get.

I can see that the something is going on when generating/retriveing the GUID for the script. I tried cutting and pasting the component and that didn't work. If I delete the script component and create a new one, I am able to open VSA and I notice on the project explorer tab of VS that my old ScriptComponent project is there. So, the project explorer shows two projects: one with the default ScriptMain class and one with the previously worked ScriptMain that was never lost. When I close VSA, I get the error dialog box. If I try to design the script again, it won't open.

Well, I hope anybody here has a clue if this is a bug with SP 2 or if there is workaround without having to re-install either SQL server 2005 or VS .NET 2005 to see if the error is gone.

Thanks,
Alonso

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)
at Microsoft.SqlServer.VSAHosting.DesignTime.LoadEngineSource(String engineMoniker, String project)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

===================================

A project with the name 'ScriptComponent_56e278ce61c7453580a57df39d4765bf' already exists.

Program Location:

at Microsoft.Vsa.IVsaEngine.LoadSourceState(IVsaPersistSite site)
at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)

You're not the only one with un-editable script components (here is the thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1) . Quite a few others are experiencing this issue (uneditable script component on SP2 for components created prior to SP2). Now, what's interesting, if I may term it that, is that your local environment is win2k3, whereas I've seen it on XP x86. Personally been in contact with Microsoft for over two weeks trying to get this resolved. If you want to call up PSS as well and send them sample packages, perhaps that would help add more data points to the investigation, and get this resolved.
|||Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.
|||

Alonso Villanueva wrote:

Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.

What operating system are you on?

There is already a hotfix for Vista, if that's your situation.|||This is my local environment configuration:

Visual Studio 2005 Professional Edition SP1
Windows Server 2003 Standard Edition SP1
SQL Server 2005 SP2
Microsoft .NET Framework v2.0.50727

Unfortunately it's not Vista :(

Like I said before. I'll try to have Microsoft PSS contacted today.

Thanks,
Alonso
|||After reading the http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1 thread, I tried opening my Script Component from a Windows 2003 server and I was able to edit it there, but not from my XP workstation. Both have SQL Server SP2 installed.|||

Windows XP, MS SQL Server 2005 SP2. I got this one after clicking 'Design Script...' in Script Transformation. Script Task swallows an error and does nothing at all. Tried to apply all solutions mentioned on this forum, however nothing helped. Could MS Guys eventually fix this?

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Retrieving the COM class factory for component with CLSID {3089D50C-DDAC-4743-9FBF-C15743A32161} failed due to the following error: 800736b1. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaEngine.CreateEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value)
at Microsoft.SqlServer.VSAHosting.DTEngines.Create(String moniker, String language, IDTEngineEvents engineEventsHandler)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

|||

Could this be the issue you are facing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1855810&SiteID=1 ?

Have you installed any .NET update recently?

Thanks,

Bob

|||The solution described there is to install SP2. As I mentioned I already have SP2 installed.|||

I am sorry -- I missed that. I will ask around if anybody has an idea.

Thanks,

Bob

|||

Hi Alonso,

Can you take a look at the scripts in that offending package and make sure there are no 2 script components with that same name (ScriptComponent_56e278ce61c7453580a57df39d4765bf). You can open the .dtsx file in notepad or any other text viewer and search for that text. If that is the case you can either remove one of those script components and re-add it which will generate it with an unique name. Pre SP2 we had some problems with using copy/paste operation on script tasks or script components that will cause problems at run time by generating scripts with the same name for both the source and the destination of the copy/paste operation.

As an workaround you can try doing a copy/paste on the offending component and then remove the source component of the copy/paste operation on a machine with SQL Server SP2 installed. That should change it's name with an unique one but make sure to rebuild the new component by opening it in the designer and closing it.

Let me know if that worked for you.

Thanks,

Silviu Guea [MSFT], SQL Server Integration Services

|||

I'm having the exact same problem as Alonso. I have SQL Server 2005 SP2 installed (in part as an attempt to fix this problem) and I've searched the code to ensure that there are no script components with the same ID (there were no duplicates). I do have two packages in the same project, and I checked the other package to see if it used the same ID (it didn't).

Please Help!

|||

We are having similar issues with the "Design Script" button in a Script Task. We get an error when clicked and it leads to an "Interface not registered" error in the detail text.

So far we have followed a number of dead end fixes (registering DLLs, tracking registry/file activity with regmon and file mon, looking for duplicate entries in the GAC, etc...).

One of our developers is dead in the water until this is resolved.

Anyone else get further?

Halvo

|||

To add more details to my specific problem: the problem also occurs with packages that have been created with both pre SP2 and post SP2 SQL Server 2005. Steps to create the problem are:

1. Create a new package, and create a data flow task

2. Add a new flat file connection manager and flat file source

3. Add Transformation type Script Component

4. Make connection between flat file source and Script Component

5. Edit Script Component node; check a couple of fields to reference as read only fields in the script

6. Click Design Script button. I end up in "Module1", but select the actual ScriptComponent_xxxxxxx ScriptMain from the Project Explorer

7. Save, and exit. A popup appears that says "Cannot show Visual Studio for Applications editor. Additional Information: A project with the name 'ScriptComponent_xxxxxxx' already exists" (same GUID as seen in the project explorer in step 6 - but it already exists because it was created as a result of designing the script! It's not a duplicate)

8. Subsequent attempts to click the Design Script button will now fail with the message:

Cannot show Visual Studio for Applications editor. Additional Information: The operation could not be completed (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.set_Name(String value)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

Incidently, you can create a new Script Task and access the VSA GUI as in step 6 above, but again you can only do this once before the same error occurs.

I really wanted to use the script component for my application but I'm running short on time for my project and will have to use an ugly workaround if I can't solve this soon.

Any help is much appreciated - I'm running out of ideas here!

Scottie

|||

Hi - I'm wondering if this problem has been resolved as I ran into it and have been unable to resolve.

I've tried everything posted on this board - more than once and am still getting the dreaded

error "Cannot Show Visual Studio for Applications Editor"

Running the following...

XP sp2

SQL 2005 Service Pack 2

Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU Service Pack 1 (KB926601)

Thanks

Error trying to design script (Script Component)

Hi everybody:
Maybe somebody around here can help me out with this one.
I applied SQL Server 2005 SP 2 to my local environment (win 2003 server) about two weeks ago week and last week I noticed an error when I tried to edit the script components of some previously created packages.
I am not 100% sure that SP 2 is the cause but that's the only thing that has changed recently.

Well, this is my error:
I click on the "design script" button of any package that was built before patching my sql server and I get an error message telling me that the "Visual Studio for Applications editor cannot be shown" and, of course, Visual Studio won't open.
I've tried creating new test packages with script components and they seem to work fine so this is only happening with older pacakges.

I'm appending below the error message that I get when I click on the technical details button of the error dialog box that I get.

I can see that the something is going on when generating/retriveing the GUID for the script. I tried cutting and pasting the component and that didn't work. If I delete the script component and create a new one, I am able to open VSA and I notice on the project explorer tab of VS that my old ScriptComponent project is there. So, the project explorer shows two projects: one with the default ScriptMain class and one with the previously worked ScriptMain that was never lost. When I close VSA, I get the error dialog box. If I try to design the script again, it won't open.

Well, I hope anybody here has a clue if this is a bug with SP 2 or if there is workaround without having to re-install either SQL server 2005 or VS .NET 2005 to see if the error is gone.

Thanks,
Alonso

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)
at Microsoft.SqlServer.VSAHosting.DesignTime.LoadEngineSource(String engineMoniker, String project)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

===================================

A project with the name 'ScriptComponent_56e278ce61c7453580a57df39d4765bf' already exists.

Program Location:

at Microsoft.Vsa.IVsaEngine.LoadSourceState(IVsaPersistSite site)
at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)

You're not the only one with un-editable script components (here is the thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1) . Quite a few others are experiencing this issue (uneditable script component on SP2 for components created prior to SP2). Now, what's interesting, if I may term it that, is that your local environment is win2k3, whereas I've seen it on XP x86. Personally been in contact with Microsoft for over two weeks trying to get this resolved. If you want to call up PSS as well and send them sample packages, perhaps that would help add more data points to the investigation, and get this resolved.
|||Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.
|||

Alonso Villanueva wrote:

Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.

What operating system are you on?

There is already a hotfix for Vista, if that's your situation.|||This is my local environment configuration:

Visual Studio 2005 Professional Edition SP1
Windows Server 2003 Standard Edition SP1
SQL Server 2005 SP2
Microsoft .NET Framework v2.0.50727

Unfortunately it's not Vista :(

Like I said before. I'll try to have Microsoft PSS contacted today.

Thanks,
Alonso
|||After reading the http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1 thread, I tried opening my Script Component from a Windows 2003 server and I was able to edit it there, but not from my XP workstation. Both have SQL Server SP2 installed.|||

Windows XP, MS SQL Server 2005 SP2. I got this one after clicking 'Design Script...' in Script Transformation. Script Task swallows an error and does nothing at all. Tried to apply all solutions mentioned on this forum, however nothing helped. Could MS Guys eventually fix this?

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Retrieving the COM class factory for component with CLSID {3089D50C-DDAC-4743-9FBF-C15743A32161} failed due to the following error: 800736b1. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaEngine.CreateEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value)
at Microsoft.SqlServer.VSAHosting.DTEngines.Create(String moniker, String language, IDTEngineEvents engineEventsHandler)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

|||

Could this be the issue you are facing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1855810&SiteID=1 ?

Have you installed any .NET update recently?

Thanks,

Bob

|||The solution described there is to install SP2. As I mentioned I already have SP2 installed.|||

I am sorry -- I missed that. I will ask around if anybody has an idea.

Thanks,

Bob

|||

Hi Alonso,

Can you take a look at the scripts in that offending package and make sure there are no 2 script components with that same name (ScriptComponent_56e278ce61c7453580a57df39d4765bf). You can open the .dtsx file in notepad or any other text viewer and search for that text. If that is the case you can either remove one of those script components and re-add it which will generate it with an unique name. Pre SP2 we had some problems with using copy/paste operation on script tasks or script components that will cause problems at run time by generating scripts with the same name for both the source and the destination of the copy/paste operation.

As an workaround you can try doing a copy/paste on the offending component and then remove the source component of the copy/paste operation on a machine with SQL Server SP2 installed. That should change it's name with an unique one but make sure to rebuild the new component by opening it in the designer and closing it.

Let me know if that worked for you.

Thanks,

Silviu Guea [MSFT], SQL Server Integration Services

|||

I'm having the exact same problem as Alonso. I have SQL Server 2005 SP2 installed (in part as an attempt to fix this problem) and I've searched the code to ensure that there are no script components with the same ID (there were no duplicates). I do have two packages in the same project, and I checked the other package to see if it used the same ID (it didn't).

Please Help!

|||

We are having similar issues with the "Design Script" button in a Script Task. We get an error when clicked and it leads to an "Interface not registered" error in the detail text.

So far we have followed a number of dead end fixes (registering DLLs, tracking registry/file activity with regmon and file mon, looking for duplicate entries in the GAC, etc...).

One of our developers is dead in the water until this is resolved.

Anyone else get further?

Halvo

|||

To add more details to my specific problem: the problem also occurs with packages that have been created with both pre SP2 and post SP2 SQL Server 2005. Steps to create the problem are:

1. Create a new package, and create a data flow task

2. Add a new flat file connection manager and flat file source

3. Add Transformation type Script Component

4. Make connection between flat file source and Script Component

5. Edit Script Component node; check a couple of fields to reference as read only fields in the script

6. Click Design Script button. I end up in "Module1", but select the actual ScriptComponent_xxxxxxx ScriptMain from the Project Explorer

7. Save, and exit. A popup appears that says "Cannot show Visual Studio for Applications editor. Additional Information: A project with the name 'ScriptComponent_xxxxxxx' already exists" (same GUID as seen in the project explorer in step 6 - but it already exists because it was created as a result of designing the script! It's not a duplicate)

8. Subsequent attempts to click the Design Script button will now fail with the message:

Cannot show Visual Studio for Applications editor. Additional Information: The operation could not be completed (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.set_Name(String value)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

Incidently, you can create a new Script Task and access the VSA GUI as in step 6 above, but again you can only do this once before the same error occurs.

I really wanted to use the script component for my application but I'm running short on time for my project and will have to use an ugly workaround if I can't solve this soon.

Any help is much appreciated - I'm running out of ideas here!

Scottie

|||

Hi - I'm wondering if this problem has been resolved as I ran into it and have been unable to resolve.

I've tried everything posted on this board - more than once and am still getting the dreaded

error "Cannot Show Visual Studio for Applications Editor"

Running the following...

XP sp2

SQL 2005 Service Pack 2

Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU Service Pack 1 (KB926601)

Thanks

Error trying to design script (Script Component)

Hi everybody:
Maybe somebody around here can help me out with this one.
I applied SQL Server 2005 SP 2 to my local environment (win 2003 server) about two weeks ago week and last week I noticed an error when I tried to edit the script components of some previously created packages.
I am not 100% sure that SP 2 is the cause but that's the only thing that has changed recently.

Well, this is my error:
I click on the "design script" button of any package that was built before patching my sql server and I get an error message telling me that the "Visual Studio for Applications editor cannot be shown" and, of course, Visual Studio won't open.
I've tried creating new test packages with script components and they seem to work fine so this is only happening with older pacakges.

I'm appending below the error message that I get when I click on the technical details button of the error dialog box that I get.

I can see that the something is going on when generating/retriveing the GUID for the script. I tried cutting and pasting the component and that didn't work. If I delete the script component and create a new one, I am able to open VSA and I notice on the project explorer tab of VS that my old ScriptComponent project is there. So, the project explorer shows two projects: one with the default ScriptMain class and one with the previously worked ScriptMain that was never lost. When I close VSA, I get the error dialog box. If I try to design the script again, it won't open.

Well, I hope anybody here has a clue if this is a bug with SP 2 or if there is workaround without having to re-install either SQL server 2005 or VS .NET 2005 to see if the error is gone.

Thanks,
Alonso

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)
at Microsoft.SqlServer.VSAHosting.DesignTime.LoadEngineSource(String engineMoniker, String project)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

===================================

A project with the name 'ScriptComponent_56e278ce61c7453580a57df39d4765bf' already exists.

Program Location:

at Microsoft.Vsa.IVsaEngine.LoadSourceState(IVsaPersistSite site)
at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)

You're not the only one with un-editable script components (here is the thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1) . Quite a few others are experiencing this issue (uneditable script component on SP2 for components created prior to SP2). Now, what's interesting, if I may term it that, is that your local environment is win2k3, whereas I've seen it on XP x86. Personally been in contact with Microsoft for over two weeks trying to get this resolved. If you want to call up PSS as well and send them sample packages, perhaps that would help add more data points to the investigation, and get this resolved.
|||Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.
|||

Alonso Villanueva wrote:

Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.

What operating system are you on?

There is already a hotfix for Vista, if that's your situation.|||This is my local environment configuration:

Visual Studio 2005 Professional Edition SP1
Windows Server 2003 Standard Edition SP1
SQL Server 2005 SP2
Microsoft .NET Framework v2.0.50727

Unfortunately it's not Vista :(

Like I said before. I'll try to have Microsoft PSS contacted today.

Thanks,
Alonso
|||After reading the http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1 thread, I tried opening my Script Component from a Windows 2003 server and I was able to edit it there, but not from my XP workstation. Both have SQL Server SP2 installed.|||

Windows XP, MS SQL Server 2005 SP2. I got this one after clicking 'Design Script...' in Script Transformation. Script Task swallows an error and does nothing at all. Tried to apply all solutions mentioned on this forum, however nothing helped. Could MS Guys eventually fix this?

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Retrieving the COM class factory for component with CLSID {3089D50C-DDAC-4743-9FBF-C15743A32161} failed due to the following error: 800736b1. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaEngine.CreateEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value)
at Microsoft.SqlServer.VSAHosting.DTEngines.Create(String moniker, String language, IDTEngineEvents engineEventsHandler)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

|||

Could this be the issue you are facing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1855810&SiteID=1 ?

Have you installed any .NET update recently?

Thanks,

Bob

|||The solution described there is to install SP2. As I mentioned I already have SP2 installed.|||

I am sorry -- I missed that. I will ask around if anybody has an idea.

Thanks,

Bob

|||

Hi Alonso,

Can you take a look at the scripts in that offending package and make sure there are no 2 script components with that same name (ScriptComponent_56e278ce61c7453580a57df39d4765bf). You can open the .dtsx file in notepad or any other text viewer and search for that text. If that is the case you can either remove one of those script components and re-add it which will generate it with an unique name. Pre SP2 we had some problems with using copy/paste operation on script tasks or script components that will cause problems at run time by generating scripts with the same name for both the source and the destination of the copy/paste operation.

As an workaround you can try doing a copy/paste on the offending component and then remove the source component of the copy/paste operation on a machine with SQL Server SP2 installed. That should change it's name with an unique one but make sure to rebuild the new component by opening it in the designer and closing it.

Let me know if that worked for you.

Thanks,

Silviu Guea [MSFT], SQL Server Integration Services

|||

I'm having the exact same problem as Alonso. I have SQL Server 2005 SP2 installed (in part as an attempt to fix this problem) and I've searched the code to ensure that there are no script components with the same ID (there were no duplicates). I do have two packages in the same project, and I checked the other package to see if it used the same ID (it didn't).

Please Help!

|||

We are having similar issues with the "Design Script" button in a Script Task. We get an error when clicked and it leads to an "Interface not registered" error in the detail text.

So far we have followed a number of dead end fixes (registering DLLs, tracking registry/file activity with regmon and file mon, looking for duplicate entries in the GAC, etc...).

One of our developers is dead in the water until this is resolved.

Anyone else get further?

Halvo

|||

To add more details to my specific problem: the problem also occurs with packages that have been created with both pre SP2 and post SP2 SQL Server 2005. Steps to create the problem are:

1. Create a new package, and create a data flow task

2. Add a new flat file connection manager and flat file source

3. Add Transformation type Script Component

4. Make connection between flat file source and Script Component

5. Edit Script Component node; check a couple of fields to reference as read only fields in the script

6. Click Design Script button. I end up in "Module1", but select the actual ScriptComponent_xxxxxxx ScriptMain from the Project Explorer

7. Save, and exit. A popup appears that says "Cannot show Visual Studio for Applications editor. Additional Information: A project with the name 'ScriptComponent_xxxxxxx' already exists" (same GUID as seen in the project explorer in step 6 - but it already exists because it was created as a result of designing the script! It's not a duplicate)

8. Subsequent attempts to click the Design Script button will now fail with the message:

Cannot show Visual Studio for Applications editor. Additional Information: The operation could not be completed (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.set_Name(String value)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

Incidently, you can create a new Script Task and access the VSA GUI as in step 6 above, but again you can only do this once before the same error occurs.

I really wanted to use the script component for my application but I'm running short on time for my project and will have to use an ugly workaround if I can't solve this soon.

Any help is much appreciated - I'm running out of ideas here!

Scottie

|||

Hi - I'm wondering if this problem has been resolved as I ran into it and have been unable to resolve.

I've tried everything posted on this board - more than once and am still getting the dreaded

error "Cannot Show Visual Studio for Applications Editor"

Running the following...

XP sp2

SQL 2005 Service Pack 2

Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU Service Pack 1 (KB926601)

Thanks

Error trying to design script (Script Component)

Hi everybody:
Maybe somebody around here can help me out with this one.
I applied SQL Server 2005 SP 2 to my local environment (win 2003 server) about two weeks ago week and last week I noticed an error when I tried to edit the script components of some previously created packages.
I am not 100% sure that SP 2 is the cause but that's the only thing that has changed recently.

Well, this is my error:
I click on the "design script" button of any package that was built before patching my sql server and I get an error message telling me that the "Visual Studio for Applications editor cannot be shown" and, of course, Visual Studio won't open.
I've tried creating new test packages with script components and they seem to work fine so this is only happening with older pacakges.

I'm appending below the error message that I get when I click on the technical details button of the error dialog box that I get.

I can see that the something is going on when generating/retriveing the GUID for the script. I tried cutting and pasting the component and that didn't work. If I delete the script component and create a new one, I am able to open VSA and I notice on the project explorer tab of VS that my old ScriptComponent project is there. So, the project explorer shows two projects: one with the default ScriptMain class and one with the previously worked ScriptMain that was never lost. When I close VSA, I get the error dialog box. If I try to design the script again, it won't open.

Well, I hope anybody here has a clue if this is a bug with SP 2 or if there is workaround without having to re-install either SQL server 2005 or VS .NET 2005 to see if the error is gone.

Thanks,
Alonso

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)
at Microsoft.SqlServer.VSAHosting.DesignTime.LoadEngineSource(String engineMoniker, String project)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

===================================

A project with the name 'ScriptComponent_56e278ce61c7453580a57df39d4765bf' already exists.

Program Location:

at Microsoft.Vsa.IVsaEngine.LoadSourceState(IVsaPersistSite site)
at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)

You're not the only one with un-editable script components (here is the thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1) . Quite a few others are experiencing this issue (uneditable script component on SP2 for components created prior to SP2). Now, what's interesting, if I may term it that, is that your local environment is win2k3, whereas I've seen it on XP x86. Personally been in contact with Microsoft for over two weeks trying to get this resolved. If you want to call up PSS as well and send them sample packages, perhaps that would help add more data points to the investigation, and get this resolved.
|||Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.
|||

Alonso Villanueva wrote:

Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.

What operating system are you on?

There is already a hotfix for Vista, if that's your situation.|||This is my local environment configuration:

Visual Studio 2005 Professional Edition SP1
Windows Server 2003 Standard Edition SP1
SQL Server 2005 SP2
Microsoft .NET Framework v2.0.50727

Unfortunately it's not Vista :(

Like I said before. I'll try to have Microsoft PSS contacted today.

Thanks,
Alonso
|||After reading the http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1 thread, I tried opening my Script Component from a Windows 2003 server and I was able to edit it there, but not from my XP workstation. Both have SQL Server SP2 installed.|||

Windows XP, MS SQL Server 2005 SP2. I got this one after clicking 'Design Script...' in Script Transformation. Script Task swallows an error and does nothing at all. Tried to apply all solutions mentioned on this forum, however nothing helped. Could MS Guys eventually fix this?

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Retrieving the COM class factory for component with CLSID {3089D50C-DDAC-4743-9FBF-C15743A32161} failed due to the following error: 800736b1. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaEngine.CreateEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value)
at Microsoft.SqlServer.VSAHosting.DTEngines.Create(String moniker, String language, IDTEngineEvents engineEventsHandler)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

|||

Could this be the issue you are facing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1855810&SiteID=1 ?

Have you installed any .NET update recently?

Thanks,

Bob

|||The solution described there is to install SP2. As I mentioned I already have SP2 installed.|||

I am sorry -- I missed that. I will ask around if anybody has an idea.

Thanks,

Bob

|||

Hi Alonso,

Can you take a look at the scripts in that offending package and make sure there are no 2 script components with that same name (ScriptComponent_56e278ce61c7453580a57df39d4765bf). You can open the .dtsx file in notepad or any other text viewer and search for that text. If that is the case you can either remove one of those script components and re-add it which will generate it with an unique name. Pre SP2 we had some problems with using copy/paste operation on script tasks or script components that will cause problems at run time by generating scripts with the same name for both the source and the destination of the copy/paste operation.

As an workaround you can try doing a copy/paste on the offending component and then remove the source component of the copy/paste operation on a machine with SQL Server SP2 installed. That should change it's name with an unique one but make sure to rebuild the new component by opening it in the designer and closing it.

Let me know if that worked for you.

Thanks,

Silviu Guea [MSFT], SQL Server Integration Services

|||

I'm having the exact same problem as Alonso. I have SQL Server 2005 SP2 installed (in part as an attempt to fix this problem) and I've searched the code to ensure that there are no script components with the same ID (there were no duplicates). I do have two packages in the same project, and I checked the other package to see if it used the same ID (it didn't).

Please Help!

|||

We are having similar issues with the "Design Script" button in a Script Task. We get an error when clicked and it leads to an "Interface not registered" error in the detail text.

So far we have followed a number of dead end fixes (registering DLLs, tracking registry/file activity with regmon and file mon, looking for duplicate entries in the GAC, etc...).

One of our developers is dead in the water until this is resolved.

Anyone else get further?

Halvo

|||

To add more details to my specific problem: the problem also occurs with packages that have been created with both pre SP2 and post SP2 SQL Server 2005. Steps to create the problem are:

1. Create a new package, and create a data flow task

2. Add a new flat file connection manager and flat file source

3. Add Transformation type Script Component

4. Make connection between flat file source and Script Component

5. Edit Script Component node; check a couple of fields to reference as read only fields in the script

6. Click Design Script button. I end up in "Module1", but select the actual ScriptComponent_xxxxxxx ScriptMain from the Project Explorer

7. Save, and exit. A popup appears that says "Cannot show Visual Studio for Applications editor. Additional Information: A project with the name 'ScriptComponent_xxxxxxx' already exists" (same GUID as seen in the project explorer in step 6 - but it already exists because it was created as a result of designing the script! It's not a duplicate)

8. Subsequent attempts to click the Design Script button will now fail with the message:

Cannot show Visual Studio for Applications editor. Additional Information: The operation could not be completed (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.set_Name(String value)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

Incidently, you can create a new Script Task and access the VSA GUI as in step 6 above, but again you can only do this once before the same error occurs.

I really wanted to use the script component for my application but I'm running short on time for my project and will have to use an ugly workaround if I can't solve this soon.

Any help is much appreciated - I'm running out of ideas here!

Scottie

|||

Hi - I'm wondering if this problem has been resolved as I ran into it and have been unable to resolve.

I've tried everything posted on this board - more than once and am still getting the dreaded

error "Cannot Show Visual Studio for Applications Editor"

Running the following...

XP sp2

SQL 2005 Service Pack 2

Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU Service Pack 1 (KB926601)

Thanks

Error trying to design script (Script Component)

Hi everybody:
Maybe somebody around here can help me out with this one.
I applied SQL Server 2005 SP 2 to my local environment (win 2003 server) about two weeks ago week and last week I noticed an error when I tried to edit the script components of some previously created packages.
I am not 100% sure that SP 2 is the cause but that's the only thing that has changed recently.

Well, this is my error:
I click on the "design script" button of any package that was built before patching my sql server and I get an error message telling me that the "Visual Studio for Applications editor cannot be shown" and, of course, Visual Studio won't open.
I've tried creating new test packages with script components and they seem to work fine so this is only happening with older pacakges.

I'm appending below the error message that I get when I click on the technical details button of the error dialog box that I get.

I can see that the something is going on when generating/retriveing the GUID for the script. I tried cutting and pasting the component and that didn't work. If I delete the script component and create a new one, I am able to open VSA and I notice on the project explorer tab of VS that my old ScriptComponent project is there. So, the project explorer shows two projects: one with the default ScriptMain class and one with the previously worked ScriptMain that was never lost. When I close VSA, I get the error dialog box. If I try to design the script again, it won't open.

Well, I hope anybody here has a clue if this is a bug with SP 2 or if there is workaround without having to re-install either SQL server 2005 or VS .NET 2005 to see if the error is gone.

Thanks,
Alonso

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)
at Microsoft.SqlServer.VSAHosting.DesignTime.LoadEngineSource(String engineMoniker, String project)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

===================================

A project with the name 'ScriptComponent_56e278ce61c7453580a57df39d4765bf' already exists.

Program Location:

at Microsoft.Vsa.IVsaEngine.LoadSourceState(IVsaPersistSite site)
at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)

You're not the only one with un-editable script components (here is the thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1) . Quite a few others are experiencing this issue (uneditable script component on SP2 for components created prior to SP2). Now, what's interesting, if I may term it that, is that your local environment is win2k3, whereas I've seen it on XP x86. Personally been in contact with Microsoft for over two weeks trying to get this resolved. If you want to call up PSS as well and send them sample packages, perhaps that would help add more data points to the investigation, and get this resolved.
|||Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.
|||

Alonso Villanueva wrote:

Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.

What operating system are you on?

There is already a hotfix for Vista, if that's your situation.|||This is my local environment configuration:

Visual Studio 2005 Professional Edition SP1
Windows Server 2003 Standard Edition SP1
SQL Server 2005 SP2
Microsoft .NET Framework v2.0.50727

Unfortunately it's not Vista :(

Like I said before. I'll try to have Microsoft PSS contacted today.

Thanks,
Alonso
|||After reading the http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1 thread, I tried opening my Script Component from a Windows 2003 server and I was able to edit it there, but not from my XP workstation. Both have SQL Server SP2 installed.|||

Windows XP, MS SQL Server 2005 SP2. I got this one after clicking 'Design Script...' in Script Transformation. Script Task swallows an error and does nothing at all. Tried to apply all solutions mentioned on this forum, however nothing helped. Could MS Guys eventually fix this?

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Retrieving the COM class factory for component with CLSID {3089D50C-DDAC-4743-9FBF-C15743A32161} failed due to the following error: 800736b1. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaEngine.CreateEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value)
at Microsoft.SqlServer.VSAHosting.DTEngines.Create(String moniker, String language, IDTEngineEvents engineEventsHandler)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

|||

Could this be the issue you are facing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1855810&SiteID=1 ?

Have you installed any .NET update recently?

Thanks,

Bob

|||The solution described there is to install SP2. As I mentioned I already have SP2 installed.|||

I am sorry -- I missed that. I will ask around if anybody has an idea.

Thanks,

Bob

|||

Hi Alonso,

Can you take a look at the scripts in that offending package and make sure there are no 2 script components with that same name (ScriptComponent_56e278ce61c7453580a57df39d4765bf). You can open the .dtsx file in notepad or any other text viewer and search for that text. If that is the case you can either remove one of those script components and re-add it which will generate it with an unique name. Pre SP2 we had some problems with using copy/paste operation on script tasks or script components that will cause problems at run time by generating scripts with the same name for both the source and the destination of the copy/paste operation.

As an workaround you can try doing a copy/paste on the offending component and then remove the source component of the copy/paste operation on a machine with SQL Server SP2 installed. That should change it's name with an unique one but make sure to rebuild the new component by opening it in the designer and closing it.

Let me know if that worked for you.

Thanks,

Silviu Guea [MSFT], SQL Server Integration Services

|||

I'm having the exact same problem as Alonso. I have SQL Server 2005 SP2 installed (in part as an attempt to fix this problem) and I've searched the code to ensure that there are no script components with the same ID (there were no duplicates). I do have two packages in the same project, and I checked the other package to see if it used the same ID (it didn't).

Please Help!

|||

We are having similar issues with the "Design Script" button in a Script Task. We get an error when clicked and it leads to an "Interface not registered" error in the detail text.

So far we have followed a number of dead end fixes (registering DLLs, tracking registry/file activity with regmon and file mon, looking for duplicate entries in the GAC, etc...).

One of our developers is dead in the water until this is resolved.

Anyone else get further?

Halvo

|||

To add more details to my specific problem: the problem also occurs with packages that have been created with both pre SP2 and post SP2 SQL Server 2005. Steps to create the problem are:

1. Create a new package, and create a data flow task

2. Add a new flat file connection manager and flat file source

3. Add Transformation type Script Component

4. Make connection between flat file source and Script Component

5. Edit Script Component node; check a couple of fields to reference as read only fields in the script

6. Click Design Script button. I end up in "Module1", but select the actual ScriptComponent_xxxxxxx ScriptMain from the Project Explorer

7. Save, and exit. A popup appears that says "Cannot show Visual Studio for Applications editor. Additional Information: A project with the name 'ScriptComponent_xxxxxxx' already exists" (same GUID as seen in the project explorer in step 6 - but it already exists because it was created as a result of designing the script! It's not a duplicate)

8. Subsequent attempts to click the Design Script button will now fail with the message:

Cannot show Visual Studio for Applications editor. Additional Information: The operation could not be completed (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.set_Name(String value)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

Incidently, you can create a new Script Task and access the VSA GUI as in step 6 above, but again you can only do this once before the same error occurs.

I really wanted to use the script component for my application but I'm running short on time for my project and will have to use an ugly workaround if I can't solve this soon.

Any help is much appreciated - I'm running out of ideas here!

Scottie

|||

Hi - I'm wondering if this problem has been resolved as I ran into it and have been unable to resolve.

I've tried everything posted on this board - more than once and am still getting the dreaded

error "Cannot Show Visual Studio for Applications Editor"

Running the following...

XP sp2

SQL 2005 Service Pack 2

Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU Service Pack 1 (KB926601)

Thanks

Error trying to design script (Script Component)

Hi everybody:
Maybe somebody around here can help me out with this one.
I applied SQL Server 2005 SP 2 to my local environment (win 2003 server) about two weeks ago week and last week I noticed an error when I tried to edit the script components of some previously created packages.
I am not 100% sure that SP 2 is the cause but that's the only thing that has changed recently.

Well, this is my error:
I click on the "design script" button of any package that was built before patching my sql server and I get an error message telling me that the "Visual Studio for Applications editor cannot be shown" and, of course, Visual Studio won't open.
I've tried creating new test packages with script components and they seem to work fine so this is only happening with older pacakges.

I'm appending below the error message that I get when I click on the technical details button of the error dialog box that I get.

I can see that the something is going on when generating/retriveing the GUID for the script. I tried cutting and pasting the component and that didn't work. If I delete the script component and create a new one, I am able to open VSA and I notice on the project explorer tab of VS that my old ScriptComponent project is there. So, the project explorer shows two projects: one with the default ScriptMain class and one with the previously worked ScriptMain that was never lost. When I close VSA, I get the error dialog box. If I try to design the script again, it won't open.

Well, I hope anybody here has a clue if this is a bug with SP 2 or if there is workaround without having to re-install either SQL server 2005 or VS .NET 2005 to see if the error is gone.

Thanks,
Alonso

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Engine returned Unknown Error (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)
at Microsoft.SqlServer.VSAHosting.DesignTime.LoadEngineSource(String engineMoniker, String project)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

===================================

A project with the name 'ScriptComponent_56e278ce61c7453580a57df39d4765bf' already exists.

Program Location:

at Microsoft.Vsa.IVsaEngine.LoadSourceState(IVsaPersistSite site)
at Microsoft.VisualBasic.Vsa.VsaEngine.LoadSourceState(IVsaPersistSite Site)You're not the only one with un-editable script components (here is the thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1) . Quite a few others are experiencing this issue (uneditable script component on SP2 for components created prior to SP2). Now, what's interesting, if I may term it that, is that your local environment is win2k3, whereas I've seen it on XP x86. Personally been in contact with Microsoft for over two weeks trying to get this resolved. If you want to call up PSS as well and send them sample packages, perhaps that would help add more data points to the investigation, and get this resolved.|||Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.|||

Alonso Villanueva wrote:

Thanks for your reply. I'll try to open a ticket with PSS today.
I'll follow the activity in your thread and give an update if any progress has been made.

What operating system are you on?

There is already a hotfix for Vista, if that's your situation.|||This is my local environment configuration:

Visual Studio 2005 Professional Edition SP1
Windows Server 2003 Standard Edition SP1
SQL Server 2005 SP2
Microsoft .NET Framework v2.0.50727

Unfortunately it's not Vista :(

Like I said before. I'll try to have Microsoft PSS contacted today.

Thanks,
Alonso|||After reading the http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1270413&SiteID=1 thread, I tried opening my Script Component from a Windows 2003 server and I was able to edit it there, but not from my XP workstation. Both have SQL Server SP2 installed.|||

Windows XP, MS SQL Server 2005 SP2. I got this one after clicking 'Design Script...' in Script Transformation. Script Task swallows an error and does nothing at all. Tried to apply all solutions mentioned on this forum, however nothing helped. Could MS Guys eventually fix this?

===================================

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.DataFlowUI.SR&EvtID=CouldNotShowVsaIDE&LinkId=20476

===================================

Retrieving the COM class factory for component with CLSID {3089D50C-DDAC-4743-9FBF-C15743A32161} failed due to the following error: 800736b1. (Microsoft.VisualBasic.Vsa.DT)

Program Location:

at Microsoft.VisualBasic.Vsa.Dt.VsaEngine.CreateEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine()
at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value)
at Microsoft.SqlServer.VSAHosting.DTEngines.Create(String moniker, String language, IDTEngineEvents engineEventsHandler)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

|||

Could this be the issue you are facing: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1855810&SiteID=1 ?

Have you installed any .NET update recently?

Thanks,

Bob

|||The solution described there is to install SP2. As I mentioned I already have SP2 installed.|||

I am sorry -- I missed that. I will ask around if anybody has an idea.

Thanks,

Bob

|||

Hi Alonso,

Can you take a look at the scripts in that offending package and make sure there are no 2 script components with that same name (ScriptComponent_56e278ce61c7453580a57df39d4765bf). You can open the .dtsx file in notepad or any other text viewer and search for that text. If that is the case you can either remove one of those script components and re-add it which will generate it with an unique name. Pre SP2 we had some problems with using copy/paste operation on script tasks or script components that will cause problems at run time by generating scripts with the same name for both the source and the destination of the copy/paste operation.

As an workaround you can try doing a copy/paste on the offending component and then remove the source component of the copy/paste operation on a machine with SQL Server SP2 installed. That should change it's name with an unique one but make sure to rebuild the new component by opening it in the designer and closing it.

Let me know if that worked for you.

Thanks,

Silviu Guea [MSFT], SQL Server Integration Services

|||

I'm having the exact same problem as Alonso. I have SQL Server 2005 SP2 installed (in part as an attempt to fix this problem) and I've searched the code to ensure that there are no script components with the same ID (there were no duplicates). I do have two packages in the same project, and I checked the other package to see if it used the same ID (it didn't).

Please Help!

|||

We are having similar issues with the "Design Script" button in a Script Task. We get an error when clicked and it leads to an "Interface not registered" error in the detail text.

So far we have followed a number of dead end fixes (registering DLLs, tracking registry/file activity with regmon and file mon, looking for duplicate entries in the GAC, etc...).

One of our developers is dead in the water until this is resolved.

Anyone else get further?

Halvo

|||

To add more details to my specific problem: the problem also occurs with packages that have been created with both pre SP2 and post SP2 SQL Server 2005. Steps to create the problem are:

1. Create a new package, and create a data flow task

2. Add a new flat file connection manager and flat file source

3. Add Transformation type Script Component

4. Make connection between flat file source and Script Component

5. Edit Script Component node; check a couple of fields to reference as read only fields in the script

6. Click Design Script button. I end up in "Module1", but select the actual ScriptComponent_xxxxxxx ScriptMain from the Project Explorer

7. Save, and exit. A popup appears that says "Cannot show Visual Studio for Applications editor. Additional Information: A project with the name 'ScriptComponent_xxxxxxx' already exists" (same GUID as seen in the project explorer in step 6 - but it already exists because it was created as a result of designing the script! It's not a duplicate)

8. Subsequent attempts to click the Design Script button will now fail with the message:

Cannot show Visual Studio for Applications editor. Additional Information: The operation could not be completed (Microsoft.VisualBasic.Vsa)

Program Location:

at Microsoft.VisualBasic.Vsa.VsaEngine.set_Name(String value)
at Microsoft.SqlServer.Dts.Pipeline.ScriptDesignTime.CreateDesignTimeEngine(String projectName, Boolean loadSource, ICodeGenerator codeGenerator)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ShowIDE()
at Microsoft.DataTransformationServices.DataFlowUI.ScriptUI.propPage_DesignScript(Object sender, EventArgs args)

Incidently, you can create a new Script Task and access the VSA GUI as in step 6 above, but again you can only do this once before the same error occurs.

I really wanted to use the script component for my application but I'm running short on time for my project and will have to use an ugly workaround if I can't solve this soon.

Any help is much appreciated - I'm running out of ideas here!

Scottie