SCCM Package Deployment issue

Hi All,
I have created one Application package in SCCM 2012, this package has been successfully distributed in DP servers. Some of my client still this package is not showing. I have updated clients side policy as well. I want to check client side logs. So
please suggest which log file I have to check for track down this package progress.
Nirmal Singh IT Administrator

Hi,
Please make sure Application Catalog web service point and Application Catalog website point are installed successfully.(ServicePortalWebService.log and ServicePortalWebSite.log)
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

SCCM Client Deployment issue

Hi guys!
I've encountered a strange issue on a client machine side and was wondering if you guys could suggest a troubleshooting step. I am able to deploy a SCCM client successfully to a machine that has a basic Windows 7 installation, but when I try to push the
client to the same machine that has an existing image I get the following lines of code in ccm.log. Because the client push is successful when I push it to a basic Windows 7 install it leads me to think there's something on the image that's blocking something
I can't figure out what exactly. Do you guys have any suggestions?
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x800706ba   SMS_CLIENT_CONFIG_MANAGER   12/18/2013 11:18:30 AM   6284 (0x188C)
Unable to connect to WMI on remote machine "DL29", error = 0x800706ba.   SMS_CLIENT_CONFIG_MANAGER   12/18/2013 11:18:30 AM   6284 (0x188C)
Deleting SMS Client Install Lock File '\\DL29\admin$\SMSClientInstall.SEC'   SMS_CLIENT_CONFIG_MANAGER   12/18/2013 11:18:30 AM   6284 (0x188C)
Execute query exec [sp_CP_SetLastErrorCode] 16777258, -2147023174   SMS_CLIENT_CONFIG_MANAGER   12/18/2013 11:18:30 AM   6284 (0x188C)
Thanks so much!
Steve

Unable to connect to WMI on remote machine "DL29", error = 0x800706ba.
Thanks so much!
Steve
Sounds like something is blocking ports. I would start with firewall settings.
Have you seen this yet?
http://social.technet.microsoft.com/Forums/en-US/8c190525-378a-4c39-a80e-04b9e95734a0/unable-to-connect-to-wmi-on-remote-machine-machinename-error-0x800706ba?forum=configmanagerdeployment

Package deployment issues

We are experiencing some issues when we deploy our packages. We bundle our java classes in to a JAR which is deployed as part of our component package in the /app/webiste-name/install folder.
As we increment the version number for our deployment packages a new JAR is added to the install folder when it is installed, so we end up with a number of JAR files in the install folder...
/app/website-name/install/
- core-1.0.1.jar
- core-1.0.2.jar
- core-1.0.3.jar
- core-1.0.4.jar
- core-1.0.5.jar
Each time we deploy the package the server creashes. Also, in our previous package installation it appears the class in 1.0.4 was being referenced instead of the latest 1.0.5 core JAR file. We removed all JAR files from the install folder, re-installed the package and the error went away.
Should we be removing all JAR files from the install directory before installing a new package version? or should we just have the name of the JAR file as core.jar without a version number? or, something else?

put "public" in this line:
public class Test extends MovieClip{

Weblogic optional package deployment issue

Hi All,
I am using WLS 10.3.4. I have an J2EE web application which references a JAR library as an optional package. Here is my definition of JAR file in the library MANIFEST.MF,
Manifest-Version: 1.0
Extension-Name: PCGCommon2.0
Specification-Version: 1.0.0.0
Implementation-Version: common055jkp
Here is my definition of JAR file reference in the application MANIFEST.MF,
Manifest-Version: 1.0
Extension-List: pcgcommon2
pcgcommon2-Extension-Name: PCGCommon2.0
pcgcommon2-Specification-Version: 1.0.0.0
pcgcommon2-Implementation-Version: common055jkp
I deployed the JAR library first successfully. Then I tried to deploy the application. It throws me this error as follows,
+[J2EE:160149]Error while processing library references. Unresolved Optional Package references (in META-INF/MANIFEST.MF): [Extension-Name: PCGCommon2.0, Specification-Version: 1, Implementation-Version: common055jkp , referenced from: /opt/oracle/Oracle/Middleware/user_projects/domains/Pinellas1qDomain/servers/Pinellas1qMS3/tmp/_WL_user/ppa/cwbd0p/war].+
Can anyone have an idea what I am missing here?
Thanks in advance,
-John
Edited by: john wang on Mar 9, 2011 8:44 AM
Edited by: john wang on Mar 9, 2011 8:58 AM

Hi John,
Please find the working TestCase in the following Location:
http://middlewaremagic.com/weblogic/?p=231#comment-3144
I am copying and pasting the README.txt file here which i attached in the TestCase:
README.txt
Step1). Make Sure that the Hello.java is compiled properly like following:
javac -d . Hello.javaActual Trick is Making the JAR using 'M' option..... :) 
Step2). The Most important step to Make the "HelloWorld.jar" along with the MANIFEST.MF file which is present inside "HelloWorld\META-INF\MANIFEST.MF"
Use the below command with *'M'* as a Flag while making JAR file so that the Jar utility will not overrite the MANIFEST.MF on it's own rather it will place our own MANIFEST.MF inside the Jar.
C:\OptionalPackageDemo\HelloWorld\> jar -cvfM HelloWorld.jar META-INF\MANIFEST.MF Hello.java com
Step3). Deploy the HelloWorld.jar and the TestWebApp
NOTE: I just now tested the attached TestCase in WLS10.3.0 And it perfectly worked for me. So if it's not working for you in WLS10.3.4 then i would request you to please open a Support Ticket with Oracle WebLogic Support Team because ideally the same test case is supposed to work fine in that version as well.
Thanks
Jay SenSharma

