execute remote stored procedure failed

I have set up a linked server to Sybase. I can run
distributed queries, but I'm trying to execute a stored
procedure on the remote server and I receive the
following message:
Error 7212: Could not execute procedure on remote server.
Any ideas as to what I'm doing wrong?
Thanks,
MTMT
Perhaps you want to look into permission issues
"MT" <anonymous@.discussions.microsoft.com> wrote in message
news:0d4b01c39e26$7ddf7c10$a301280a@.phx.gbl...
> I have set up a linked server to Sybase. I can run
> distributed queries, but I'm trying to execute a stored
> procedure on the remote server and I receive the
> following message:
> Error 7212: Could not execute procedure on remote server.
> Any ideas as to what I'm doing wrong?
> Thanks,
> MT
>
>
>|||Was there ever a satisfactory solution to this? I am having very similar problems when using a Sybase OLE DB linked server. No such problems when using an ODBC link
-- MT wrote: --
I have set up a linked server to Sybase. I can run
distributed queries, but I'm trying to execute a stored
procedure on the remote server and I receive the
following message
Error 7212: Could not execute procedure on remote server
Any ideas as to what I'm doing wrong
Thanks
M

Execute Package Task says Login failed for 'sa'

Please help me with this error, I am desperate.

SSIS package "Clear.dtsx" starting.
Error: 0xC0202009 at Clear, Connection manager "10.11.60.30.msdb.sa": An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'sa'.".
Error: 0xC00220E4 at Execute Package Task: Error 0xC0202009 while preparing to load the package. An OLE DB error has occurred. Error code: 0x%1!8.8X!.
.
Task failed: Execute Package Task
Warning: 0x80019002 at Clear: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "Clear.dtsx" finished: Failure.
Did you run this package in BIDS or the command line? As we're talking about in your other similar post, SSIS doesn't store passwords when promoting them to the server for execution. Either that, or you have the wrong password indicated for "sa."|||Child package is using different username so error should not be for 'sa'. Parent is using sa in Connection which is used to call this child package.|||

Hi Fahad,

If you are absolutely certain the sa password is supplied correctly, the issue may lie with the Package ProtectionLevel property.

First, I would ensure the sa password is correct. Make sure you can connect to the msdb database on the target server using the sa account credentials and that you can execute some simple query: Select 1 As 'One' or Select GetDate() are my favorites. If this succeeds:

Try setting the ProtectionLevel property on the Control Flow properties to either EncryptAllWithPassword or EncryptSensitiveWithPassword. You will need to supply a PackagePassword for this test as well - it's located just above the ProtecionLevel property.
When you're done, rebuild and re-deploy the package. You will need to supply the password when executing the package. If this succeeds, the issue is with the Package ProtectionLevel.

To address this, I recommend using Windows Authentication to connect to the server.

Hope this helps,
Andy

Execute Package Task Failed when deployed to server..

Hi,

I have a package that contains an Execute Package Task... it works fine when on my local machine and on our test-server.
After deploying the SSIS solution to our customers server, I open the project in Visual Studio and run the mainPackage in debug mode and the Task fails when trying to execute the package.. if I remove everything in the childpackage it still fails... the path to the package is correct and I know that I have rigths to execut it. I do not use any package security/encryption..
If i create a new package in the project and create a new fileconnection to it the Execute Package Task executes correctly, with the exact same content as the original package...

So my guess is that something in the FileConnetion object is set wrong, but i cannot understand what it is. The errormessage i get is something like this. "Execute Package Failed. Could not execute package".

Anyone had the same problem as I? I′m grateful for any help!

/erik

Hi Erik,

This could be the package ProtectionLevel property. You can check if this is the problem by setting it to EncryptSensitiveWithPassword and then supplying a password. You will need to pass the password in using the /Decrypt switch in DTExec or by setting it in an SSIS job step definition.

Hope this helps,
Andy

