Sql Server Multi server job issue

Hi,
I have configured a multi server job in maintenance plan, Master server sql2012 sp1 and i have connected 4 target servers, out of 4 target server, 3 of them is same sql2012 version created MSX job is running and only one server is sql 2008r2 MSX
job is not running it throws an error'The package could not be loaded', My question is why the job is not running in Multi server method and i want to know maintennance plan of 2012 will support lower version 2008r2 or not.

According to Books Online, you cannot have lower versions of SQL Server as target servers when you run SSIS packages. Perhaps you can run the package using DTEXEC.EXE instead of SSIS job step type. Assuming that you are indeed executing an SSIS package
in the first place, that is!
Tibor Karaszi, SQL Server MVP |
web | blog

Similar Messages

SQL Server upgradation Issue : 2012 to 2014. A job step received an error at line 1 in a PowerShell script. The corresponding line is 'set-executionpolicy RemoteSigned -scope process -Force'. Correct the script and reschedule the job.

Message
Executed as user: CORPTST\XXXXX. A job step received an error at line 1 in a PowerShell script. The corresponding line is 'set-executionpolicy RemoteSigned -scope process -Force'. Correct the script and reschedule the job. The error information returned
by PowerShell is: 'Security error. '. Process Exit Code -1. The step failed.
I receive this error during the sql server job 'syspolicy_purge_history' execution when sql server got upgraded form SQL Server 2008 to 2014.

Hi Vishnu,
According to the error message, it also occurs in SQL Server 2012. Here is a feedback about the error in the link below.
https://connect.microsoft.com/SQLServer/feedback/details/754063/sql-server-2012-syspolicy-purge-history-job-step-3-fails-with-security-error
To resolve this issue, please change the value of the following registry key from ‘RemoteSigned’ to ‘Unrestricted’. For more details, you can review this similar
blog.
HKLM\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.SqlServer.Management.PowerShell.sqlps120\ExecutionPolicy
Thanks,
Lydia Zhang

Firing SQL Server Job Through Java

Hi All
How can I fire a SQL Server Job from Java. I am from data warehousing background and new to java. I process my cubes though a package in DTS and have encapsulated the package in a job.
I can connect to the SQL Server where the package & job reside.
Regards
Abhinav

Can it be called like a stored procedure? If so (and probably it can) look into CallableStatement... a good first step would be to see how to run it through SQl statements in an admin tool (like QueryAnalyzer) to see how it can be invoked.
If it can be invoked through SQL at all you can call it in Java. Also be aware of permission issues.

Alternative step on Biztalk "terminator" process, regarding disabling all sql server jobs prior to running.

I am getting errors in one of the BT jobs, they recommend running a terminator tool available from MS ... One of the requirements is to disable all the sql server jobs, my question is: Can I just stop the sql server agent? Or this won't do it ....
Thanks
Bico Bielich

Hi,
I assume that you are talking about issue identified by Monitor BizTalk Server job.
Why you want to stop the sql server agent? There could be other Non-BizTalk jobs running too.
You just need to make sure that you have a BizTalk Backup of your databases, all the BTS hosts have been stopped,
BTS SQL Agent jobs have been disabled.
Refer:
http://blogs.msdn.com/b/biztalkcpr/archive/2011/02/10/using-biztalk-terminator-to-resolve-issues-identified-by-biztalk-msgboxviewer.aspx
Pls follow the link and perform action based on the respective issue reported by the
Monitor BizTalk Server job.
Rachit

What is the commands for SQL server job to ftp file to remote server?

I created the job to bcp data out and create file on file system. after that, I need to ftp the file over to another box. how can I do it from sql server job?
JulieShop

I would like to suggest a SSIS package with a
FTP Task instead.
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL Server jobs fail if I signout the Remote Desktop connection

I have some SSIS jobs running in the production server which we usually take that server by Windows' Remote Desktop Connection to monitor the jobs. The problem in our case is If we sign out the server in remote connection, all the sql server jobs getting failed
until we reestablish a remote connection but the jobs work fine if we close the remote connection explicitly by the (x) mark on the Remote Connection interface
Any idea on this issue

