Notify more than 1 operator in a SQL Agent job

Hi Forum,
is there a way to notify more than one operator if a SQL Agent job fails?
TIA
Alex

Hello Alex,
If you are using a "maintenance plan" task "Notify operator" you can select several operators from a list.
In a SQL Server Agent job itself you can only add several operator for "warnings", but for the notifications like "finished" just one.
Olaf Helper ----------- * cogito ergo sum * errare humanum est * quote erat demonstrandum * Wenn ich denke, ist das ein Fehler und das beweise ich täglich http://olafhelper.over-blog.de

Similar Messages

More than one operation defined. Unable to resolve operation

Hi,
Using the attached WSDL to define a BPEL sequence I allways get the following error message:
More than one operation defined. Unable to resolve operation:
This occured in the moment i introduced a seconde operation. With one operation everything works fine.
Does anybody know how to define a WSDL that works for the BPEL system with more than one operation?
Best Regards,
Axel.
WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://dummy.ws.axelbenz.de/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://dummy.ws.axelbenz.de/" name="StringInOutService" xmlns:plink="http://schemas.xmlsoap.org/ws/2004/03/partner-link/">
<types>
<xsd:schema>
<xsd:import namespace="http://dummy.ws.axelbenz.de/" schemaLocation="upperService.xsd" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" />
</xsd:schema>
</types>
<message name="lowerMessage">
<part name="lowerParameters" type="tns:lowerType" />
</message>
<message name="lowerMessageResponse">
<part name="lowerResponseParameters" type="tns:lowerTypeResponse" />
</message>
<message name="upperMessage">
<part name="upperParameters" type="tns:upperType" />
</message>
<message name="upperMessageResponse">
<part name="upperResponseParameters" type="tns:upperTypeResponse" />
</message>
<portType name="StringInOut">
<operation name="lowerOperation">
<input message="tns:lowerMessage" />
<output message="tns:lowerMessageResponse" />
</operation>
<operation name="upperOperation">
<input message="tns:upperMessage" />
<output message="tns:upperMessageResponse" />
</operation>
</portType>
<binding name="StringInOutPortBinding" type="tns:StringInOut">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<operation name="lowerOperation">
<soap:operation soapAction="lower" style="document" />
<input>
<soap:body use="literal" parts="lowerParameters" />
</input>
<output>
<soap:body use="literal" parts="lowerResponseParameters" />
</output>
</operation>
<operation name="upperOperation">
<soap:operation soapAction="upper" style="document" />
<input>
<soap:body use="literal" parts="upperParameters" namespace="" />
</input>
<output>
<soap:body use="literal" parts="upperResponseParameters" />
</output>
</operation>
</binding>
<service name="StringInOutService">
<port name="StringInOutPort" binding="tns:StringInOutPortBinding">
<soap:address location="http://GWBE0040.int.gematik.de:18181/DummyServices/StringInOutService" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" />
</port>
</service>
<plink:partnerLinkType name="partnerlinktype1">
<plink:role name="serviceRequestor" portType="tns:StringInOut"/>
</plink:partnerLinkType>
</definitions>
XSD:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema version="1.0" targetNamespace="http://dummy.ws.axelbenz.de/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="lower" type="ns1:lowerType" xmlns:ns1="http://dummy.ws.axelbenz.de/" />
<xs:complexType name="lowerType">
<xs:sequence>
<xs:element name="inp" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
<xs:element name="lowerResponse" type="ns2:lowerTypeResponse" xmlns:ns2="http://dummy.ws.axelbenz.de/" />
<xs:complexType name="lowerTypeResponse">
<xs:sequence>
<xs:element name="return" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
<xs:element name="upper" type="ns3:upperType" xmlns:ns3="http://dummy.ws.axelbenz.de/" />
<xs:complexType name="upperType">
<xs:sequence>
<xs:element name="inp" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
<xs:element name="upperResponse" type="ns4:upperTypeResponse" xmlns:ns4="http://dummy.ws.axelbenz.de/" />
<xs:complexType name="upperTypeResponse">
<xs:sequence>
<xs:element name="return" type="xs:string" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:schema>

What client are you using? Are you using the netbeans enterprise pack test driver? If so, you can set the soap action in the test properties to match the ones you have defined in the WSDL.
Also if you could post the actual soap message you are sending that would help.
I also noticed that you're using parts defined via types with a document/literal binding. To be more basic profile compliant in that casue you may want to use RPC style instead - it is not strictly necessary, but increases interoperability.
Andi