|||Sticky|||I still do not know what caused the problem. I "solved" it by creating a new package with the exact same content. I tried to do as Andy suggested but it dit not help...|||

Hi Erik,

Thanks for the feedback - glad you got it working.

Andy

Execute Package Task error: Failed to decrypt protected XML node "DTS:Password"

I have a package (PackageA) with an Execute Package Task that execs PackageB. When I run PackageA I get this error on the Execute Package Task :

Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.

PackageB has 'EncryptSensitiveWithUserKey' ProtectionLevel. I'm providing passwords in the dtsConfig so I'm guessing I should change it to 'DontSaveSensitive'?

Interestingly, PackageA also has 'EncryptSensitiveWithUserKey' ProtectionLevel, but I don't get an error about PackageA, just on the task that runs PackageB.

(SP1 is installed).

Al C. wrote:

PackageB has 'EncryptSensitiveWithUserKey' ProtectionLevel. I'm providing passwords in the dtsConfig so I'm guessing I should change it to 'DontSaveSensitive'?

Yes, since the data is configured somewhere else, DontSaveSensitive is correct choice.

Al C. wrote:

Interestingly, PackageA also has 'EncryptSensitiveWithUserKey' ProtectionLevel, but I don't get an error about PackageA, just on the task that runs PackageB.

The message is only raised when the package contains the actual protected data - passwords, connection strings that can't be decrypted. If the package had 'EncryptSensitiveWithUserKey' ProtectionLevel, but does not have any sensitive data, you will not see this message.

|||Thanks Michael. That explains it all!

execute package task can't continue when the child package failed?

I use a execute package task to run a child package in which I run some sql task.

as the error handle I insert a script task and link a line from execute package task to script task

of course the line is red,

but I found when the child package failed, the execute package task turns red,it stopped

the script task can't be run, I don't konw why?

I tried it again.

I found that if the child package successed then the parent package can run in the success flow

but if child package falied then the parent package will stop at the execute package task, can't run the failure flow.

Anybody konws this....

|||

ycjj wrote:

I tried it again.

I found that if the child package successed then the parent package can run in the success flow

but if child package falied then the parent package will stop at the execute package task, can't run the failure flow.

Anybody konws this....

i'm not sure if this will work. however, try setting the FailParentOnFailure property of the child package to "false".|||

thank you for the answer.

I also think it seems strange....

I tried it. The default value of FailParentOnFailure is false.

I tried it by setting false and true

the result is same.The child package stopped when it failed.

|||

ycjj wrote:

thank you for the answer.

I also think it seems strange....

I tried it. The default value of FailParentOnFailure is false.

I tried it by setting false and true

the result is same.The child package stopped when it failed.

ok. the child package will always stop executing when it fails. my understanding was that you wanted control to return to the parent package when the child package fails. to execute a script task when the child package fails, an on failure precedence constraint from the child package should be connected to the script task.|||

>my understanding was that you wanted control to return to the parent package when the child package fails. to execute a script task when the child package fails, an on failure precedence constraint from the child package should be connected to the script task.

first thanks for your attention.

yes, I want to return to parent package after the child package failed and I hope that the parent package will continue to execute from the execute package task on the failure precedence constraint to a script task as a error handle.but now the execute package task stops if the child package fails.

maybe the failure precedence constraint is wrong......

|||

I found the prpperty "LogicalAnd" of the failure precedence constraint from execute package task to script task(error handle)

I change the value of property "LogicalAnd" from "True" to "False", it works well, but I still don't know the reason.

|||

I made some study and know the reason now .

in my parent package, some execute package tasks have a common error handle task, but I set property "LogicalAnd" of these failure precedence constraint "false"(dedault), it means all of execute package tasks fail will cause error handle task running, of course this is not right,

it must be one of of execute package tasks fails will cause error handle task running, so the value of property "LogicalAnd" is "True" is correctly.

thanks.

Execute Package Logon Failed for User....

