SSIS package is failing when using SQL server agent

I am trying to execute an SSIS package through an SQL server agent and receiving the following error:
Message
Executed as user: serv-syst\SYSTEM. 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:56:53 PM Error: 2014-04-21
13:56:54.81     Code: 0xC0202009     Source: PACKAGEWMG Connection manager "DestinationConnectionOLEDB"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E4D Description: "Login failed for user 'hsnzha'.". End Error Error: 2014-04-21
13:56:54.82     Code: 0xC00291EC     Source: Drop table(s) SQL Task 1 Execute SQL Task     Description: Failed to acquire connection "DestinationConnectionOLEDB". Connection may not be configured
correctly or you may not have the right permissions on this connection. End Error Error: 2014-04-21 13:56:54.82     Code: 0xC0202009     Source: PACKAGEWMG Connection manager "DestinationConnectionOLEDB"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E4D Description: "Login
failed for user 'hsnzha'.". End Error Error: 2014-04-21 13:56:54.82     Code: 0xC00291EC     Source: Preparation SQL Task 1 Execute SQL Task     Description: Failed to acquire connection
"DestinationConnectionOLEDB". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:56:53 PM
Finished: 1:56:54 PM Elapsed: 0.844 seconds. The package execution failed. The step failed.
My SSIS package retrieves a excel file and saves the vales into an SQL table. When I run the package by itself in my server it works fine but when it's called from a SQL agent, it fails with the above error. Please help me resolve it.

That's the issue. If it's a SQL login the password cannot be retrieved by account executing the package from the job which is why login fails. In that case best thing would be set password in job properties or pass it using configuration created in the package
See
HTTP://blogs.msdn.com/b/runeetv/archive/2011/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs
My package is saved with ServerStorage which appears under \\server\Stored Packages\MSDB\PACKAGE and when I run it, it works fine.
There is a new error message that I get now after following the steps from the link...
Message
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.1600.1 for 32-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 3:34:22 PM
Error: 2014-04-21 15:34:23.82
   Code: 0xC0202009
   Source: PACKAGEWMG Connection manager "SourceConnectionExcel"
   Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Office Access Database Engine" Hresult: 0x80004005 Description: "Unexpected error from external database driver (????????).".
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC020801C
   Source: Data Flow Task 1 Source - 'Contact Center$' [1]
   Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" 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-04-21 15:34:23.82
   Code: 0xC0047017
   Source: Data Flow Task 1 SSIS.Pipeline
   Description: component "Source - 'Contact Center$'" (1) failed validation and returned error code 0xC020801C.
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC004700C
   Source: Data Flow Task 1 SSIS.Pipeline
   Description: One or more component failed validation.
End Error
Error: 2014-04-21 15:34:23.82
   Code: 0xC0024107
   Source: Data Flow Task 1
   Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 3:34:22 PM
Finished: 3:34:23 PM
Elapsed: 1.25 seconds

Similar Messages

Running multiple SSIS packages using SQL Server Agent question.

I have a multitude of SSIS packages I want to run using SQL Server Agent. What would the best practice be for running these jobs using SQL Server Agent? One job per package or running all pakages from one job? If you have an answer can
you explain the technical reasoning behind your answer? Thanks in advance.
Stan Benner

Hi, maybe a bit more analysis will give a better answer
Do all the packages have to run in sequence? (if yes, single job better)
Can the list of packages to be executed be grouped by dependency (ex package 1,2 and 5 must run in sequence and can be executed by one job, while package 3,4 are not dependent on package 1,2 and 5 can be run by a separate job).
Can any jobs be run in parallel?
How often will the package execution sequence change?
How will you deploy your packages and job? (the more jobs to create the more install script needed and upgrade scenarios become messy).
My personal preference:
I create ONE ssis package which is executed by ONE sql agent job. lets call this 'PackageExecutionWrapper.dtsx'
PackageExectionWrapper then contains multiple 'Execute Package' tasks for the packages you want to execute.
In the package you can apply any package execution rules - which packages have to run after the other, which packages can run concurrently, which packages should only run if previous succeeded.
If you need to change the sequence, simple, just update the PackageExecutionWrapper package.

SSIS Import XML task running in SQL Server Agent fails