Service interface with more than one operation

Hi all,
is it possible to have a service interface with more than one operation?
I have found this blog:
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID0209118050DB10459657028039341762End?blog=/pub/wlg/15123
But this sentence:
ABAP proxy (inbound/ outbound) cannot be developed out of a Service Interface having Operations with different type of messages included. If an ABAP proxy is to be developed then all the messages included should be of one type i.e. either the included messages should be Message Type, External Message, IDOC or RFC Message. This behavior can be observed when a Service Interface is created and then subjected for a check
regards

Hi,
now the interface is running but I get another error in .NET.
"The header 'Diagnostic' from the namespace 'http://sap.com/xi/XI/Message/30' was not understood by the recipient of this message, causing the message to not be processed. This error typically indicates that the sender of this message has enabled a communication protocol that the receiver cannot process. Please ensure that the configuration of the client's binding is consistent with the service's binding. "
Any ideas?
regards

Publish more than one operation by WebService

Hi all
Somebody can helpme saying me how to do the following with eGate ( i cant use eInsight ):
For now im enabled to publish one operation and one webservice, but mi problem is that i can't publish one WebService with more than one operation and i can't change the mandatory "ExecutePortType", all my webservices url are in the form:
http://<server>:<port>/myws/ExecutePortType
1. Why the context name is about the WebService and why ExecutePortType is mandatory ?
2. I can't publish a Web Service with more than one operation ( The documentation says that the ExecutePortType supports just one operation )?
some body can helpme with an example ?

What client are you using? Are you using the netbeans enterprise pack test driver? If so, you can set the soap action in the test properties to match the ones you have defined in the WSDL.
Also if you could post the actual soap message you are sending that would help.
I also noticed that you're using parts defined via types with a document/literal binding. To be more basic profile compliant in that casue you may want to use RPC style instead - it is not strictly necessary, but increases interoperability.
Andi

Javax.jbi.messaging.MessagingException: More than one operation defined

Hi,
i had already implemented a web service consisting of 6 methods that works fine. Now i want to access this service via JBI. Therefore i developed a service assembly containing only of a soap binding component. When i try to access the jbi environment via the inbound endpoint OpenESB throws following exception:
[#|2006-07-26T16:23:50.531+0200|WARNING|sun-appserver-pe9.0|com.sun.jbi.component.com.sun.httpsoapbc-1.0-2com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor|_ThreadID=32;_ThreadName=httpWorkerThread-12010-2;_RequestID=a33dbb24-d088-4a6a-9642-96187c32bb36;|Exception in processing request.
javax.jbi.messaging.MessagingException: More than one operation defined. Unable to resolve operation: {http://service}UseRepositoryService,UseRepository,inbound
     at com.sun.jbi.httpsoapbc.InboundMessageProcessor.execute(InboundMessageProcessor.java:214)
     at com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.processAsynchRequest(GrizzlyRequestProcessor.java:214)
     at com.sun.jbi.httpsoapbc.embedded.GrizzlyRequestProcessor.service(GrizzlyRequestProcessor.java:173)
     at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
     at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:70)
     at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:143)
     at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:132)
     at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:81)
     at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
     at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
How can i specify in my service assembly that if i send a SOAP request for method X on my client that OpenESB routes this message to the correct Outbound endpoint?
Thank you
Thomas