Business package deployment issue EP 7.3

Hi all,
I am deploying business packages in my portal, but i am getting validation error with 3 packages..
SAP ESS 633
SAP MSS 630
SAP_ESS_LGP 6.33
But i have deployed the below packages:
SAP PCUI_GP 633
UTXSSLGP 633
BP ERP05 MSS 1.51
BP ERP UT XSS 1.51
BP ERP05 SELF-SERV ADMIN 1.3
Kindly suggest the relevant package needs to deploy for EP.
Details:
EP 7.3, Release 720, sup_pckg 68
BR,
Kutty

Hi Kutty,
Looks like your using correct packages, Do you have XML file from the Solution manager Maintenance Optimizer ? if not, try to download the relevant packages and XML from Maintenance optimizer (Solman) and try again.
Refer to below link and check the section - Upgrade to EHP5 and/or NW7.3
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES
Thanks,
Arjun

SCCM VBS Script Program Package Deployment

I'm trying to get this VBS script to run from a package to run but its not working as planned.
It works fine from an Administrator command propmt locally, but not as an sccm package/program.
Its a script to remove a SCOM management group. No matter what I try this doesn't run remotely. Even with administrative rights configured. Runs fine locally as administrator. Any ideas? Using a command line program of "cscript removescom.vbs"
Option Explicit
Dim objMSConfig
Set objMSConfig = CreateObject("AgentConfigManager.MgmtSvcCfg")
Call objMSConfig.RemoveManagementGroup ("SCOMManagementGroupNameHere")

This could also be a permissions issue. When you deploy a package with ConfigMgr, it runs as SYSTEM, which may not have SCOM rights.
You can easily test this by running your script manually with psexec -s
to emulate running as SYSTEM account.
http://blogs.technet.com/b/askds/archive/2008/10/22/getting-a-cmd-prompt-as-system-in-windows-vista-and-windows-server-2008.aspx
Daniel Ratliff | http://www.PotentEngineer.com

SCCM 2012 package deployment reboot behaviour

Hi,
When i deploy package from SCCM 2012 with default reboot behavior it forces reboot. I want to suppress the reboot and let user to postpone the reboot whenever they want with popup window as like available for SCCM patch deployment. Is there way to achieve
this. Can someone please provide suggestion if already done it.
Regards,
Madhan

Actually, default behavior does *not* force a reboot. To have ConfigMgr force a reboot, you must choose the option that says ConfigMgr forces a reboot. Thus, the command-line you've configured is forcing the reboot which means you need to adjust the command-line
to suppress the reboot as that's outside of ConfigMgr's control.
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM: Application deployment vs Package deployment with requirements and prerequisits.

