SQL SERVER AGENT DASHBOARD and Monitoring system

Hi
we are shopping around for a SQL SERVER management system where users that are not familiar with SQL can monitor Jobs and Job steps. Users will be able to see when a job failed and restart the job (if allowed) or call DBAs if needed based on instructions.
does anybody know of such a tool that would help operations peform their job?
thanks
eddy
eddy.a

Sorry mistakenly marked as proposed answer.
Sql Server 2012 has come with so many nice features which has helped me also to get validated so many stuffs in on place and that is called as Policy Based Management. Here I need to register all required servers and then all applicable policies will be
validated by executing them on daily or whenever you like.
Also Central Management Server:
An instance of SQL Server that is designated as a Central Management Server maintains server groups that contain the connection information for one or more instances of SQL Server. Transact-SQL statements and Policy-Based Management policies can be executed
at the same time against server groups. You can also view the SQL Server log files on instances that are managed through a Central Management Server. Versions of SQL Server that are earlier than SQL Server 2008 cannot be designated as a Central Management
Server.
Transact-SQL statements can also be executed against local server groups in Registered Servers.
More on below link:http://msdn.microsoft.com/en-in/library/bb895144.aspx
For question on SSRS, there is option to embed buttons and by which you have option to put some commaned to execute like you can call some batch file to execute some jobs on other servers by using osql and others. This way you can try and check.
Santosh Singh

Similar Messages

SQL Server Agent Job And Database Mail - Error formatting query, probably invalid paramters

We have a stored procedure that we are trying to call with a SQL Server Agent Job. The stored procedure calls Database Mail. This is SQL 2008. The execute task is simply:
USE [Production]
GO
EXEC [dbo].[JOB_EMAIL_SCHEDULED_REPORTS]
GO
When the job runs, it is erroring out immediately, with the error:
Execute as user: NT AUTHORITY\NETWORK SERVICE. Error formatting query, probably invalid paramters [SQLSTATE 42000] (Error 22050). The step failed.
When we go into SQL Server Manager and just execute the SQL query, it works though. Something within the SQL Server Agent job, and Database Mail is causing problems. Any ideas? Thanks.

Justin,
If you use SSMS then the procedure is executed under a different user when compared to running using a SQL Server Agent Job.
Isolate the problem by running a SQL Server agent job that sends a mail. Also check if the NT Authority\Network Service account is
in good standing. Look at the below thread with a similar problem that had an expired account.
http://social.msdn.microsoft.com/Forums/en/sqltools/thread/bac7ecee-a156-4313-b532-ba15813a0700
http://SankarReddy.com/

Reporting Services 2012 for SharePoint and SQL Server Agent "Subscriptions and Alerts"

After installing Reporting Services for SharePoint (Denali) in my test farm, I'm trying to configure the "SQL Server Agent" access for Reporting Services. From Central Admin I'm going to the Reporting Service applicaiton configuration screen and selecting
"Provision Subscriptions and Alerts". I've tried both options on this screen. I've manually executed the "download sql script" in SQL Server, as well as entering a user with SQL sys admin rights on the SQL server into the login fields on the screen.
The role and permissions have been created for the application pool service account, but Reporting Services is still trying to connect with the annonymous login because I'm getting the following alert each time I open the "Provision Subscriptions and Alerts"
screen:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
The "status" on the screen still shows "SQL Server Agent State cannot be determined". Has anyone else seen this?
Thanks!!

Thanks for your reply!
1) Looks like the new Reporting Services does not run as a Windows Service so it's not listed in the "Configure Service Accounts" pulldown. As a result, I don't see how to set the service account. It's only assigned to an application pool.
I installed it into an existing application pool and that application pool "is" in the list and has a domain service account already assigned.
2) Which users need to be in here in order to configure the "Provision Subscriptions and Alerts" screen? I already have the farm admin account which is the account I use when running Central Admin.
3) As mentioned in #1, I've installed Reporting Services into an existing application pool with other service apps.
4) This link is for Reporting Services 2008 R2 which is very different install process. But I did follow the SQL Server Reporting Services 2012 RC0 installation instructions and the Reporting Services is functioning correctly with no errors.
I'm just not able to configure the sceduling the alerting with interfaces with the SQL Server Agent.
Thanks!

