Error when using SSL encryption for SQL server 2000

Hi,
I am having trouble connecting to SQL server 2000 using SSL.
My environment is as follows:
1. Microsoft Certificate server running on a Windows 2000 server machine.
2. SQL Server 2000 running on a Win NT machine with SP6 installed. SQL
Server service pack 3a has been installed.
3. Client machine running Windows XP with SQL Server service pack 3a
installed.
We use a type 4 JDBC secure driver to connect to SQL server from our Java ap
plication running on the client machine.
We also setup the certificate as described in the article 276553 - HOW TO: E
nable SSL Encryption for SQL Server 2000 with Certificate Server.
The installation of the certificate was successful. However, when I tried to
connect to the SQL server using SQL Query Analyzer, I received the followin
g error message.
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Encryption not supported on SQL Serv
er
Thanks,
Chacko.Usually, you receive that error if you enable SSL from the client and the
server doesn't have the certificate.
But, the bad news is you won't be able to use SSL with a type 4 Java driver.
The implementation of protocol encryption requires the driver to access
SSL. In
particular protocol encryption uses SSL APIs implemented in NT. Type 4 JDBC
drivers have a problem in that they are not allowed to directly call system
dlls. There is no library in Java 1.4 or below that emulates the protocol
encryption behavior of SSL from Windows NT.
If your JDBC application requires protocol encryption to SQL 2000,
you will have to use alternate method of encryption such as IPSEC or use a
suitable SSL enabled Type 3 JDBC Driver.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Thanks for your response.
We did generate and install the certificate using the web browser and not us
ing MMC since it is a Win NT 4.0 box. When we look at the certificate on the
database server machine via the IE properties applet, the certificate shows
up fine as described in th
e Microsoft setup document. So, I am not sure where I am going wrong. Is the
re any way to trouble shoot this issue?
Also, we are not even trying the connectivity with the type 4 JDBC driver ye
t even though that is what we want to do ultimately. However, right now we a
re using Query Analyzer on the client machine to test the communication. We
get the error when we try a
nd login to the database via Query Analyzer.
About the type 4 JDBC driver, the documentation from i-net OPTA type 4 JDBC driver says
that it supports SSL for SQL Server 2000. Am I misunderstanding something here? You ca
n find information about i-net OPTA at [url]http://www.inetsoftware.de/English/Produkt[
/url]
e/OPTA/default.htm
Your thoughts are greatly appreciated.
Thanks Kevin.
Chacko.

Error using UnaryOperatorColumn on a Many-to-Many linked dimension

Hi,
i made a small debugging environment for a problem i am getting, it has 2 fact and 2 dimension tables:

FactAccount - fact - (AccountKey,Balance)
DimAccount - dimension - (AccountKey,Code,Name)
BridgeAccountReport - fact - (AccountKey,ReportKey)
DimReport - dimension - (ReportKey,ParentReportKey,Code,Name,UnaryOperator)

the dimension usage is as follows:

for BridgeAccountReport
DimAccount - Regular
DimReport - Regular

for FactAccount
DimAccount - Regular
DimReport - Many-to-Many using BridgeAccountReport as intermediate fact table

DimReport has a self-referencing hierarchy using ParentReportKey.

The idea is to be able to use the same facts recorded at the DimAccount level under different analysis structures recorded in DimReport.

The problem i am getting is that the UnaryOperatorColumn is only having an effect on the inmediate superior level,
but the result on that level is not afterwards used to calculate the aggregations on upper levels.

Here is a sample result:

Net profit 53 (NO typing error!!)
Profit 6
Income 28
Expenses 22 (unary operator set to '-')
Taxes 3

Profit, which is correctly calculated based on unary operator as 6 is not the used as it is to calculate Net Profit which ends up with a value of 53.
Instead the full values of the lower levels seem to be used to calculate it.

To contrast these results i made a similar example, but this time with only:

FactAccount (AccountKey,Balance)
DimAccount (AccountKey,ParentAccountKey,Code,Name,UnaryOperatorColumn)

and i get:

Net profit 9
Profit 6
Income 28
Expenses 22 (unary operator set to '-')
Taxes 3

Correct results.

So, the difference must be somehow related to the indirect relation over the many-to-many link.