Hello Andi,
thanks for your reply. To exclude the soap action error i will post the complete wsdl file now. But in my opinion every operation has its own input and output definition.
The consumer wsdl:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://service" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://service" xmlns:intf="http://service" xmlns:tns1="http://types" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>
<schema elementFormDefault="qualified" targetNamespace="http://service" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://types"/>
<element name="loadEcore">
<complexType>
<sequence>
<element name="ecoreId" type="xsd:long"/>
</sequence>a
</complexType>
</element>
<element name="loadEcoreResponse">
<complexType>
<sequence>
<element name="loadEcoreReturn" type="xsd:base64Binary"/>
</sequence>
</complexType>
</element>
<element name="loadInstance">
<complexType>
<sequence>
<element name="instanceId" type="xsd:long"/>
</sequence>
</complexType>
</element>
<element name="loadInstanceResponse">
<complexType>
<sequence>
<element name="loadInstanceReturn" type="xsd:base64Binary"/>
</sequence>
</complexType>
</element>
<element name="loadInstanceForProject">
<complexType>
<sequence>
<element name="instanceId" type="xsd:long"/>
</sequence>
</complexType>
</element>
<element name="loadInstanceForProjectResponse">
<complexType>
<sequence>
<element name="loadInstanceForProjectReturn" type="xsd:base64Binary"/>
</sequence>
</complexType>
</element>
<element name="deleteInstance">
<complexType>
<sequence>
<element name="instanceId" type="xsd:long"/>
</sequence>
</complexType>
</element>
<element name="deleteInstanceResponse">
<complexType>
<sequence>
<element name="deleteInstanceReturn" type="xsd:boolean"/>
</sequence>
</complexType>
</element>
<element name="getAllInstancesFromDB">
<complexType/>
</element>
<element name="getAllInstancesFromDBResponse">
<complexType>
<sequence>
<element maxOccurs="unbounded" name="getAllInstancesFromDBReturn" type="tns1:InstancePackageValueBean"/>
</sequence>
</complexType>
</element>
<element name="saveInstance">
<complexType>
<sequence>
<element name="resourceBytes" type="xsd:base64Binary"/>
<element name="fileName" type="xsd:string"/>
</sequence>
</complexType>
</element>
<element name="saveInstanceResponse">
<complexType>
<sequence>
<element name="saveInstanceReturn" type="xsd:boolean"/>
</sequence>
</complexType>
</element>
</schema>
<schema elementFormDefault="qualified" targetNamespace="http://types" xmlns="http://www.w3.org/2001/XMLSchema">
<complexType name="InstancePackageValueBean">
<sequence>
<element name="ecoreId" type="xsd:long"/>
<element name="fileName" nillable="true" type="xsd:string"/>
<element name="id" type="xsd:long"/>
<element name="name" nillable="true" type="xsd:string"/>
<element name="usedModels" nillable="true" type="xsd:string"/>
</sequence>
</complexType>
</schema>
</wsdl:types>
<wsdl:message name="loadEcoreRequest">
<wsdl:part element="impl:loadEcore" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadEcoreResponse">
<wsdl:part element="impl:loadEcoreResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="saveInstanceResponse">
<wsdl:part element="impl:saveInstanceResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadInstanceForProjectResponse">
<wsdl:part element="impl:loadInstanceForProjectResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadInstanceResponse">
<wsdl:part element="impl:loadInstanceResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="getAllInstancesFromDBRequest">
<wsdl:part element="impl:getAllInstancesFromDB" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadInstanceRequest">
<wsdl:part element="impl:loadInstance" name="parameters"/>
</wsdl:message>
<wsdl:message name="getAllInstancesFromDBResponse">
<wsdl:part element="impl:getAllInstancesFromDBResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="loadInstanceForProjectRequest">
<wsdl:part element="impl:loadInstanceForProject" name="parameters"/>
</wsdl:message>
<wsdl:message name="saveInstanceRequest">
<wsdl:part element="impl:saveInstance" name="parameters"/>
</wsdl:message>
<wsdl:message name="deleteInstanceRequest">
<wsdl:part element="impl:deleteInstance" name="parameters"/>
</wsdl:message>
<wsdl:message name="deleteInstanceResponse">
<wsdl:part element="impl:deleteInstanceResponse" name="parameters"/>
</wsdl:message>
<wsdl:portType name="UseRepository">
<wsdl:operation name="loadEcore">
<wsdl:input message="impl:loadEcoreRequest" name="loadEcoreRequest"/>
<wsdl:output message="impl:loadEcoreResponse" name="loadEcoreResponse"/>
</wsdl:operation>
<wsdl:operation name="loadInstance">
<wsdl:input message="impl:loadInstanceRequest" name="loadInstanceRequest"/>
<wsdl:output message="impl:loadInstanceResponse" name="loadInstanceResponse"/>
</wsdl:operation>
<wsdl:operation name="loadInstanceForProject">
<wsdl:input message="impl:loadInstanceForProjectRequest" name="loadInstanceForProjectRequest"/>
<wsdl:output message="impl:loadInstanceForProjectResponse" name="loadInstanceForProjectResponse"/>
</wsdl:operation>
<wsdl:operation name="deleteInstance">
<wsdl:input message="impl:deleteInstanceRequest" name="deleteInstanceRequest"/>
<wsdl:output message="impl:deleteInstanceResponse" name="deleteInstanceResponse"/>
</wsdl:operation>
<wsdl:operation name="getAllInstancesFromDB">
<wsdl:input message="impl:getAllInstancesFromDBRequest" name="getAllInstancesFromDBRequest"/>
<wsdl:output message="impl:getAllInstancesFromDBResponse" name="getAllInstancesFromDBResponse"/>
</wsdl:operation>
<wsdl:operation name="saveInstance">
<wsdl:input message="impl:saveInstanceRequest" name="saveInstanceRequest"/>
<wsdl:output message="impl:saveInstanceResponse" name="saveInstanceResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="UseRepositorySoapBinding" type="impl:UseRepository">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="loadEcore">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="loadEcoreRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="loadEcoreResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="loadInstance">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="loadInstanceRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="loadInstanceResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="loadInstanceForProject">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="loadInstanceForProjectRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="loadInstanceForProjectResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="deleteInstance">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="deleteInstanceRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="deleteInstanceResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="getAllInstancesFromDB">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="getAllInstancesFromDBRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="getAllInstancesFromDBResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="saveInstance">
<wsdlsoap:operation soapAction=""/>
<wsdl:input name="saveInstanceRequest">
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output name="saveInstanceResponse">
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="UseRepositoryService">
<wsdl:port binding="impl:UseRepositorySoapBinding" name="UseRepository">
<wsdlsoap:address location="http://localhost:12010/service/repository"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
Except for the service name, port, address etc the provider wsdl is the same.
Could you tell me if it works when i will only use one operation for example?
I had already implemented a service assembly which contained only one operation. That SA worked fine.
If the Service Assembly and Binding Component descriptors had wrong references e.g. the wrong interface-name, would OpenESB throws an exception while deployment?
In addition, could you tell me a good link to a nice bpel engine example? How is the interaction between client ans service using the bpel engine?
I think using the SoapBC the interaction is following:
Client --> BC --> Service
With Bpel engine?
Client --> BC --> bpel --> BC2 --> service?
Thanks a lot
Thomas

