Showing posts with label task. Show all posts
Showing posts with label task. Show all posts

Thursday, March 29, 2012

Error: Failed to load script task

I have an email script that keeps failing to load when I execute my script task. I have the precompileintobinarycode set to true. Anyone know why it won't load the script? I would use the Send Mail task but it can't find my smtp connection or something.

Thanks,

Mike

This error can spontaneously appear for no apparent reason. It seems that if you have the PreCompile property set to True, but you have precompiled script in the package, which is what spontaneously disappears, this error will be raised. To resolve this issue:

a. Open the package

b. Open the Script Task editor

c. Click Design Script

d. Close the VSA Editor

e. Close the Script Task Editor

f. Save and close the package.

|||

didn't work I still get the same error.

sql

Error: Failed to load script task

I have an email script that keeps failing to load when I execute my script task. I have the precompileintobinarycode set to true. Anyone know why it won't load the script? I would use the Send Mail task but it can't find my smtp connection or something.

Thanks,

Mike

This error can spontaneously appear for no apparent reason. It seems that if you have the PreCompile property set to True, but you have precompiled script in the package, which is what spontaneously disappears, this error will be raised. To resolve this issue:

a. Open the package

b. Open the Script Task editor

c. Click Design Script

d. Close the VSA Editor

e. Close the Script Task Editor

f. Save and close the package.

|||

didn't work I still get the same error.

Monday, March 26, 2012

ERROR: A variable may only be added once to either the read lock list or the write lock list.

Hi,
I have set of 2 DTS packages, one of which calls the other by forming a command-line (dtexec) using a Execute Process task.

From the parent package-> Execute Process Task->
dtsexec /F etc... /<pkg variable> = "servername"

Each of the parent and the called package have a variable: "User::DWServerSQLInstance" which is mapped to the SQL server connection manager server name property using an expression. The outer package has the above variable and so does the inner called package (which gets assigned through the command line from the outerpackage call to inner)

I "sometimes" get the following error:

OnError,I4,TESTDOM\Administrator,ACDWAggregation,{A1F8E43F-15F1-4685-8C18-6866AB31E62B},{77B2F3C7-6756-46EB-8C01-D880598FB4B3},5/22/2006 5:10:28 PM,5/22/2006 5:10:28 PM,-1073659822,0x,The variable "User::DWServerSQLInstance" is already on the read list. A variable may only be added once to either the read lock list or the write lock list.

Help would be appreciated!

I have seen other posts on this but, not able to relate the solution to my scenario.

Do you have multiple tasks (in the same package) executing in parallel, and using same variable, e.g. in property mappings?

If yes, I think this problem is fixed by this post-SP1 fixes collection:
http://support.microsoft.com/Default.aspx?id=918222

Alternatively, you may change the package so the tasks are executed sequentially by creating precedence constraints.|||

Hi Brian,
The child Package uses the User Variable: DWSQLInstanceName mentioned above to initialize 4 SQL Server connections (2 OLEDB & 2 ADO .NET) -- Only <<Server Name>> property using expressions.

I also checked that this error seems to be only on Multi-proc machine. Don't get the same on my laptop.

I cannot seralize the tasks since, the error is coming @. package level while evaluating the package expressions (i.e. for the connections) when the package starts.

What is the best way to still use expressions for connection server names but, get around this error?
Is this what is fixed in SP1?

Also, it seems that the packages does not fail when it encounters the error which I am getting. I have MaxErrorCount = 1 for Package. The package goes ahead.

|||I believe the issue with connections sharing the variable is fixed in the commulative hotfix package I've mentioned above. It should be installed on top of SP1: first, install SP1 then install all the component packages from the hotfix package in the order they are listed in the article.

http://www.microsoft.com/downloads/details.aspx?FamilyId=CB6C71EA-D649-47FF-9176-E7CAC58FD4BC
and then
http://support.microsoft.com/Default.aspx?id=918222|||This was indeed a bug and the post SP1 hotfix "fixes" it.

However, you can still create the bug. It's harder but stil there...|||

Thanks Michael and Crispin for the help on this!

I think we will need to upgrade to SP1 and install the Hotfix bundle for SP1. I think this should fix the issue which I am facing i.e. use of same variable for setting connection "Server Name" - Property in the expressions.