Am i forgetting something? Is it a bug in analysis services?

thanks for any hint or comment, af.Hi,
I have encountered the same problem. On the leaf level the unary operator is considered, but on higher level it is ignored.

Have you found any solution or workaround?

Any hint would be helpful ...thx.|||Hi, so i am not crazy :-)
Yours is the first answer i got both from this forum and from the Connect bug report which you can visit here:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=200152

I was also planning to describe this more in detail in a forum dedicated to many-to-many relations but i couldnt find the time so far. The forum is in:
http://www.sqlbi.eu/Forum/tabid/72/forumid/17/scope/threads/Default.aspx

On that site there is also an excellent paper on many-to-many modelling.

Let me know if you find some answer to this problem.

af.

Error using UnaryOperatorColumn on a Many-to-Many linked dimension

Hi,
i made a small debugging environment for a problem i am getting, it has 2 fact and 2 dimension tables:

FactAccount - fact - (AccountKey,Balance)
DimAccount - dimension - (AccountKey,Code,Name)
BridgeAccountReport - fact - (AccountKey,ReportKey)
DimReport - dimension - (ReportKey,ParentReportKey,Code,Name,UnaryOperator)

the dimension usage is as follows:

for BridgeAccountReport
DimAccount - Regular
DimReport - Regular

for FactAccount
DimAccount - Regular
DimReport - Many-to-Many using BridgeAccountReport as intermediate fact table

DimReport has a self-referencing hierarchy using ParentReportKey.

The idea is to be able to use the same facts recorded at the DimAccount level under different analysis structures recorded in DimReport.

The problem i am getting is that the UnaryOperatorColumn is only having an effect on the inmediate superior level,
but the result on that level is not afterwards used to calculate the aggregations on upper levels.

Here is a sample result:

Net profit 53 (NO typing error!!)
Profit 6
Income 28
Expenses 22 (unary operator set to '-')
Taxes 3

Profit, which is correctly calculated based on unary operator as 6 is not the used as it is to calculate Net Profit which ends up with a value of 53.
Instead the full values of the lower levels seem to be used to calculate it.

To contrast these results i made a similar example, but this time with only:

FactAccount (AccountKey,Balance)
DimAccount (AccountKey,ParentAccountKey,Code,Name,UnaryOperatorColumn)

and i get:

Net profit 9
Profit 6
Income 28
Expenses 22 (unary operator set to '-')
Taxes 3

Correct results.

So, the difference must be somehow related to the indirect relation over the many-to-many link.

Am i forgetting something? Is it a bug in analysis services?

thanks for any hint or comment, af.Hi,
I have encountered the same problem. On the leaf level the unary operator is considered, but on higher level it is ignored.

Have you found any solution or workaround?

Any hint would be helpful ...thx.|||Hi, so i am not crazy :-)
Yours is the first answer i got both from this forum and from the Connect bug report which you can visit here:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=200152

I was also planning to describe this more in detail in a forum dedicated to many-to-many relations but i couldnt find the time so far. The forum is in:
http://www.sqlbi.eu/Forum/tabid/72/forumid/17/scope/threads/Default.aspx

On that site there is also an excellent paper on many-to-many modelling.

Let me know if you find some answer to this problem.

af.

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

Error Trying to Deploy Report - SQL Server CTP 2005

