As I said, the Execute Task is not changing any code (I don't think), so I shouldn't have to check out or set the package to not be read-only.
Main Topics
Browse All TopicsI've got a SSIS package solution (in Visual Studio 2005) which is linked into Visual SourceSafe 6. If I try to execute a task, for some reason it's prompting me to check out the package.
Since I'm not making any changes to the code, I don't wish to check it out.
Is there somehow I can execute a specific task without checking out the package?
Thank you.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
My package has 'Execute SQL Task' (some with bypass prepare set to true and others set to false) and 'Data Flow Task' components.
Regardless of which item I select and right click and select "Execute Task" it prompts me to check out the package. If I click cancel on the check out, the task doesn't execute.
Nonetheless, I can execute the whole package (ie, F5 or 'Start Debugging') without being prompted to check out.
In my Visual Studio Editor, under Tools -> Options, I have the following set up under Source Control:
Plug-in Selection: Current source control plug-in set to 'Microsoft Visual SourceSafe'
Environment: Source Control Environment Settings set to 'Custom', and none of the checkboxes on that page are ticked, and in Checked-in item behaviour I have 'Prompt for check out' for both On Save and On Edit.
Plug-in Settings: Plug-in Settings set to 'Custom' and the Perfrom background status updates is checked. If I click on the Advanced button, I get a SourceSafe Options dialog. The 'General' tab has got all the checkboxes unticked, with 'Check in unchanged files' set to 'Undo Check Out', 'Use visual merge' set to 'Only if there are conflicts' and 'Double-click on a file' set to 'Ask'. The Local Files tab has got the following two items checked (everything else is unchecked): 'Use read-only flag for files that are not checked out' and 'Copy keyword-expanded files into working folder', and the 'Compare files by' set to 'Checksum', 'Replace writable files' set to 'Ask' and 'Set date/time on local files' set to 'Current'. The last tab, Integration, has got all checkboxes checked ('History' and 'Diff'), and 'Choose SourceSafe Database' set to 'Prompt'.
I may have spoken too soon. My copy does check out the package when I try to execute a task. If I run the whole package it doesn't ask. It seems like this is a bug that's been present in SQL Server 2005 and hasn't been resolved at least as of SP3 which is installed on my machine. I'm thinking SSIS tries to write something to the package when a specific task is executed as opposed to the whole package.
I looked around for an answer to this and all I found were other people having the same issue. I don't believe there is a way around this issue, at least with SourceSafe. I personally don't execute single tasks often, and if I do, it's usually after I've had the package checked out and edited already.
You can wait to see if someone else has a better response or a solution I'm unaware of.
Business Accounts
Answer for Membership
by: pratima_mcsPosted on 2009-10-12 at 00:03:17ID: 25549045
you can't Execute Task in SSIS If Package id Readonly that is not checked out
You can undo checkout when your work over
Or change the Readonly property of package