Content Deployment Job - Schedule

I have a moderlately large publishing site collection with 600+ sub sites and 12000+ pages. I have received requests to increase the frequency of content deployment incremental jobs from once a day to once every hour. I have 4 web servers and 4 app
servers. My question is, will increasing the frequency of the job to every hour degrade the performance of live site? I am asking because as people are accessing my live site, the import job will be importing content too, correct?
I didnt see any best practice around how frequently should the job be run. MS only says that do no have a very long gap b/w jobs but nothing about how frequent is good and what is dangerous.
Regards, Mahesh

Hi Mahesh,
The performance of the content deployment job will be affected by many elements, so it depends on the situation what frequency the job should run.
As the content deployment incremental jobs deploys only the modified content and items directly linked to the modified content, this increases the chance for problems which can cause incremental content deployment to fail.
In case that you have a large content deployment running with several GB of content it can happen that the decompression phase takes longer than 600 seconds, and then there will be a timeout. To avoid such Timeout message, you need to increase
the RemoteTimeout value.
Please check the link below for more details:
http://blogs.technet.com/b/stefan_gossner/archive/2009/01/16/content-deployment-best-practices.aspx
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Similar Messages

AppParts and Content Deployment Jobs

One of our SharePoint customers' environment has a bunch of publishing pages with SP hosted AppParts on these pages.
Customer prefers Content Deployment Jobs to publish the pages from Staging to Production.
Is it a viable option to have the publishing pages with AppParts moved to production env using Content Deployment Jobs?
What are the other recommended options to move pages with AppParts from one env to another?

Hi ,
No, as the page which contains App Parts is related to a SharePoint Hosted App and a special isolated app domain.
For the issue, customer need to migrate the SharePoint Hosted App, such as change the SharePoint Site url in the properties of the SharePoint project , change the client web part page in the app part properties and so on.
Reference:
http://stackoverflow.com/questions/16830125/how-to-change-the-deployment-url-in-a-sharepoint-hosted-app-later
https://social.msdn.microsoft.com/Forums/en-US/31af83c9-e3d3-4d5c-9b6b-45ff44822176/sharepoint-hosted-app-migration?forum=appsforsharepoint
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Content deployment JOB

Hi,
I am running content deployment job since log between two farms, since long it has been running fine. Suddenly it starting running FULL instead of Incremental and exported 1300,000 document which never happened. s per our history in the full CD it used to
export max 200,000 contents and now in incremental it started exporting 1300,000 contents. Any idea what could be the reason, i feel it is taking full CD however surprised suddenly how come in between can take full CD.
-Shweta
Me

what i beleive, content deployment only run FUll when you create a new path and new job....after that all the time its incremental.
things to check which trigger this much items to export.
1) are you deploying the whole site collection or subset of the site collection...
2) any body edit the CD job and include more sites into the CD....
3) what you mean by content, is it images, documents, list items and users etc...check the export log.
4) check if any workflow or retention policy change some properties on the site which trigger this change.
5) did you guys restored the source site or deleted the target site?
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Content Deployment Job Stuck on Exporting Phase

I have my one site collection and i executed content deployment jon on that site collect and skip one site named current vaccancies which include 4500 Pages , images , etc.
I created another job for that skipped site to deploy content on production. But whenever i run Job my kob stuck on export phase always on this site. What is reason...
Please help me ..

Hi,
You can check event viewer -> Application logs to check event id 4958, 5323, 5325, 5335...then please follow URL
http://technet.microsoft.com/en-us/library/ee924661(v=office.14).aspx
Best practices for content deployment
http://technet.microsoft.com/en-us/library/hh292621(v=office.14).aspx
You can post your error, so we can help you further !!
Regards
Prasad Tandel

Using Managed Paths along with Content Deployment Jobs

I have a quick question relating to Managed Paths and Content Deployment paths/jobs. I have a main web app with about 10 or so managed paths underneath. So for example webapp.com/accounting, webapp.com/IT, webapp.com/marketing. Then I have
all my site collections grouped under each managed path. I'm trying to set up some content deployment paths and jobs to deploy into another environment. When I set it up at the main web app level, it only deploys content at that level and not through
the sites under the various managed paths. In this scenario, am I required to set up a content deployment path and job for each and every site collection?