HOw to avoid DeadLocks when you schedule a Sql Server Agent Job and calling SSIS packages

Hi All,
I have scheduled 2 packages in in Sql Server Agent jobs .
First job which is having Package 1 executing at 11 AM and where I am inserting the data in the table.
Second job which is having Package 2 executing at 12 AM and where I am updating the data in the table based on the first job inserted records.
When I am executing my first job it taking more time and executing till 12 AM and from 12 AM my job 2 also starting ,so getting deadlocks conflicts because inserting happening from job1 and updating happening from Job 2.
How to avoid deadlocks and fix the issue.
Please Suggest .
Thanks & Regards,
Anand

Hi Anand,
Here is another solution, you can set the Job 2 not to run based on a schedule, and create another SQL Server Agent Job which starts at 12 AM and run with a specified time interval to execute a SQL statement in which you do the following steps:
1. Get the status information of Job 1 using the statement:
DECLARE @i int;
EXEC @i = msdb.dbo.sp_help_job @job_name = ‘Job Name'
2. If the value of @i is 1 which means the status of job 1 is success and current time is, then start the job 2. So, the statement is as follows:
IF @I = 1
EXEC msdb.dbo.sp_start_job @job_name= ‘Job Name’
Regards,
Mike Yin
TechNet Community Support

SQL Server Agent Job Duration monitor alerts incorrectly

As per SQL Server MP guide, changes in Dec 2007 update : Fixed a script that was resulting in invalid alerts being generated from the agent job's Job Duration monitor.
In my SCOM 2012 environment on few SQL servers I'm getting an alert from Job Duration monitor for SQL jobs that have completed well within the defined thresholds. Interestingly this monitor then resets on its own(The monitor has been initialized for
the first time or it has exited maintenance mode) and immediately turns critical again. I do not see any pattern around these state changes. These are weekly jobs, however the Job Duration monitor continues to alert for these specific jobs 10-15 times a day.
This is creating unnecessary noise in the environment.
Is anyone else facing this issue? I know I can disable this default monitor and create my own monitor. However I want to check if this is a known bug in this SQL MP(version 6.4.1.0).
Note : I'm aware about an updated MP version 6.5.1.0, however the release note doesn't specify if it fixes this issue.
Thanks,
Harry
Thanks, Harry :-)

Resolution: The issue was that the SCOM Agent was getting restarted repeatedly. Post restart health calculation was done again and the SQL Job duration monitors would reset and generate new alerts.
There is a recovery configured in an aggregate monitor to restart the SCOM Agent if Handle Count/Private Bytes of Health Service/Monitoring Host breach a set threshold. I had to create an override to change the thresholds for all Health Service/Monitoring
Host and exclude the recovery on Physical servers.
If there are large number of workflow on an SCOM Agent due to multiple MP(SQL, HP, etc.), the increase in Handle Count/Private Bytes is usual.
Thanks, Harry :-)

Sql server agent roles and job's owner issue

Hi,
We have a tricky question about agent role and job owner. If I granted sqlagentoperatorrole to a windows account in a sql instance, the account will have permission to create a sql job, the job's owner is the account and he can edit the job. But we want
to keep all agent jobs' owner as SA. But after I (have sysadmin role) changed the job's owner to SA, the windows account won't be able to edit the job any more. but I don't want to give sysadmin role to the account, Does anybody have solution for my issue?
so recap my question,
1. all jobs owners should be SA
2. Allow some accounts without sysadmin permission can edit these jobs
3. Which kid of permission shall I grant to these accounts?
Thanks
David

