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/

Similar Messages

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 fails with error : The package execution returned DTSER_FAILURE (1).

Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:01 AM Error: 2014-08-15 10:00:07.20
Code: 0xC0047062 Source: Data Flow Task LEAN [6761]
Description: Teradata.Client.Provider.TdException: [Teradata Database] [3006] Logons are disabled.
at Teradata.Client.Provider.WpMessageManager.CheckForError()
at Teradata.Client.Provider.WpMessageManager.ProcessResponse()
at Teradata.Client.Provider.WpLogonManager.Action()
at Teradata.Client.Provider.WpSession.ManagerAction(WpMessageManager manager, UtlStopwatchWrapper watch, Int32 connectionTimeout)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout, String password)
at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout)
at Teradata.Client.Provider.Connection.Open(UtlConnectionString connectionString, UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.CreateConnection(UInt32 timeout)
at Teradata.Client.Provider.ConnectionPool.GetConnectionFromPool(Object owningObject)
at Teradata.Client.Provider.ConnectionFactory.GetConnection(Object owningObject, UtlConnectionString connStr)
at Teradata.Client.Provider.TdConnection.Open()
at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
End Error Error: 2014-08-15 10:00:07.35 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline
Description: component "LEAN" (6761) failed validation and returned error code 0x80004005. End Error Error: 2014-08-15 10:00:07.48
Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation.
End Error Error: 2014-08-15 10:00:07.60 Code: 0xC0024107 Source: Data Flow Task
Description: There were errors during task validation. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:01 AM Finished: 10:00:07 AM
Elapsed: 6.692 seconds. The package execution failed. The step failed.
SQL Server agent job fails with above error, Please let me know process tohandle it.
Thanks,
Vishal.

The error message suggests its the issue with Teradata source database to which SSIS tries to connect within the data flow task. Make sure Teradata database is available and LOGON is enabled.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Error while executing SSIS package which contains Script component through SQL Server Agent Job

Hello All,
I have written one SSIS 2012 package which is fetching records from CSV and put it into staging DB and from staging DB , using SSIS script component task, I am inserting data into Dynamics CRM. So far it is working fine when
I manually execute SSIS package.
but when I run the SSIS package using SQL server agent job, I encounter below error. After seeing below error at step "Insert TLM Headers Script Component " I understand that it is failing at script component which I have used in SSIS package,
but I am not sure what is the cause behind that? please advise.
Error:
Executed as user: domain\user account. Microsoft (R) SQL Server Execute Package Utility Version 11.0.5556.0 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 1:21:41 PM Error: 2015-02-25
13:21:45.94     Code: 0xC0047062     Source: Insert TLM Headers Script Component [205]     Description: System.ServiceModel.FaultException: The server was unable to process the request due to an internal
error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to
the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.    Server stack trace:      at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message
reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)     at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage
methodCall, ProxyOperationRuntime operation)     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:      at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception
e)    at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)     at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper100
wrapper, Int32 inputID, IDTSBuffer100 pDTSBuffer, IntPtr bufferWirePacket) End Error Error: 2015-02-25 13:21:45.94     Code: 0xC0047022     Source: Insert TLM Headers SSIS.Pipeline
Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Script Component" (205) failed with error code 0x80131501 while processing input "Input 0" (215). The identified component returned an error
from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:21:41 PM Finished: 1:21:45 PM Elapsed: 4.009 seconds. The package execution failed. The step failed.
Thanks
Pankaj

domain\user account has not proper rights
That being said, often SSIS jobs require a proxy to be runnable and this is how you make one up
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Arthur
MyBlog
Twitter

How to run Exe file through Sql server agent job

Hello All
i have 2 servers
1.Application Server
2.Database server
Application server has a .exe file so i wanted to run this exe file through SQL server agent job from database server.
What is the process for run this Exe file
Can you plz suggest me step by step process
Kamal

While i'm trying to implement this below method
Step1 : Right Click SQL Server Agent. Select New -> Job. This will open a wizard to schedule a new
job.
Step2 : Select Steps from options given on the left side of wizard. This is the main place to set your
exe\program as a running step. Give some name to this step, Select Operating System (cmdexec) for the Type and give the full path of exe in Text box for Command.
ex:\\10.11.00.98(your application serverIP)\ch.exe
Thanks vanchan-Please
mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers
I got this below error
Message
Executed as user:NJROSJ345\SYSTEM. The process could not be created for step1 of job
(Reason:Access is Denied)The step failed.
But i have sys admin rights on the both the servers
Kamal

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....

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...

Database Mail Fails For SQL Server Agent Jobs / Maintenace plans - Why ?