Hey,
My organization is in the process of implementing a new remote networking solution for all employees, however some employees require additional software vs others. What I am trying to find out is if there is a way to have one package with supersedes and
requirements that we can use to do a massive deployement.
Here are the different scenarios with order of installation:
Financial group Desktop:
1.Install New solution
2.Install Configuration
3.Install Token Authentication
(nothing crazy)
Financial Group Laptops
1.Install Token Authentication
2.Install New Solution
3.Install COnfiguration
4.Un-uninstall Old Solution
5.Un-install Tunnel Guard application (requires a reboot, that's why it's last). (this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 5, but do 4, when 4 is triggered, it does 3 first, etc...)
All other laptops
1.Install New Solution
2.Install COnfiguration
3.Un-uninstall Old Solution
4.Un-install Tunnel Guard application (requires a reboot, that's why it's last).(this is the application that would be deployed with requirements to go back up the chain of supersedes (meaning, deploy 4, but do 3, when 3 is triggered, it does 2 first, etc...)
Because of the different requirements, is there a way to have one deployment with multiple deployment types to say based off:
1. Computer types (we have a naming convention that identifies laptops and desktops.
2. Only install certain pieces of software (Token validator in this case if financial application is detected on the machine).
Or should I create different applications for each case with different collections or go with 3 different packages and collections with install this package first set in the package deployment
Thanks for your help.

The problem is the last uninstall, because it's not applicable to all machines. That means that if you would deploy that with all it's dependencies, it wouldn't do anything on the desktops as it's not applicable to them.
In this case, if you want to use one deployment, the easiest solution is a task sequence. That way you can target everything in one time and still build some logic to prevent some (un-)installs.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Packaging/deploying a webapp client to already deployed EJBs

I have a webapp/ejb deployed on WLS 6.1. If it matters, the EJBs are
deployed in jar files but the webapp component is deployed in exploded
directory format.
Now I want to deploy another webapp that uses the same EJBs. At this
point in development, I am attempting to deploy this in exploded
directory format as well. I have run ejbc manually against the original
jars to create the EJB deployable units containing generated WL classes.
This also created a ejb-client.jar, but it does not contain any impl
classes for the home or remoted interfaces.
I tried placing the ejb-client.jar in my WEB-INF/lib but it doesn't seem
to be able to find the interface classes. Perhaps the exception I'm
getting does not mean what I think it does. It is included below.
I also tried adding the generated impl classes to the ejb-client.jar
manually, but this didn't work either. I have read the
packaging/deploying docs but don't seem to find this issue addressed
directly. From all I know, I have done this correctly, but obviously I
am missing something somewhere.
Thanks in advance for your consideration.
<May 10, 2002 1:53:57 PM CDT> <Error> <HTTP>
<[WebAppServletContext(9605583,adminApp,/adminApp)] Servlet failed with
Exception
java.lang.ExceptionInInitializerError
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:42)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:30)
at java.lang.reflect.Constructor.newInstance(Constructor.java:277)
at java.lang.Class.newInstance0(Class.java:301)
at java.lang.Class.newInstance(Class.java:254)
at javax.rmi.CORBA.Util.createDelegateIfSpecified(Util.java:342)
at javax.rmi.CORBA.Util.<clinit>(Util.java:54)
at
javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:182)
at
javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:61)
at
net.verizon.storm.util.DataBroker.initialize(DataBroker.java:102)
at
net.verizon.storm.util.DataBroker.getInstance(DataBroker.java:158)
at
net.verizon.storm.util.OrderDispatcher.<init>(OrderDispatcher.java:70)
at
net.verizon.storm.admin.OrderService.startOD(OrderService.java:159)
at
net.verizon.storm.admin.OrderService.processRequest(OrderService.java:104)
at
net.verizon.storm.admin.OrderService.doPost(OrderService.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Caused by: java.lang.RuntimeException: could not find or instantiate any
UtilDelegate class
at
weblogic.iiop.UtilDelegateImpl.<clinit>(UtilDelegateImpl.java:72)
... 24 more

Hi.
I tried placing the ejb-client.jar in my WEB-INF/lib but it >>doesn't seem to beable to
find the interface classes. Perhaps
the exception I'm getting does not mean what I think it does. >>It is includedbelow.
It seems fine since it is the way your webapp always to use its EJB client jar.
I also tried adding the generated impl classes to the ejb-
client.jar manually, but this didn't work either.Nope, you should never do this since Impl classes are used on Server Side ( webapp
treated as client of EJB in this case ) only.
It is so hard for us to analyze the problems without a test case, I would suggest
you to create a support case via http://support.bea.com/welcome.jsp to BEA support
for detailed work.
Thanks.
Ji Zhang
Developer Relations Engineer
BEA Support

Reading data file(txt) present in a file system from a package deployed in SSISDB

Hi,
I am trying to create and later read a data file from a package deployed in SSISDB, but it is not reading it while it is successfully creating the file. The same package when run from the file system package, runs successfully. Generating ispac and deploying
in SSISDB is running for infinite time. Any idea? Is it a permission issue?
Thanks
Ayush