Its not secessary to have SA for all the jobs, normally we avoid using SA...
Depends if you want to have some sort of security measures in place. If not, doesn't matter much. As for the 'sa' topic, I change the name of that account or disable immediately after install. It practically eliminates that vector of attack.
If you SQLAgentOperatorRole permissions then you can do the below... this is just a agent role so this comes under MSDB....
http://msdn.microsoft.com/en-us/library/ms188283.aspx
Also if you have sql SA access with doamin account or sql account then you can play with sql server completely without any issues, no harm in this...
Agenet principals are scoped to msdb; make sure you are running the statement from msdb DB. For example:
use [msdb]
go
-- The code where @userName is declared & set
EXEC sp_addrolemember 'SQLAgentOperatorRole', @userName
go
If you still have problems let us know, and please include the error number and message in order to help us understand the nature of the fauilure.
Best practice...
http://technet.microsoft.com/en-us/library/cc966485.aspx
Raju Rasagounder Sr MSSQL DBA

SQL Server Agent and Jobs and executing @EventData

I have a SQL Server Agent Job and within it a Job Step which states "Execute Report Subscriptions" and a command which has...
exec msdb.dbo.sp_start_job '6FF53AED-855F-43AB-9FB7-064062B8012E' --9:07 subscription
GO
WAITFOR DELAY '00:08';
Now, I find within SQL Server Agent the Job '6FF53AED-855F-43AB-9FB7-064062B8012E' and its step command which is...
exec [ReportServer].dbo.AddEvent @EventType='TimedSubscription', @EventData='ca4e5410-2758-4a1a-9b06-513821e0d962'
How can I drill-down further into the @EventData 'ca4e5410-2758-4a1a-9b06-513821e0d962' to see what it does? I do not see 'ca4e5410-2758-4a1a-9b06-513821e0d962' within SQL Server Agent and Jobs or am I way off base here as to what exactly the @EventData
parameter seems to be?
Thanks for your review and am hopeful for a reply.

Hi ITBobbyP,
According to your description, you need to know the what does SQL Server Reporting Services do when fire a subscription, right?
When you create a subscription several things are added to the RS server
A row is placed in the Subscriptions table identifying the name of the report, along with parameter settings, data driven query info and so on to process the subscription
A row is placed in the Schedule and ReportSchedule tables with the timing of the subscription
A SQL Server Agent job is created to control the scheduled execution of the report, and this is stored in the sysjobs and sysjobsteps of the MSDB database.
When the subscription runs several things happen
The SQL Server Agent job fires and puts a row in the Event table in the RS catalog with the settings necessary to process the subscription
The RS server service has a limited number of threads (2 per CPU) that poll the Event table every few seconds looking for subscriptions to process
When it finds an event, it puts a row in the Notifications table and starts processing the subscription
Please refer to the links below to see the details.
http://blogs.msdn.com/b/deanka/archive/2009/01/13/diagnosing-and-troubleshooting-subscriptions.aspx
http://blogs.msdn.com/b/deanka/archive/2010/02/16/troubleshooting-subscriptions-part-ii-using-the-report-services-trace-log-file.aspx
Regards,
Charlie Liao
TechNet Community Support

Getting an error running an SSIS package from SQL server agent

This is the first time I'm running an SSIS package in SQL server agent.
I'm running a SQL server agent job and getting this error message:
Am I using the correct options? (options list below)
Message
Executed as user: SITEX\stxdatasqlexec. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started: 1:42:00 PM Error: 2014-04-17
13:42:01.01     Code: 0xC0011007     Source: {B72BF421-785A-44EC-9570-D2A40B046CA7}      Description: Unable to load the package as XML because of package does not have a valid XML format. A
specific XML parser error will be posted. End Error Error: 2014-04-17 13:42:01.02     Code: 0xC0011002     Source: {B72BF421-785A-44EC-9570-D2A40B046CA7}      Description: Failed
to open package file "C:\Users\halexandrovich\Documents\Nbr_Rolls_base.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly
into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. End Error Could not load package "C:\Users\halexandrovich\Documents\Nbr_Rolls_base.dtsx"
because of error 0xC0011002. Description: Failed to open package file "C:\Users\halexandrovich\Documents\Nbr_Rolls_base.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a
package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. Source:
{B72BF421-785A-44EC-9570-D2A40B046CA7} Started: 1:42:00 PM Finished: 1:42:01 PM Elapsed: 0.047 seconds. The package could not be found. The step failed.
Here are the options I'm using:
package source - file system
data source destination = my SQL server db
execution option - use 32 bit runtime
command line entry:
- /FILE "C:\Users\halexandrovich\Documents\Nbr_Rolls_base.dtsx" /CONNECTION DestinationConnectionOLEDB;"\"Data Source=esxdspr-sql01.sitex.com;Initial Catalog=SuesTbls;Provider=SQLNCLI10;Integrated Security=SSPI;Auto Translate=false;\""
/CONNECTION SourceConnectionFlatFile;"\\sitex.com\dfs\Production\SFTPData\LPSEFTProcess\FromAADFS\Rpt_Nbr_Rollsperbatch_20140331_20_0.txt"
/X86 /CHECKPOINTING OFF /REPORTING E
I checked the filename so it must be the XML format it's complaining about.