Database Mail Fails For SQL Server Agent Jobs / Maintenace plans - Why ?
This has been a very common question I have seen relatedt to Database mail and I thought will post here so if you run into this issue, it could be due to one of the following and also have mentioned below how to get around them. Bottom line is datbase mail works fine with SQL Agent jobs and maintenace plans in SP1 on all platforms.
1. If you see this on 64 bit platform and on RTM build, this is a bug that is addressed in SP1.
2. If you see the below error message, it is known issue and this is because of design that requires SQL Agent to restart, if SQL Agent was started before enabling databasemail and setting a new profile. We are evaluating to change this design of not requiring to restart agent for our future release.
Re: 264] An attempt was made to send an email when no email session has been established
This problem will go away after restarting SQL Server Agent in this case. Thanks,
Gops Dwarak, MSFT

This may be related to the fact that DBMail, by default, shuts itself down after 10 minutes of inactivty. If the mail service isn't running, you won't be able to queue up any mail messages.
There may be a built-in mechanism for addressing this problem, but I found that I can detect this situation and start the mail listener before sending db mail. I use the following in stored procs that need to send email.
You could increase the inactivity period for db mail shutdown from 600 seconds to some larger value.  It might not make sense to do so, since shutting it down releases its resources back to teh system; if your SQL server only sneds mail infrequently, it might be better to start the mail listener on demand. Someone with more experience than I might want to add their two cents' worth. :-)
/* Check the mail engine. Start the service if is is stopped         */
/* -- the DB Mail engine shuts down after 10 minutes (of inactivity) */
/* -- this setting can be changed, but we probably don't need to.    */
DECLARE @rc INT
IF NOT EXISTS (SELECT * FROM msdb.sys.service_queues
               WHERE name = N'ExternalMailQueue' AND is_receive_enabled = 1)
    EXEC @rc = msdb.dbo.sysmail_start_sp
    -- TODO: add handling and logging for any engine start issues

SQL Agent Job Notification - Database Mail problem

Hi
I'm a little stumped. Have setup database mail on SQL Server 2008 (SP1 x64) and its working fine except when its supposed to send out a SQL Agent job notification.
I've enabled database mail on SQL Agent and have specified a profile, but when it tries to send an email on agent job completion it errors with "NOTE: Failed to notify '<operator>' via email."
Can anybody help?
Thanks

Hi Webdawg,
As suggested above, try these steps.
1. Try test email first, this can be by done (right click on database mail under mangement folder). prior to that you should already have a profile configured to send the emails and make sure you got the right SMTP server and do not block
port 25.
2.If test is succeeds, enable mail option under sql server agent properties and select 'database mail' and corresponding profile.Add the reciepents email to the operators under sql server agent(check the enabled option here). Restart the SQL sever
here.
3. Create your sql job and in the notifcations section you should see email option and should have the operator email you configured above.
Try it out. let us know. Hope it helps.
If the test succeeds and still you did not get the email from sql job, check the database mail log and check whether it is being queued. let us know.
Please mark as 'Answer', if the solution solves your problem.

SQL SERVER AGENT JOB ERROR - SSIS PACKAGE

Hi ,
I have a SQL server agent job which runs SSIS package as the daily job. The SSIS package contains multiple child package. Its a master package which calls other SSIS package. The master package calls 23 SSIS packages, few of the packages runs in parallel.
I am getting the below 2 different errors more frequently. It fails only in the production server, I scheduled the job in UAT server, it did not fail. Also when we run the master package with out sql agent job, it did not fail.
Error 1 :
R6025 - pure virtual function call. The return value was unknown. The process exit code was 255. The step failed.
Error 2 : The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
We tried browsing for the answers ,no luck. It failing in live , so we need to run the package manually in live server every time.
Please help me to resolve this issue. Thanks in advance.
Regards,
Dhivya Sivakumar

Hi Vijeth,
Thanks for your reply.
1) Run the Package manually and check whether it runs successfully. -
No Failures. Package completed succesfully
2) If Step 1 is successful,
a) Point the same package to the UAT database and run it and check whether it runs successfully or not. -
We tried to schedule the package almost for 1 month. No failures in UAT.
b) In UAT database, point to the Production database and run the package. - I am not sure, if i can do this.I will try and let you know the result.
These steps will help us identify whether the problems lies within the package or the Environment.
3) Run the Package manually in production Environment using dtexec utilily. -
No Failures. Success.
4) Check the ID used to run the SQL Agent job and modify to an account with elevated permissions or GRANT more permissions to the existing ID. -
The account used currently is having all the privileges. Its the most powerful user in live DB.
Regards,
Dhivya S

SQL Server agent job failing to back up database

I have set up a SQL server agent job to back up database on regular basis.. For some reason the back up fails.. Could not find any meaningful info in the logs.. Transaction logs are getting created for the same DB but not the database back up..
The below is my environment..
MS SQL Server 2005 - 9.00.1399.06
Windows 2003 server SP2
Any pointers would be helpful.. I checked the event logs and the agent logs and did not see obvious error.
Thanks