Hi Mark,
Per my knowledge, the content deployment deploys content from a source site collection to a destination site collection.
The content deployment paths and jobs are defined at the site collection level, so if the select the root site collection as the source site collection, then only content in the root site collection can be deployed to the source site collection.
If you need to deploy other site collections’ content, then you need to create new content deployment paths and jobs to define the source site collection to be the site collection which you need.
More references about the content deployment:
http://technet.microsoft.com/en-us/library/ee721058(v=office.14).aspx
http://melick-rajee.blogspot.kr/2011/10/how-to-do-sharepoint-2010-content.html
Best regards.
Thanks
Victoria Xia
TechNet Community Support

SharePoint 2007 Content deployment Error: 'A folder with the name already exists.

Hi, In SharePoint 2007 one Content deployment job is failed with below error:
Content deployment job 'Remote import job for job with sourceID = some id' failed.The exception thrown was 'Microsoft.SharePoint.SPException' : 'A folder with the name PublishingImages/AEI-2014/Blue already exists.'
From last 3 days I am getting this error and previously this Job was running without any Error.
In Import Log file getting message: "FatalError: A folder with the name PublishingImages/sg-2015/yellow already exists."
Please tell me how to resolve the issue.

Hello,
It seems same folder exist in destination server that's why job is failing. You need to check destination server and remove the same name/GUID from site then try again.
See this technet for more info: (see "Conflicting content on source and destination" section)
http://technet.microsoft.com/en-us/library/dd795107%28v=office.12%29.aspx
Hemendra:Yesterday is just a memory,Tomorrow we may never see<br/> Please remember to mark the replies as answers if they help and unmark them if they provide no help

Alternative ways of Content deployment

Hi,
Can anyone suggest me the alternatives of Content deployment job? Instead of going with CD, is there any other way to help us to achieve the same?
-Shweta
Me

Hi Shweta,
For SharePoint 2010 content deployment , you can also consider backup &restore and WSP package.
http://blogs.msdn.com/b/russmax/archive/2009/10/21/sharepoint-2010-granular-backup-restore-part-1.aspx
http://technet.microsoft.com/en-us/library/cc262995(v=office.14).aspx
And there are some 3rd Party Content Deployment Tools:
http://www.quest.com/sharepoint/migration.aspx
http://spdeploymentwizard.codeplex.com/
Also you could write a web service or delve into the land of SharePoint Object Model coding, that scans the content of your staging environment and maps it into production.
http://blogs.technet.com/b/stefan_gossner/archive/2007/08/30/deep-dive-into-the-sharepoint-content-deployment-and-migration-api-part-1.aspx
Reference:
http://www.sharepointgeoff.com/content-deployment-whats-the-best-way/
Thanks,
Eric
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support,
contact [email protected]
Eric Tao
TechNet Community Support

Content deployment problem

An incremental content deployment job that has been working for years between two SharePoint 2007 farms has stopped working. There seems to be a problem with one of the sub-sites, but excluding it from the deployment job does not solve the problem and
as far as the logs say, some parts of that site are still being exported and imported (unsuccessfully).
The farms are both post SP3 but not exactly the same version. There also seems to be a slight difference between a specific list in the root sire between the two sites. I am sure the first difference has been around for a long time, the second one I am not
sure but I am quite positive the error in the import process does not refer to the list in question.
This is the relevant log fragment:
[3/16/2015 8:38:44 PM]: Verbose: Updating field ContentTypeId.
[3/16/2015 8:38:44 PM]: Verbose: Updating field _HasCopyDestinations.
[3/16/2015 8:38:44 PM]: Verbose: Updating field _CopySource.
[3/16/2015 8:38:44 PM]: FatalError: Object reference not set to an instance of an object.
   at Microsoft.SharePoint.Deployment.ContentTypeSerializer.GetContentType(SPContentType sourceContentType, ImportObjectManager importObjectManager, Boolean isParentSystemObject)
   at Microsoft.SharePoint.Deployment.ContentTypeSerializer.ProcessContentType(SPContentType sourceContentType, String contentTypeXml, ImportObjectManager importObjectManager, Boolean IsParentSystemObject)
   at Microsoft.SharePoint.Deployment.ContentTypeSerializer.SetObjectData(Object obj, SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
   at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType, Boolean isChildObject)
   at Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType, Boolean isChildObject, DeploymentObject envelope)
   at Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream serializationStream)
   at Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream serializationStream)
   at Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader xmlReader)
   at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects()
   at Microsoft.SharePoint.Deployment.SPImport.Run()
