SSIS : Stored Packages Error - MSDB
Aug 22, 2005Hi All
View 4 Replies
ADVERTISEMENT
SSIS - Browse MSDB Stored Packages Error
May 10, 2007I've just installed sql 2005x64 and sp2 on a active/passive cluster on 2003. Everything is working fine except browsing the stored msdb packages in SSIS. Remote acces is enabled - as are named pipes. I've tried doing this on the local server as well. I was able to create a maintenance plan and run it with no problems.
We got an error during the install pertaining to SSIS, but hit ignore and it went on successfully.
It was - failed to install and configure assemblies .....MSMQTask.dll in the com+ catalog. Error -2147467259.
description: Error HRESULT E_FAIL has been returned from a call to a COM component.
The browsing error is below.
Thanks!
Sam
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
------------------------------
BUTTONS:
OK
------------------------------
List Of All SSIS Packages Stored In MSDB
Mar 14, 2006Hi,
I am writing one program in vb.Net where I need to bind a treeview with all the SSIS packages stored in SQL server MSDB database.
Is it possible to get all the SSIS packages by using T-SQL query or Object model ?
Thanks
About: Deploy SSIS Packages To MSDB
Apr 10, 2008Hi, everyone,
Here's the situation:
I want to deploy my SSIS packages on SQL's MSDB database, but i can't open the MSDB directory
in Integration Services's Management Studio.
The error message said :
can not load files or components System.EnterpriseServices.Wrapper.dll'
System can't find the special file。 (MsDtsSrvr)
------------------------------
can not load files or components 'System.EnterpriseServices.Wrapper.dll'
System can't find the special file。 (System.EnterpriseServices)
Exception happened whith HRESULT: 0x80070002)
I had confirmed my .net framework is 2.0.50727, Wrapper.dll version is 2.0.50727.1433,
SQL DataBase Engine version is 9.0.3042, Integration Services version is 9.0.3054
This problem happened after i update Integration Services to SP2
Any ideas how to solve it
Thanks a lot.
SSIS Editing MSDB Packages
Jul 25, 2007Since I'm new at SSIS, just wondering how you edit a SQL Server 2005 SSIS stored Package saved in the MSDB? I'm used to SQL 2000 DTS, etc.
SQL 2012 :: Refreshing MSDB SSIS Packages From One Server To Another
Mar 25, 2015I was recently tasked with creating an automated process to refresh SSIS packages from MSDB on one server to another and I decided to go the route of using Powershell, however this wasn't as straight forward as I originally imagined so I thought I would share my solution in case others encounter the same request. The below PowerShell code will create all Integration Services folders from the source MSDB (that contain SSIS packages) on the target instance of MSDB then copy all packages to the proper folder locations. The /QUIET option is used to automatically overwrite packages that already exist on the target so make sure you want to overwrite the current versions of your packages before executing.
[Reflection.Assembly]::LoadWithPartialName("Microsoft.SQLServer.ManagedDTS") | out-NULL
$app = New-Object Microsoft.SqlServer.Dts.Runtime.APPLICATION
$SourceServer = "<source server name>"
$TargetServer = "<target server name>"
$Packages = Invoke-Sqlcmd -MaxCharLength 10000000 -ServerInstance $SourceServer -Query "
[Code] .....
Problem Opening MSDB Folder Under Stored Packages
Jun 6, 2006I am able to connect to Integration Services in MSSMS. However, when I try to expand and click on MSDB under Stored Packages, I get a Login Timeout expired error. I get this error both locally, and remotely. Error message suggested "does not allow remote connections", but I checked Surface Area Configuration, and remote connection is already enabled. Moreover, I get the same error even when connecting locally.
any ideas?
Error Trying To Import Packages To The MSDB
Jun 5, 2006When I try import a SSIS package into the MSDB I get the following error message:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
The .Net Framework OleDb Data Provider requires Microsoft Data Access Components(MDAC) version 2.6 or later. Version 2.12.4202.3 was found currently installed. (MsDtsSrvr)
------------------------------
BUTTONS:
OK
------------------------------
I do have default instance installed and the SSIS servie is running. When I look at the SSIS service configuration it shows a period for the server which I thought meant local host. Also I have MDAC 2.8 installed. What else do I need to look at?
SQL Jobs Calling SSIS Packages Within MSDB Not Referencing Connection Info In Config Files
Nov 13, 2007I have deployed to production a number of nested packages (parent packages that call child packages) to the SQL msdb via the Save As option rather than building a deployment utility. These packages reference configuration files in a static location off of the c: drive on the production server. In the development environment, when connection changes are made and I run the Reload with Upgrade option the connection manager takes on the new server and user id settings. However, out on the production side I get the following error from the SQL job log:
Cannot load the XML configuration file. The XML configuration file may be malformed or not valid.
As a result the SQL job uses the default connection information which references the development database rather than the production database. I did research the error but found no good solutions. Is there a way to ensure the configuration files are formed correctly and that the packages are correctly referencing the configuration files? We are trying to run the ETL updates via a SQL job.
Any suggestions? Thanks.
T
Integration Services :: How To Change SSIS Packages Deployed To MSDB - Image Data Type
Jun 22, 2014Is there a way to change an image data type? I want to make a change to some deployed SQL 2008 SSIS deployed packages. I have a TSQL SELECT that searches the packages for a string. But I would like to be able to change a string. I have googled it but cannot find anything.
View 5 Replies View RelatedSSIS / MSDB Stored Procedures / Permissions
Jul 23, 2007All,
Here is my problem, its very simple, But I dont have a solution.
To run / import / what ever I else I forgot (?) SSIS in SQL SERVER, what are permissions I'll need.
So far I have developed everything in BIDS, when I try to migrate it to a sql server by using Import package in Integration Services I got the below error.
TITLE: Import Package
------------------------------
The EXECUTE permission was denied on the object 'sp_dts_listpackages', database 'msdb', schema 'dbo'. (Microsoft SQL Native Client)
------------------------------
ADDITIONAL INFORMATION:
The EXECUTE permission was denied on the object 'sp_dts_listpackages', database 'msdb', schema 'dbo'. (Microsoft SQL Native Client)
The error is very clear in itself, While I have raised a request for the execute permission of this stored procedure, i also like to know what kind of permissions I will need in MSDB to work with out any problems. So that I dont have to go to DBA for execute permission for each error I may get for this.Right now I dont have execute permission on any of the Stored Procs in MSDB.
If any body can show any pointers that would be help full.
SSIS Error Message When Trying To Open MSDB In Management Studio
Jan 4, 2006Hi all,
I get this error when trying to open folder MSDB in management studio.
I'm running Win 2003, SQL server 2005 64 bit on AMD with two instances of SQL.
Any one that have a solution ? I havent found any thing that works.
If I enable VIA in SQL Server I can't start SQL Service
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
VIA Provider: The specified module could not be found. (Microsoft SQL Native Client)
------------------------------
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
VIA Provider: The specified module could not be found. (Microsoft SQL Native Client)
Strange Packages In MSDB - Where Are They Coming From?
Aug 10, 2007Hello:
I see some packages in the MSDB folder in Mgmt. Studio that I cannot figure out where they are coming from. The SSIS project in BIDS does not contain them, I do not see it in the Deployment folder, nor do I see it in the destination folder to which the manifest file deploys the packages. Which folder location am I missing? Each time I delete them they keep reappearing when I deploy.
Deploy Packages To Folder Other Than MSDB
Apr 10, 2007
Is it possible to create a folder within the MSDB folder in Integration Services and deploy packages in it?
Deploy Packages To An MSDB Subfolder
Nov 21, 2005In SSIS you can create subfolders in the MSDB folder. However, when deploying a SSIS solution to the server, it seems you cannot specify a subfolder. When selecting MSDB as the target, all packages in the solution end up directly underneath the MSDB folder.
View 4 Replies View RelatedDTS Migration Wizard, How To Edit MSDB Packages?
Oct 30, 2006Thanks to Sean for helping me find the migrated packages. I'd like to edit one of the connections on a bunch of packages that I migrated. I see in the Run Package there are configuration options that would allow me to mofify the connection string at that point in time, but I would like to modify the package so it has the new connection string. I was thinking I could access it in BI Dev studio, but I'm not sure how to get to it. I suppose I could migrate to a file and then edit the file prior to importing, but I'm curious if there's a way I can modify the packages that show up under Integration Services/Stored Packages/MSDB.
Thanks,
John
Running SSIS-packages In Stored Procedure Using Dtexec
Apr 2, 2008
Hi,
I'm running several SSIS-packages in stored procedure using dtexec. Actually, there is a software that is running the procedure, but that's not important here.
The problem: if some of the packages failes, the whole procedure does not fail and I don't know if all the packages are successfully completed.
Here is a sample list of ssis-packages from procedure:
exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedataaaa.dtsx"'
exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedatabb.dtsx" '
exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedataccc.dtsx"'
exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedataddd.dtsx"'
exec xp_cmdshell 'dtexec /f "E:SSISSourcedataSourcedataeee.dtsx"'
So, if eg bbb.dtsx would fail, is it possible to get the whole procedure failing?
To List Ssis Packages Stored In File Folder
Nov 13, 2007Hi,
newbie to sql2005. I am trying to write a VB.NET program to list all ssis packages we have stored in a file folder (not in MSDB) where both SqlServer and ssis servers are located. These packages currently running on daily basis by automated jobs with no problem.
I have found the following link on the web that includes VB.Net program. If you scroll down under Example (SSIS Package Store) , you'll see a VB.NET program that I am trying to get it to work for me but keep getting error message like "Cannot find folder......"
http://msdn2.microsoft.com/en-us/library/ms403343.aspx
My goal is to:
1. List all ssis packages stored in the file systems (.dstx)
2. List DB source and distination providers(tables in/out) in a ssis package
3. List properties for DB providers
4. List FlatFile & Excel file provider properties in a ssis package.
My assumption, but not sure, is that I may need to register this file folder (where packages are located) to the SqlServer if that is not done already. Any command or sys table in Sql2005 to figure this out?
I would appreciate any help on this in advance.
Thank You.
Encrypt Required To Connect To Msdb Deployed Packages ?
Mar 15, 2006Hi There
I am using SS2005 Enterprise Edition, proper release version not a ctp or anything
When i try navigate to my packages in MSDB i get the following error.
Encrypt not supprted in Sql Server.
I have done some checking and it is a known fact the sql server will enxrypt packages, and that the resolution is to use certificates.
Also some indications from links i have found that this is just a ctp or beta version issue.
Can someone please tell me if there is anyway around this besides certificates.
One is to use file system for packages, but how can i at least delete the packages deployed to sql server so far ???
nxPlease help , Thax
How To: Deploy Packages To A Subfolder Under MSDB Using Deployment Wizard
Jan 21, 2006Hi ,
I'm deploying the packages to SQL Server using the deployment utility. It goes through. However i wish to organize the packges into folders on the SSIS Server -> MSDB.
I'm able to create folder under the MSDB node. By default "Maintenance Plans" exists. But while deploying the package to the server i'm unable to specify the folder into which the package to be deployed.
Is this a known gap in the deployment wizard or am i missing something?
MTIA.
ERROR EXECUTING Ssis PACKAGES
Jan 18, 2008HI ALL.
I HAVE A PACKAGES WHICH THEN EXECUTES CHILD PACKAGES. tHE CONNECTION managers are specified. and environmental variables are saved on xml file. when i run(debug) parent packages on BIS , it gives me error saying the "error loading package file "childpackage_name.dtsx1st ".the system canot find the file specified.
how ever if i build solution it gives me output saying build successful..
i do not ge this..
anyhelp guys.
Error Handling For SSIS Packages In .NET
Oct 15, 2007Hi guys,
i'm running my SSIS package via a web application,
Microsoft.SqlServer.Dts.Runtime.Application app = new Microsoft.SqlServer.Dts.Runtime.Application();
Package pkg = app.LoadFromSqlServer("\send mail test", "localhost", null, null, null);
Variables vars = pkg.Variables;
vars["username"].Value = "C# user Name ";
vars["message"].Value = "C# body text";
DTSExecResult result = pkg.Execute();
//MessageBox.Show(result.ToString(), "result from dts"); --app mode
now sometimes the "result" variable return Failure, but i don't know what's wrong, when i run the package in debug mode (in VS) it works fine. DTSExecResult only returns "Success" or "Failure", is there a way to find out more information about the result. like why did the package fail?
the ssis package is built with event handlers but they don't get triggered. it's just when i execute from the web it just returns failed. i checked all the SQL connections as well, they are all fine, as they use SQL authentication, and connection strings are hardcoded as expressions.
any help?
SQL 2012 :: Import / Add Packages From MSDB To Data Tools / BIDS?
Jan 20, 2015I have a bunch of packages in msdb. Is there any easier way to move those packages from msdb to DataTools/BIDS, instead of adding one package at a time using ADD option.
View 9 Replies View RelatedExecuting Packages On SQL Server MSDB From Visual Studio Project
Jan 5, 2007I created several packages (MyProjectPart1 - MyProjectPart9) which I execute on the server directly(right-click package in integration services and execute). These packages alI deployed the server with logging and configuration files. Before deploying I edited the configuration file (changed all dependent file names and sql server name from default on my workstation to those unique to the server I'm deploying it to) and then ran the manifest file which pushed it onto the server. I then ran the packages from the server an it ran beautifully. I then tried to build a package which executes all the packages in the correct order (by adding 9 execute package tasks). The dependen files are on the E: emp folder on the server.
I have included the error messg...but it looks like it's looking for dependent drives on the C drive on my workstation. I don't get this? How do I supply configuration files? Why is it executing differently when I call it from package execute task and when I execute it on SQL Server
SSIS package "RUN_MY_PACKAGES_ONSERVER.dtsx" starting.
Information: 0x40016041 at ProjectInfo_NET_SSISA: The package is attempting to configure from the XML file "C:TempMyProjectPart1-03-2007-MyProjectPart1.dtsConfig ".
Error: 0xC001404B at MyProjectPart1, Log provider "SSIS log provider for Text files": The SSIS logging provider has failed to open the log. Error code: 0x80070015.
The device is not ready.
Error: 0xC001404B at MyProjectPart1, Log provider "SSIS log provider for Text files": The SSIS logging provider has failed to open the log. Error code: 0x80070015.
The device is not ready.
Error: 0xC001404B at MyProjectPart1, Log provider "SSIS log provider for Text files": The SSIS logging provider has failed to open the log. Error code: 0x80070015.
The device is not ready.
Error: 0xC002F304 at Drop Unecessary Tables, Execute SQL Task: An error occurred with the following error message: "The device is not ready.
".
Task failed: Drop Unecessary Tables
Warning: 0x80019002 at MyProjectPart1: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
Task failed: Execute Package Task MyProjectPart1
Warning: 0x80019002 at RUN_MY_PACKAGES_ONSERVER: The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "RUN_MY_PACKAGES_ONSERVER.dtsx" finished: Failure.
Error: Could Not Get A List Of SSIS Packages From The Project.
Apr 26, 2007Hello,
I have a SSIS package and I am trying to build it using devenv.com from command line. It gives me this error:
Error: Could not get a list of SSIS packages from the project.
However if I open the project in Visual Studio it builds properly. In project property I have set CreateDeploymentUtility=true.
This is what I do from command line:
devenv.com MySSIS.sln /Build "Development|Default"
Any idea what I should do ?
Thanks
Deval
SSIS Error With Duplicate IDs Of Copied Packages
Nov 30, 2006Hi,
I recently encountered an error when I created several copies of one package.
It's always nearly the same package with small modifications. I call this packages from a parent package which is part of our datawarehouseing-framework.
The problem is, when copying a packages or using a packages as template the packages' IDs and Task's-IDs are the same. And this isn't only an issue concerning logging!! :
When the parent package calls one of the copied packages the first task is executed in every package parallely. Furthermore ... when I for example set a breakpoint on a data transformation task in one of the packages, the breakpoint is set in all packages on the same task! This is resulting in strange errors because the tasks-states and variable values seem to get mixed up.
Unfortunately there is only a possibility to change the package's ID, but the IDs of tasks are readonly!
One solution is, to create a new package and copy all the tasks to the new package which creates new IDs, but doing so, I have to manually recreate a long list of variables, all the configurations, all the connection-managers once again. Furthermore I loose the layout of tasks.
I found some posts about it here
http://groups.google.de/group/microsoft.public.sqlserver.dts/browse_thread/thread/6f85a31ea190608a/0eae312aa8440cf8?lnk=gst&q=pitfall&rnum=1&hl=de#0eae312aa8440cf8 or
http://groups.google.de/group/microsoft.public.sqlserver.dts/browse_thread/thread/760093d58bf6ccb5/32ced2f2020ef3f7?lnk=st&q=data+flow+task+id+copy&rnum=2&hl=de#32ced2f2020ef3f7
saying the issue will be fixed by SP2, but now I don't see any comment on it in the CTP of Service Pack 2.
Is there any solution to this problem or official roadmap about a fix from Microsoft??
Greetings Monte
Error Executing, SSIS Packages Coppied From Another Server
Apr 16, 2007Hello All,
I am working on an application used to move packages (SSIS Packages) from one server to another.The packages are saved under MSDB folder.
Case: When the application is running on my system, i try to copy packages created from another server to my Server.I am using package protection level as "Server Storage". When i try to execute the coppied package from my system, it is giving me error.
An oledb error has occured, Error Code 0x80040E4D, An Oledb record is available, Source : Microsoft OLedb Provider for Sql Server", Description : "Login failed for sa".
Case : When the Package Coppier application is running on my system, i try to copy packages created on my server to my another Server.I use the same package protection level as "Server Storage". When i try to execute the copied package on destination server it is working fine without errors.
Please guide me on this issue, as soon as possible
Thanks And Regards
Subin
Error Importing SSIS Packages On SQL Management Studio
Aug 6, 2007
I encounter this error when importing SSIS packages using SQL Server Management Studio:
===================================
Unable to cast object of type 'Microsoft.SqlServer.Dts.ObjectExplorerUI.ImportPackageAsAction' to type 'Microsoft.SqlServer.Dts.ObjectExplorerUI.ISimpleAction'. (Microsoft.SqlServer.DtsObjectExplorerUI)
------------------------------
Program Location:
at Microsoft.SqlServer.Dts.ObjectExplorerUI.DtsServerMenuItem.Invoke(INodeInformation parent, String mode, String assembly, String type)
The Integration Services that I'm using has just been rebuilt due to problems after installing SP2. I'm using Integration Services 9.0.3042. I can't find anything having this same problem. Any help will be appreciated.
Thanks!
Error On Executing SSIS Packages On A Remote Machine Using Code
Apr 10, 2007Hello all,
I am trying to execute the ssis packages using code.These packages are hosted on remote server under MSDB in local Network.
Below is the code tried to Execute
--------------------------------------------------
DTSExecResult execRslt = _dtsxPackage.Execute();
foreach (DtsError dtserr in _dtsxPackage.Errors)
{
Console.WriteLine("Source: " + dtserr.Source + ", Description: " + dtserr.Description);
}
I get hte following Error
--------------------------------
"Dupaco Load MMAs"-------------"An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.".
"
"Data Flow Task" -------"The AcquireConnection method call to the connection manager "Dupaco" failed with error code 0xC0202009.
"
"Data Flow Task" ----------"component "OLE DB Destination" (119) failed validation and returned error code 0xC020801C.
"
"One or more component failed validation.
"
"There were errors during task validation.
"
When i try to execute the same code on the server where all the package are hosted. It is working fine.
More Info:
In thepackage we are using one "Source Flat file connection" and one "Oledb Destination connection"
Please help me to solve this problem, as my client needs it very badly
Thanks
Subin
Access Denied Error When Calling Several SSIS Packages In A Chain
Jun 22, 2007Hi.
I have problem executing several SSIS-packages in a chain.
To be more precise:
I have implemented a Biztalk 2006 application which via a local webservice executes an SSIS package. The package it self calls another SSIS package, which is located in the same folder as the calling package. The second package then calls a third package etc.
The problem arises, when the first package calls the second package. An Access Denied exception is received. Can any one explain me how to fix this?
The user connected to the application-pool that the weservice is running under, has execution-rights on all of the packages.
Thanks
Execute A Stored Procedure Which Calls SSIS Packages Using A Proxy Account For Non Sysadmins In Sql Server 2005
Sep 18, 2007
Hi all,
I have a problem while i create a proxy account.The situation is like this...There is a user who has an login in to the server.He has a stored procedure which calls some on the SSIS packages and XP_cmdshell...so this stored procedure basically load some data in to the tables .So for the login in order to execute the stored procedure as he is not a Sys admin I have created a proxy account in my account as Iam an SA and then in the proxies and in principals I selected his login name and this way I have created a credential and a proxy account.
Now the problem is if he logins with his id and password and try to execute the stored procedure it gives an error message
Server: Msg 15153, Level 16, State 1, Procedure xp_cmdshell, Line 1
The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '##xp_cmdshell_proxy_account##' credential exists and contains valid information.
....so this mean the login is not able to see the proxy account.So what I did is I created a job and then in the job owner tab I have selected his login and then created a step with the type operating system (CmdExec) as I need to just execute the stored procedure and used the proxy account that I have created.
so I gave the command -- exec <stored procedure> --.
But this job fails and gives the error message as
[298] SQLServer Error: 536, Invalid length parameter passed to the SUBSTRING function. [SQLSTATE 42000]....
So now ....first My question is am I doing in a right way....if its right then why Iam not able to execute the stored procedure.
If there is any other way through which I can execute the stored procedure using a proxy account for the logins who are not sys admins....please do let me know.....
Thanks
Raja.V
Calling SSIS Packages From ASP.NET - Packages With File System Tasks End Abruptly
Jan 9, 2007I've run into a problem with SSIS packages wherein tasks that write or copy files, or create or delete directories, quit execution without any hint of an error nor a failure message, when called from an ASP.NET 2.0 application running on any other machine than the one where the package was created from. By all indications it appeared to be an identity/permissions problem.
Our application involves a separate web server and database server. Both have SQL Server 2005 installed, but the application server originally only had Integration services. The packages are file system-deployed on the application server, and are called using Microsoft.SqlServer.Dts.Runtime methods. For all packages that involve file system tasks, the above problem occurs.
When the above packages are run using the command prompt (either DTEXEC or DTEXECUI) the packages execute just fine. This is expected since we are using an administrative account. However when a ShellExecute of the same command is called from ASP.NET, the same problem occurs.
I've tried giving administrative permissions to the ASPNET worker process user to no avail.
I have likewise attempted to use the SQL Server Agent job approach but that approach might not be acceptable for our clients since it means installing SQL Server 2005 Database services on the application server.
I have read the relevant threads in this forum, namely http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1044739&SiteID=1 and http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=927084&SiteID=1 but failed to find any solution appropriate for our set up.
Anybody got any idea on how to go about this?
SQL 2012 :: Error Executing Packages In SSIS Project On Server After Editing On Client
Sep 24, 2014I am building a bunch of packages on our new server and all was going well until I edited the project using the client tools on my PC. I now receive the below error if I try to execute any of the packages on the server (all is still fine on the client). I have scoured the net but I don't seem to be able to come up with a solution. I have tried altering the folder & object permissions for my login (that created the project on the server and edited using the client) but I still get the error.
ERROR:
TITLE: Microsoft Visual Studio
------------------------------
Failed to start project
------------------------------
ADDITIONAL INFORMATION:
Exception deserializing the package "Access to the path 'G:VisualStudioTestTestbinDevelopmentTest.ispac' is denied.". (Microsoft.DataTransformationServices.VsIntegration)
------------------------------
Access to the path 'G:VisualStudioTestTestbinDevelopmentTest.ispac' is denied. (mscorlib)
------------------------------
BUTTONS:
OK
------------------------------