Showing posts with label package. Show all posts
Showing posts with label package. Show all posts

Wednesday, March 28, 2012

Problems in Loading configuration file

Hi,

We have configured package to load configurations from XML file.

But whenever we try to run the package, it throws below warning message

and continues to download the configuration file and finally ending up in low memory exception

The package is attempting to configure from the XML file "E:\Cybage\Deployment\MSCERT\MSCERT_MainPackgeConfig.dtsConfig".

I have made sure the file exists at the above location.

Please let me know if anyone have any solution on this.


Regards,

sachin

What exactly is the file name you are trying to supply? What are the machine specs where the package is running? What exactly is configured in the xml file?
|||

SachinS wrote:

The package is attempting to configure from the XML file "E:\Cybage\Deployment\MSCERT\MSCERT_MainPackgeConfig.dtsConfig".

That's an informational message. Where's the error/warning message? That message will occur every single time (and it is valid) that the package runs.|||

We are storing connection strings in this config file.

'Loading configuration settings from file' message gets repeated n number of times and it does not stop until it gets some memory exception

|||Do you have the same configuration file listed multiple times in the package configuration window?sql

Wednesday, March 21, 2012

Problems calling packages from package.

John
I think you will be better to put the question to DTS.newsgroup and also
look at www.sqldts.com .
Personally , I have been calling DTS Package from stored procedure which is
accepted a parameter for GV.
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:OSDjL$ETEHA.2480@.TK2MSFTNGP10.phx.gbl...
> (SQL Server 2000, SP3a)
> Hello all!
> I have a DTS package, that I'll call "A", which calls another package "B".
In A's Global
> Variable (GV) space, I'm defining the following variables:
> SourceServer
> SourceDatabase
> SourceUser
> SourcePassword
> DestinationServer
> DestinationDatabase
> DestinationUser
> DestinationPassword
> I also define these same GVs in B.
> I have A define the values for the GVs and I believe that they should
"propagate" to B by
> placing these variables in the "Outer Package Global Variables" tab.
> However, when I try to change a value from A, it's like B "remembers" the
last successful
> value that was used (it's not picking up the changed value).
> Am I doing something wrong with respect to GVs and packages calling other
packages?
> Thanks!
> John Peterson
>Thanks Uri...however, it *seems* like it's not working correctly in my case.
:-(
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:O3NZtGFTEHA.2944@.tk2msftngp13.phx.gbl...
> John
> I think you will be better to put the question to DTS.newsgroup and also
> look at www.sqldts.com .
> Personally , I have been calling DTS Package from stored procedure which i
s
> accepted a parameter for GV.
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:OSDjL$ETEHA.2480@.TK2MSFTNGP10.phx.gbl...
> In A's Global
> "propagate" to B by
> last successful
> packages?
>|||A better question might be, what exactly do the two tabs do? That is, if I
want to
propagate my out (caller) package's GVs to the inner (callee), do I do that
from the Outer
Package tab? Or should that be done from the Inner Package tab?
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:eyt8UOFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
> Thanks Uri...however, it *seems* like it's not working correctly in my cas
e. :-(
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:O3NZtGFTEHA.2944@.tk2msftngp13.phx.gbl...
>|||From this article: 47.html" target="_blank">http://www.winnetmag.com/SQLServer/...
47.html
<Quote>
Inside the Execute Package task, you can easily pass global variables to the
child
package, as Figure 1 shows. If you click the Inner Package Global Variables
tab in the
Execute Package task, DTS scans the child package for any global variables t
hat it
expects, and you can set them to your own values. Inner global variables let
you set the
global variables for the child package from the Execute Package task. Inner
global
variables are useful when you're calling auditing packages and you want to p
XXX to the
child package certain errors based on events in the parent package. Outer gl
obal variables
send global variables from the parent package to the child package. If a glo
bal variable
exists in the child package, DTS updates the child's global variable to the
parent's
value. If the global variable doesn't exist in the child package, DTS create
s it.
</Quote>
It would *seem* that my understanding of this is accurate. Though, clearly
I'm still
doing something wrong...
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:OvKJxQFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
> A better question might be, what exactly do the two tabs do? That is, if
I want to
> propagate my out (caller) package's GVs to the inner (callee), do I do that from t
he
Outer
> Package tab? Or should that be done from the Inner Package tab?
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:eyt8UOFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
>

Problems calling packages from package.

John
I think you will be better to put the question to DTS.newsgroup and also
look at www.sqldts.com .
Personally , I have been calling DTS Package from stored procedure which is
accepted a parameter for GV.
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:OSDjL$ETEHA.2480@.TK2MSFTNGP10.phx.gbl...
> (SQL Server 2000, SP3a)
> Hello all!
> I have a DTS package, that I'll call "A", which calls another package "B".
In A's Global
> Variable (GV) space, I'm defining the following variables:
> SourceServer
> SourceDatabase
> SourceUser
> SourcePassword
> DestinationServer
> DestinationDatabase
> DestinationUser
> DestinationPassword
> I also define these same GVs in B.
> I have A define the values for the GVs and I believe that they should
"propagate" to B by
> placing these variables in the "Outer Package Global Variables" tab.
> However, when I try to change a value from A, it's like B "remembers" the
last successful
> value that was used (it's not picking up the changed value).
> Am I doing something wrong with respect to GVs and packages calling other
packages?
> Thanks!
> John Peterson
>
Thanks Uri...however, it *seems* like it's not working correctly in my case. :-(
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:O3NZtGFTEHA.2944@.tk2msftngp13.phx.gbl...
> John
> I think you will be better to put the question to DTS.newsgroup and also
> look at www.sqldts.com .
> Personally , I have been calling DTS Package from stored procedure which is
> accepted a parameter for GV.
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:OSDjL$ETEHA.2480@.TK2MSFTNGP10.phx.gbl...
> In A's Global
> "propagate" to B by
> last successful
> packages?
>
|||A better question might be, what exactly do the two tabs do? That is, if I want to
propagate my out (caller) package's GVs to the inner (callee), do I do that from the Outer
Package tab? Or should that be done from the Inner Package tab?
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:eyt8UOFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
> Thanks Uri...however, it *seems* like it's not working correctly in my case. :-(
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:O3NZtGFTEHA.2944@.tk2msftngp13.phx.gbl...
>
|||From this article: http://www.winnetmag.com/SQLServer/A...747/19747.html
<Quote>
Inside the Execute Package task, you can easily pass global variables to the child
package, as Figure 1 shows. If you click the Inner Package Global Variables tab in the
Execute Package task, DTS scans the child package for any global variables that it
expects, and you can set them to your own values. Inner global variables let you set the
global variables for the child package from the Execute Package task. Inner global
variables are useful when you're calling auditing packages and you want to pass to the
child package certain errors based on events in the parent package. Outer global variables
send global variables from the parent package to the child package. If a global variable
exists in the child package, DTS updates the child's global variable to the parent's
value. If the global variable doesn't exist in the child package, DTS creates it.
</Quote>
It would *seem* that my understanding of this is accurate. Though, clearly I'm still
doing something wrong...
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:OvKJxQFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
> A better question might be, what exactly do the two tabs do? That is, if I want to
> propagate my out (caller) package's GVs to the inner (callee), do I do that from the
Outer
> Package tab? Or should that be done from the Inner Package tab?
>
> "John Peterson" <j0hnp@.comcast.net> wrote in message
> news:eyt8UOFTEHA.2692@.TK2MSFTNGP09.phx.gbl...
>

Friday, March 9, 2012

PROBLEM: Grouping tasks: Connections disappear ?

Guys,

anyone seen this before?

I've just finished me lovely big package.. decided to tidy it up and make it look nice...
(when will I ever learn?)

So I selected a few tasks, right clicked and selected "group". Named the group.....

And now all the connectors between the tasks in the group have disappeared.... tried ungrouping.. still not there...

The package still runs fine... the tasks are executed in the right sequence and all that... but the connectors are jut not visible...

If I try to recreate the connector I get an error dialog saying "Cannot create connector. Only one workflow can exist between the same two executeables.". So they must still exist...

It'd be ok to leave it as it is I suppose.. if I didn't now need to modify the precedence constraint on one of the connectors.... and I can't actually select the feckin connector..

Any suggestions? Any way to refresh the display? Have already exited the environment and come back in.. will try rebooting machine now anyway...

PJ

I've seen problems like this before. Sometimes moving the tasks about makes them reappear. If not, you might be stuck.

In my opinion its a bug.

-Jamie

|||

They're back!

Phew..

I started copying and pasting new versions of the tasks... thinking I could delete the old ones and reconnect the new ones...

And after the first copy and paste... the connections reappeared...magic!

Suppose its good to have a note about this somewhere in the forums for anyone else that comes on this problem...

Now I'm off to get this thing into Sourcesafe (which I should have done from the start)

Thanks Jamie,

PJ

Wednesday, March 7, 2012

Problem with xml configuration

<Configuration CnfiguredType="Property" Path="\Package.Properties[PackagePassword]" ValueType="String"><ConfiguredValue></ConfiguredValue>

</Configuration>

</DTSConfiguration>

I've a package using a xml configuration file. And i want to set the package password in the string above. But the thing is, it doesn't work. Here's what it looks like after i've putted the password.

<Configuration CnfiguredType="Property" Path="\Package.Properties[PackagePassword]" ValueType="String"><ConfiguredValue>value</ConfiguredValue>

</Configuration>

</DTSConfiguration>

But when i try to run it. It complains. So i've to set the password at the comand line using decrypt. Anybody got a similar problem? I really want to don't have to set the password in the command line.

Thanks,

Adriano Coura

I think, and someone else may correct me on this, that the package can't be opened in order to begin reading the configurations until a password is supplied.|||

jwelch wrote:

I think, and someone else may correct me on this, that the package can't be opened in order to begin reading the configurations until a password is supplied.

True.|||Then why there's the option to set the package password in the config file? Because it looks good? Can somebody explain to me that? I really would like to know.

Thanks|||

abcoura wrote:

Then why there's the option to set the package password in the config file? Because it looks good? Can somebody explain to me that? I really would like to know.

Thanks

It looks like that list of properties simply contains the list of public methods that are writable.

http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.package_members.aspx

Problem with WMI tasks : waiting for files in parallel in a SSIS package

Hi,

I have a problem with the task "event watcher".

I've made a query like the one in msdn (SELECT * FROM __InstanceCreationEvent WITHIN 10 WHERE Targetinstance ISA "CIM_DirectoryContainsFile" and TargetInstance.GroupComponent= "Win32_Directory.Name=\"e:\\\\temp\""). I have 20 similar tasks for watching in different folders, but when there are too much tasks in parallel, it doesn't work anymore. I change the numbers of executables to 128 (in the general properties of the package (to test)) but it doesn't seems to work.

I don't understand why it works when there are only 1 or 2 (6 seems to be the maximum) tasks and not if there are more than 6.

Could you help me with this issue?

Configuration : Windows Server 2003, SQL Server 2005, SSIS, Sql Server Agent

Thanks a lot.

Julien.

I forgot to tell you that the package work when I execute it on debug, on the local machine but not on the server with a sql job.

Thanks.

|||

I don't know anything about WMI, but it looks like you're waiting for files to be created. Have you looked at the File Watcher Task that's available for download from SQLIS.com?

http://www.sqlis.com/23.aspx

Hopefully someone will have an idea about the WMI problem, but this might get you around the problem in the interim...

|||

Hi,

I don't really want to add tasks that are not supported by Microsoft, that's why I tried this WMI stuff.

Any idea?

Thanks.

Julien.