Fairly new to SSIS.I have created a package in BIDS, and am trying to execute it so i can test/debug the flow and view the data in the data viewers. I continually get a logon failed for user... its the user id i am using to connect to my SourceConnection OLEDB. I have been struggling with this for a while now, and getting frustrated. I tried Windows Authentication also, still i get an error message logon failed for user......

I have tried all of the security settings, from Do not save sensitive to Encrypt all with password, entered the password, and then try to Execute Package from the solution explorer and still get error message. Thanks for your help!

Here is the error message

An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'UserName'.".

I suffered a similar problem with ado .net connection. I changed ProtectionLevel property to ServerStorage and it ran fine.

BTW, what about the log?

|||

I guess i can try that, but i like the ease of deployment having the packages file based.

What log?

|||log for that dtsx. By default ssis packages haven't. You can create one from Logging menu option|||Gotcha! thanks for that tip! Is there a package level security i can use for file based packages that is basically no security? We are not concerned about encrypting the sensitive information for this package.|||

OK I logged it to event viewer. It looks like the userid i am using to logon to the sourceconnection (SQL server native client) is also the userid that the package is failing to connect to the local (CLIENT) machine. Why is it trying to logon onto the local PC? Does the user that logs onto this local server USERID1 have to be the same as the userid we are using to logon to the SQL server database USERID2? That doesnt make sense? or does it?

|||Thanks for your help. I was able to figure this out. I was using Package configuration and in it i had selected to override the userid for the sourceconnection (SQL native client). After I took that out, and made the sourceconnection use windows authentication now i am able to execute the package. BTW i also added my local user to the SQL database users. Thanks! I am learning....

Execute Package Logon Failed for User....

Fairly new to SSIS.I have created a package in BIDS, and am trying to execute it so i can test/debug the flow and view the data in the data viewers. I continually get a logon failed for user... its the user id i am using to connect to my SourceConnection OLEDB. I have been struggling with this for a while now, and getting frustrated. I tried Windows Authentication also, still i get an error message logon failed for user......

I have tried all of the security settings, from Do not save sensitive to Encrypt all with password, entered the password, and then try to Execute Package from the solution explorer and still get error message. Thanks for your help!

Here is the error message

An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'UserName'.".

I suffered a similar problem with ado .net connection. I changed ProtectionLevel property to ServerStorage and it ran fine.

BTW, what about the log?

|||

I guess i can try that, but i like the ease of deployment having the packages file based.

What log?

|||log for that dtsx. By default ssis packages haven't. You can create one from Logging menu option|||Gotcha! thanks for that tip! Is there a package level security i can use for file based packages that is basically no security? We are not concerned about encrypting the sensitive information for this package.|||

OK I logged it to event viewer. It looks like the userid i am using to logon to the sourceconnection (SQL server native client) is also the userid that the package is failing to connect to the local (CLIENT) machine. Why is it trying to logon onto the local PC? Does the user that logs onto this local server USERID1 have to be the same as the userid we are using to logon to the SQL server database USERID2? That doesnt make sense? or does it?

|||Thanks for your help. I was able to figure this out. I was using Package configuration and in it i had selected to override the userid for the sourceconnection (SQL native client). After I took that out, and made the sourceconnection use windows authentication now i am able to execute the package. BTW i also added my local user to the SQL database users. Thanks! I am learning....

Execute DTS package from ASP failed

I am trying to run DTS Package from ASP 3.0 with the following codes:

Set objDTSPackage = server.CreateObject("DTS.Package")
objDTSPackage.LoadFromSQLServer "serverName", "", "", 256,,,,"pkgName"
objDTSPackage.FailOnError = true
objDTSPackage.Execute

It failed with this message, "Package failed because Step 'DTSStep_DTSDataPumpTask_1' failed".

I am using NT Authentication in both IIS and SQLServer, and both Web and SQLServer are in the same machine.