always same error like the following
Code: 0xC0014009 Source: Connection manager "Invoice"
Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server. End Error Error: 2015-01-12 08:00:05.26 Code: 0x0000020F Source: DFT GetData [2]
Description: The AcquireConnection method call to the connection manager Invoice failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error:
2015-01-12 08:00:05.26
Code: 0xC0047017 Source: DFT GetData SSIS.Pipeline
Description: Data failed validation and returned error code 0x80004005. End Error Error: 2015-01-12 08:00:05.27
Code: 0xC004700C Source: DFT GetData SSIS.Pipeline
Description: One or more component failed validation. End Error Error: 2015-01-12 08:00:05.28
Code: 0xC0024107 Source: DFT GetData
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:00:00 AM Finished: 8:00:06 AM Elapsed: 5.678 seconds. The package execution
failed. The step failed.

SQL Server Job Monitoring

Hi,
I am looking at implementing Grid Control monitoring on our SQL Server estate.
One of the items we need to monitor for is SQL Server jobs which have failed (including job name and date).
Does anyone have an idea of how this can be done. I'm sure I must be missing a trick here as it would seem strange that this information is being collected but can't be put into a metric or notification.
Any assistance or pointers greatly appreciated!

Could you please clarify what exactly is your question and what phase are you in implementing monitoring SQL Server usign Grid Control?
Are you just about to install the plug-in for SQL Server or you are already trying to configure monitoring SQL Server jobs? I'm asking this because you mentioned "I am looking at implementing Grid Control monitoring on our SQL Server estate." which implies you are just planning to implement.
Try reading metalink note 367797.1. You'll find lots of information and other metalink notes which may resolve your problem.
If you can clarify your exact problem, the better.

Required info on SQL Server Performance Issue Analysis and Troubleshoot way

Dear All,
I am going to prepare the simple documentation steps on SQL Server Performance Issue Analysis and troubleshoot method. I am struggling to make this documentation since we have different checklist (like network latency,disk latency, memory/processor pressure,SQL
query tuning etc) to validate once application performance issue reported from the customer.So, I am looking for the experts document or link sharing .
Your input will help for document preparation in better way.
Thanks in advance.

Hi,
Recommendations and Guidelines on configuring disk partitions for SQL Server
http://support.microsoft.com/kb/2023571
Disk and File Layout for SQL Server
https://blogs.technet.com/b/dataplatforminsider/archive/2012/12/19/disk-and-file-layout-for-sql-server.aspx
Microsoft SQL Server 2012 Performance Tuning: Implementing Physical Database Structure
http://www.packtpub.com/article/sql-server-2012-implementing-physical-database-strusture
Database Mirroring Best Practices and Performance Considerations
http://technet.microsoft.com/en-us/library/cc917681.aspx
Hope the information helps.
Tracy Cai
TechNet Community Support

Sql server job is succeeding even though it should fail