Hi Ayush,
If I understand correctly, you directly execute a package from the file system source via Execute Package Utility, it works fine. When you right-click on a package under Integration Services Catalog \ SSISDB \ <Folder name> \ Projects \ <Project
name> \ Packages \ <Package name> and select Execute... to run a package in SQL Server Management Studio, it fails.
When we execute a package under Integration Services Catalog, the package will run under the credentials used to connect to SQL Server Management Studio. Please note that we need run the package using Windows Authentication.
As to your issue, please make sure the account connects to SQL Server Management Studio has required permissions to access the file folder and file outside the SSIS package.
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

OIM 11g: Event Handler Packaging/Deployment

Need some advice/guidance on best practices for packaging/deploying Event Handlers in OIM 11g.
In our OIM 9.1 environment, we organized all of our custom code by "functional area" so we have JAR's named oim-common.jar, oim-ad.jar, oim-oid.jar, etc. Within each one of these JAR's we have all adapter code, scheduled tasks, and 10g event handlers related to that area. This approach was done to promote code reuse and make unit testing easier.
From what I've read on 11g Event Handlers, it sounds like each event handler needs to be packaged as a plugin along with it's own JAR so that we'd have one JAR per event handler. So, if we have 100 event handlers, we'd need 100 JAR's? Is this required or can our plugin ZIP files just contain the XML definitions as long as the referenced classes are on the classpath?

Gyanprakash Pandey wrote:
You should have a separate plugin package for each event handler. Practically we should have number of event-handlers as less as possible. If there are more event-handlers we must modify the design as event handler cause performance issues.
Regards,
GPHi Gyanprakash,
I'm going to use event handlers in my project, so I'm interested very much in hearing about the performance issues.
Besides, I do not see why I shall package every handler separately. Is this intended behavior or because of some bugs in OIM?
Regards,
Vladimir

How to find in SCCM 2012, Which(sccm admin) deployed Application on machines.

Hi,
Looking log files, to find who(sccm 2012 admin) deployed applications on machines.
Deployment has been deleted from console, However in database it is shwoing number of machines having with particular application.
Some sccm 2012 admin deployed application on machines by mistake, how to check from server or client logs, who(sccm admin) deployed application on machines.
Please let me, if anyone know about this.

Likely would want to run the "Deployments Created, Modified, or Deleted" status message query ":-)
Wally Mead
Wally is right but watch out for these status message, I have not check in CM12 yet but in CM07 just open and click "ok" to close the package/ advert/ etc. would create a status message saying it was modified.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Use Package Parameters in Package Deployment Model

Can you use Package Parameters when you use the Package
Deployment Model? The Parameter tab is visible in SSDT and in SSDT they seem to work, but can you use them outside SSDT? In a SQL Agent Job or on the command prompt?
And if not... why is the tab visible? ;-)

Hi HansAnderss,
Integration Services (SSIS) parameters allow us to assign values to properties within packages at the time of package execution. We can create project parameters at the project level and package parameters at the package level. But the use of parameters
are only supported in Project Deployment Model, we cannot use parameters in Package Deployment Model. This is by design.
Just as you said, we can also see the Parameters tab in Package Deployment Model. And I couldn’t find a way to hide the pane. If you have concern about this issue, I recommend you that submit the requirement at
https://connect.microsoft.com/SQLServer/. If the requirement mentioned by customers for many times, the product team may consider to add this feature in the next SQL Server version. Your feedback
is valuable for us to improve our products and increase the level of service provided.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Best report to check application and package deployment compliancy?

I am looking for the best report to check application and package deployment compliancy.
Preferably targeting a collection.
tconners

I'm recommending this one:
Software Distribution - Application Monitoring folder -
All application deployments (advanced)
It allows you to select Collections and applications
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

Outbound BPEL Process deployment Issue in SOA (binding.jca-12600)