I have created an SSIS package to import some XML files into my SQL2014 datawarehouse. If I run this package through the visual studio designer it works fine. The XML files are stored on a remote share accessed via UNC path. When I schedule the package to
run using SQL server agent it fails with the following errors :-
Executed as user: SPRINGFIELD\MSSQL. Microsoft (R) SQL Server Execute Package Utility Version 12.0.2000.8 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 12:01:53 Error: 2014-11-18 12:01:59.78
Code: 0xC02090CF     Source: Import Screen XML XML Source [199]     Description: There was an error setting up the mapping. The device is not ready. End Error Error: 2014-11-18 12:01:59.78
Code: 0xC0047019     Source: Import Screen XML SSIS.Pipeline     Description: XML Source failed the prepare phase and returned error code 0xC02090CF. End Error DTExec: The package execution returned DTSER_FAILURE
(1). Started: 12:01:53 Finished: 12:03:32 Elapsed: 98.859 seconds. The package execution failed. The step failed.
The user MSSQL has been granted full permissions to the remote share. If I remove these permissions then I don't get an error - but I also don't get any data imported. I have granted the MSSQL user xp_cmdexec permission. Both my SQL server database engine
and agent are running as the MSSQL user.
There must be some permission step I am missing - can anyone tell me what it may be ?

FYI: The XSD path is hardcode... if you want it to be more flexible you can add an expression on that property:
http://microsoft-ssis.blogspot.com/2014/09/xsd-location-hardcoded-in-xml-source.html
Please mark the post as answered if it answers your question | My SSIS Blog:
http://microsoft-ssis.blogspot.com |
Twitter

Running .exe file on remote computer using SQL server Agent JOb

I am trying to run exec file on a remote server by using sql server Agent job,
what is the best way to do this
k

Configure it as an operating system job step:
http://technet.microsoft.com/en-us/library/ms190264.aspx
Alternate: build an SSIS package and schedule it as a job.
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Run the SSIS Package using sql server Agent--Memory utilization Problem

Hi,
I have Created one SSIS Package it was working fine in BIDS but in SQL Server Agent it takes all the server memory and server gets very slow now.
in that ssis package i am using merge join,sorting tasks.Can you please suggest me how to handle in the memory usage for this..pls refer the below screen

Hi aravindhrm,
You can enable BufferSizeTuning logging event on the Data Flow Task to get how many rows in buffer. Or you can use Performance Counter to obtain more details about the buffers.
http://microsoft-ssis.blogspot.com/2013/04/performance-best-practice-more-rows-per.html
http://www.sql-server-performance.com/2009/ssis-an-inside-view-part-3/
Then, you can tweak the DefaultBufferMaxRows and DefaultBufferMaxSize size settings.
Besides, you can also go through the blog mentioned by Visakh and try suggestions such as increase OS pagefile size.
Regards,
Mike Yin
TechNet Community Support

Is it possible to Deploy a SSIS package to catalog with a Sql Server Identity in SQL Server 2012 programmly ?

Hi,
how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
This question has worried me for days.
Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
Or just an new solution instead of using the catalog.deploy_project?
best wishes from Qingyuan Lee.

Sorry, my description may be confusable.
I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
In fact, I don't care about the authority.
I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
so, using EXECUTE AS to change the execution context is accaptable.
The requirement for a Windows Authentication Account makes sense.
I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
Thanks very much for your help.

SP 2013 - Database Recovery Mode When Using SQL Server Mirroring

Hello Community,
Our DBA is configuring a High Availability Architecture for our SharePoint 2013 Farm. Essentially he is using SQL Server Database mirroring with a clustered automatic failover using a witness server. He has informed me that mirroring requires
that the databases are set to Full Recovery Mode, but that several of the databases are set to Simple Recovery Mode, the databases are the following:
SearchService_DB
SearchService_DB_CrawlStore
SearchService_DB_AnalyticsReportingStore
SearchService_DB_LinksStore
WSS_UsageApplication
User_Profile_DB
User_Sync_DB
User_Social_DB
However, when I checked the following article -
http://technet.microsoft.com/en-us/library/cc678868.aspx - I see that Simple Recovery Mode is the default configuration for these databases. So, finally, here is my question - will it be detrimental to these databases to set them to the Full Recovery
Mode?
Thanks!
Tom
Tom Molskow - Senior SharePoint Architect - Microsoft Community Contributor 2011 and 2012 Award -
Linked-In - SharePoint Gypsy