I have set up a SQL server agent job to back up database on regular basis.. For some reason the back up fails.. Could not find any meaningful info in the logs.. Transaction logs are getting created for the same DB but not the database back up..
The below is my environment..
MS SQL Server 2005 - 9.00.1399.06
Windows 2003 server SP2
Any pointers would be helpful.. I checked the event logs and the agent logs and did not see obvious error.
Thanks
NO answer can be provided unless you show us the error message. There can be numerous reasons for backup job to fail. See job history for details please post complete information present in job history.
Check errorlog and note what error message is there at time when the backup job failed. You could find something useful. Please learn how to post question in forum just saying I have a problem will not help both of us.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Error While executing a SSIS package which contains a script task through SQL Server Agent job

Hi,
I have a SQL Server 2012 SSIS package with a script task along with other tasks [data flow, execute sql tasks ]. When I manually executed the job through BIDS, its completed successfully.
Then I have automated the execution of the package through SQL Server Agent Job. But when I executed the package through SQL Agent job, it runs successfully for all the tasks except script task. When it comes to execute the Script Task, it is getting failed
with the below error message.
"Error: 2012-08-29 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
I have installed the SSIS on the 64-bit environment and SSIS service is running. Also I tried to run the job through 32 bit [job option] but I am getting the above error in all cases.
Any help will be greatly appreaciated !
Thanks,
Navin
- naveen.reddy

Hi Arthur,
My script task access the excel files in a network share, refresh them all and save them. When I execute the ETL manually or thru DTEXEC, it is executing successfully. I am facing the issue when I am executing thru SQL Agent Job only. Logging also showing
the same error.
"Error: 2012-08-23 12:45:14.67
Code: 0x00000001
Source: Script Task
Description: Exception has been thrown by the target of an invocation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 12:45:10 PM
Finished: 12:45:14 PM
Elapsed: 4.353 seconds
- naveen.reddy

Error: Failed to acquire connection while exporting a file using SSIS package through SQl Server Agent job.

Hi Team,
I am running a sql server job which is loading data to a sharepoint document library.File is an excel format and is getting loaded
when executed through SSDT solution .But when i am using an SQL Agent job to pick up the file it doesnt get the path and agent job fails with the error "Failed to acquire connection".I have deployed the SSIS Package through SQL Server 2012 deployment
methodologies.
I am not able to trace the error of loading data from a sharepoint library.library. Sql agent jobs works fine when i give local path.The
account which is running the sql agent job is the same who has access to document library.I also tried to run the job through proxy account. I am using a xml configuraion to store my credentials.I am able to palce the same file to a network drive in the same
server through sql server agent job. The only problem is when I am trying to load the file to a sharepoint folder.
Thanks,
Arsa..

Is that the WebDAV method that you are suggesting here to map the n/w drive?
Its kind of webdav but you will be using windows nw drive to store data
yes, I am able to create the file to D: , but didn't check with the C:.
Try with c:, as c: require special permisssions
If this helped you resolve your issue, please mark it Answered

SQL Server Agent Jobs error for Slowly changing dimension

Hi,
I have implemented Slowly changing dimension in 5 of my packages for lookup insert/update.
All the packages are running good in SSDT. And when i deployed the project to SSISDB and run the packages all are running successfully. But when i created a job out of that and run the packages, then 3 packages ran successfully and 2 packages failed.
When i opened All Execution Report. I found the following error:
Message
Message Source Name
Subcomponent Name
Process Provider:Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description:
"Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing
a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.". An OLE DB record is available.
Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ".
Process Provider
Slowly Changing Dimension [212]
Then i opened Provider package in SSDT and changed the source reading record limit from 4,00,000 to 15,000 in source query and deployed again and run, then the job succeeded. more than 15,000 failed.
And in the 2nd experiment, I removed slowly changing dimension task and implemented normal lookup for insert/update, and set the source reading limit again to 4,00,000 and deployed again and run, then the job succeeded.
Now i am not able to figure out, what exactly is the problem with Slowly changing dimension task for more than 15,00 records in SQL Server Agent Job run?
Can anybody pls help me out.
Thanks
Bikram

Hi Vikash,
As i have mentioned in the above post, below 2 scenarios:
"Then i opened Provider package in SSDT and changed the source reading record limit from 4,00,000 to 15,000 in source
query and deployed again and run, then the job succeeded. more than 15,000 failed.
And in the 2nd experiment, I removed slowly changing dimension task and implemented normal lookup for insert/update, and set the source reading limit again to 4,00,000 and deployed again and run, then the job succeeded."
That means i am able to connect to sql server.
But if i change the 1st scenario and read 4,00,000 records, the job fails and shows the above mentioned error.
Similarly in the 2nd scenario, if i implement SCD look up, the job fails and shows the above mentioned error.
And i am consistently reproducing this.
Thanks
Bikram

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

Similar Messages

Maybe you are looking for