Some time While trying to save ssis packages .The save as window appears and it prompts "the .dtsx file already exist and want to replace or not?"
If i press yes it displays "The operation could not be completed".I am using a SSIS 2008 R2.Is it some kind of bug?
If not what is the solution?
Related
The Problem
I'm using a scheduled task to open an MS Access database, run a macro to email a report in PDF format, and then close the database. The report is relatively basic and the macro simply uses the EmailDatabaseObject action to export & email the report in PDF format.
This has been running successfully on a daily basis for the past 4 years on a Windows 7 machine running the latest version of Office 365 compatible with Windows 7.
I've recently updated the machine to Windows 10 and I'm now encountering a No Current Record error when running the scheduled task. After clicking OK to the error several times, Windows reports that MS Access has stopped working and the application crashes.
If I manually open the database and manually run the macro, everything is successful.
Setup
Windows 10 Pro 20H2 (19042.964) 64-bit
Office 365 Apps for Business 2104 (13929.20296) 32-bit
My Research
I've found this MS KB article describing the issue, however, this reportedly applies to MS Access 2003 & 2007. My report has no grouping, but does contain summations in the report footer. However the suggested solution is not feasible since removing the summations would remove necessary information from the report.
I've found this related question, however, this attributes the cause to accessing the database from OneDrive as opposed to a mapped network drive, whereas I am accessing the database from a mapped network drive.
This looks to be the same issue, but I cannot access the 'solution' at Experts Exchange...
What I've Already Tried
Rolling back Office 365 to an earlier version (version 2101).
Running the Scheduled Task with Highest Privileges - but this results in no access to mapped network drives.
Running the macro from a batch file.
Opening the database from another PC and running the macro from a batch file.
Perform the operations using the AutoExec macro rather than invoking a specific macro by name.
Imported all objects from the database into a new local database.
Exporting the report as a PDF locally using the ExportWithFormatting action.
Using the DoCmd.SendObject method to email the report - this results in MS Access immediately crashing.
Changing the default Windows printer & default report printer to 'Microsoft Print to PDF' to rule out possible printer driver issues.
Current Workaround
I've found that this error only arises when the export format is set to PDF; as such, my current workaround is to export the report to RTF format - but this is obviously not ideal.
Update
I've now systematically removed items from the report until I was able to run the report successfully from the scheduled task.
I removed items until I was left with a single static label in the Report Header and a set of fields in the Report Detail referencing basic numeric & text data from a single table in the database.
Removing the Report Header & Footer resulted in the report running successfully from the scheduled task, and so I determined that the issue must be caused by a setting associated with the Report Header/Footer.
I isolated the issue to the 'Force New Page' setting in the Report Header:
With this set to 'After Section', the report crashes; but if this is set to 'None', the report is successful.
However, when setting this to 'None' in the original report, the report still crashes when run from the Task Scheduler and output to PDF.
Steps to Reproduce the Problem
I've uploaded an incredibly basic database here, containing a single table, a single report, and a single macro which executes the ExportWithFormatting action followed by the QuitAccess action.
To reproduce the problem, open a command prompt window and issue the following commands:
cd C:\Program Files (x86)\Microsoft Office\root\Office16
msaccess.exe C:\YourPath\test.accdb /x macro1
MS Access should then open and you may be presented with the 'No Current Record' error.
Has anyone else encountered this issue and knows of a solution?
Many thanks for your time.
enter image description here
I am not able to execute this package? i fixed run 64bitrun time to false and used Provider=SQLOLEDB
my source is oracle and destination is sql server
Your package is set to Work Offline mode. You can change this by going to the menu bar. This feature is added to avoid long open times when packages are large.
SSIS -> Work Offline
http://agilebi.com/jwelch/2009/05/12/setting-work-offline-without-opening-the-project/
I have converted my project to Project deployment model. When I was converting there was a checkbox which said “Remove configurations from all packages after conversion" and I did not check it when I shouldn't have. Now all the configurations are part of my local project. Is there a way I could remove all the configurations after the conversion is complete?
Thanks
You can try this and let me know if it works:
Double click on package to open and see its properties in right
side.
Click three dots in configuration as shown in image.
Now
enable the package configuration. It should show your config which
you can simply delete.
I know this is old, but I came across the same issue and hoping this will help someone. I am using Visual Studio 2017 v15.9.11 and SSDT v15.9.0 on Windows 10 Enterprise. This was done for a package destined for SQL 2016, but I believe it would work on any package for SQL 2012+.
You can remove/disable package configurations after conversion by doing the following:
Find your dtsx file in Solution Explorer
Press F7 (or right-click the package > View Code)
Search for the <DTS:Configurations> element and remove the entire section
Save the file and re-open in designer view. Right-click the package and "Package Configurations..." should no longer be in the context menu.
Example from one of my packages - this is what was deleted:
<DTS:Configurations>
<DTS:Configuration
DTS:ConfigurationString=""CONFIG";"[dbo].[SSIS_CONFIG]";"YourConfigName1";"
DTS:ConfigurationType="7"
DTS:CreationName=""
DTS:DTSID="{C2C3EDFC-392A-401F-AC75-4D4C82A9CD68}"
DTS:ObjectName="Configuration 1" />
<DTS:Configuration
DTS:ConfigurationString=""CONFIG";"[dbo].[SSIS_CONFIG]";"YourConfigName2";"
DTS:ConfigurationType="7"
DTS:CreationName=""
DTS:DTSID="{A7F0C4DD-4891-44E1-817A-AB8431DA6509}"
DTS:ObjectName="Configuration 2" />
</DTS:Configurations>
I've gone through this URL:
How to loop through Excel files and load them into a database using SSIS package
And I followed the same steps mentioned there but I got this warning:
[Excel Source [14]] Warning: The external columns for component
"Excel Source" (14) are out of synchronization with the data source
columns. The column "state" needs to be added to the external columns.
The external column "state " (27) needs to be removed from the external
columns.
and this error:
[SSIS.Pipeline] Error: "component "Excel Source" (14)" failed validation
and returned validation status "VS_NEEDSNEWMETADATA".
I have found with this error, it is sometimes fixed by simply double clicking on each of the components, viewing the columns and various transformations, then pressing OK. I then save and re-run and it works. Make sure no red x's are lingering around or any other warnings.
The reason for this error is change in metadata, in my case a column name was renamed in Excel source. Verify the Excel column names and respective mapping.
There is problem with excel source when you are working on it. There are some steps to avoid it:
1) make sure you get the Excel connection and do not change the excel file connection string or folder( physically don't move the file)
2) Check the Red Cross (X), if you see that locate the arrow in excel file source and it will show you the error code.
3) Open the excel source and check the column and check the preview
4) click ok
Note: you should not have Red Cross(X)
The column's name is different. You have a space in de the name "state" vs "state ". And it's case sensitive too.
Remove the unused or blank excel sheets from excel source and try to execute the package again.
This happens when you change the excel which you predefined in your connection manager during development. If you want to change the excel, make sure you do the changes in excel connection manager too(though you have configured to make use of other names).
I have a relatively big SSIS package which I'm trying to edit. I basically need to update a query on an Execute SQL Task. Problem is the solution is not saving the query when I do the change. I open the SQL Task, change the query and close the task. I verify the change before saving and it's there but as soon as I click on the save button the change on the query disappears.
I verified for opened instances of the package but there are no other sessions on the machine. It does seems to be saving correctly on other packages included in the solution, but for some reason is not saving on my main package.
Make sure you have a backup copy of your package before you try this:
close the package (but keep the solution open)
right click the package and view code
search for your query and replace the query text with your new query text
save it
now double click the package to open it up like you normally do and view the query