[3/16/2015 8:38:44 PM]: Progress: Import Completed.
[3/16/2015 8:38:44 PM]: Finish Time: 3/16/2015 8:38:44 PM.
[3/16/2015 8:38:44 PM]: Completed with 0 warnings.
[3/16/2015 8:38:44 PM]: Completed with 1 errors.
Changing the site selection or creating a new job with just the root site selected did not solve the problem either.
We currently cannot run a full deployment job because of disk space limitations.
Can we do anything besides creating a new content database and starting over?

Have you had a look at Troubleshoot content deployment and Stefan Goßner's Content
Deployment - Best Practices?
You may need to increase the ULS logging level for Content Deployment to see more information about what is happening.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Sharepoint 2013 Content Deployment Issue

I configured content Deployment from source farm to destination. The content is migarated from source to destionation and updates are went well. But when i update the attachement in Source, it is not getting updated in destination. I can find the below message
from import log
[2/18/2015 3:49:03 PM] [ListItem] [1_.000] Warning: Cannot add attachments because: The specified name is already in use.
The document or folder name was not changed. To change the name to a different value, close this dialog and edit the properties of the document or folder.
Please suggest me

Hello,
Looking at the last error message:
"The remote upload Web request failed"
there are a couple of possible reasons for this.
1. No space available on the destination web server
There needs to be enough disk space for the content to be uploaded to on the destination server. This is done in two stages - the first stage zips and copies the content to the destination server, and the second stage extracts the zip files and adds the
content to the destination server. You need enough space on the destination server to store the zip files and the extracted content.
2. Permissions on the destination server
The content deployment job needs to use a security account that has permission to the destination server farm to perform the deployment task.
3. Firewall/network settings
The destination server needs to be accessible by the source server.
Regards,
Gavin McKay

Sharepoint 2010 Content Deployemnt Job issue with duplicate fields in User information List

Hi friends,
I am facing below issue with the content deployment job.
It was working earlier. But now since from couple of days all the content deployment jobs in production environment are failing with below error.
Field name already exists. The name used for this field is already used by another field in the list. Select another name and try again.
ObjectName="User Information List".
When I check the fields in User information list in targeted site, I found couple of columns are dupicate like "ask me about",first name","Last name" etc.
Do i Need to drop target site collection or recreate with fresh content deployment job.
Please suggest.
Please help .
Regards
Subrat

Hi,
According to your post, my understanding is that you got duplicate field error.
Based on the error message, you can try to use the following code sample to remove duplicate records, and check whether it works:
http://social.msdn.microsoft.com/Forums/en-US/sharepointgeneralprevious/thread/41ee04bd-91fb-4bf9-932a-bac42c56c357
Here is a similar issue, you can also use the ‘RemoveDuplicateColumn64’ provided:
http://sharepointsurfer.wordpress.com/2012/04/27/how-to-fix-publishing-site-content-deployment-error-duplicate-first-name-column/
What’s more, as you had said, you can recreate a site with a fresh deployment job.
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Upgrade log file in MaintenanceLogs library breaks content deployment