I have a report that tests inthe design environment OK.
When trying to deploy I get an error
"a connnection could not be made to the report Server
http://localhost/reportServer"
What causes this? How do I correct this?
I'm logged in with admin priviledges to SQL server;
There are several questions similar to this in the post and on GoogleI'm curious, why is your deployment site 'localhost' (hopefully, this is
localhost on the production server, which means you have vs.net running in
production)?
I have a similar problem, because of the way DNS handles the localhost
translation in our production environment. As a workaround, simply use the
upload functionality on your production server(s) to upload the .RDL (and
then define shared datasources as needed).
Rob
"Sammy" wrote:
> I have a report that tests inthe design environment OK.
> When trying to deploy I get an error
> "a connnection could not be made to the report Server
> http://localhost/reportServer"
> What causes this? How do I correct this?
> I'm logged in with admin priviledges to SQL server;
> There are several questions similar to this in the post and on Google|||It is localhost because I'm testing the functionality of Reporting Server on
a single user machine.
"tutor" wrote:
> I'm curious, why is your deployment site 'localhost' (hopefully, this is
> localhost on the production server, which means you have vs.net running in
> production)?
> I have a similar problem, because of the way DNS handles the localhost
> translation in our production environment. As a workaround, simply use the
> upload functionality on your production server(s) to upload the .RDL (and
> then define shared datasources as needed).
> Rob
> "Sammy" wrote:
> > I have a report that tests inthe design environment OK.
> > When trying to deploy I get an error
> > "a connnection could not be made to the report Server
> > http://localhost/reportServer"
> >
> > What causes this? How do I correct this?
> >
> > I'm logged in with admin priviledges to SQL server;
> >
> > There are several questions similar to this in the post and on Google|||Sammy,
How did you install RS2005? Did you choose the default configuration?
Or did you opt to configure manually?
If the latter, how have you configured Reporting Services?
Have you confirmed that the Reporting Services service is running?
Have you confirmed that the TCP/IP protocol is enabled?
Andrew Watt
MVP - InfoPath
On Tue, 1 Nov 2005 22:22:01 -0800, "Sammy"
<Sammy@.discussions.microsoft.com> wrote:
>I have a report that tests inthe design environment OK.
>When trying to deploy I get an error
>"a connnection could not be made to the report Server
>http://localhost/reportServer"
>What causes this? How do I correct this?
>I'm logged in with admin priviledges to SQL server;
>There are several questions similar to this in the post and on Google|||It turns out it was a configuration problem on my part . I fixed it and it
works fine
"Andrew Watt [MVP - InfoPath]" wrote:
> Sammy,
> How did you install RS2005? Did you choose the default configuration?
> Or did you opt to configure manually?
> If the latter, how have you configured Reporting Services?
> Have you confirmed that the Reporting Services service is running?
> Have you confirmed that the TCP/IP protocol is enabled?
> Andrew Watt
> MVP - InfoPath
> On Tue, 1 Nov 2005 22:22:01 -0800, "Sammy"
> <Sammy@.discussions.microsoft.com> wrote:
> >I have a report that tests inthe design environment OK.
> >When trying to deploy I get an error
> >"a connnection could not be made to the report Server
> >http://localhost/reportServer"
> >
> >What causes this? How do I correct this?
> >
> >I'm logged in with admin priviledges to SQL server;
> >
> >There are several questions similar to this in the post and on Google
>

Error trying to create Maintenance plan

We have a SQL server installation on a managed hosting environment and last night they upgraded our version from standard to enterprise. It looks as if they uninstalled, and then reinstalled. So now I need to re-configure our maintenance plans but when I try right-click on Maintenance Plans and select New Maintenance Plan in Management Studio I get the following error: An OLE DB error 0x800004005 occured while enumerating packages. A SQL statement was issued and failed.

I thought it had something to do with the new installation not running as a particular user/system account and the account it wass running under didnt have the proper permissions. As a smoke test I made the user it's running as (sqlservice) an admin in SQL Server, but that didnt fix the problem

Any help would be appreciated.Have you installed SSIS too in this case if that was also available previouslY?

Error Trapping