Thanks,
Gaurav

Thursday, March 22, 2012

Error: -2147024770 when i scheduled a package containing a custom task

I create a VB ActiveX DLL custom task, when i execute the package containing the DLL custom task, all is ok
But when i scheduled the package i receive the message "Error: -2147024770 The specified module could not be found"
In the code of the VB custom task i use the sysdtssteplog table from MSDB and it doesn't log anything
What's the problem
Thanks!Whenever I seen that error from VB - SQL it has always
been in the context that the SQL command run from VB has
not worked.
Try a trace to see exactly what SQL was processed.
J
>--Original Message--
>I create a VB ActiveX DLL custom task, when i execute the
package containing the DLL custom task, all is ok.
>But when i scheduled the package i receive the
message "Error: -2147024770 The specified module could
not be found".
>In the code of the VB custom task i use the sysdtssteplog
table from MSDB and it doesn't log anything.
>What's the problem?
>Thanks!
>.
>|||Jay,
When you run it, what context (login, machine, etc) are you running under?
When you schedule it (I assume through SQL Agent), what context (login,
machine, etc) are you running under?
I suspect that the SQL Server account (either the account running the SQL
Server service or the SQL Agent proxy account) does not have rights to the
location where the DLL is stored. Make sure that the DLL can be reached by
the SQL Server.
Russell Fields
"JayF" <anonymous@.discussions.microsoft.com> wrote in message
news:025B1AE0-EDC9-482C-B93E-788775D19D24@.microsoft.com...
> I create a VB ActiveX DLL custom task, when i execute the package
containing the DLL custom task, all is ok.
> But when i scheduled the package i receive the message
Error: -2147024770 The specified module could not be found".
> In the code of the VB custom task i use the sysdtssteplog table from MSDB
and it doesn't log anything.
> What's the problem?
> Thanks!

Error: -2147024770 when i scheduled a package containing a custom task

I create a VB ActiveX DLL custom task, when i execute the package containing
the DLL custom task, all is ok.
But when i scheduled the package i receive the message "Error: -2147024770
The specified module could not be found".
In the code of the VB custom task i use the sysdtssteplog table from MSDB an
d it doesn't log anything.
What's the problem?
Thanks!Jay,
When you run it, what context (login, machine, etc) are you running under?
When you schedule it (I assume through SQL Agent), what context (login,
machine, etc) are you running under?
I suspect that the SQL Server account (either the account running the SQL
Server service or the SQL Agent proxy account) does not have rights to the
location where the DLL is stored. Make sure that the DLL can be reached by
the SQL Server.
Russell Fields
"JayF" <anonymous@.discussions.microsoft.com> wrote in message
news:025B1AE0-EDC9-482C-B93E-788775D19D24@.microsoft.com...
quote:

> I create a VB ActiveX DLL custom task, when i execute the package

containing the DLL custom task, all is ok.
quote:

> But when i scheduled the package i receive the message

Error: -2147024770 The specified module could not be found".
quote:

> In the code of the VB custom task i use the sysdtssteplog table from MSDB

and it doesn't log anything.
quote:

> What's the problem?
> Thanks!
sql

Sunday, March 11, 2012

Error: 0xC001000E - connection not found

Hello,

Does anyone know what this error means and how to resolve it? I get this error when I attempt to run a Data Flow Task. The Data Flow Task has one subcomponent, a Flat File Source. I have set up the connection manager to access the flat file, which is on a local directory. I have tried everything to fix this. What could possibly be the problem?

Thanks

Error: 0xC001000E at : The connection "{B9E11DD7-21A1-4FD7-986F-6BDC5B81F51D}" is not found. This error is thrown by Connections collection when the specific connection element is not found.

K108 wrote:

Hello,

Does anyone know what this error means and how to resolve it? I get this error when I attempt to run a Data Flow Task. The Data Flow Task has one subcomponent, a Flat File Source. I have set up the connection manager to access the flat file, which is on a local directory. I have tried everything to fix this. What could possibly be the problem?

Thanks

Error: 0xC001000E at : The connection "{B9E11DD7-21A1-4FD7-986F-6BDC5B81F51D}" is not found. This error is thrown by Connections collection when the specific connection element is not found.

Go in and edit the flat file source - make sure it is pointing at the correct connection manager.