Thank you, pituach.
I tried running the package using just my c drive without partition, C:\Nbr_Rolls.dtsx, but still getting the same
error. I do not see any option on this site to post my package. I know it's not the path that's the issue. Our support desk already fixed that because I was getting a different message before.
Message
Executed as user: SITEX\stxdatasqlexec. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started: 11:23:00 AM Error: 2014-04-18
11:23:00.44     Code: 0xC0011007     Source: {2BEE62EB-DD08-4867-9F5C-660167964650}      Description: Unable to load the package as XML because of package does not have a valid XML format. A
specific XML parser error will be posted. End Error Error: 2014-04-18 11:23:00.45     Code: 0xC0011002     Source: {2BEE62EB-DD08-4867-9F5C-660167964650}      Description: Failed
to open package file "C:\Nbr_Rolls.dtsx" due to error 0x800C0006 "The system cannot locate the object specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of
either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. End Error Could not load package "C:\Nbr_Rolls.dtsx" because of error 0xC0011002. Description: Failed
to open package file "C:\Nbr_Rolls.dtsx" due to error 0x800C0006 "The system cannot locate the object specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of
either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. Source: {2BEE62EB-DD08-4867-9F5C-660167964650} Started: 11:23:00 AM Finished: 11:23:00 AM
Elapsed: 0.125 seconds. The package could not be found. The step failed.

How to pass values to SQL server Agent Job which internally calls SSIS

Hi,
I have a requirement where i need to call remotely SSIS package from ASPX. After following MSDN form, I have creaed one SQL server agent job and calling that job from ASPX. I am ablt call SQL server agent job from ASPX. Only issue i am facing is: I need
to pass 2 variables from ASPX to SQL Agent job so that from Job i can map the same to SSIS Package.
I am using system SP (sp_start_job) for calling SQL server agent job as mentioned in MSDN forum.
below is the code , which i am using to call SQL serve agent job.
Code:
SqlConnection
jobConnection;
SqlCommand jobCommand;
SqlParameter jobReturnValue;
SqlParameter jobParameter;
int jobResult;
                jobConnection =