I have two SharePoint 2013 farms: authoring and publishing target. Content deployment jobs are used to push changes from authoring. This has been working just fine until I applied the latest updates. The upgrade process create a log
files in the _catalog/MaintenanceLogs library. The Content Deployment process wants to deploy this list now. Since it already exists on the target, the import fails.
Has anyone run into this? Is there any way to tell Content Deployment to not export this? There's really no reason to publish this library. Any way to delete it on the target so it just gets re-created?
Ray Riopel

Hi,
Thank you for your question.
We are currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.
Thanks,
Linda Li
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Linda Li
TechNet Community Support

Hi any one please explain background job scheduling

Hi any one please explain background job scheduling . Good answer can be rewarded.
Thanks

Background jobs are pgms that are scheduled to be run in the Background without user interaction. So this can be done only for Type 1(executable) Program and not for Module-Pool Programs. Typically, a variant is defined and the pgm is run using the same.
The transaction code is sm36 -Define Background job. Using the Start Condition tab you can define when you want the job to run (specific time or if it has to follow after a particular job is done etc.,) Using the Step tab you can assign the pgm name and variant.
After the job is scheduled, you can check the status in sm37, along with the Job log and Spool.
For more info:
http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm

What is the spool, what is its role in background job scheduling

Hi,
I want to know what is meant by Spool request and spool number generated.
Tell about transaction SP01.
How it is linked to Background job scheduling.
thanks.
sam.