I have a linked server setup in a SQL Server 2000 environment that links to
an Oracle database. I then have a Trigger on a SQL Server table, that on
insert, inserts a row of data into the Oracle table via the linked server.
All of this is driven by a front-end application written in VB.NET. I want
the front end to be oblivious to trigger. In other words, if the linked
server loses connection to the Oracle database I don't want the trigger to
execute. I have a "clean-up" stored proc that will insert any rows that
weren't inserted by the trigger. Any ideas on how I can accomplish this? I
am unable to trap the error before it actually occurs. I would like to be
able to somehow check the status of the linked server before executing the
trigger. If it is offline (or errors) then the trigger should not execute
and no errors should be sent to the VB.NET front end. Thanks for any advice
.
Marcocould you not just write a sProc that uses the below and execute it from .ne
t
as follows:
Private Function RunExecRoutines()
Try
cn = New SqlClient.SqlConnection("user id=" & UserName.Text & ";password=" &
Password.Text & ";database=" & Database.Text & ";server=" & Server.Text)
cn.Open()
Catch ex As Exception
sqlCnError = ("Error: Could not establish database connection")
End Try
cmd = New SqlClient.SqlCommand
cmd.Connection = cn
cmd.CommandText = ProcToExec -- whatever sProc you wanna run
cmd.CommandTimeout = 9000
cmd.CommandType = CommandType.StoredProcedure
-- any params you want to pass or receive back...
cmd.Parameters.Add("@.pWho", UNameRoutine)
cmd.Parameters(0).Direction = ParameterDirection.Input
cmd.Parameters.Add("@.pRESULT", SqlDbType.Int)
cmd.Parameters(1).Direction = ParameterDirection.Output
Try
cmd.ExecuteNonQuery()
Catch ex As Exception
sqlCnError = ("Error: Could not execute " + ProcToExec + " stored procedure"
)
MessageBox.Show(sqlCnError, "AppName", MessageBoxButtons.OK, _
MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
End Try
cmd.Dispose()
cn.Close()
cn.Dispose()
end fuction
select srvid, srvstatus, srvname, srvproduct, providername, catalog from
master.dbo.sysservers where srvstatus & 32 <> 0
sp_helptext sp_sqlagent_get_perf_counters -- msdb
sp_helptext sp_enum_oledb_providers -- master
sp_helptext xp_enum_oledb_providers -- master|||Marc,
Thanks for the advice but I am working with a trigger that is executed in
SQL Server. The error occurs in SQL Server and is then reported to the app.
I had thought about the try...catch method but it does me no good since I am
working with a trigger that is idenpendent of .NET. Do you have any other
ideas? I would rather not reengineer my front-end app if at all possible.
Thanks,
Marco
"marcmc" wrote:

> could you not just write a sProc that uses the below and execute it from .
net
> as follows:
> Private Function RunExecRoutines()
> Try
> cn = New SqlClient.SqlConnection("user id=" & UserName.Text & ";password="
&
> Password.Text & ";database=" & Database.Text & ";server=" & Server.Text)
> cn.Open()
> Catch ex As Exception
> sqlCnError = ("Error: Could not establish database connection")
> End Try
> cmd = New SqlClient.SqlCommand
> cmd.Connection = cn
> cmd.CommandText = ProcToExec -- whatever sProc you wanna run
> cmd.CommandTimeout = 9000
> cmd.CommandType = CommandType.StoredProcedure
> -- any params you want to pass or receive back...
> cmd.Parameters.Add("@.pWho", UNameRoutine)
> cmd.Parameters(0).Direction = ParameterDirection.Input
> cmd.Parameters.Add("@.pRESULT", SqlDbType.Int)
> cmd.Parameters(1).Direction = ParameterDirection.Output
> Try
> cmd.ExecuteNonQuery()
> Catch ex As Exception
> sqlCnError = ("Error: Could not execute " + ProcToExec + " stored procedur
e")
> MessageBox.Show(sqlCnError, "AppName", MessageBoxButtons.OK, _
> MessageBoxIcon.Error, MessageBoxDefaultButton.Button1)
> End Try
> cmd.Dispose()
> cn.Close()
> cn.Dispose()
> end fuction
>
> select srvid, srvstatus, srvname, srvproduct, providername, catalog from
> master.dbo.sysservers where srvstatus & 32 <> 0
> sp_helptext sp_sqlagent_get_perf_counters -- msdb
> sp_helptext sp_enum_oledb_providers -- master
> sp_helptext xp_enum_oledb_providers -- master|||would this be any use?
if @.varName <= 0 goto trig_error
trig_error:
raiserror('Allocation Error - Unable to Allocate Zero Quantity',16,-1)|||Marc,
Thanks for the ideas. What I ended up doing was adding a status indicator
field to my table. In the front end I try to connect to the database. If I
cannot connect it sets this indicator field to a 1. If on insert that field
is set to one the Trigger then ignores the inserted row. This will also
allow me to monitor, a bit more closely, any connectivity issues I may have
with the Oracle database. thanks again for your help.
Marco
"marcmc" wrote:

> would this be any use?
> if @.varName <= 0 goto trig_error
> trig_error:
> raiserror('Allocation Error - Unable to Allocate Zero Quantity',16,-1)
>