new
SqlConnection("Server=ServerName;Initial
Catalog=msdb;Integrated Security=SSPI;user id=username;Password=password");
                jobCommand =
new
SqlCommand("sp_start_job",
jobConnection);
                jobCommand.CommandType =
CommandType.StoredProcedure;
                jobReturnValue =
new
SqlParameter("@RETURN_VALUE",
SqlDbType.Int);
                jobReturnValue.Direction =
ParameterDirection.ReturnValue;
                jobCommand.Parameters.Add(jobReturnValue);
                jobParameter =
new
SqlParameter("@job_name",
SqlDbType.VarChar);
                jobParameter.Direction =
ParameterDirection.Input;
                jobCommand.Parameters.Add(jobParameter);
                jobParameter.Value =
"ImportCMTData";
                jobConnection.Open();
                jobCommand.ExecuteNonQuery();
                jobResult = (
Int32)jobCommand.Parameters["@RETURN_VALUE"].Value;
                jobConnection.Close();
switch (jobResult)
case 0:
Console.WriteLine("SQL
Server Agent job, RunSISSPackage, started successfully.");
break;
default:
Console.WriteLine("SQL
Server Agent job, RunSISSPackage, failed to start.");
break;
Console.Read();
Thanks
Pankaj

"3-4 concurrent users are calling the SSIS package from ASPX page" this is not a proper design
If the data is being ingested than it is likely that this concurrency will lead to one of the packages die
What you shell do is to just queue the data ingress/processing.
In general, again, packages should not be called from ASP web pages, SSIS is ETL-server side technology there is nothing signalling back to the user whether it was successful. The proper way is to write a REST service or alike.
Arthur
MyBlog
Twitter

Can't launch executable from SQL Server Agent Job

I'm trying to launch an .exe from SQL Server Agent Job and basically nothing happens. I created a job, with 1 step, type is Operating System (CmdExec), run as sql agent service account, and in the command box I typed "start notepad" (no quotes). The job owner is set to administrator. I manually start the job, it processes successfully yet notepad does not launch. I've tried with other .exe's and result is the same. Any advice? Thanks!

I tried several things and not just with notepad, I tried a couple other small executables. I've tried:
c:\notepad --(I copied it to c:\ thinking it maybe it's not finding the file.)
c:\notepad.exe
notepad.exe
start notepad
start notepad.exe
and also launching it from a batch file.
If I use just notepad the job hangs saying it's executing and I have to stop it. If I use start notepad it comes back as executed but actually nothing happens, ie, notepad does not launch. I've tried different security settings within SQL Server (ie assigning all available default roles to the login at the same time and individually one at a time) with identical results. SQL Server is loging in with local administrator priviledges and so is SQL Server Agent. My settings are the default installation settings (for Windows Server 2003 and SQL Server 2005) except that I read the BOL page "Configuring SQL Server Agent" which indicates the permissions needed for the following:
Adjust memory quotas for a process
Act as part of the operating system
Bypass traverse checking
Log on as a batch job
Log on as a service
Replace a process level token
And they have been set. Still the same. BTW, I get the same result when trying to launch the file using xp_cmdshell with all the variations, and the proxy account for xp_cmdshell has been set to a login with administrator priviledges....
I think it's some security setting in Windows Server, if only because I think I've tried all the settings within SQL Server...
BTW, also, nothing is setup for Proxies under the SQL Server Agent node, but I don't think I should need to if I'm using the administrator level login...

Getting SQL Server Agent running

I am trying to get my SQL Server Agent running, and no conventional means thus far have worked.
I set it to run automatically in the Services window of the Control Panel. Attempting to run it from there yields the error "The SQL Server Agent (BENTLEYECAD) service on Local Computer started then stopped. Some services stop automatically if they
are not in use by services or programs"
Attempting to start the Server agent in the Server configuration manager yields the error "The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details"
The resulting error log in SQLAGENT.OUT is
2015-02-19 15:58:44 - ? [100] Microsoft SQLServerAgent version 10.50.1600.1 (x86 unicode retail build) : Process ID 6064
2015-02-19 15:58:44 - ? [101] SQL Server HFC-RND-104-D\BENTLEYECAD version 10.50.1600 (0 connection limit)
2015-02-19 15:58:44 - ? [102] SQL Server ODBC driver version 10.50.1600
2015-02-19 15:58:44 - ? [103] NetLib being used by driver is DBNETLIB.DLL; Local host server is HFC-RND-104-D\BENTLEYECAD
2015-02-19 15:58:44 - ? [310] 4 processor(s) and 4096 MB RAM detected
2015-02-19 15:58:44 - ? [339] Local computer is HFC-RND-104-D running Windows NT 6.1 (7601) Service Pack 1
2015-02-19 15:58:44 - ! [000] This installation of SQL Server Agent is disabled. The edition of SQL Server that installed this service does not support SQL Server Agent.
2015-02-19 15:58:44 - ? [098] SQLServerAgent terminated (normally)
I have installed this version of SQL alongside Promise V8i (M). Any advice on how to get this server agent running is welcome
-Eugene

I see.
I'm not sure if it's Express or not, how can I tell? The start-up for the server management studio just says "Microsoft SQL Server 2008 R2"
If this is the case, will any other version of SQL besides Express work? or is it only specific ones?
Thanks,
Eugene O'Donnell

"Disable Check for SQL Express" against SQL Server Agent

Good afternoon,
Seeing as it has been a know issue for many years now[1],
is there a reason why Microsoft has yet to include a “Disable Check for SQL Express” override (similar to the
Automatic Configuration (& other) monitors) for each of the following objects included in the
Microsoft SQL Server Management Pack?
SQL Server Agent Windows Service (Monitor)
Discover SQL Server Agent for a DB Engine (Discovery)
This would prevent me from have to continually create overrides
disabling the monitor|discovery each time a new instance of SQL Express is installed in our Management Group.
Thanks,
Larry
[1]
http://jmkehayias.blogspot.ca/2009/01/sql-server-2008-express-sql-agent-won.html
http://sqlblogcasts.com/blogs/sqldbatips/archive/2008/06/28/sql-server-2008-express-installs-sql-agent-but-don-t-bother-trying-to-start-it.aspx

Hello,
This is much easier
http://blogs.technet.com/b/emreguclu/archive/2013/01/21/undiscovering-stop-monitoring-sql-2008-express-editions.aspx
just exclude sqlexpress
Regards
Mohammad, IT NOC Team

Want to change the SQL Server Agent Job History Text Files Location

We have SQL Server 2014 installed on a couple servers, but they were not consistent on directory paths during the installs. I am trying to get the servers to all match.
On one server, SQL Server the Agent Log and Job History files were being written to [H:\Data Root Directory\MSSQL12.MSSQLSERVER\MSSQL\Log].
I want to change that to [H:\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log] to match the other server.
I have ALREADY gone into SSMS - [SQL Server Agent] - [Properties] and changed the "Error Log " "Fle Name" to [H:\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\SQLAGENT.OUT]. And that is working great.
In [SQL Server Configuration Manager] - [SQL Server (MSSQLSERVER)] - [Properties] - Startup Parameters entries have been changed to the new path (-d, -e, and -l), and under [Advanced] both Data Path and Dump Directory are pointing to the new path.
In [SQL Server Configuration Manager] - [SQL Server Agent (MSSQLSERVER)] - [Properties] - [Advanced] Dump Directory is pointing to the new path.
However, the job's History text files are still being written to the old path.
There is no setting in the Jobs or the Maintenance Plans that controls the history file location.
I have searched the registry and changed three settings from the old path to the new path. The registry does NOT contain any more references to the old path.
I rebooted the server, but when the jobs run their history text files are still be written to the old path.
Does anybody have any ideas?? Thanks

I checked the [Job] - [Step] - [Advanced ] - "Output File", and the field is blank.
I then reviewed all the tabs and left menu items in the Job...I cannot find any where the references the old path.
I then went to the Maintenance Plan and checked every thing there. Still cannot find what is referencing this old path.
SQL Server is also still writing xel files to this old path...if that offers any clues.
The text file being generated is the recap of the Job run. Starts with this:
Microsoft(R) Server Maintenance Utility (Unicode) Version 12.0.2430
Report was generated on "xxxxxxxxxxxxxxx".
Maintenance Plan: SQL_Backups_Log
Duration: 00:00:03
Status: Succeeded.
Details:
Thanks for the ideas....

The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.

One of my replication job failed with below error, which means job failed because of permission issue on the folder. To resolve that, I have granted the permission and it started working fine. Now the question is as my job was running fine since long time
without any issue then how suddenly the permission of the folder got omitted automatically? I am sure that no one deleted the permission from the folder and as the server is part of SQL cluster no failover occurs.
Error:-The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\110\COM' directory. System returned errorcode 5.
Rahul

Hi Rahul,
Error code 5 indicates that the error is "access is denied." Please make sure that the COM folder is excluded from any antivirus scan that occurs on the system.
If the issue still persists, I recommend you use
Process Monitor to find out a bit more about the accounts and access requests involved. Then grant write permission to the exact COM folder for the account that is running the SQL Server Agent service. For more details, please review the following similar
thread.
http://www.sqlservercentral.com/Forums/Topic1364832-1550-1.aspx
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.

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

SQL SERVER AGENT DASHBOARD and Monitoring system

Similar Messages

Maybe you are looking for