Hi,
I have Designed an Outbound BPEL Process for Siebel CRM Service Integration using Jdeveloper (11.1.1.3.0). After that I am facing the deployment issue of this application in SOA suite (11.1.1.6.0). Following is the deployment.log status in jdeveloper:-
[10:57:54 AM] ---- Deployment started. ----
[10:57:54 AM] Target platform is (Weblogic 10.3).
[10:57:54 AM] Running dependency analysis...
[10:57:54 AM] Building...
[10:57:58 AM] Deploying profile...
[10:57:58 AM] Wrote Archive Module to C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Deploying sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:57:58 AM] Processing sar=/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Adding sar file - C:\JDeveloper\mywork\Siebel_Outbound_BPEL\QueryWithView_Invoke\deploy\sca_QueryWithView_Invoke_rev1.0.jar
[10:57:58 AM] Preparing to send HTTP request for deployment
[10:57:59 AM] Creating HTTP connection to host:10.10.22.81, port:7001
[10:57:59 AM] Sending internal deployment descriptor
[10:57:59 AM] Sending archive - sca_QueryWithView_Invoke_rev1.0.jar
[10:58:00 AM] Received HTTP response from the server, response code=500
[10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:58:00 AM] HTTP error code returned [500]
[10:58:00 AM] Error message from server:
#;There was an error deploying the composite on AdminServer: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
#;Generic error.
#;Cause: Unable to find suitable outbound binding.
#;Please create a Service Request with Oracle Support.
#;: Generic error.
#;Generic error.
#;Cause: Unable to find suitable outbound binding.
#;Please create a Service Request with Oracle Support.
[10:58:00 AM] Check server log for more details.
[10:58:00 AM] Error deploying archive sca_QueryWithView_Invoke_rev1.0.jar to partition "default" on server AdminServer [10.10.22.81:7001]
[10:58:00 AM] #### Deployment incomplete. ####
[10:58:00 AM] Error deploying archive file:/C:/JDeveloper/mywork/Siebel_Outbound_BPEL/QueryWithView_Invoke/deploy/sca_QueryWithView_Invoke_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
And the following is the SOA Server Side log file status:-
####<Jun 3, 2013 10:36:05 AM AST> <Info> <Health> <HOSADDAT02> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-00000000000000f4> <1370244965280> <BEA-310002> <36% of the total memory in the server is free>
####<Jun 3, 2013 10:36:12 AM AST> <Error> <ServletContext-/soa-infra> <HOSADDAT02> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <4be72ac3bdb5ebae:-a61256d:13f08d94c98:-8000-000000000000182b> <1370244972343> <BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
 at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:64)
 at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
 at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
 at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
 at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.fabric.common.FabricDeploymentException: [JCABinding] [QueryWithView_Invoke.QueryWithView/1.0]Unable to complete load due to: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
: Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
{rootCauses=[]}
 at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:458)
 at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
 at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
 at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
 at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
 at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
 at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
 at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy314.load(Unknown Source)
 at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
 at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
 at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
 at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
 at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: BINDING.JCA-12600
Generic error.
Generic error.
Cause: Unable to find suitable outbound binding.
Please create a Service Request with Oracle Support.
 at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterBindingConfig.addAdapterReference(AdapterBindingConfig.java:206)
 at oracle.integration.platform.blocks.adapter.AdapterReference.setupAdapterReference(AdapterReference.java:506)
 at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:425)
 at oracle.integration.platform.blocks.adapter.AdapterReference.load(AdapterReference.java:82)
 at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deployReferences(CompositeDeploymentConnection.java:201)
 at oracle.integration.platform.blocks.deploy.CompositeDeploymentConnection.deploy(CompositeDeploymentConnection.java:93)
 at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.initDeployment(CompositeDeploymentManagerImpl.java:150)
 at oracle.integration.platform.blocks.deploy.CompositeDeploymentManagerImpl.load(CompositeDeploymentManagerImpl.java:63)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
 at oracle.integration.platform.blocks.deploy.DeploymentEventPublisher.invoke(DeploymentEventPublisher.java:77)
 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
 at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
 at $Proxy314.load(Unknown Source)
 at oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordinatorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinatorImpl.java:59)
 at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deployNewComposite(BaseDeployProcessor.java:415)
 at oracle.integration.platform.blocks.deploy.servlet.BaseDeployProcessor.deploySARs(BaseDeployProcessor.java:250)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:167)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeployWork(DeployProcessor.java:112)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.doDeploy(DeployProcessor.java:99)
 at oracle.integration.platform.blocks.deploy.servlet.DeployProcessor.process(DeployProcessor.java:81)
 at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPostInsideLoggingSession(CompositeDeployerServlet.java:219)
 at oracle.integration.platform.blocks.deploy.servlet.CompositeDeployerServlet.doPost(CompositeDeployerServlet.java:130)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Kindly help me in this regard

Solution:
Workaround the issue immediately by removing the "ns1:" qualification on the operation for the binding.jca entry in the composite.xml and redeploying.
For example:
From:
<binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
operation="ns1:BAPI_COMPANYCODE_GETDETAIL"/>
To:
<binding.jca config="BAPI_COMPANYCODE_GETDETAIL_invoke_3P.jca"
operation="BAPI_COMPANYCODE_GETDETAIL"/>
Regards,
Shaheer Badar

SCCM Package Deployment issue

Similar Messages

Maybe you are looking for