Can someone help? Thank you.The DTS package must be executed in the same security context as the web page. In ASP web pages are executed under the IIS account that begins with IUSR_. You can find this account name by right clicking My Computer and clicking Manage. Expand Local Users and Groups and look in the users folder.

Then set up a SQL server account for this login like 'MyComputerName\IUSR_...'.

Be careful to only give this account public access to the database the DTS package is accessing and I even go to the trouble of restricting permission to the specific tables.|||ps In the SQL account change the default database to the affected database (not master) and do not give it a server rol for security reason|||Thanks for the prompt reply.

I am using NT Authentication in IIS for all my web applications, does this matter?

I've also tried creating SQL Server login ID with 'myMachineName\IUSR_...', but my company's system wouldn't allow me do this - for security reason.

Any alternatives?|||No it should'nt matter.

are you not allowed to create SQL logins?

or is it giving an error?

try 'yourdomain\youriusraccount'. It might work.

The only other alternative using DTS I know creates a big ugly security hole for hackers to climb in. It invloves firing the DTS package from a shell command and going into the SQL agent properties and setting up a proxy account under the job system tab. The ramifications are ugly.|||I do have the rights to create login ID, but this is something to do with different domain in the system, and I guess not all users in certain domain can be created.

Let me clarify a bit, when you say, create login ID for 'MyComputerName\IUSR_...', you do mean to say the computer that I am personally using now, correct? Not the computer name with IIS installed, right?

I have to find a way to create login ID for this 'IUSR_...', so if this is created, I can use the ASP codes I showed to execute DTS?

Thanks.|||MyComputerName is the name of the computer where your IIS install is.

If you do this your code will work. I've incorporated DTS into 3 ASP projects in the last 4 years.|||Thank you.

I'm still tryihg find "IUSR_" for my web server in SQL Server login creation. Is there any possible reason you can think of that I can't find the "IUSR_" on SQL Server, "New Login"?|||Just want to update and close this:

I've found the IUSR account for the new login to SQL Server. The domain of this IUSR account will be the name of the server (since IUSR is a local user). I've found it there. Thanks.|||did it work?|||Yes and No, Sorry for this terrible answer. Thank you for keep interests in this.

I have used client-side VBscript to make it work - instead of server-side ASP code, I guess this bypasses the IIS issues (?). I am a bit concerned of the security, other than all the stuffs I am still learning. I think I will come back with ASP server-side code to make it work.

HOWEVER, I am having another problem. After I executed successfully the DTS Package, my query and subsequent SQL operations to the destination table don't work anymore. It gives no error messages, but it is not doing anything. A simply query to check the row count, comes back with 0 rows, even though the DTS has transform records to the table.

Help me, if you have any idea? I am not sure where the problem is coming from?!|||how do you know the DTS package executed successfully?

does it work when you fire it from the EM (i.e. rows in the table)?

what is the code you are using to execute the DTS?

i am betting this is another permissions issue and has to do with this client side script you have.

here is some vbscript that should tell you where the package is failing. Depending on how you are doing the package will not always throw errors.

http://www.sqldts.com/default.aspx?t=6&s=104&i=207&p=1&a=7

I converted this script to VB 6 that I wrapped in a COM object which is BTW how I accomplish this. See below.

Option Explicit

Private m_sError As String

Public Function Execute(ByVal sServer As String, ByVal sPackageName As String) As Boolean
On Error GoTo Err_Handler
Dim oPKG As DTS.Package, oStep As DTS.Step
Set oPKG = New DTS.Package

Dim lErr As Long, sSource As String, sDesc As String

Execute = True

' Load Package
oPKG.LoadFromSQLServer sServer, , , _
DTSSQLStgFlag_UseTrustedConnection, "!J1LLYB3@.N!", , , sPackageName

' Set Exec on Main Thread
For Each oStep In oPKG.Steps
oStep.ExecuteInMainThread = True
Next

' Execute
oPKG.Execute