Out of interest, what is the point of a data-flow with only one component in it?

-Jamie

|||

I am just trying to test for now, that is why there is only one component. Why add more components when I can't even get the one to work correctly.

Anyways I resolved the problem... this error was occuring on a DTS migrated pkg. Apparently there are some ghost connections that are persisting, so by starting the pkg from scratch the problem has disappeared. This is my theory anyways.

|||

K108 wrote:

I am just trying to test for now, that is why there is only one component. Why add more components when I can't even get the one to work correctly.

Ah gotcha. That makes sense.

K108 wrote:

Anyways I resolved the problem... this error was occuring on a DTS migrated pkg. Apparently there are some ghost connections that are persisting, so by starting the pkg from scratch the problem has disappeared. This is my theory anyways.

This error most commonly occurs when you copy tasks/components from one package to another. I know that's not exactly what you've done but its not a huge jump from it. I guess that must be something to do with it.

Glad its fixed anyway.

-Jamie

|||

Yes, the problem (after much testing on my part) ALWAYS crops up when I am trying to run components from a migrated DTS package.

In this case, I have an EXECUTE SQL task, for which I've defined a NEW connection and deleted the old connection completely, and it still throws this error about the connection not existing, even though the sql runs correctly in the database.

I have found that the only solution to this problem is to start the package from scratch, and use the EXECUTE DTS 2000 PACKAGE object instead, instead of trying to run it from the migrated package itself.

Friday, March 9, 2012

error wmi task

i have really hard time with this.it sits there showing yellow or it neither runs...

how should this be actually set?

Again, Books On-Line will help you.

http://msdn2.microsoft.com/en-us/library/ms141130.aspx|||i have look at everything but this dosent seem to work at all...|||

That doesn't help us. We don't know what your trying to accomplish, and we don't know what settings you've tried, etc... Provide more details and perhaps we can help you.

|||

ok i transfer from flat file to sql database

i want to put this task in place to check if the file had arrived.If so i want my packge execution to begin.

In my control flow i have wmi task

the file is located on shared drive.and not on my local machine.(ex t:\test\files\text.txt)

here

Connection managers:

servename=\\localhost

namespace=\root\cimv2

WMIQuerySourceTypeirectinput

WMIQuerySource:

SELECT * FROM __InstanceCreationEvent WITHIN 10 WHERE Targetinstance ISA "CIM_DirectoryContainsFile" and TargetInstance.GroupComponent= "Win32_Directory.Name=\"t:\test\files\text.txt""

Rest of the fields i leave as they are..

Is this right?please let me know..

|||

sureshv wrote:


ok i transfer from flat file to sql database

i want to put this task in place to check if the file had arrived.If so i want my packge execution to begin.

In my control flow i have wmi task

the file is located on shared drive.and not on my local machine.(ex t:\test\files\text.txt)

I wouldn't use WMI for this. I'd probably write a script task to periodically check for the file and sleep in between. Or use the File Watcher task. http://www.sqlis.com/23.aspx

|||

I've played around with the WMI components some, but not enough to remember proper syntax...

That said, you might look at the fact that you're specifying the Win32_Directory.GroupComponent as an individual file. I believe you might want it as the PartComponent.

|||i am just going mad with this task...i try several things and read stuff on it....but i just cant get it to work....it runs and shows yellow forever....could anyone let me know how it work?
your help is appreciated....

error wmi task

i have really hard time with this.it sits there showing yellow or it neither runs...

how should this be actually set?

Again, Books On-Line will help you.

http://msdn2.microsoft.com/en-us/library/ms141130.aspx|||i have look at everything but this dosent seem to work at all...|||

That doesn't help us. We don't know what your trying to accomplish, and we don't know what settings you've tried, etc... Provide more details and perhaps we can help you.

|||

ok i transfer from flat file to sql database

i want to put this task in place to check if the file had arrived.If so i want my packge execution to begin.

In my control flow i have wmi task

the file is located on shared drive.and not on my local machine.(ex t:\test\files\text.txt)

here

Connection managers:

servename=\\localhost

namespace=\root\cimv2

WMIQuerySourceTypeirectinput

WMIQuerySource:

SELECT * FROM __InstanceCreationEvent WITHIN 10 WHERE Targetinstance ISA "CIM_DirectoryContainsFile" and TargetInstance.GroupComponent= "Win32_Directory.Name=\"t:\test\files\text.txt""