This really depends on your recovery objectives. The main reason for taking log backups, aside from truncating the log, is to be able to recover to a specific point-in-time. This is very helpful in mission-critical, highly transactional systems. I have not
seen a SharePoint environment require a point-in-time restore of the content or application service database. So for this case, you can overwrite the LDF bakups. Just make sure that you can recover your databases appropriately and meet your recovery objectives
on the farm level.
As far as the log file growth is concerned, you are correct. If you cap the size of your LDF file to let's say 10 GB, regular log backups will truncate the log, thereby, having space for additional transaction log records. The only risk here is when your
log backups are not frequent enough that the LDF file fills up before the next log backup runs to truncate the log. You run the risk of your database behaving as read-only and that will affect the site collections/applications using those databases
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Getting error code 1 when calling SSIS package from a stored procedure (SQL Server 2008 R2)

Hello,
I am trying to execute a SSIS package from SQL Server 2008 R2 stored procedure but getting error code 1 (as per my knowledge, error code description is as below:
0 The package executed successfully.
1 The package failed.
3 The package was canceled by the user.
4 The utility was unable to locate the requested package. The package could not be found.
5 The utility was unable to load the requested package. The package could not be loaded.
6 The utility encountered an internal error of syntactic or semantic errors in the command line.
Details:
I have a stored procedure named "Execute_SSIS_Package" (see below sp) which executes 'Import_EMS_Response' SSIS package (when I execute this package directly from SQL Server BID it works fine it means package itself is correct) and calling
it from SQL as:- EXEC Execute_SSIS_Package 'Import_EMS_Response'.
Here I receives error code 1.
Can anyone help me to resolve this issue please?
Thanks in advance!
CREATE PROCEDURE [dbo].[Execute_SSIS_Package]
@strPackage nvarchar(100)
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
DECLARE @cmd VARCHAR(8000)
DECLARE @Result int
DECLARE @Environment VARCHAR(100)
SELECT @Environment = Waarde
FROM Sys_Settings
WHERE Optie = 'Omgeving'
--print @Environment
SET @strPackage = '"\W2250_NGSQLSERVER\BVT\' + @Environment + '\' + @strPackage + '"'
SET @cmd = 'dtexec /SQL ' + @strPackage + ' /SERVER "w2250\NGSQLSERVER" /Decrypt "BVT_SSIS" /CHECKPOINTING OFF /REPORTING E'
--print @cmd
EXECUTE @Result = master..xp_cmdshell @cmd, NO_OUTPUT
--print @Result
END

It has something to do with the security.
E.g. cmdshell is not enabled or the caller has not rights over the package.
There could be a syntax error, too.
I suggest you make the package runnable off a SQL Agent job then trigger the job from the stored proc with
sp_start_job <job name>
Arthur
MyBlog
Twitter

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

Run SSIS package in a machine without Sql Server

Hi All,
I have 3 packages which are doing fairly easy job. First uploading flat file to remote server from my local machine. Second does some transformation and third load file back to my local machine. I am running all of them through batch file. Now, I have to
run those 3 batch files in my colleague machine which doesn't have any instance of MSSQL or Visual Studio.I sent batch files to his machine and when he runs, first one is working probably which uploads file to remote server, however second batch file doesn't
working. My guess is because batch file has some tsql syntax whereas he doesn't have MSSQL is making issue. (I added the code below). Is it possible? I can not install SQL Server to his machine but I need to run these packages(or batch files). Is there any
idea how to achieve this? Thanks in advance for your input.
osql -U sa -P mypassword -S myremoteserver -Q "msdb.dbo.sp_start_job N'ExistingOpp'"
pause

Hi Ozkantr,
The osql utility is installed by SQL Server. You need to make sure the utility is installed on your colleague machine.
To run SSIS package outside the BIDS, only the DTExec utility which is a client tool is not enough, the server components for Integration Services Service (SSIS runtime) is also required. To install SSIS runtime and DTExec utility, we must install the Integration
Services shared feature from the SQL Server install media. So, you need to install SSIS service on the machine where the SSIS packages jobs run.
References:
http://www.bigator.com/2012/03/11/ways-to-execute-ssis-package/
http://www.codeproject.com/Articles/219494/SSIS-Overview-Part-I
Regards,
+1
You need to install Integration Services, which installs the necessary bytes on your computer and the SSIS service as well. The service can be disabled though, you don't need it to run packages.
I wrote a blog post about it some time ago:
When is DTEXEC installed?
ps: osql is deprecated. Better start using sqlcmd.
MCSE SQL Server 2012 - Please mark posts as answered where appropriate.

How to export SSIS package to File system in SQL Server 2012

I am accessing SSIS package by connecting to a database engine. I wanted to export the SSIS to file system. How to get it done in sql server 2012? I tried Util utility , i got package not present. Let me know what other options are available to export to
file system?
Mano

Hi Mano,
After exporting the project stored in a SSISDB catalog to an .ispac file, we can modify the extension .ispac to .zip, then, we can extract the zip file to get the .dtsx package files. Besides, please note that if there are project level connection managers
or parameters, their definition cannot be exported to individual packages.
Regards,
Mike Yin
TechNet Community Support

Selecting data source in physical view in OBIEE 11G when using sql server

Hi,
I doing my physical view against a 2008 R2 SQL Server. Looks like the list goes upto 2005. Should I select 2005 in that case? As per image: http://i.imgur.com/3H7MO.png
Cheers.
I am using OBIEE 11G 32bit Windows.

Hi,
Yes can. either you can select as SQL 2005 or ODBC basic also can
I hope your version less than obiee11.1.1.5.0, version 11.1.1.1.6.0 and above has update SQL 2008 in the data source selection list.
refer,
http://imgur.com/JSYoL
Thanks
Deva

Scheduling without using SQL Server Agent

Can I have a scheduling job that run a group of packages on SSIS in a specific time? I can't use SQL Agent Job...

Yes, you can.
1) You have to create batch (.bat) file which will have a command that will run your ssis package by using dtexec.
E.g. dtexec.exe /F "C:\ImportCSV\Package.dtsx"
2) Schedule above .bat file using Windows Task Scheduler
http://geekepisodes.com/sqlbi/2010/schedule-ssis-package-execution-with-windows-task-scheduler/
http://syntaxsiragugall.blogspot.in/2013/04/deploying-ssis-in-task-scheduler-with.html
Cheers,
Vaibhav Chaudhari
[MCTS],
[MCP]