' Get Status and Error Message
For Each oStep In oPKG.Steps
If oStep.ExecutionResult = DTSStepExecResult_Failure Then
oStep.GetExecutionErrorInfo lErr, sSource, sDesc
m_sError = m_sError & "Step """ & oStep.Name & _
""" Failed" & vbCrLf & _
"Error: " & lErr & vbCrLf & _
"Source: " & sSource & vbCrLf & _
"Description: " & sDesc & vbCrLf & vbCrLf
Execute = False
Else
m_sError = m_sError & "Step """ & oStep.Name & _
""" Succeeded" & vbCrLf & vbCrLf
End If
Next

oPKG.UnInitialize

Clean_Up:
Set oStep = Nothing
Set oPKG = Nothing

Exit Function

Err_Handler:
Execute = False
m_sError = "Error in Object Execution" & vbCrLf & _
"Number: " & Err.Number & vbCrLf & _
"Source: " & Err.Source & vbCrLf & _
"Description: " & Err.Description
GoTo Clean_Up
End Function

Public Function GetErrorDetails() As String
GetErrorDetails = m_sError
End Function|||Before DTS starts, the destination table is cleared, then after the DTS, I went into EM to check, and they are rows in the tables. I assume that means DTS is working.

And this is my client-side VB code:

Dim objDTSPackage,
On Error Resume Next
Set objDTSPackage = CreateObject("DTS.Package")
objDTSPackage.LoadFromSQLServer "server", "", "", 256,,,,"pkgName"
objDTSPackage.FailOnError = true
objDTSPackage.Execute
objDTSPackage.UnInitialize()
Set objDTSPackage = Nothing

I will also study your codes. Thank for your help.|||Not sure if anyone would still read this long thread, but...

I've made this to work by putting codes into a VB DLL.

However, if I execute a simple SELECT statement against the destination table after the DTS execution is completed. It gives no error, but with no result either.

But if I reload the ASP page immediately, in other words, DTS is executed the second time, the SELECT statement produces the results from the FIRST DTS execution, instead of coming from the 2nd DTS execution!?

It seems to me the first DTS exectuion doesn't exist - as far as the SELECT statement is concerned.

Anyone has idea? Please help.|||rweide,
I am still here. watching this forum keeps me from working on my current ptoject which requires no effort or creativity and is boring me to death. So this is how I pass my days.

Might need to see some code here. Are you executing the DTS package and the select on the same post to the server?|||I'm so happy that you're bored!!! :)

I've decided just copy your codes into VB and created the DLL. But at the point, I'm only using client-side VBScript to call the DLL, which sits locally on my machine - I will move it to server whenl all these problems is resolved.

The DTS package is very simple - move the data from a flat text file to a holding/destination table, and it uses Windows authentication. And 2 SQL stored procedures are executed to check row count (to see if DTS works at all) and to update the main DB table using data from the temporary holding table after DTS is run.

As I've mentioend, the simply query give no result (row count = 0) and no error. But by checking thru EM, I know the DTS has populated the destination table. If I reload the ASP page (running DTS again), the query gives the result from the first DTS execution!!

Here is the abbreviation of the codes:

<Body>
<%
On Error Resume Next
Set Session("adoCnn") = server.CreateObject ("ADODB.Connection")
Session("adoCnn").ConnectionString = "connection string here"
Session("adoCnn").Open
%>

<Script Language=VBScript>
Set mc = CreateObject("mc.mcDTS")
mc.Execute
document.write mc.GetErrorDetails
set mc = nothing
</script>
<%
Response.Write "<BR><BR> Row Count in Holding Table: " & CountRows()
Call UpdateManual()

Response.Write "<BR><BR>Count Close Table: " & CountClose()
If Err.number = 0 Then
response.write "<BR><BR>Updated from Holding table to Main Table completed..."
End If
%>
</Body>
</HTML>
<%
Function CountRows()
Dim cmd, rs, Parm1

On Error Resume Next
Set cmd = Server.CreateObject("ADODB.Command")
Set rs = Server.CreateObject("ADODB.Recordset")

rs.CursorType = adOpenStatic
cmd.CommandText = "spCountHoldingRows"
cmd.CommandType = adCmdStoredProc
' cmd.CommandText = "SELECT COUNT(*) row FROM tbl_mc_Monthly_Close_Holding"
' cmd.CommandType = adCmdtext
Set Parm1 = cmd.CreateParameter("return", adInteger, adParamReturnValue)
cmd.parameters.append parm1
cmd.ActiveConnection = Session("adoCnn").ConnectionString
set rs = cmd.Execute
If err.number <> 0 Then
Response.Write "<BR>Count Rows - " & err.number & " - " & err.Description
End If
CountRows = cmd(0)
Set cmd = Nothing
set rs = nothing
End Function

Function CountClose()
Dim cmd, rs, Parm1

On Error Resume Next
Set cmd = Server.CreateObject("ADODB.Command")
Set rs = Server.CreateObject("ADODB.Recordset")

rs.CursorType = adOpenStatic
cmd.CommandText = "spCountCloseRows"
cmd.CommandType = adCmdStoredProc
Set Parm1 = cmd.CreateParameter("return", adInteger, adParamReturnValue)
cmd.parameters.append parm1
cmd.ActiveConnection = Session("adoCnn").ConnectionString
set rs = cmd.Execute
If err.number <> 0 Then
Response.Write "<BR>Count Close Rows - " & err.number & " - " & err.Description
End If

CountClose = cmd(0)
Set cmd = Nothing
set rs = nothing
End Function

Sub UpdateManual()
Dim cmd

On Error Resume Next
Set cmd = Server.CreateObject("ADODB.Command")
cmd.CommandText = "spUpdateMain"
cmd.CommandType = adCmdStoredProc
cmd.CommandTimeOut = 1800
cmd.ActiveConnection = Session("adoCnn").ConnectionString
cmd.Execute
If err.number <> 0 Then
Response.Write "<BR>UpdateManual - " & err.number & " - " & err.Description
End If
Set cmd = Nothing

End Sub

%>

And I don't really think the combination of client-side and server-side codes will mess up the operation. I remember at one time, I changed all codes to be executed on the client-side, and it still doesn't work.

I wonder if this has anything to do with memory?|||I am not sure where to start.

Where does your database reside? First, get you database, web server, and DTS package all on the same server. (professionally I reccomend having the web and database server on different machines with a firewall between the 2).

Change this back to server side script:

<Script Language=VBScript>
Set mc = CreateObject("mc.mcDTS")
mc.Execute
document.write mc.GetErrorDetails
set mc = nothing
</script>

Next hide your connection string in an include file in another directory that your IUSR account does not have access to.

Finally and this meant to be constructive criticism, you write too much code. Keep it simple and concise. do not use functions unless you have reptitive code. Look at this below. It works. I just did it.

<HTML>
<Head>
<Title>My Module</Title>
</Head>
<BODY>
<H2>Sourcing Module</H2>
<H3>Upload Bibliography Data to Sterling</H3>
<%
Dim mySmartUpload
Set mySmartUpload = Server.CreateObject("aspSmartUpload.SmartUpload")
Server.ScriptTimeout = 10000
mySmartUpload.Upload
mySmartUpload.Save("/downloads")
Set mySmartUpload = Nothing
Dim oExecDTS
Dim sServer, sPackageName
Dim bResult
sServer = "MySQLServer"
sPackageName = "Mydts"
Set oExecDTS = CreateObject("SQLDTS_ExecDTS8.ExecutePackage")
bResult = oExecDTS.Execute(sServer, sPackageName)
If bResult Then
Response.Write "<p>Package " & sPackageName & " succeeded</p>"
Else
Response.Write "<p>Package " & sPackageName & " failed</p>"
Response.Write "<p>" & Replace(oExecDTS.GetErrorDetails, vbCrLf, "<br/>") & "</p>"
End If
Set oExecDTS = Nothing
Dim con,rs,constring,sql
Set rs = Server.CreateObject("ADODB.Recordset")
Set con = Server.CreateObject("ADODB.Connection")
sql = "SELECT count(*) as thecount FROM DP_PRELIMBIB"%>
<!-- #include file="includes\sourcingDBconnection.inc" -->
<%con.Open constring
rs.Open sql, con
Response.Write rs("thecount")
rs.Close
con.Close
Set rs = Nothing
Set con = Nothing
%>
</BODY>
</HTML>


aspSmartUpload is a third party component I use to upload and download files for personal applications.

Execute DTS 2000 Package Task. Mischievous task?

Hi everyone,

For first time I'm testing this task and surprisingly, when I try "Edit Package" option:

1)The DTS host failed to load or save the package properly

2)The selected package cannot be opened

3)Error HRESULT E_FAIL has been returned from a call to a COM component

But after these messages you can see all the tasks but they haven't name!!

It seem as if RCW mechanism has failed between managed and unmanaged coded-partially.

I don't dare to follow doing more stuff, I don't know if that package is well-loaded or not from there. ??

Any guidance or idea about this?

Jamie? Darren?|||Do you mean that you are trying to open the DTS package from Management Studio via the Management->Legacy folder?

If so, I had the same problem opening DTS packages even though I had the SQL2005_DTS.msi components installed.

When you open the package, you will get the 3 error messages and then the DTS Designer window will display the DTS package's tasks without names or correct icons. I've found that saving the opened package under a new DTS package : and then opening the new package will remove the error messages. You will be able to open the tasks and modify them, I still have to test if the new saved package works correctly. I will give you an update on this soon.

|||

Enric,

This is already answered here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124252&SiteID=1. We have to try this fix: http://support.microsoft.com/kb/917406/en-us

In my case, it's an x64 machine, the above fix doesnot work.. Anybody who has fixed this on x64 ?

Thanks

Subhash Subramanyam

|||

Hi Friends,

I got it working on the Method 2 posted here, but I wonder if it is a must to Install Enterprise Manager Client tools for an X64 to get rid of these errors.

Thanks

Subhash Subramanyam

Execute DTS 2000 Package Task. Mischievous task?

Hi everyone,

For first time I'm testing this task and surprisingly, when I try "Edit Package" option:

1)The DTS host failed to load or save the package properly

2)The selected package cannot be opened

3)Error HRESULT E_FAIL has been returned from a call to a COM component

But after these messages you can see all the tasks but they haven't name!!

It seem as if RCW mechanism has failed between managed and unmanaged coded-partially.

I don't dare to follow doing more stuff, I don't know if that package is well-loaded or not from there. ??

Any guidance or idea about this?

Jamie? Darren?|||Do you mean that you are trying to open the DTS package from Management Studio via the Management->Legacy folder?

If so, I had the same problem opening DTS packages even though I had the SQL2005_DTS.msi components installed.

When you open the package, you will get the 3 error messages and then the DTS Designer window will display the DTS package's tasks without names or correct icons. I've found that saving the opened package under a new DTS package : and then opening the new package will remove the error messages. You will be able to open the tasks and modify them, I still have to test if the new saved package works correctly. I will give you an update on this soon.|||

Enric,

This is already answered here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=124252&SiteID=1. We have to try this fix: http://support.microsoft.com/kb/917406/en-us

In my case, it's an x64 machine, the above fix doesnot work.. Anybody who has fixed this on x64 ?

Thanks

Subhash Subramanyam

|||

Hi Friends,

I got it working on the Method 2 posted here, but I wonder if it is a must to Install Enterprise Manager Client tools for an X64 to get rid of these errors.

Thanks

Subhash Subramanyam