Hi,
Refer this link.
https://www.sdn.sap.com/irj/sdn/inf?rid=/library/uuid/7a5f4061-0a01-0010-c9bc-a4e4cb100438
About SP01.
Printing does not work in SAP. There is a printer definition for your local printer, but it does not work. Presuming that you use the program SAPLPD on your computer.
Boot your computer and start only the SAPLogon and the SAPLpd program.
Delete all of your old print jobs in the SAP system (Transaction SP01).Generate only one new print job.
Check that there is enough resource in your computer. Check the free memory (Win 3.1x) and the free disk space (The lists are temporarily saved on your disk).
Open the SAPLPD and read the print log in the window. The printer definition must correspond with the parameters shown here.
Check that the standard printer is on the same lpt (Win 3.1: Control panel, Printer) as defined for the printer (usually lpt1).
In Transaction SP01 read the protocol of your print job. Do not generate new print jobs! Wait till the SAP system changes the status of the print job.
If you can not find the print job in SP01 anymore, then the print job was successfully printed out. If it didn't come out on your printer and the SAPLpd didn't indicate an incoming print job, then the connection was realised with another PC. Then SAP printer definition you used, does not correspond with your computer.
Scheduling Background Jobs:
1.        Background jobs are scheduled by Basis administrators using transaction SM36.
2.        To run a report in a background, a job needs to be created with a step using the report name
and a variant for selection parameters. It is recommended to create a separate variant for each
scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.
company codes).
3.        While defining the step, the spool parameters needs to be specified
(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users
to find the spool request. The following parameters needs to be maintained:
a.        Time of printing: set to u201CSend to SAP spooler Only for nowu201D
b.        Name u2013 abbreviated name to identify the job output
c.        Title u2013 free form description for the report output
d.        Authorization u2013 a value defined by Security in user profiles to allow those users to access
this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching
authorization value in their profiles will be able to see the output.
e.        Department u2013 set to appropriate department/functional area name. This field can be used in
a search later.
f.        Retention period u2013 set to u201CDo not deleteu201D if the report output needs to be retained for more
than 8 days. Once the archiving/document repository solution is in place the spool requests could
be automatically moved to the archive/repository. Storage Mode parameter on the same screen
could be used to immediately send the output to archive instead of creating a spool request.
Configuring user access:
1.        To access a report output created by a background job, a user must have at
least access to SP01 (Spool requests) transaction without restriction on the user
name (however by itself it will not let the user to see all spool requests). To have
that access the user must have S_ADMI_FCD authorization object in the profile with
SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).
2.        To access a particular jobu2019s output in the spool, the user must have
S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used
in the Print Specifications of the job (see p. 3.d above).
3.        Levels of access to the spool (display, print once, reprint, download, etc) are
controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least
BASE access (display).
On-line reports:
1.        Exactly the same configuration can be maintained for any output produced
from R/3. If a user clicks u201CParametersu201D button on a SAP Printer selection dialog, it
allows to specify all the parameters as described in p. 3 of
u201CScheduling background jobsu201D section. Thus any output created by an online report
can be saved and accessed by any user authorized to access that spool request
(access restriction provided by the Authorization field of the spool request
attributes, see p. 3.d of u201CScheduling background jobsu201D section).
Access to reportu2019s output:
1.        A user that had proper access (see Configuring user access above) can
retrieve a job/report output through transaction SP01.
2.        The selection screen can be configured by clicking u201CFurther selection
criteriau2026u201D button (e.g. to bring u201CSpool request name (suffix 2)u201D field or hide other
fields).
3.        The following fields can be used to search for a specific output (Note that
Created By must be blank when searching for scheduled jobu2019s outputs)
a.        Spool request name (suffix 2) u2013 corresponds to a spool name in p. 3.b in
u201CScheduling background jobsu201D section above).
b.        Date created u2013 to find an output of a job that ran within a certain date range.
c.        Title u2013 corresponds to spool Title in p. 3.c in u201CScheduling background jobsu201D
section above).
d.        Department - corresponds to spool Department in p. 3.e in u201CScheduling
background jobsu201D section above).
4.        Upon entering selection criteria, the user clicks the Execute button   to
retrieve the list of matching spool requests.
5.        From the spool list the user can use several function such as view the
content of a spool request, print the spool request, view attributed of the spool
request, etc. (some functions may need special authorization, see p.3 in
Configuring user access)
a.        Click the Print button   to print the spool request with the default attributes
(usually defined with the job definition). It will print it on a printer that was
specified when a job was created.
b.        Click the u201CPrint with changed attributedu201D button   to print the spool request
with the different attributes (e.g. changing the printer name).
c.        Click the u201CDisplay contentsu201D button   to preview the spool request contents. A
Print    and Download   functions are available from the preview mode.
Exporting the Contents of a Spool Request
Use
You want to export the contents of a spool request as a text file to the SAP GUI working directory or to a directory of your choice. The content of the spool request is downloaded as plain text without, for example, graphics, images, or specific fonts.
The following procedures are irrelevant for the PDF-based form printing integrated as of SAP Web Application Server 6.40, since the print data can be opened and stored as a PDF. See also Displaying and Printing PDF-Based Forms.
Procedure
Exporting to the SAP GUI Working Directory:
Choose Spool Request ® Forward® Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
.txt
Example: ABC0000004327.txt
You require appropriate authorization for this function.
Exporting to a Directory of Your Choice:
With this method of exporting a spool request, the content of the spool request is first displayed and you then download the screen list as a text file to the directory of your choice.
       1.      Select the spool request to be exported and choose Display Contents.
       2.      In the case of SAPScript/Smart Forms documents, activate list display by choosing Goto.
       3.      Choose System ® List ® Save ® Local File.
       4.      Choose one of the available formats and confirm your choice.
       5.      Choose a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto ® Display Requests ® Settings and making the desired entries in the Display Area group box.

Data capturing in background job scheduling

HI,
I hava a specific requirement in background job scheduling.
in my layout i have to show <b>pagenumber / total number of page numbers.</b>
for that iam useing a variable with value '$$$' and iam replacing this variable with total number of pages..
when we run in foreground it is working fine. but in background the variable is not being replaced..
how can i modify the data in spool..

REPORT ztest no STANDARD PAGE HEADING
                                 MESSAGE-ID zfi
                                 LINE-COUNT 65(1)
                                 LINE-SIZE 165.
DATA:        v_sum(3) TYPE c VALUE'$$$'.
CONSTANTS: c_slash    TYPE c VALUE '/'.        "Stores /
parameters : p_1 type c.
START-OF-SELECTION.
WRITE : 'Hi'.
SKIP 80.
WRITE : 'Helloo'.
END-OF-SELECTION.
*To print the total no. of pages in report heading.
PERFORM f_replace_totpage.
TOP-OF-PAGE
TOP-OF-PAGE.
Display Standard Report Header
PERFORM f_report_header.
*&      Form f_replace_totpage
     To print the total no. of pages in report heading.