How to Notify more than one person in case of error in ALE

In ALE/EDI, While maintaining Partner Profile(we20), if in case we want to notify more than one person in case of error, how to maintain it in the <b>Post Processing: Permitted Agent tab</b>? Can anyone guide me navigating through the steps on how to proceed with this?

enter in to the T-code.
first it asks for validation from date click it.U will get th einitial screen.
1.Enter the organisation name & description found at the basic data tab and press enter u can see that name will be diaplayed at the top grid.
2.In the tool bar of the grid u can see drop down box in that select staff assignment.
3.Now select createposition icon.
4.Now place the cursor in user field right click & select assign->user in that enter ur user.
Repeat the process to number of users.
Save it.

Assignment of components to more than one operation in routing.

Hi to all,
I am trying to allocate components of material BoM to more than one operation in routing. I know one way to do it is to define that components again & agin in material BoM & assigned them to operations in routing. Are other ways available to do the same.
Thanks & regards,
Abu Arbab

Dear,
Now I am clear.
You need to create different 2 BOM and with BOM items, as below,
example - total requirement of material A is say 10.
Semi finished Product- X BOM
BOM item 1 - material A-qty 8
BOM item 2 - material B-qty -5
Finished material Y - BOM
BOM item 1 - semifished material X-qty 10
BOM item 2 - material C-qty 10
BOM item 3 - material A-qty 2
BOM item 4 - material D-qty -2
You need to create above 2 BOM's if you want to see semifished product into inventory, if not proceed as below
Finished material Y - BOM
BOM item 1 - material A-qty 8 assign it to routing operation 10
BOM item 2 - material B-qty -5 assign it to routing operation 10
BOM item 2 - material C-qty 10 assign it to routing operation 20
BOM item 3 - material A-qty 2 assign it to routing operation 30
BOM item 4 - material D-qty -2 assign it to routing operation 30
I think this is the only way you can map it.

Is it possible to monitor more than one target/Host with one agent in OEM 12c?

Hi,
Is it possible to monitor more than one target/Host with one agent in OEM 12c? Please assist me on this

Since by definition a single EM agent must reside on a single database host, then, no, you can't monitor multiple hosts.
Unless you mean that you want to monitor multiple virtual hosts from a single physical host ... but in that case, you'd still need one host per database host.
That's just the way EM works. Always has, probably always will.

