Hi, the message below is generated when I try to generate an SSIS configuraiton file. The link does not provide any help. Do you have any suggestion what could cause this error?
Thanks, Piet
==========
TITLE: Microsoft Visual Studio
------------------------------
Could not generate the configuration file. (Microsoft.DataTransformationServices.Wizards)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.Wizards.ConfigurationWizardPages.ConfigurationWizardSR&EvtID=CouldNotGenerateConfigurationFile&LinkId=20476
I am using Office 2007 beta. I have a SSIS package that exports the records from sql server to excel file, when number of records is less than 24000 then it exports well, but if number of records is greater than 24000 than it does not export anything to excel file.
But when I give administrative privilages to the service account under which the SSIS package is running, it export even more than 24000.
On prod server giving administrative privilages to service account is not a good option. I don't know what are the minimum permissions it needs while exporting more data into excel 2007 file.
I thought this is the problem in office 2007 beta, but same behaviour is with RTM also.
We are deploying our SSIS packages into different folders. For example: Test1 est2 production
Test1 points to the Test1 database, etc.
So, I configured my SSIS package to use a database connection called dbMAIN.
I then setup the SSIS File Configuration (XML) so that "dbMain" points to Test1. This xml file, called Global.dtsConfig, sits in C: est1, the same place as my ssis.dtsx file.
I want to copy my dtsx file and my dtsconfig file into est2 and production. The problem is that the the location of dtsconfig is HARDCODED in the ssis package!
How do I dynamically change it?
I tried to hardcode the location to ".Global.dtsconfig", but that did not work! Please advise!
In my project, developers enable configuration on the packages they develop. This means that if a project has 100 packages, each one has its own configuration file.
If our primary database server changes, I have to go an update 100 configuration files.
This defeats the purpose of having a configuration file in the first place.
I want to have a configuration file which contains common settings for all the packages in the project.
At the same time, I should have the flexibility of having individual configuration files for the project.
I have problems when exporting data into Excel file from SSIS. It all works fine with numeric columns but an apostrophe is attached at the beginning of each text cell. I tried using derived columns and data conversions but it didn't work. It seems to me that problem is in 'excel destination' task... I saw many people had this kind of problems too... Is there any solution possible?
Thanks to some earlier help from this forum, I have my package running using configuration files and Windows Authentication. However, when I try to execute the package using Sql authentication, login fails for the user i am specifying. When I check out the configuration file, the connection string does not contain the password. I added the password to the connection string, but it does not cone back. I followed the instructions found on the following site:
I have an SSIS package (which is already delivered to the customer, so I can't change it), but I want to switch off (disable) one of the elements. I use a dtsConfig file (XML), so I want to just send an update to that config file to switch off the element.
So, I used the Package Configurations Organizer to generate a new config file with the element switched off, and it generated the following:-
<Configuration ConfiguredType="Property" Path="PackageRun Data LoadForeach Data FileLoad Invalid Format Recs into rej_dat_format_errors.Properties[Disable]" ValueType="Boolean"> <ConfiguredValue>0</ConfiguredValue> </Configuration>
So I copied these lines into my "production" config file and ran the package, but got the following warning message:-
Warning: 0x80012017 at ImportData: The package path referenced an object that cannot be found: "PackageRun Data LoadForeach Data FileLoad Invalid Format Recs into rej_dat_format_errors.Properties[Disable]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
Can anyone explain why? Is there some issue with having spaces in the Path name perhaps? Is there some syntax to get around it? Why did it generate a Path that is wrong? Thanks - AA
Started: 10:48:56 AM Info: 2008-01-24 10:49:02.92 Code: 0x40016041 Source: SsisEndBatch Description: The package is attempting to configure from the XML file "C:Program Files (x86)Microsoft SQL Server90DTSPackagesBridgeNet.BI.SSIS.EndBatc ENDBATCH TEST ENV.dtsConfig". End Info Warning: 2008-01-24 10:49:03.15 Code: 0x80012011 Source: SsisEndBatch Description: Cannot load the XML configuration file. The XML configuration file may be malformed or not valid. End Warning
I've been given the task of migrating a DTS package to SSIS (neither of which I am particularly familar with). The first job in the DTS package is to read a .ini file and set a bunch of variables. These variables are then used throughout the DTS package. After running the DTS package through the SSIS migration wizard this job turns into an execute script task and I can't see if it is still reading the .ini file. However, the only real purpose of this step is to allow different parameters to be passed in development, test, production etc. So I am thinking this whole step can be removed and effectively replaced with a package configuration (I'll probably use an XML file). My understanding is that by selecting the name/value pairs as appropriate in the XML package configuration file means this values will be passed in at runtime and achieve the same functionality. Is this the correct way to do this in SSIS, or do I still need the .ini file and variables?
I am using the following useful article regarding exporting a multi-record file: http://vsteamsystemcentral.com/cs21/blogs/steve_fibich/archive/2007/09/25/multi-record-formated-flat-file-with-ssis.aspx
I have created the 2 datasources, ordering each on a field commmon to both.
I have created the two derived columns headers and am now moving on to the merge.
It is failing with the following error: "the input is not sorted"
And whilst I definitely have an order by on the query, when I look at the metadata between the datasource and the derived column, the Sort Key Position items displays "0" for all my fields, I was expecting the sort field to have a "1" in this column. What am I missing?
Hi, I am using custom dll in script component in SSIS package. This dll is looking for some configuration settings and dsplays the message as "Configuration section could not be found in the configuration source" . Please tell me the configuration source it looks for.
I'm exporting reports daily to a file share and I need to rename the reports with a pseudo time stamp.
Example: I have a report named "Disk Usage" and when I export (using a data-driven subscription) I want to rename it "Disk Usage - (Jan07)" - or something to that effect.
I cannot get the log file path read from the configuration.
If the path in the Connection Manager is invalid, package throws an error "SSIS logging provider has failed to open the log" instead of reading it from the config.file. What am I doing wrong?
Here is the portion of the config file. Everthing else is read from the config file correctly.
I have been able to export to Excel with success. However, here is a big issue
Destination spreadsheets that contain colums. This seems to work OK but what is strange (by design???) is that appearently it reads the first seven or several rows and then determines the data types (numeric or string). Why doesn't it just use the data types from the source fields? If the last row is column headings (strings, such as Jan, Feb, etc) it treats EVERY row data element in the column as string or character data type. Why??? For my testing, I had to put a full row of 0's in my monthly buckets, so the data would be imported as numbers in the spreadsheet, otherwise it was string or charater data type.
Please tell me there is some logical reasoning behind this Excel export "feature". Or is there someting I am missing? I really want the destination Excel spreadsheet to be a template and have formated Title, Headings (different fonts), columns etc. My thinking is that it would just drop the data at the end of the spreadsheet (in this case the first row following the column headings) with the same data types as the fields in the source. I hope I am wrong and there is away to accomplish exporting to Excel as described above. A very simple approach, Microsoft could have possibly taken is have the ability to specify the starting row, column as a propert(ies) in the Excel Destination object / control.
I am trying to create a package in BIDS that reads data from a table and exports it into a flat file (.csv). The file needs to have a row for the header and a row representing the column names as well as the data rows. My problem is: 1.I need to add a value in the header row that is a count of all the data rows. 2. I need to add the year and period based on the year and period in the data rows. (the year and period will always be the same in the data rows)
below is an example of what I want the file to look like (it is a delimited file)
1;Varese;O027200702ACT;F1_V4;BATCH;2326;test company CUSTOMER_ID;BU_ID;YEAR_ID;PERIOD_ID;ACTIVITY_ID;SCENARIO_ID;ACCOUNT_ID;DATA_UNIT_ID;DATA_VALUE 000001;ZA01000001;2007;2;01;1;70;ZAR;.04 000001;ZA01000001;2007;2;01;1;912;ZAR;6080374 000001;ZA01000001;2007;2;01;1;941;ZAR;-.16
The value in bold represent the values that i want dynamically updated...
200702 represents a concatenation of the year and period
I have a report returning about 50000 rows, when i export this into excel it takes a few minutes and the file size is about 13MB, When i try to open up a 13mb file it is so slow...it is better for me to execute the dataset in SQL analyser and copy the results directly into excel whereby the file is 8mb and opens up also instantly...
My exported version is just data and no graphics however the page appears to be ''white'' although i set the fill in excel to transparent...maybe this is making the file hard to open...
Anybody have problems with exporting to excel and actually able to use it without running into long delays due to the file size...what can i do to fix this
Hi, I have 2 very similar copies of a report. The only difference between them is that they point to different datasources. The report is fairly simple and contains a table with a group header and a detail row. Report A exports fine, however Report B does not export the values of the header row. I've tried a variety of output options to try to get the value in the export file, but all I get is textbox1, textbox2, etc. Does anyone have any ideas on what else I can check? This one report is the only one that is giving me trouble! Thanks in advance!!
I currently have a export that takes data from my SQL Server 2005 DB and exports it into Excel. This process works correctly. My excel template has the first row headers and the data is dumped in the row after the header. I would like to know if it is possible for me to add borders around my data without doing it within the template? I don't know how much data is going to be exported so I can't put borders within the template. I put borders around the headers to see if it will copy the formatting down to the data and it didn't. Thank You for any help.
Can network latency or insufficient memory cause SSIS packages to fail? I run an agent job that consists of many individual SSIS packages. Most of these packages read flat files from a network drive, format the data, and load the data into SQL Server tables. Each step normally takes only about 30 seconds. Occasionally, the same step that took 30 seconds would take over 5 minutes to process. Sometimes a step would fail with a package execution error (no other clue given).
It seems that after the server is rebooted, the job runs successfully. If a package step fails due to some sort of resource limitation, shouldn't the error be noted somewhere?
1. I am attempting to export data from a SQL DB (single table using a query) to a "flat file". 2. I would then like to take this "flat file" and import the data into a different SQL DB (same schema structure as first DB).
I have a request from a vendor to export data out of my SQL Server 2K database view to a 'flat fixed file'.
What kind of file is this exactly, not a .csv ? Does EM have the capabilities through the DTS wizard, by choosing the output to a text file and fixed width ?
I am trying to find a convenient way to export parts of tables to text files.
One way I see is BCP: Is there a way to avoid writing the command and options into the command prompt by hand? I.e. a way to write the commands into a text file and then to execute them?
Are there other ways? I`d like to find a way that a user who uses a web interface can use.
Is there a way to send the text files via mail to a remote user?
I have a record set I have to export on a weekly basis into a CSV file for a customer/client. One of the fields being included in the export is a TEXT field. When I export this field, the CSV file is truncating the record significantly.
Is there a way I can get the export to pass all the data in the TEXT field, or is this a limitation on the data transformation, or is it a limitation on the CSV file (because of the size/nature of the TEXT field).
Reading through the forums, I found some great imformation for importing/exporting an excel spreadsheet via a stored procedure, however, the amount of data I have won't fit in excel. Can someone help me export a CSV file via a stored procedure? I don't know if XML is the answer or if there is another way. I am able to use Bulk for an insert of a csv via stored procudure, although it doesn't allow me to use a variable for the file name and pass it in. We are currently using SQL Server 2000.
I am trying to setup ssis data flow package to export a smalldatetime field to just date only. I have changed the dattype to datbase date [DT_DBDATE] AND ALSO [DT_DATE] but it still exports datetime format. What is the best and easiest way to setup flat file connection manager to only export date and not the time. Do I have to add another setup to convert to date only?
I'm trying, through the SQL 2005 Mgt Studio, to export a simple table in a delimited format. I'm selecting a double quote as the text qualifier. My expectations were that only text type fields would be exported with the double quotes an numerical fields would not have any quotes around them. SQL 2000 does this just fine, but 2005 is exporting all my text type and numeric fields with double quotes. Is this a change to SQL 2005 or am I doing something wrong.
Hi i am trying to export data from .csv file to sql server and my data is coming as "xyz" where i want only to store as XYZ i am using derived column but i am not able to capture " and replace it what approach should i take here , also i am trying to convert String True to Boolean 1 and vice versa for False in database how do i do that please help me with this.