Hi,
I created a sql server job with one job step for a SSIS package using Powershell.
When I run the job (manually), it shows "success" state, but it should fail (because of the bad configuration parameters).
But if I go to job properties, and then edit job step properties (don't have to make any changes here, just clicking ok button is enough)
then the job run will fail as expected.
I am not sure why it is not failing first time?
Any help is appreciated.
Thanks
-Bhargavi

I set "QuitWithFailure" option for the 'OnFailAction' of the job.
$jobStep.OnFailAction = "QuitWithFailure"
Here is the code:
       write-Host ""
        Write-Host "Create job for $tenantid"
        $jobName = "Auto-"+$tenantid
        $job = New-Object Microsoft.SqlServer.Management.SMO.Agent.Job($server.JobServer,$jobName)
         #Delete the job if it already exists
        if($Server.JobServer.Jobs.Contains($jobName))
             write-host "Deleting job $jobName"
            $sqlCommand.CommandText = "EXEC msdb.dbo.sp_delete_job @job_name = N'$jobName',
           @delete_unused_schedule=1;"
            $result = $sqlCommand.ExecuteNonQuery()
        $job.Create()
        #Create job step
        Write-host "Creating job step for $jobName"
        $jobStep = New-Object Microsoft.SqlServer.Management.Smo.Agent.JobStep($job, $jobName)
        $jobStep.Subsystem= [Microsoft.SqlServer.Management.Smo.Agent.AgentSubSystem]::SSIS
        $jobStep.Command = "/ISSERVER \SSISDB\"+$ssisFolderName+"\"+$ssisProjectName+"\Test.dtsx"+" /SERVER "+$instanceName
        $jobStep.OnSuccessAction = "QuitWithSuccess"
        $jobStep.OnFailAction = "QuitWithFailure"
        $jobStep.Create()
        $job.ApplyToTargetServer($instanceName)
        $job.StartStepID =$jobStep.ID
        $job.Alter()

SQL Server Connection Issue

I've tried going through the steps to resolve the issue, but I am still coming up blank. The part that I am not understanding is the, "A non-recoverable error occurred during a database lookup." part.
Is this a security problem? I can establish an ODBC connection to the server as well as connect and query through visual studio, however when trying to run it through one of our custom programs, it throws this error message.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A non-recoverable error occurred during a database lookup.)

There are many reasons of SQL server connectivity issue. Refer checklist to find out the real cause of connectivity issue.
1. Check SQL services are running
2. Check SQL Browser service is running
3. Check remote connections are enabled
4. Network connectivity between database & application servers by TRACERT command
5. Check TCP/IP protocol enabled at SQL server
6. Check talent connectivity – telnet <IP address> <port no on SQL server running>
7. Check UDP port 1434 is open or not on SQL Server
8. Check firewall is running or not Check
9. If firewall running, SQL Server & UDP port must be added in exception in firewall
10. Run SQL Discovery report on machine SQL server installed, to check you are using correct instance name to connect( default \named) -http://mssqlfun.com/2013/02/26/sql-server-discovery-report/
http://mssqlfun.com/2012/09/28/check-list-for-sql-server-connectivity-issue/
Regards,
Rohit Garg
(My Blog)
This posting is provided with no warranties and confers no rights.
Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

Sql Server Connection Issues

After reinstalling Windows Server 2008 R2 EE my SQL 2008 R2 Sp2 Instances have some connection issues.
The server were installed under the same hostname, but he got a new sid in my active directory.
On the server there one DB Engine MSSQLSERVER, two named Reporting Services for MS crm 4.0 and SCOM and one Analysis Services Instance.
The DB Engine will collect Data from another DB, before writing to Analysis Services.
Here are the problems on the server:
When I connect via SSMS remotly, I sometimes get this error: Failed to connect to server <hostname> ... Named Pipes Provider, error 40 - Could not open a connection to SQL Server - Error 5
Both RS Instances have many event log errors like "Report Server (Instance) cannot connect to the report server database.". RS Reports are working fine, but sometimes the rendering is taking a long
time.
The DB Engine Agent Job to collect Data sometimes throw the following error: 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: "Unable to complete login process due to delay in opening server connection". End Error Error: 2013-12-10 06:03:40.41 Code: 0xC00291EC
User use Excel to connect to the Cube on my server. Often they got timeout errors. When they connect again it will work.
Are there any solutons on this?
Thanks a lot!

Hello,
The server were installed under the same hostname, but he got a new sid in my active directory.
Did you connect to SQL Server instance with Windows authentication? Since the SID of domain account is changed, the SQL Server instace may cannot verify the login account which stored in the master with old SID. In that case, please try to connect
SQL Server with SQL authentication and then readd the domian as login the instance.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SQL Server Job that were written in SSIS packages failed