Errors running SQL Agent Jobs for 64 bit SSIS packages on a 64 bit server, but Source server 32 bit

Hi,
I can able ran the SSIS package in BIDS, since set to false in Run64BitRuntime property.
Then I created SQL server Agent job I tried the following ways
Step 1:
Type is set as SQL Server Integration Services Packages,
Run as - SQL Server Agent Service Account
Package source - FileSystem
then Execution option tab I selected 32 bit runtime
and then run the job I am getting the below error
Message
Executed as user: CIT\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 7:29:17 AM Error: 2013-11-28
07:29:18.57     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 07:29:18.57
Code: 0xC0014009     Source: Imports20_OAC_Gifts Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the
database server. End Error Error: 2013-11-28 07:29:18.59     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection
manager DataSource.DataExtract 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: 2013-11-28 07:29:18.59
Code: 0xC0047017     Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-2
Step 2:
Type - Operating sytem (CmdExec)
Run as - Sql Server agent service account
Command - C:\Program Files\Microsoft SQL Server\110\DTS\Binn\dtexec.exe /FILE "D:\Example\Example.dtsx" /x86 /CHECKPOINTING OFF /REPORTING E
then run the job I am getting the below error
Message
Executed as user: MIS\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 6:37:58 AM Error: 2013-11-28
06:37:58.94     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 06:37:58.96
Code: 0xC0014009     Source: Example Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.
End Error Error: 2013-11-28 06:37:59.01     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection manager DataSource.DataExtract
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: 2013-11-28 06:37:59.07     Code: 0xC0047017
Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-28 06:37:59.12     Code: 0xC004700C
Source: DFT_Example SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2013-11-28 06:37:59.16     Code: 0xC0024107     Source: DFT_Example
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1).Started: 6:37:58 AM Finished: 6:37:59 AM Elapsed: 1.373 seconds. Process Exit Code 1.
The step failed.
Note:
My source server is 32 bit and development environment in 64 bit
if anybody have idea please share your knowledge

Hi BIRam,
Based on the current information, the issue may be caused by the factor that the SQL Server Agent Service Account doesn’t have access to the MySQL server. Try to create a SQL Server Agent Proxy account that has sufficient permission on the MySQL server.
In addition, also pay attention to the package protection level setting.
For more information, please see:
http://social.technet.microsoft.com/Forums/sqlserver/en-US/e13c137c-1535-4475-8c2f-c7e6e7d125fc/how-do-i-troubleshoot-ssis-packages-failed-execution-in-a-sql-agent-job?forum=sqlintegrationservices.
Regards,
Mike Yin
TechNet Community Support

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.

Permissions to modify SQL Agent Jobs

Permissions
on SQL Server Agent
I would
like to assign the permission to user ,who can edit all SQL agent job(even own by others) without assigning the sysadmin role.
is it possible?
regards
EA