Rest of the fields i leave as they are..

Is this right?please let me know..

|||

sureshv wrote:


ok i transfer from flat file to sql database

i want to put this task in place to check if the file had arrived.If so i want my packge execution to begin.

In my control flow i have wmi task

the file is located on shared drive.and not on my local machine.(ex t:\test\files\text.txt)

I wouldn't use WMI for this. I'd probably write a script task to periodically check for the file and sleep in between. Or use the File Watcher task. http://www.sqlis.com/23.aspx

|||

I've played around with the WMI components some, but not enough to remember proper syntax...

That said, you might look at the fact that you're specifying the Win32_Directory.GroupComponent as an individual file. I believe you might want it as the PartComponent.

|||i am just going mad with this task...i try several things and read stuff on it....but i just cant get it to work....it runs and shows yellow forever....could anyone let me know how it work?
your help is appreciated....

Sunday, February 26, 2012

Error with Execute sql task and full result set: " not been initialized before calling 'Fi

This is the first time I've tried creating an "execute sql task" with a "full result set".

I've read in the documentation that I must set the resultname to 0, which is done, and that the variable must be of type object. Also done.

[Execute SQL Task] Error: Executing the query "select * from blah" failed with the following error: "The SelectCommand property has not been initialized before calling 'Fill'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Has anyone else had success with a full result set?

Thanks,
-Lori

Yes. I have an example doing exactly this here:

SSIS Nugget: Execute SQL Task into an object variable - Shred it with a Foreach loop
(http://blogs.conchango.com/jamiethomson/archive/2005/07/04/1748.aspx)

-Jamie

|||Jamie,

The variable *is* of type Object (i believe i mentioned that).
Since this fails, I cannot move forward with the foreach loop.

I'm using 64bit sql server but debugging in Run64BitRuntime as False.

Any other ideas?

-Lori|||

lorijean44 wrote:

Jamie,

The variable *is* of type Object (i believe i mentioned that).

Yes you did. You also asked if anyone else has had any success which I have and was giving you a downloadable example of it working which I thought might be useful to you.

lorijean44 wrote:


Since this fails, I cannot move forward with the foreach loop.

I'm using 64bit sql server but debugging in Run64BitRuntime as False.

Any other ideas?

-Lori

Afraid not. Without being there its hard to say what the problem might be.

Regards

-Jamie

|||I noticed that you said in your blog, "just update the connection to point to your sql server". I thought I should mention that I'm actually trying to run this against a mysql server, with an ADO.net connection. I don't think that should matter, but who knows?

I'll play around and see if it works against a SQL Server just to try it.|||Yep, works great against a sql server (OLE DB Connection).

I will then update my question to be:
has anyone gotten a full result set to work with an ADO.net connection?|||

lorijean44 wrote:

I noticed that you said in your blog, "just update the connection to point to your sql server". I thought I should mention that I'm actually trying to run this against a mysql server, with an ADO.net connection. I don't think that should matter, but who knows?

I'll play around and see if it works against a SQL Server just to try it.

I'd bevery surprised if that was anything to do with it but who knows - give it a try.

Also note that my example used OLE DB Connection Manager rather than ADO.Net. That could be an avenue of investigation also.

-Jamie

Error with Execute sql task and full result set: " not been initialized before calling

This is the first time I've tried creating an "execute sql task" with a "full result set".

I've read in the documentation that I must set the resultname to 0, which is done, and that the variable must be of type object. Also done.

[Execute SQL Task] Error: Executing the query "select * from blah" failed with the following error: "The SelectCommand property has not been initialized before calling 'Fill'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

Has anyone else had success with a full result set?

Thanks,
-Lori

Yes. I have an example doing exactly this here:

SSIS Nugget: Execute SQL Task into an object variable - Shred it with a Foreach loop
(http://blogs.conchango.com/jamiethomson/archive/2005/07/04/1748.aspx)

-Jamie

|||Jamie,

The variable *is* of type Object (i believe i mentioned that).
Since this fails, I cannot move forward with the foreach loop.

I'm using 64bit sql server but debugging in Run64BitRuntime as False.

Any other ideas?

-Lori|||

lorijean44 wrote:

Jamie,

The variable *is* of type Object (i believe i mentioned that).

Yes you did. You also asked if anyone else has had any success which I have and was giving you a downloadable example of it working which I thought might be useful to you.

lorijean44 wrote:


Since this fails, I cannot move forward with the foreach loop.

I'm using 64bit sql server but debugging in Run64BitRuntime as False.

Any other ideas?

-Lori

Afraid not. Without being there its hard to say what the problem might be.

Regards

-Jamie

|||I noticed that you said in your blog, "just update the connection to point to your sql server". I thought I should mention that I'm actually trying to run this against a mysql server, with an ADO.net connection. I don't think that should matter, but who knows?

I'll play around and see if it works against a SQL Server just to try it.|||Yep, works great against a sql server (OLE DB Connection).

I will then update my question to be:
has anyone gotten a full result set to work with an ADO.net connection?|||

lorijean44 wrote:

I noticed that you said in your blog, "just update the connection to point to your sql server". I thought I should mention that I'm actually trying to run this against a mysql server, with an ADO.net connection. I don't think that should matter, but who knows?

I'll play around and see if it works against a SQL Server just to try it.

I'd bevery surprised if that was anything to do with it but who knows - give it a try.

Also note that my example used OLE DB Connection Manager rather than ADO.Net. That could be an avenue of investigation also.

-Jamie

error with Execute package task

Hi,

We have used an execute package task in our master package to execute a child package and we have set the execute out of process=false. This master package is running fine in 32 bit server but is failing in 64 bit server. is there any settings to be done in the server or is it the problem with the property setting(execute out of process)

Vivek S

sorry for posting in SSRS category. Has been reposted in SSIS

Error with Data Flow Task

I am having problems with the Data Flow task. It does not even show up in the list of items to drop into the SSIS project.

If I go to the Data Flow tab and hit create, I get the follow error. I have tried repairing and reinstalling, but nothing seems to clear up the error. Without rebuilding my machine, is there anyone who knows how to get the Data Flow Task reinstalled properly?

Thanks

Wayne

TITLE: Microsoft Visual Studio


Registration information about the Data Flow task could not be retrieved. Confirm that this task is installed properly on the computer.


ADDITIONAL INFORMATION:

TaskHost "{C3BF9DC1-4715-4694-936F-D3CFDA9E42C5}"' is not installed correctly on this computer. (Microsoft.DataTransformationServices.Design)

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


BUTTONS:

OK


Did you search the forum?

it looks like that has been asked before:

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

Wednesday, February 15, 2012

Error while executing SSIS package from other SSIS package

Hi,

In our project we have two SSIS package.

And there is a task (Execute SSIS package) in First package that calls the execution of second package.

I m continuously receiving an error "Failed to decrypt protected XML node "PackagePassword" 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."

As we are running first package by job, job runs successfully logging above error

The protection level of second package is set to "EncryptSensitiveWithUserKey"

Can anybody please suggest how to handle it?

If these DTSX has been saved on the MSDB you could use 'Server Storage' as protection level.

EncryptSensitive.. is the default protection level for the packages.

|||

If protection level property of the package has EncryptSensitive WithUSerKey means that only the author of the package is allowed to run it. This KB offers diffrent alternatives to solve your issue:

An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step:

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

|||

Admin,

This topic is a good candidate for a "sticky" for the forum.

This question is asked once a day... we could come up with a synopsis on package encryption

|||

The DTSX is not saved in the MSDB,

its at disk only.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.

Error while debugging the script task

I am getting an while trying to run the script task in debug mode in SSIS package.

"SQL Server Integration Services Script Task has encountered a problem and needs to close. We are sorry for the inconvenience."

Any idea why i am getting this error.

Thanks,

Deepak,

Did you ever find a solution to your issue? I'm having the same thing.

Thanks,
Todd

|||I don't know what the problem is, but I had the same problem as you. I found that I had some Breakpoints sit in other script tasks. When you select the Debug Menu -> Delete All Breakpoints, I assumed it deleted all breakpoints. However, it doesn't seem to clear them out of the script tasks very well. Anyway, I went into every Script Task .NET code and explicity looked and removed all breakpoints. Then, I executed the package. Finally, I added my desired breakpoints back into the particular script task I was debugging. I hope that helps.