SQL SYNC AGENT is not

Hi,
I am having below error in SQL DATA SYNC AGENT. please do transfer if i left the message in wrong room.
"Connection to Microsoft  SQL DATA Sync windows service timed out. Please unsure that micosoft data sync windows services
is running and restart local sync agent "
I have already restarted local sync agent.i checked the sql data sync winodws service is running in local services .
Please advice?
Superman

Hi,
Could you please check whether there are any error logs through the Event Viewer? Under the category "Applications and Service Logs" -> "SQL Data Sync".
Regards,
Bowen

Similar Messages

  • Sql server agent is not highlighting start and stop options

    I configured snapshot replication , after that sql server agent is not highlighting start and stop options in instance.
    But I can start & stop it in services.msc
    how I can solve this?

    Hi,
    Can you post exact error message.
    Also refer below article, may be similar issue like yours.
    How to start SQL Server Agent when Agent XPs show disabled
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    Praveen Dsa | MCITP - Database Administrator 2008 |
    My Blog | My Page

  • PSE7 BACKUP/SYNC AGENT does not work.

    Under the Preferences box , the Backup/Sync Agent does not open. I can't alter or change anything. When I sign in , my sign in and password are both accepted ,however where the Welcome is on top, it used to say Welcome, with my first name. It does not do this anymore. When I try to upload my pics to Photoshop.com it states I am not logged in. No one at Adobe has been able to help after 4 months .

    Hi,
    Can you please contact me on [email protected]
    I would like to suggest few things offline...

  • SQL Server Agent Jobs- Not running

    Team,
    We have a production database hosted on SQL Server 2008R2 SP2(10.50.4000). We have application jobs which are scheduled and basically have packages called from this job. These jobs were running all good till yesterday and it has stopped working since yesterday
    even though its enabled. Manual runs are successful. Other jobs are running fine. 
    Checked the Owner of these jobs and the account is SQL Server account which is a proxy account. It had enforce password policy. I have removed that and reset the password to original. However it didnt work.
    The last change on this server was windows patching which was performed last week. Apart from that the SQL Server agent service was changed. This is a clustered environment.
    The last resort is restart the agent, however would like to get some inputs before I perform this action. 
    Please let me know your valuable inputs.
    Regards,
    Sharath

    If job is not executed at all, that is, there are no entries in the job history, check:
    1) The job is enabled.
    2) The schedule(s) is enabled.
    3) The scdedule does not have an end date has has passed.
    4) And that all other conditions on the schedule says that the job should run.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • SQL Data Sync Agent can not start - Debug error in windows 7 x86

    Log file as per below
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:Main,
    message:Microsoft SQL Data Sync Windows service is starting as a Windows Service.
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
    message:Microsoft SQL Data Sync Windows service starting.
    LocalAgentHost 1/3/2013 11:55:31 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:00000000-0000-0000-0000-000000000000, agentInstanceId:00000000-0000-0000-0000-000000000000, version:4.0.89.0, methodName:OnStart,
    message:Starting a service worker thread.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:OnStart,
    message:Started a service worker thread.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:OnStart,
    message:Microsoft SQL Data Sync Windows service started successfully.
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartUxWcfService,
    message: Namedpipe bd54233d-16ce-46d3-8858-5e564732b21c, BaseAddress net.pipe://localhost/bd54233d-16ce-46d3-8858-5e564732b21c
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartUxWcfService,
    message: Opened WCF Host
    LocalAgentHost 1/3/2013 11:55:32 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:StartServiceThread,
    message: GetEntryAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, GetExecutingAssembly().Location: C:\Program Files (x86)\Microsoft SQL Data Sync\bin\LocalAgentHost.exe, Process.GetCurrentProcess().StartInfo.WorkingDirectory:
    LocalAgentHost 1/3/2013 11:55:37 AM  id:LocalAgentHost_Info, rId:, sId:00000000-0000-0000-0000-000000000000, traceLevel:Info, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0, methodName:AgentConfigDataManager.DownloadAndCacheServiceUrisFromLocator,
    message:Scale unit found
    AgentCore 1/3/2013 11:55:40 AM  id:AgentCore_InstanceStarted, rId:, sId:65915150-1284-4a17-9c13-d58e2830fcd9, agentId:6843e83c-6015-433c-97ae-4cb63815f4b5, agentInstanceId:bbd9490b-e160-4176-8988-9707b79ecd75, version:4.0.89.0
    ThreadId:40. Dispatcher started. Waiting
    ThreadId:43. GetRequest started.
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:46. GetRequest started.
    ThreadId:41. GetRequest started.
    ThreadId:48. GetRequest started.
    ThreadId:45. GetRequest started.
    ThreadId:42. GetRequest started.
    ThreadId:47. GetRequest started.
    ThreadId:44. GetRequest started.
    ThreadId:49. GetRequest started.
    ThreadId:50. GetRequest started.
    ThreadId:51. GetRequest started.
    ThreadId:52. GetRequest started.
    ThreadId:53. GetRequest started.
    ThreadId:54. GetRequest started.
    ThreadId:55. GetRequest started.
    ThreadId:56. GetRequest started.
    ThreadId:57. GetRequest started.
    ThreadId:58. GetRequest started.
    ThreadId:59. GetRequest started.
    ThreadId:60. GetRequest started.
    ThreadId:61. GetRequest started.
    ThreadId:62. GetRequest started.
    ThreadId:63. GetRequest started.
    ThreadId:64. GetRequest started.
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest
    ThreadId:40. Dispatcher calling GetRequest

    Hi,
    I believe that your issue is resolved by now. Please try this step is the issue still persists.
    its security issues and re-install the data sync with domainname\Myaccount user and give the user as adminitsrator privileges and change the time of your system.
    http://social.technet.microsoft.com/wiki/contents/articles/2655.sql-azure-data-sync-troubleshooting-guide.aspx
    Girish Prajwal

  • Sql server agent not starting

    I installed sql server 2008 r2 sp2
    sql server agent is not allowing me to start it.
    I run SSCM right click agent but start,stop menus are disabled

    i have only one sql instance named SQLEXPRESS
    The SQL Server Agent is installed with the Express Edition of SQL Server, but it's not a Feature of the Express Edition, therefore you can't start the Agent.
    See
    Features Supported by the Editions of SQL Server 2014
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • How do I delete a sync agent?

    I am trying to clean up my Azure environment. I have a bunch of Sync Agents that are no longer being utilized, but each time I select one to attempt to delete, I get an error that states "The Sync Agent was not deleted",
    without giving me any specifics.
    Does anyone know how I can go about deleting Sync Agents that are no longer in use?
    Thanks

    Hi,
    1. Local Agent cannot be deleted if its associated on-Premise database is unreachable
    Description/Symptoms : If a local end point (database) that is registered with a local SQL Azure Data Sync
    agent becomes unreachable, the local agent cannot be deleted.
    Cause : The local agent cannot be deleted because the unreachable database is still
    registered with the agent and when you try to delete the agent, the deletion
    process tries to reach the database, which fails. This database cannot be
    unregistered too, because during unregistration process, local agent tries to
    connect to database which cannot be reachable.
    Resolution/Workaround : Create a local database with the same name as the one that cannot be reached,
    unregister this database from local agent, and then proceed to delete the agent.
    2.  Sync Group cannot be deleted within 3 minutes of uninstalling/stopping the agent Description/Symptoms
    You are not able to delete a sync group with in 3 minutes of uninstalling/stopping the associated local SQL Azure Data Sync agent.
    Resolution/Workaround : Remove a sync group with associated sync agents online (strongly recommended).
    If agent is offline but installed, bring it online on the on-premise computer, wait for the status of the agent as online in Azure portal, and then remove the sync group.
    If agent is offline because it was uninstalled, perform the following steps and try deleting the sync group.
    -Remove agent XML file from the SQL Azure Data Sync installation folder if the file exists
    -Install the agent on same/another on-premise machine, submit agent key from portal generated for the agent that’s showing offline
    3. cannot delete my sync group
    Description/Symptoms : You fail in your attempt to delete a sync group.
    Cause/Fix : Any of the following can result in a failure to delete a sync group.
    The agent is offline  : Be sure that the agent is online then try again.
    The Data Sync service is stopped :
    * In the Start menu search on Services
    * Click Services in the Programs section of the search results.
    * Find the SQL Azure Data Sync Preview service.
    * If the service status is Stopped right-click the service name and select Start from the dropdown menu.
    A database is offline : Check your SQL Azure and SQL Server databases to be sure they are all online.
    The sync group is provisioning or synchronizing : Wait until the provisioning or synchronizing process finishes then retry deleting the sync group.
    Hope this helps.
    Regards,
    Shirisha Paderu

  • SQL Server Agent

    Hello
    I am using SQL Server 2012 Express with advanced services however I cannot connect to the SQL Server Agent.  The Instance is local and the SQL server Agent service is installed and has the correct permissions.  
    According to http://www.microsoft.com/en-gb/download/details.aspx?id=29062 SQL server agent should be available.  
    Reporting services is greyed out and should also be available in this version.  
    Regards
    Ray

    Hello
    I am using SQL Server 2012 Express with advanced services however I cannot connect to the SQL Server Agent.  The Instance is local and the SQL server Agent service is installed and has the correct permissions.  
    According to http://www.microsoft.com/en-gb/download/details.aspx?id=29062 SQL server agent should be available.  
    Reporting services is greyed out and should also be available in this version.  
    Regards
    Ray
    SQL Server agent is not present in express edition.YOu might see agent XP in sp_configure but acctual SQL server agent is not present.This feature is not provided by Microsoft for express edition.There is nothing mentioned about agent in link you posted.It
    does have reporting feature
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Execution of a batch file within SSIS fails in Sql Server Agent Job

    Hi All,
    I have an SSIS Package, which simply runs a batch file , the code for the batch file is
    MOVE \\cambosnapp01\Claims\Analytics\NICB\CurrentAlerts\* \\cambosnapp01\Claims\Analytics\NICB\AlertsArchive
    If i run the SSIS package manually it runs fine and moves all the files, however if i run the package through a Sql Agent Job it fails with the following error
    The directory "\\Cambosnapp01\Claims\Analytics\NICB" does not exist
    This is where the batch file is located, i am not able to understand if the SSIS package is running fine then why not the sql agent job?
    I also tried to create a sql agent job using Operating System(CmdExec) and i copied my batch file code in the command i am running it as SQL Server Agent Service Account , and here it fails as
    Executed as user: CAMELOT\svcDW. Access is denied.  Process Exit Code 1.  The step failed
    Does this mean this user doesnt have the rights to excute a batch file? how did this user even come up i am not running it from this user i am running it from SQL Server Agent Service Account . I dont know who is that user and if he even has the rights to
    execute a batch file.
    Can someone please help me with any solution for this? either first way or second way anything works fine for me.
    Thanks

    Hi SQLDEV,
    According to your description, you are experiencing the issue "The directory "\\Cambosnapp01\Claims\Analytics\NICB" does not exist" when run the SSIS package
    in SSMS by using SQL Server Agent, right?
    In your scenario, since you can run the package in SSDT manually. So as per my understanding, the issue can be caused by that the Services Account of your SQL Server Agent do not have the permission on that folder. To avoid this issue, you can set the folder
    permission for your SQL Server Agent account or change the services account to an account who have the corresponding permission. Please refer to the link below to see the details.
    https://msdn.microsoft.com/en-us/library/bb727008.aspx
    https://msdn.microsoft.com/en-us/library/ms345578.aspx
    Regards,
    Charlie Liao
    If you have any feedback on our support, please click
    here.
    Charlie Liao
    TechNet Community Support

  • Scheduling SSIS packages to run using SQL Server Agent Service

    The job failed.  The Job was invoked by Schedule 11 (run package).  The last step to run was step 1 (Execute Package)". how do i resolve this?

    Most probable causes: the developer runs the package in BI studio, it works. The job is deployed and runs in a schedule.
    the sql job agent does not have same rights as the developer.
    the test in BI studio was doen in 32-bit mode , the job by default ran in 64-bit mode. some oledb-odbc drivers may not work.
    Jan D'Hondt - SQL server BI development

  • SQL Azure Sync Agent

    Hi,
    Anyone can share on the network port and IP address requirement for the SQL Database sync? 

    1433 is between the Data Sync Agent and your SQL Server.  443 is bidirectional for Data Sync Agent to connect to Azure Data Sync Service.
    the Data Sync Service itself do not connect to your on-premise SQL Server directly. Neither does the Data Sync Agent connect to the Azure SQL Database Correctly.
    to illustrate 
    on-premise SQL <-> Data Sync Agent <-> Azure Data Sync Service <-> Azure SQL Database

  • Error trying to run SSIS Package via SQL Server Agent: DTExec: Could not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object

    Situation:
    SSIS Package designed in SQL Server 2012 - SQL Server Data Tools
    Windows 7 - 64 bit.
    The package (32 bit) extracts data from a SQL Server db to an Excel Output file, via an OLE DB connection.
    It uses 3 package variables:
    *) SQLCommand (String) to specify the SQL Statement to be executed by the package
    Property path: \Package.Variables[User::ExcelOutputFile].Properties[Value]
    Value: f:\Output Data.xls
    *) EXCELOutputFIle (String) to specify path and filename of the Excel output file
    Property path: \Package.Variables[User::SQLCommand].Properties[Value]
    Value: select * from CartOrder
    *) VarObjectDataSet (Object) to hold the data returned by SQL Server)
    Property path: \Package.Variables[User::VarObjectDataSet].Properties[Value]
    Value: System.Object
    It consists out of 2 components:
    *) Execute SQL Task: executes the SQL Statement passed on via a package variable. The resultng rows are stored in the package variable VarObjectDataSet
    *) Script Task: creates the physical output file and iterates VarObjectDataSet to populate the Excel file.
    Outcome and issue:The package runs perfectly fine both in SQL Server Data Tools itself and in DTEXECUI.
    However, whenever I run it via SQL Server Agent (with 32 bit runtime option set), it returns the errror message below.
    This package contains 3 package variables but the error stating that a package variable can not be set, pops up for the VarObjectDataSet only.  This makes me wonder if it is uberhaupt possible to set the value of a package variable
    of type Object.
    Can anybody help me on this please ?
    Message
    Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.2100.60 for 32-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  6:40:20 PM  DTExec: Could
    not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object.  Started:  6:40:20 PM  Finished: 6:40:21 PM  Elapsed:  0.281 seconds.  The package execution failed.  The step failed.
    Thank you very much in advance
    Jurgen

    Hi Visakh,
    thank you for your reply.
    So, judging by your reply, not all package variables used inside a package need to be set a value for when run in DTEXEC ?
    I already tried that but my package ended up in error (something to do with "... invocation ...." and that error is anything but clearly documented. Judging by the error message itself, it looks like it could be just about anything. that is why I asked my
    first question about the object type package variable.
    Now, I will remove it from the 'set values' list and try another go cracking the unclear error-message " ... invocation ...". Does an error message about " ... invocation ..." ring any bells, now that we are talking about it here ?
    Thx in advance
    Jurgen
    Yes exactly
    You need to set values only forthem which needs to be controlled from outside the package
    Any variable which gets its value through expression set inside package or through a query inside execute sql task/script task can be ignored from DTExec
    Ok I've seen the invocation error mostly inside script task. This may be because some error inside script written in script task. If it appeared after you removed the variable then it may because some reference of variable existing within script task.
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Excel Import Fails in SQL Server Agent Job but not when executed in BIDS

    We have a SQL Server agent job that has ran successfully for the past 6 months.  It started failing about a week ago.  I don't believe anyone installed anything on the server.  The proxy account used to run the job is an admin on the server.   
    I've tried everything I can think of or that I found on searches.  I even changed the connection manager from an Excel source to using an Microsoft office 12.0 Access Database Engine OLEDB connection and it still runs in BIDs and not as an agent job. 
    I also setup my LANID as a proxy account to see if the job would run (checking security) -- and it fails with the same error.   I also made sure the path is
    \\server\share rather than a drive letter.   Any ideas?
    The package is executed in 32 bit mode.  The package still runs fine in BIDS (where BIDs is opened on the server) but fails in the SQL Agent job with:
    Executed as user: xxxxxx\xxxxxx. Microsoft (R) SQL Server Execute Package Utility  Version 11.0.2100.60 for 32-bit  Copyright (C) Microsoft Corporation. All rights reserved.    Started:  9:00:00 AM  Error: 2014-12-01 09:00:02.46    
    Code: 0xC0202009     Source: xxxxxx Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.  An OLE
    DB record is available.  Source: "Microsoft Access Database Engine"  Hresult: 0x80004005  Description: "External table is not in the expected format.".  End Error  Error: 2014-12-01 09:00:02.65    
    Code: 0xC020801C     Source: Load File to Staging Excel Source [43]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager
    "Excel Connection Manager" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.  End Error  Error: 2014-12-01 09:00:02.77    
    Code: 0xC0047017     Source: Load File to Staging SSIS.Pipeline     Description: Excel Source failed validation and returned error code 0xC020801C.  End Error  Error: 2014-12-01 09:00:02.90    
    Code: 0xC004700C     Source: Load File to Staging SSIS.Pipeline     Description: One or more component failed validation.  End Error  Error: 2014-12-01 09:00:03.02     Code: 0xC0024107    
    Source: Load File to Staging      Description: There were errors during task validation.  End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  9:00:00 AM  Finished: 9:00:03 AM 
    Elapsed:  2.761 seconds.  The package execution failed.  The step failed.

    I logged on to the server with the account that the SQL Agent runs under and ran the following from a command
    line to execute the package:
    "D:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\DTEXEC.exe" /FILE
    "\"K:\SSIS\xxxxxx\xxxxx.dtsx\"" /CHECKPOINTING OFF 
    /REPORTING EWCDI  /X86
    I wanted to see if it was a security issue with the agent account account - but
    this ran fine.
    I then updated the SQL Agent job to use an operating system command instead
    of a SSIS package on the job step.  This fails...
    The issue is definately with the SQL Server Agent

  • Not able to run the SSIS package in SQL Server Agent Job in SQL 2012

    Hi,
    I scheduled a job (SQL SERVER AGENT) which will call my SSIS package. This package will execute 5 packages in loop.
    When I execute this job I am getting error as below
    ============================================================
    Started  : 12:30:19 PM 
    Error  : 2014-01-23 12:30:20.37    
    Code  : 0xC00220EC    
    Source  : Execute Package Task     
    Description : Error 0x80070005. Failed to create an instance of empty child package.
        The Distributed Component Object Model (DCOM) configuration or the installation of SQL Server Integration Services,
        may be corrupted on your machine.  End Error 
    Error  : 2014-01-23 12:30:20.37    
    Code  : 0xC00220DE    
    Source  : Execute Package Task     
    Description : Error 0x80070005 while loading package file "D:\SSIS\RetailMobileApp\Staging_Pkg\stg_Category_Master.dtsx". Access is denied.End Error 
    DTExec  : The package execution returned DTSER_FAILURE (1). 
    Started  : 12:30:19 PM 
    Finished : 12:30:20 PM 
    Elapsed  : 1.123 seconds. 
    The package execution failed. 
    The step failed.
    ============================================================
    In the STEPS I have selected as follows:
    Type  : SQL Server Integration Services Package
    Run as: SQL Server Agent Service Account
    Package Source: File System
    What config I need to check here ? This job is not able to access the package stored in the folder.
    Sridhar

    Thanks for your reply. I had created credentials and used this while creating the Proxy account. With the Proxy account I am able to execute the Job Successfully. Concern here is I used my NT account to create this Proxy. Suppose If I left from the
    current project if some one is coming to this project later they need to change the credential with their NT account and run the JOB? Is this right way or we an create any other account in common? If so how?
    Sridhar

  • SQL server agent job running as Agent Service Account whose service account does not have r/w access but is still able to write?

    Hi. I am newer to SQL server security and am reviewing some of our SQL server's configuration to make sure the services are running under accounts with least privilege.  I have a SQL server 2012 instance whose Agent service is configured to run
    under an AD user account named 'SQLServices'.  The jobs on this server are configured to run as 'SQL server agent service account', which means they should execute as user 'SQLServices'.  The jobs are set up to execute SSIS packages which read and
    write to a database on the same server where the agent job is scheduled and SSIS package installed (all on same server).  The jobs are currently executing without error and are reading writing data correctly.  Upon close examination, it turns out the
    SQLServices account is not assigned to the 'sysadmin' role and had no users mapped to any databases on this server.  How are these jobs working?  I verified in profiler that the login name indeed is 'SqlServices'.  I also verified
    that SQLServices login has no database access by remote-ing onto the server and trying to log into the DB, and access was denied as expected.  According to the literature, the Agent service needs to be a member of 'sysadmin role' but I am reading
    some cases where that is not necessarily the case.  So this is not so concerning.  What is concerning is that the login 'SQLServices' had no access to the databases on that server yet it is reading and writing to the databases as if it does. 
    The only thing I can think of is maybe jobs run as 'SQL server agent service account' on the same server as the databases it r/w to somehow has some kind of default access.  What am I missing here?  Any input would be helpful.

    After 2 days on this forum I found the answer to my own question.  In retrospect, I should have posted this under 'SQL Server Security', but I didn't know it existed.
    The 2 threads below explain that Sql agent actually runs using SID (service) NT SERVICE\SQLSERVERAGENT if you chose that when you installed.  This will automatically create an associated login NT SERVICE\SQLSERVERAGENT in SQL server with sqladmin
    role.  This is the login that Agent uses to connect to the local instance of SQL server.  If you changed to domain account to run the service during install or after using config manager, basically NT SERVICE\SQLSERVERAGENT is still
    used to connect to your local instance behind the scenes (even though you will still see your domain user as account), and the domain account is used to reach outside the server. 
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9e6bb2de-8fd0-45de-ab02-d59bbe05f72e/servicedatabase-accounts-nt-servicemssqlserver-nt-servicesqlserveragent-what-are-they-for
    https://social.technet.microsoft.com/Forums/sqlserver/en-US/b83a52fd-fe11-4c28-a27b-88be8ae79f2a/how-do-i-change-sql-server-agent-service-account-to-nt-servicesqlserveragent?forum=sqlsecurity

Maybe you are looking for

  • Can't download firefox from the mozilla site

    When I try to download fire fox, I get a message saying its downloading but nothing happens. It copies the stub.exe file to my download folder but nothing else happens

  • ITS Mobile Blank page on Windows Mobile 5.0

    Hi, I created set of services for WM RF transaction and they work as expected in IE 6.0 on Windows XP. I have a handheld (Symbol MC9090) with Windows Mobile 5.0 and when I call-up URL in the IE on the hanheld, nothing is displayed. I get messages Con

  • When will CC Photoshop subscription be available in Croatia?

    I would like to become a CC subscriber but it's not availabel in Croatia at this time. Please advise and give some information when you plan to include Croatia in CC subscription packages since all dealers have much higher prices for same products he

  • EDI Subsystems vs XI - functional differences

    I have seen from posts in this forum and other resources that it is possible to use XI as an EDI subsystem (please correct me if that is incorrect). However, what I would like to know is what functionality is missing if you do that. Also, I thought t

  • RPM installation error on Linux 4 during installation of R12

    On Linux 4 during pre-requisite steps of R12 i found following error. rpm -ivh gcc-3.4.6-3.i386.rpm warning: gcc-3.4.6-3.i386.rpm: V3 DSA signature: NOKEY, key ID 0c98ff9d error: Failed dependencies: cpp = 3.4.6-3 is needed by gcc-3.4.6-3.i386 Please