Hallo Ekbal,
only granting access to the procs will not fit because internally these procs check whether the executing account is member of the sysadmin-role of of any other roles which need the required permissions.
What you have to do is the development of a wrapper-proc which covers the execution with a different user. Get details concerning here:
http://msdn.microsoft.com/en-us/library/ms178106(v=sql.90).aspx
Long story short - you have to do the following steps if you execute the procedures in the context of a certificate:
1. Create a certificate you want to use for the execution of the wrapper procs in msdb
CREATE CERTIFICATE cert_Jobs
ENCRYPTION BY PASSWORD = 'myUltracomplexPassword'
WITH SUBJECT = 'Certificate for JobManagement',
START_DATE = '20120101',
EXPIRY_DATE = '29991231'
2. Backup the certificate for later implementation in the master and implementation in master database
BACKUP CERTIFICATE cert_JobHistory TO FILE = 'C:\temp\cert_JobHistory.cer';
USE master;
GO
CREATE CERTIFICATE cert_JobHistory FROM FILE = 'C:\temp\cert_JobHistory.cer';
3. Create a login based on the certifcate and make it a sysadmin
CREATE LOGIN login_JobHistory FROM CERTIFICATE [cert_JobHistory];
GRANT AUTHENTICATE SERVER TO [login_JobHistory];
GO
EXEC sp_addsrvrolemember @loginame = 'login_JobHistory', @rolename = 'sysadmin';
4. create a user in msdb for the login, create a wrapper proc for sp_update_job
USE msdb
GO
CREATE USER login_JobHistory FROM LOGIN [login_JobHistory];
GO
CREATE PROC dbo.proc_wrapper_update_job
@paramter_list of sp_upate_job
WITH EXECUTE AS OWNER
AS
BEGIN
EXEC dbo.sp_update_job @parameter_list
END
5. add signature of certificate to the proc
ADD SIGNATURE TO OBJECT::dbo.proc_wrapper_update_job
BY CERTIFICATE [cert_JobHistory]
WITH Password = ''myUltracomplexPassword';
6. Grant EXECUTE-permission on the proc to dedicated users you want to manage the jobs
IMHO this process is a bad workaround and - just my point of view - not practicable but I don't see any other solution than granting sysadmin privileges for the dedicated users. What you can do also is doing the modification to the mentioned procs but this
is definitely not recommended because these procs are system procs and you will loose support from Microsoft!
Get more details concerning execution of procedures by certificates by visiting the following links:
AUTHENTICATE SERVER:
http://support.microsoft.com/kb/906549
Using certificates for execution of procs:
http://msdn.microsoft.com/en-us/library/bb283630(v=sql.105).aspx
Uwe Ricken
MCSE - SQL Server 2012
MCSA - SQL Server 2012
MCITP Database Administrator 2005
MCITP Database Administrator 2008
MCITP Microsoft SQL Server 2008, Database Development
db Berater GmbH
http://www-db-berater.de
SQL Server Blog (german only)

LcsCDR & QoEMetrics Purge and Usage Summary SQL Agent Jobs

Hello.
On our SQL instance that hosts the LcsCDR & QoEMetrics databases I have the following SQL Server Agent Jobs:
LcsCDR_Purge
LcsCDR_UsageSummary
QoEMetrics_Purge
QoEMetrics_UsageSummary
I'd like to know if anyone else has these same jobs on their instances as it's unclear looking at the job descriptions, when they were created, and the code they run if these are part of the core Lync system or something that has been set up randomly
afterwards.
One thing I do know is that these jobs don't work correctly when you use database mirroring. I will elaborate on this if/when I can find out any more information about them first.
Thanks