could not load package files system because of error 0x80070002. Description: could not find file 'C:\program files\microsoft SQL Server\100\DTS\Binn\. The package could not be loaded. The step failed. I found this error on one of my job configured in
ssis packages which take a view statement from my production server, which actually is in a cluster environment. Thank you guys

It's a little difficult to infer what could be happening without having an idea about what the package does. If you can share one or two screenshots of it, it would be great. You will need Business Intelligence Development Studio (BIDS) for SQL 2008 or previous,
or SQL Data Tools if SQL 2012. Right click over the package in the file system and select "Edit".
In the meanwhile, let me give some ideas for troubleshooting:
If your servers are 64bits, be sure your SQL Agent Job step for the SSIS package is running also in 64bits.
Assuming your package basically takes data from the view and move it to other server, main of the workload should be at read time from the view. Try running the SQL statement that package is issuing and take the time. If the time is still less than
3 minutes, your package should have more logic/transformations doing other tasks that we will need to look in. If time is much more, maybe you have much more data in the view underlying tables.
If querying from the view is still so fast, we will need to understand what the package is doing after the initial read.
HTH
Please, mark this post as Answer if this helps you to solve your question/problem.
Alan Koo | "Microsoft Business Intelligence and more..."
http://www.alankoo.com

Running SSIS 2005 in SQL Server Job Agent 2012

Hi Guys,
I'm trying to create a job in SQL 2012 that calls an SSIS 2005 package, however i'm getting some issue. I researched the issue a bit and got this link . The given link suggested to use dtexec as SQL 2012 try to convert it in the memory.
I used the dtexec but I'm still getting an issue.
"Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 4:11:19 PM Error:
2015-04-13 16:11:26.24 Code: 0xC0012024 Source: OTH Market Exist? Description: The task "OTH Market Exist?" cannot run on this edition of Integration Services. It requires a higher level edition. End
Error Error: 2015-04-13 16:11:26.24 Code: 0xC0012024 Source: Arcticle CSV Exist? Description: The task "Arcticle CSV Exist?"
cannot run on this edition of Integration Services. It requires a higher level edition. End Error Error: 2015-04-13 16:11:26.24 Code: 0xC0012024 Source: BV Market Exist? Description:
The task "BV Market Exist?" cannot run on this edition of Integration Services. It requires a higher level edition. End Error Error: 2015-04-13 16:11:26.51 Code: 0xC002F210 Source: No Input
Files Email Execute SQL Task Description: Executing the query "DECLARE @result int; EXEC @result = security.dbo.spSendEmail
@Subject='[GFK Import & Export] - All Input Files Are Missing',
@Message ='Processing has been stopped due to missing input files',
@ToID =25, @ccID =0,
@Attachment =''" failed with the following error: "Database 'security' does not exist. Make sure that the name is entered correctly.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly,
It seems that I do need to upgrade my packages to run in SQL 2012 unless if there's another way without upgrading it that would be great.
I just want to get the confirmation if possible or not
Many thanks guys.

Hi Vaibhav,
I created 2 jobs. the first job calls a simple package that execute a single SQL. It ran
successfully when I execute the said job using this command
DTEXEC /FILE "\"C:\TFS\WDSHE SSIS Packages from DTS\GFK_Test_package.dtsx\"" /DECRYPT stud10 /CHECKPOINTING OFF /REPORTING E
2nd Job, calls a complex package which contains several execute process tasks. this job fails with the error mentioned at the top.
Now, I modified the simple package in the first job and add an Execute Process Task.
I'm started to get an issue
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 4:51:57 PM Error: 2015-04-13
16:52:01.32 Code: 0xC0012024 Source: Unzip BV ZIP Description: The task "Unzip BV ZIP" cannot run on this edition of Integration Services. It requires a higher level edition. End Error DTExec:
The package execution returned DTSER_FAILURE (1). Started: 4:51:57 PM Finished: 4:52:01 PM Elapsed: 4.212 seconds. Process Exit Code 1. The step failed.
Have you had a similar issues before?
I will try to install the SSIS service and see how I go. thanks for the link