FORM f_replace_totpage .
DATA: l_tot_page(3) TYPE c,
        l_pgcnt TYPE i,
        l_licnt TYPE i VALUE '3'.
Assign value of total number of pages into l_tot_page.
l_tot_page = sy-pagno.
To replace the value of v_sum ($$$) by total number of pages after
reading the content of fourth line of each page.
WHILE l_pgcnt LE l_tot_page.
    l_pgcnt = l_pgcnt + 1.
    READ LINE l_licnt OF PAGE l_pgcnt.
    REPLACE v_sum WITH l_tot_page INTO sy-lisel.
    MODIFY LINE l_licnt OF PAGE l_pgcnt.
ENDWHILE.
CLEAR: l_tot_page,
         l_pgcnt,
         l_licnt.
ENDFORM.                    " f_replace_totpage
*&      Form f_report_header
      Report Header display
FORM f_report_header.
FORMAT COLOR 1 INTENSIFIED ON.
Text-246 - Page:
WRITE:/1 text-247, 45 text-241, 110 text-242, 150 space.
WRITE:/1 text-243, sy-repid, 110 text-244, sy-datum, c_slash, sy-uzeit,
         150 space.
WRITE:/1 text-245, sy-uname, 110 text-246, sy-pagno,c_slash,v_sum,
         150 space.
FORMAT COLOR OFF.
ULINE.
ENDFORM.                    " f_report_header

SSIS Package compiled successful, in SQL Server Integration Service package executed sucessful, But fail to run in MS SQL Job Scheduler

Hi Everyone,
I having a problem to transfer data from MS SQL 2005 to IBMAS400. Previously my SSIS was running perfectly but there is some changes I need to be done in order for the system to work well. Considers my changes are minimal & just for upgrades (but I did
include DELETE statements to truncate AS400 table before I insert fresh data from MS SQL table to the same AS400 table), so I compile my SSIS package & it run successfully & I passed it into MS SQL Integrated Service as 1 of the packages & manually
executed the package & the result is the same, that mean it was successful again but when I try to run it in a MS SQL Job Scheduler, the job failed with these message shown below as extracted from the job View history.
Date today
Log Job History (MSSQLToAS400)
Step ID 1
Server MSSQLServer
Job Name MSSQLToAS400
Step Name pumptoAS400
Duration 00:00:36
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: MSSQLServer\SYSTEM. ... 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: today time
Error: on today time
Code: 0xC0202009 Source: SSISMSSQLToAS400 Connection manager "SourceToDestinationOLEDB"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "IBMDA400 Session"
Hresult: 0x80004005
Description: "CWBSY0002 - Password for user AS400ADMIN on system AS400SYSTEM is not correct ". End Error
Error: today
Code: 0xC020801C
Source: Data Flow Task OLE DB Destination [5160]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationClearData" failed with error code 0xC0202009. There may be error messages posted before
this with more information on why the AcquireConnection method ca... The package execution fa... The step failed.
So I hope somebody can shed some hints or tips for me to overcome time problem of mine. Thanks for your help in advance. As I had scoured thoroughout MSDN forums & found none solution for my problem yet.
PS: In the SQL Integrated Services when I deployed the package I set the security of the packages to Rely on server...
Hope this will help.

Hi Ironmaidenroxz,
From the message “Executed as user: MSSQLServer\SYSTEM”, we can see that the SQL Server Agent job ran under the Local System account. However, a Local System account doesn’t have the network rights natively, therefore, the job failed to communicate with
the remote IBMAS400 server.
To address this issue, you need to create a proxy account for SQL Server Agent to run the job. When creating the credentials for the proxy account, you can use the Windows domain account under which you executed the package manually.
References:
How to: Create a Credential
How to: Create a Proxy
Regards,
Mike Yin
TechNet Community Support

Content Deployment Job - Schedule

Similar Messages

Maybe you are looking for