Installation failed when using Jumpstart Server to install SUN Netra T1 200

I have a problem to install a couple of Sun Netra T1 200 Servers with a Jumpstart Server. The Jumpstart Server is set up and I have executed the add_install_client Script. If I boot the Server which should to be installed the server crashes after getting the assigned IP-Address with a software fault.
Attached i will sent the Jumpstart-Client-Output and the config Files of the Jumpstart-Server.
****Netra T1 Server Output, while configured as an Jumpstart client:****
ok boot net -install
Resetti
LOM event: +2h28m47s host reset
ng ...
`
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #16692502.
Ethernet address 8:0:20:fe:b5:16, Host ID: 80feb516.
Executing last command: boot net -install
Boot device: /pci@1f,0/pci@1,1/network@c,1 File and args: -install
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
Timeout waiting for ARP/RARP packet
2ae00 Warning: boot will not enable cache
Requesting Internet address for 8:0:20:fe:b5:16
Enter filename [kernel/sparcv9/unix]:
Enter default directory for modules [platform/SUNW,UltraAX-i2/kernel /platform/sun4u/kernel /kernel /usr/kernel]:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
whoami: no domain name
panic[cpu0]/thread=300010a9ba0: Can't invoke , error 2
000002a1000f7a40 genunix:icode+274 (ffbefff0, 0, 300010a7b88, 0, ffbefffc, ffffffffffffffff)
%l0-3: 00000000ffbefffc 0000000000000000 0000000000002000 000002a10000fd20
%l4-7: 0000000000000bb8 0000000010423a00 000000001041b2f8 00000000000007a9
syncing file systems... done
skipping system dump - no dump device configured
rebooting...
Resetti
LOM event: +2h36m51s host reset
ng ...
p
Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
OpenBoot 4.0, 1024 MB memory installed, Serial #16692502.
Ethernet address 8:0:20:fe:b5:16, Host ID: 80feb516.
Executing last command: boot
Boot device: disk File and args:
SunOS Release 5.8 Version Generic_108528-13 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
configuring IPv4 interfaces: eri0.
Hostname: infrasrv
The system is coming up. Please wait.
checking ufs filesystems
/dev/rdsk/c1t0d0s4: is stable.
/dev/rdsk/c1t0d0s6: is stable.
Starting IPv4 routing daemon.
starting rpc services: rpcbind done.
Setting netmask of eri0 to 255.255.255.0
Setting default IPv4 interface for multicast: add net 224.0/4: gateway infrasrv
syslog service starting.
Print services started.
Jun 26 04:48:14 infrasrv sendmail[220]: My unqualified host name (infrasrv) unknown; sleeping for retry
volume management starting.
The system is ready.
infrasrv console login: root
Password:
Last login: Thu Jun 26 02:13:59 on console
Jun 26 04:48:24 infrasrv login: ROOT LOGIN /dev/console
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
# uname -i
SUNW,UltraAX-i2
# ^[[A
^[[A: not found
# uname -m
sun4u
*****Config Files of the Jumpstart-Server******************
Sysidcfg
bootparams
bash-2.03# more bootparams
infrasrv root=adminws:/cdrom/sol_8_202_sparc/s0/Solaris_8/Tools/Boot install=ad
minws:/export/install boottype=:in sysid_config=adminws:/export/sysidcfg install
_config=adminws:/export/config rootopts=:rsize=32768
bash-2.03#
rules
bash-2.03# more rules
#       @(#)rules 1.12 94/07/27 SMI
# The rules file is a text file used to create the rules.ok file for
# a custom JumpStart installation. The rules file is a lookup table
# consisting of one or more rules that define matches between system
# attributes and profiles.
# This example rules file contains:
#   o syntax of a rule used in the rules file
#   o rule_keyword and rule_value descriptions
#   o rule examples
# See the installation manual for a complete description of the rules file.
# RULE SYNTAX:
# [!]rule_keyword rule_value [&& [!]rule_keyword rule_value]... begin profile fi
# nish
# "[ ]" indicates an optional expression or field
# "..." indicates the preceding expression may be repeated
# "&&" used to "logically AND" rule_keyword and rule_value pairs together
# "!" indicates negation of the following rule_keyword
# rule_keyword a predefined keyword that describes a general system
# attribute. It is used with the rule_value to match a
# system with the same attribute to a profile.
# rule_value a value that provides the specific system attribute
# for the corresponding rule_keyword. A rule_value can
# be text or a range of values (NN-MM).
# To match a range of values, a system's value must be
# greater than or equal to NN and less than or equal to MM.
# begin a file name of an optional Bourne shell script
# that will be executed before the installation begins.
# If no begin script exists, you must enter a minus sign (-)
# in this field.
# profile a file name of a text file used as a template by the
# custom JumpStart installation software that defines how
# to install Solaris on a system.
# finish a file name of an optional Bourne shell script
# that will be executed after the installation completes.
# If no finish script exists, you must enter a minus sign (-)
# in this field.
# Notes:
# 1. You can add comments after the pound sign (#) anywhere on a line.
# 2. Rules are matched in descending order: first rule through the last rule.
# 3. Rules can be continued to a new line by using the backslash (\) before
# the carriage return.
# 4. Don't use the "*" character or other shell wildcards, because the rules
# file is interpreted by a Bourne shell script.
# RULE_KEYWORD AND RULE_VALUE DESCRIPTIONS
# rule_keyword rule_value Type rule_value Description
# any minus sign (-) always matches
# arch text system's architecture type
# domainname text system's domain name
# disksize text range system's disk size
# disk device name (text)
# disk size (MBytes range)
# hostname text system's host name
# installed text text system's installed version of Solaris
# disk device name (text)
# OS release (text)
# karch text system's kernel architecture
# memsize range system's memory size (MBytes range)
# model 'text' system's model number
# network text system's IP address
# totaldisk range system's total disk size (MBytes range)
# RULE EXAMPLES
# The following rule matches only one system:
# hostname sample_host - host_class set_root_pw
# The following rule matches any system that is on the 924.222.43.0 network
# and has the sun4c kernel architecture:
# Note: The backslash (\) is used to continue the rule to a new line.
#network 924.222.43.0 && \
# karch sun4c - net924_sun4c -
# The following rule matches any sparc system with a c0t3d0 disk that is
# between 400 to 600 MBytes and has Solaris 2.1 installed on it:
#arch sparc && \
# disksize c0t3d0 400-600 && \
# installed c0t3d0s0 solaris_2.1 - upgrade -
# The following rule matches all x86 systems:
#arch i386 x86-begin x86-class -
# The following rule matches any system:
#any - - any_machine -
hostname infrasrv - infrasrv_class -
hostname msm_srv1 - msm_srv_class -
hostname msm_srv2 - msm_srv_class -
bash-2.03#
class
bash-2.03# more infrasrv_class
install_type initial_install
system_type standalone
partitioning explicit
filesys c0t0d0s0 2048 /
filesys c0t0d0s1 10
filesys c0t0d0s3 1024 swap
filesys c0t0d0s4 2048 /var
filesys c0t0d0s5 2048 /opt
filesys c0t0d0s6 free /export
cluster SUNWCXall
bash-2.03# more msm_srv_class
install_type initial_install
system_type standalone
partitioning explicit
filesys c0t0d0s0 2048 /
filesys c0t0d0s1 10
filesys c0t0d0s3 1024 swap
filesys c0t0d0s4 2048 /var
filesys c0t0d0s5 free /opt
cluster SUNWCXall
bash-2.03#
ethers
bash-2.03# more ethers
8:00:20:fe:b5:16 infrasrv
bash-2.03#
hosts
bash-2.03# more hosts
# Internet host table
127.0.0.1 localhost
192.168.0.220 adminws loghost
192.168.0.210 infrasrv
192.168.0.200 tc
bash-2.03#
dfstab
bash-2.03# more dfstab
# Place share(1M) commands here for automatic execution
# on entering init state 3.
# Issue the command '/etc/init.d/nfs.server start' to run the NFS
# daemon processes and the share commands, after adding the very
# first entry to this file.
# share [-F fstype] [ -o options] [-d "<text>"] <pathname> [resource]
# .e.g,
# share -F nfs -o rw=engineering -d "home dirs" /export/home2
share -d "jumpstart conf dir" /export/config
share -F nfs -o ro,anon=0 /export/install
share -F nfs -o ro,anon=0 /cdrom/sol_8_202_sparc/s0/Solaris_8/Tools/Boot
bash-2.03#
tftpboot
bash-2.03# pwd
/tftpboot
bash-2.03# ls -al
total 348
drwxrwxr-x 2 root other 512 Jun 26 11:45 .
drwxr-xr-x 24 root root 512 Jun 26 11:45 ..
lrwxrwxrwx 1 root other 26 Jun 26 11:45 C0A800D2 -> inetboot.SUN4U.Solaris_8-1
lrwxrwxrwx 1 root other 26 Jun 26 11:45 C0A800D2.SUN4U -> inetboot.SUN4U.Solaris_8-1
-rwxr-xr-x 1 root other 159416 Jun 26 11:45 inetboot.SUN4U.Solaris_8-1
-rw-r--r-- 1 root other 318 Jun 26 11:45 rm.192.168.0.210
lrwxrwxrwx 1 root other 1 Jun 26 11:45 tftpboot -> .
bash-2.03#

Hi,
It seems to me that you have not created a proper sysidcfg file. From your post, it looks to me like your sysidcfg contains no entries. This is why it prompts you to enter the kernel path. Look on docs.sun.com for a guide to creating the sysidcfg file .

Schedule SSIS packages as job in SQL Server Agent errors

Hi, I am using SQL Server 2008 R2 and created few SSIS packages and schedule them using SQL Server Agent and every time I try to schedule packages via SQL Server Agent my jobs keep failing. I am using domain/ione as the owner and when I invoke the job on
ServerA let's say and the job gets executed by domain/ServerA$ and fails as it does not have enough privileges. How do I fix this issue firstly without the proxy and why is the job being executed by domain/ServerA$ when the owner & user who invokes
it is domain/ione?
Thanks in advance............
Ione

Hi Ione,
The owner of any SQL jobs should be SA or any other non-expiring account
If you do not want the proxy used, then add the needed priveleges.
The owner of the job is one, the SSIS step gets executed by the account the Agent is running under.
Arthur
MyBlog
Twitter

SSIS package is failing when using SQL server agent

Similar Messages

Maybe you are looking for