Conversion Error During the Execution of SQL Server Job

Hello,
I have a production SQL server and a test SQL server that mimics the production server. On the production server all the jobs which do a variety of things using Transact SQL and SSIS packages work flawlessly. However one of the jobs on the test server fails
at a step and issues the following error:
executed as user: DomainName\administrator. Conversion failed when converting datetime from character string. [SQLSTATE 22007] (Error 241).
The step failed.
Here is the code contained in the steps Command window (same exact code that works fine on the production server):
declare @Now datetime
declare @DB_Date datetime
declare @Trip_Err datetime
select @Now = convert(varchar,getdate(),101)
select @DB_Date = (select convert(varchar,max(ProcessDate),101) from I_Loans)
if @now <> @DB_Date
begin
truncate table I_Loans
end
else
select @Trip_err = 'error'
I don’t see anything preventing this code from executing. However, I am not a programmer. My SQL Server version is below:
Microsoft SQL Server 2005 - 9.00.5324.00 (Intel X86)
Aug 24 2012 14:24:46 Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 6.0 (Build 6002: Service Pack 2)
Any advice or solutions will be greatly appreciated. Please let me know if I need to provide more information.
Thank you,
Dave
David Young

Could you run this query from management studio in test?
select convert(varchar,max(ProcessDate),101) from I_Loans
It could be something to do with the ProcessDate value which had issues to convert
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Executing SSIS packages through SQL Server Jobs.

Hi,
I have an SSIS package which generates xml and text files and ftps it to an ftp site. When i run the package from BIDS it works successfully but when i run it from a job it fails. My SSIS package connects to DB server A and though i'm creating a job on DB
server A but my folder structure and the package resides in server B from where i'm connecting to DB server A through Management Studio. I'm using File system in SQL server Agent Job to call the package. When i execute the job i get following error:
Executed as user: I\A. ...er Execute Package Utility Version 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 5:08:05 PM Error: 2011-06-21 17:08:05.11
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: 2011-06-21 17:08:05.11 Description:
Failed to open package file "E:\P\H\R\Tools\R\R\R.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 . The step failed.
Could you please tell me where am i going wrong?
Thanks,
Deepti
Deepti

Hi Christa Kurschat,
I'm running the job under proxy account. And that account has sysadmin permissions.
I used following script to create proxy account and run my package under that account:
I. Create job executor account
Highlight Security->New Login, say to make login as devlogin, type your password, default database can be your target database.
Server roles: check �sysadmin�
User mapping: your target database
Msdb database: you make sure to include
SQLAgentUserRole, SQLAgentReaderRole, SQLAgentOperatorRole
Then click OK
II. Create SQL proxy account and associate proxy account with job executor account
Here is the code and run it the query window.
Use master
CREATE CREDENTIAL [MyCredential] WITH IDENTITY = 'yourdomain\myWindowAccount', secret = 'WindowLoginPassword'
Use msdb
Sp_add_proxy @proxy_name='MyProxy', @credential_name='MyCredential'
Sp_grant_login_to_proxy @login_name=' devlogin', @proxy_name='MyProxy'
Sp_grant_proxy_to_subsystem @proxy_name='MyProxy', @subsystem_name='SSIS'
III. Create SSIS package
In MS SQL Server Business Intelligence Development Studio, you use job executor account devlogin to create the SSIS package (DTS) and make sure you can execute this package
in SQL Server Business Intelligence Development Studio. Compile/build this package.
IV. Create the job, schedule the job and run the job
In SQL Server Management Studio, highlight SQL Server Agent -> Start. Highlight Job ->New Job�, name it , myJob.
Under Steps, New Step, name it, Step1,
Type: SQL Server Integration Service Package
Run as: myProxy
Package source: File System
Browse to select your package file xxx.dtsx
Click Ok
Schedule your job and enable it
I followed these steps.
Thanks,
Deepti
Deepti

Sql Server Multi server job issue

Similar Messages

Maybe you are looking for