Thank you for the reply.
The problem with these jobs is that when they attempt to run against a database which is a mirror, it causes the job to fail. That would not seem to be a big deal right, except our policy (and many other SQL shops I imagine) is to send e-mail notifications
each and every time a SQL agent job fails on any server, not just those associated with Lync.
As it stands these jobs are not configured on either the principal or mirror server to notify anyone as I’d get an e-mail every hour on the hour from the mirror server telling me that a job has failed (even though it didn’t actually need to do anything
) giving the impression something is wrong somewhere. This is quite a common trap to fall into with SQL Agent jobs and database mirroring.
Remember that because as Lync uses automatic failover either server could be the mirror at any given time so there is no mileage in setting the e-mail notifications on just the server that is currently the principal.
What this job should do then is when it attempts to run on the mirror, check if it’s the mirror first and if it is then do nothing instead of failing each time. This will enable e-mail notifications to be set up on the jobs on both servers, so when
the job fails we know there is potentially a genuine problem to be investigated.
Each job contains two steps, I’ll use the QoEMetrics_UsageSummary as the example.
The code in step 1 is this, which causes the job to error out if it is attempting to run against the mirror.
declare @_MirroringRole int
set @_MirroringRole = (
select mirroring_role
from sys.database_mirroring
where database_id = DB_ID('QoEMetrics')
if (@_MirroringRole is not NULL and @_MirroringRole = 2) begin
raiserror('Database is mirrored', 16, 1)
end
else begin
print ('Database is not mirrored')
end
I re-wrote this job to run in one-step like this, which runs from the master database, which as I mentioned above doesn’t make the job error out when it realises it’s trying to run against a mirror.
DECLARE @_MirroringRole INT
SET @_MirroringRole = ( SELECT mirroring_role
FROM sys.database_mirroring
WHERE database_id = DB_ID('QoEMetrics'))
-- if this is not a mirrored database or it's the principal, attempt to run usage summary op
IF (@_MirroringRole IS NULL OR @_MirroringRole = 1)
BEGIN
DECLARE @_Sql NVARCHAR(4000)
SET @_Sql =
'USE [QoEMetrics];
DECLARE @_UpdatingSkipped INT
EXEC dbo.RtcRegularMaintainDatabase @_UpdatingSkipped = @_UpdatingSkipped output'
EXEC (@_Sql)
END
ELSE -- if the database is a mirror, don't do anything
BEGIN
PRINT 'there is nothing to do, the database is a mirror'
END
The same logic can be applied to the other 3 jobs and I was intending to suggest it as a connect item, except there doesn’t seem to be a section for Lync so I will contact product support and see what they think.
Thanks again.

Powershell sql agent jobs

Hi, I am trying to check status of sql agent jobs on various servers using powershell howerver I successfully list all the servers but cant seem to be able to
Write-Output
$job.name
for any of the servers including the monitoring server that I am absolutely sure I have all required permissions. I get no errors which makes troubleshooting that much
more difficult. Any ideas? Thank you
foreach($sqlserver
in $sqlservers)
#***THIS WORKS***
write-host
$sqlserver.instancename
$srv
= New-Object ('Microsoft.SqlServer.Management.Smo.Server')
$sqlserver;
foreach ($job
in $srv.Jobserver.Jobs)
$jobName
= $job.Name;
$jobEnabled
= $job.IsEnabled;
#***THIS DOESN'T WORK***
write-host
$jobName
write-host
$job.Name
Paula

I figured it out
The line
$srv = New-Object ('Microsoft.SqlServer.Management.Smo.Server') $sqlserver;
should be:
$srv = New-Object ('Microsoft.SqlServer.Management.Smo.Server') $sqlserver.InstanceName ;
Paula

SQL agent job schedule

Hi,
I have multiple SQL agent jobs , i need to schedule these jobs to run one after other , below explanation should give you more info
job 1 scheduled every day @ 12 : 00 am
job 2 scheduled every day @ 2 : 00 am
job 3 scheduled every day @ 3 : 00 am
Issue here is some times my job 2 is starting before job 1 finishes . Which is causing problems
i want job 2 run only after job 1 is done and job 3 after job 2 and goes on
can some one please help how to do this ,any help will be appreciated

If you want the process to be sequential why not merge all of the processes into same job itself as different consecutive steps? That would be the easiest to ensure they run in sequence
If thats not possible then way to do this is as follows
1.Add a new first step to Job 2 and Job 3 as follows
IF EXISTS(
select 1
from msdb.dbo.sysjobs_view job
inner join msdb.dbo.sysjobactivity activity on job.job_id = activity.job_id
where
activity.run_Requested_date is not null
and activity.stop_execution_date is null
and job.name = <Previous Job Name Here>
RAISERROR 'Previous Job Not Completed Yet!',16,1
Replace job name correctly based on your case
Then in advanced tab make On Failure Action as quit the job reporting failure and OnSuccessAction
to default. Also set retry attempts to non zero number (say 10) and
retry interval to say 15 minutes
Once this is done Job 2 will start and keep on failing until Job 1 gets finished and it will retry itself in 15 minutes for 10 times. When Job 1 finishes in the interim the next retry will be a success and job will quit.
Do the same for Job 3 too replacing name of the job as that of Job2
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

SSIS ETL does not pick the file from Share point when it execute through SQL Agent job

I have created one SSIS packages, which pick the file from the Share point document library. its work successfully, once it execute through the VS project application.
But when i create a job in SQL Server Agent for this package then it does not pick the file and job getting fail.
Just for more update, SQL Server has been install in Cluster mode and using BIDS 2012 with SQl Server 2012.

Hi PriyankGupta,
SQL Server Integration Services is not cluster awareness, and does not support failover from one cluster node to another. So, in your clustered environment, make sure SSIS is installed on each node in the cluster. In other word, SSIS must be installed on
the server where the SQL Server Agent job is created.
If you use any third party task/component or drivers, make sure they are installed on the SQL Server Agent job server. Besides, also pay attention to the protection level of the package as well as 32-bit or 64-bit runtime mode of the package. For more information,
please see:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/e13c137c-1535-4475-8c2f-c7e6e7d125fc/how-do-i-troubleshoot-ssis-packages-failed-execution-in-a-sql-agent-job
If the issue persists, please post the error message in the job history for further analysis.
Regards,
Mike Yin
TechNet Community Support

Notify more than 1 operator in a SQL Agent job

Similar Messages

Maybe you are looking for