Netbeans Deployment issues

Hi,
I have a weird issue deploying in a new oc4j instance. I created the project using Netbeans with the oc4j plugin from http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml.gz
Everything is working just fine, i can deploy my EnterpriseApplication from Netbeans to my server without any issues. The problem is i can't do the deployment from the Application Server Control.
I keep getting the message " Failed in uploading archive. Invalid archive file: Se ha utilizado el prefijo de espacio de nombres 'oc4j' pero no se ha declarado"
wich means i'm using oc4j namespace, but i didn't declare it.
Any light on this? what am i missing? I even tried to use the proprietary deployment descriptor i got when i uploaded my project:
<?xml version="1.0" encoding="utf-8"?>
<orion-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/orion-ejb-jar-10_0.xsd" deployment-version="10.1.3.4.0" deployment-time="1221ce267aa" schema-major-version="10" schema-minor-version="0" >
<enterprise-beans>
<session-deployment name="NewSessionBean" location="NewSessionBean" local-location="EnterpriseApplication1-ejb_NewSessionBeanLocal" persistence-filename="NewSessionBean">
</session-deployment>
<session-deployment name="NewWebService" location="NewWebService" local-location="EnterpriseApplication1-ejb_NewWebServiceLocal" persistence-filename="NewWebService">
</session-deployment>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping name="<default-ejb-caller-role>" impliesAll="true" />
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>
and then i undeployed and tried to deployed it from the Application Server Control using the file above, with no luck.

I suggest making this post on [email protected] . You'll get a better response.
More on NetBeans mailing lists:
http://www.netbeans.org/community/lists/

Similar Messages

EPMA Deployment Issues (Rollback Database)

I have seen some posts where users were able to rollback their EPMA databases. This could be helpful when running into deployment issues. Can anyone outline the steps that are needed to rollback an EPMA database?
Thank you

spring_patel wrote:
i really appreciate you trying to solve my problem..
but i think...my estion is fairly simple and straight forward...and i've provided every detail of my problem(if uv'e read my opening post of this thread)....
and as far as that link goes...i've already checked it b4 u guys mentioned it... as it is provided right there in the tutorial i've provided link of...
and i've tried my options b4 making use of this forum...and i didnt find a solution that's why i'm taking ur help..
nevertheless...i repeat my question...
there's a tutorial at this link...[http://www.netbeans.org/kb/docs/java/gui-db.html]...in it is described how to create a java desktop database applicaiton...
at the end of the tuorial there is a section called: "Building and Deploying the Application"
in that section they have instructed to exit netbeans IDE and try and run the application outside it...which is not happening
the reason they say is that i've to start Java DB from outside of the IDE...that is wat my problem is ..
i dont know how to start Java DB from outside the Netbeans ide...You are not telling us anything.
If I tell you "my automobile doesn't work" how do you know what is wrong. Instead I need to tell you one of the following.
1. The engine didn't start.
2. The wheel fell off.
3. The engine caught fire.
4. When I went to the driveway the car wasn't even there.
When you "run" something then something happens. When I run notepad from a console window if notepad is not in the path then I will get an error about command not found. if it is in the path then the command executes and notepad pops up. Even if I don't see notepad pop up I know that the command seemed to execute from the command window.
The above are examples of describing what you did and what did happen. In detail.
"It doesn't work" provides neither detail about how you ran it nor what did happen when you did attempt to run it.

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

Adobe Acrobat 9 Pro deployment issue

Hello. I am having a deployment issue with Adobe Acrobat 9 using Altiris. I create the rip which is bassically an image of the install. My facility has pruchased 50 seats for this software so I know we are covered for the users that we have to use this software. The issue that I am having after I make the rip, and deploy it to a machine it asks for the CD key again in order to use. Am I having an issue with my installation or is Adobe put some kind of security into their software so that when you try to make a rip of the installation is asks for teh CD Key again after the install? Is this an issue that can be resolved?

SOLUTION:
The issue was somehow related to DPI (START > Settings > Control Pannel > Display > Settings Tab > Advanced button). Eventhough the DPI was set to normal, I switched it to LARGE, restarted the machine, logged in after the reboot, changed it back to normal size, restarted again, logged in once more, checked the Printer Preferences and PRESTO --- a properly displayed window.

Deploy issue from JDeveloper 10.1.3.5 to OAS 10.1.2

I have written an application using ADF on JDeveloper 10.1.3.5 and need to deploy it to our OAS 10.1.2. I have run the adfinstaller on the linux server to upgrade the ADF libraries to the correct versions, updated the web.xml files to have the correct versions, changed to J2SE 1.4.2_19 for the application and have still got deployment issues.
Error
An error occurred while redeploying application "FormsSiebelIntegration". See base exception for details.
Resolution:
See base exception for details.
Base Exception:
java.lang.UnsupportedClassVersionError
com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0). com/sun/faces/application/ApplicationAssociate (Unsupported major.minor version 49.0)
Removing the jsf-impl.jar file allows the application to deploy, but when running on the app server I get the following errors:
OracleJSP: oracle.jsp.parse.JspParseException:
/codename.jspx: Line # 6, <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0" xmlns:h="http://java.sun.com/jsf/html" xmlns:f="http://java.sun.com/jsf/core" xmlns:af="http://xmlns.oracle.com/adf/faces" xmlns:afh="http://xmlns.oracle.com/adf/faces/html">
Help! I'm starting to have total mind block as to what to do next.
Error: Unable to load taghandler class: http://java.sun.com/jsf/html

I had already applied all of this before trying to deploy.
The error seems to be a versioning error in the jsf-impl.jar file as the ApplicationAssociate class is found there. I have changed the JDK and J2EE to 1.4.2 and 1.3 respectively, rebuilt everything, updated all the settings to the right versions for 10.1.2 but it still keeps failing on the deploy.

A very urgent deployment issue about DBAdapter

Hello All,
I have a very urgent deployment issue about DBAdapter.
That DBAdapter is connect to DB2 AS400 Database. I have a developing database (jdbc:as400://server01/TEST) and a production database (jdbc:as400://server01/PROD).
During developing, I used DBAdapter wizard to create it, and import some tables, and set the Adapter to use jabc/DB2DS as connection information for easily deployment later.
Then I deploy to Production. I configured Data-source.xml and oc4j-ra.xml rightly; I set DB connection point to production database. But the DBAdapter still write into developing Database.
I checked the DBAdapter, the imported tables are something like this, TEST.table1, TEST.table2. And there are a lot "TEST" located in DB2Writer_toplink_mapping.xml, DB2Writer.xml, TEST.schema, DB2Writer.table1.ClassDescriptor.xml.
This TEST is refrer to the TEST in connect String jdbc:as400://server01/TEST.
I think this might be the reason cause the problem. As to production database, "TEST" should replaced by "PROD". If I changed it manually, I have to change every time when switch between TEST and PROD. And I also don't know if it is safe to do it? (I tried, and bring some toplink mapping problem)
By the way, for Oracle Database, because we use 2 instances for testing and production with same schema name, and do not have this issue.
Anyone could help and many thanks.
Kerr
Message was edited by:
Kerr

Hi Kerr,
The idea is to set up all connections in the BPEL or ESB services with logical names, e.g. typically of the form eis/DB/MyFinancialSystem or eis/DB/MyLogisticsSystem. This way, you do not have to modify code when deploying it onto different environments that serve different purposes.
When moving your services through their lifecyle, on every environment you deploy these to you will have the same logical connections configured on each instance, e.g. for DEV, QA, SIT, UAT and PROD. Only, in case of QA the actual physical connection is configured to point to the QA instance of the systems that your services interact with whereas in case of UAT it points to the UAT instance of the same system.
Maybe your problem is caused by connecting as user "SomeUser" when running the DB Adapter wizard during development and actually selecting objects from a different schema than you used to connect with, e.g. "Test" in your case.
Hth,
Sjoerd

Re: Deployment Issues

Hi Dale;
We have the similar situation. We wrote an application to be able to send
alert message before we shut down the Forte application. When we upgrade our
applications, we will send alert message to all users before we shut down the
Forte application through ECONSOLE which forces all users to log out, and then
overwrite the files.
Our client files are sitting at one of our network servers instead of
individual user's PC, so the user accesses the files through network. So we
are facing the same issue that we have to shut all users down before we
upgrade our applications. If you install those files on your individual user's
PC, you may try to use "compatible level" to update your application.
Hope this helps.
Lu Wang
Eli Lilly and Company
[email protected]

My problem lies more in the way that we update the Forte software. We are
controlled enough with a new distribution from the application side that
there are not problems there.
My question is: how is everyone updating their client PC's from say Forte
R2 to R3. This was not a problem before because we didn't have very many
clients. Now we have quite a few and we can't just copy the proper files
because of the registry updates that are required.
Does anyone have any suggestions? Can I run the Forte client software off
the Novell server?
Thanks,
Tony
-----Original Message-----
From: Lu Wang X1 <[email protected]>
To: Dale V. Georg <[email protected]>
Cc: Forte Users <[email protected]>; Gardner, Steve
<[email protected]>
Date: Wednesday, November 19, 1997 11:17 AM
Subject: Re: Deployment Issues
You are right. Through econsole, we can only shut down the serverpartitions,
even though we can uninstall the application, as long as the clientpartition
is running, we can't overwrite the files. We were probably lucky that nouser
was running the application when we upgraded it.
Since our applications can capture the system alert message, probably wecan
make changes to our application to be able to shut itself down when it
receives certain type of alert message. Just a thought. Don't know ifthere
is any better way to handle it.
Lu
"Dale V. Georg" <[email protected]> on 11/19/97 03:02:27 AM
Please respond to "Dale V. Georg" <[email protected]>
To: Lu Wang X1/AM/LLY
cc: Forte Users <[email protected]>, "Gardner, Steve"
<[email protected]>
Subject: Re: Deployment Issues
On Tue, 18 Nov 1997 11:04:53 -0500, Lu Wang X1 wrote:
Hi Dale;
We have the similar situation. We wrote an application to be able to send
alert message before we shut down the Forte application. When we upgradeour
applications, we will send alert message to all users before we shut down
the
Forte application through ECONSOLE which forces all users to log out, andthen
overwrite the files.If I remember correctly, econsole will only forcibly close down the
server partitions, not the client partitions.
Our client files are sitting at one of our network servers instead of
individual user's PC, so the user accesses the files through network. So
we
are facing the same issue that we have to shut all users down before we
upgrade our applications. If you install those files on your individualuser's
PC, you may try to use "compatible level" to update your application.We did think about using the compatibility level at one point, but that
introduces extra maintenence whenever a new version of the application
is rolled out. On the other hand, if that's the cost of a smooth and
reliable upgrade, then it may be worth paying.
Dale
================================================
Dale V. Georg
Systems Analyst
Indus Consultancy Services
[email protected]
================================================

Ear deployment issue.

Hi,
i am using jdev Studio Edition Version 11.1.1.4.0
I have created EAR of my application and trying to depoly it on Weblogic server.
I have following entry in weblogic-application.xml
<library-ref>
<library-name>adf.oracle.domain</library-name>
</library-ref>
[03:12:39 PM] ---- Deployment started. ----
[03:12:39 PM] Target platform is (Weblogic 10.3).
[03:13:07 PM] Retrieving existing application information
[03:13:07 PM] Running dependency analysis...
[03:13:07 PM] Building...
[03:13:28 PM] Deploying 3 profiles...
[03:13:29 PM] Moving WEB-INF/adfc-config.xml to META-INF/adfc-config.xml
[03:13:30 PM] Wrote Archive Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventoryManagerUi.jar
[03:13:38 PM] Wrote Web Application Module to /home/kpophale/CDMR/13June/frontend/ConsoleApps/AppsInventoryManagerUi/deploy/AppsInventory.war
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-api.jar*
*[03:13:38 PM] Removing the following prohibited entry from the EAR: lib/trinidad-impl.jar*
[03:13:38 PM] removed bundleresolver.jar from lib because it cannot be part of an EJB deployment
[03:13:54 PM] Wrote Enterprise Application Module to /home/kpophale/CDMR/13June/frontend/deploy/AppsInventoryManager.ear
[03:13:55 PM] Entering Oracle Deployment Plan Editor
[03:15:53 PM] Deploying Application...
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'bam_server1'. Deployment is deferred until 'bam_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'bam_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'osb_server1'. Deployment is deferred until 'osb_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'osb_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'soa_server1'. Deployment is deferred until 'soa_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'soa_server1'.
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: [Deployer:149145]Unable to contact 'adf_server1'. Deployment is deferred until 'adf_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'adf_server1'.
[03:16:41 PM] [Deployer:149193]Operation 'deploy' on application 'AppsInventoryManager' has failed on 'AdminServer'
[03:16:41 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application AppsInventoryManager on AdminServer.: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'.
[03:16:41 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
*[03:16:41 PM] Caused by: java.lang.NoClassDefFoundError: org/apache/myfaces/trinidad/webapp/UIXComponentELTag*
[03:16:41 PM] See server logs or server console for more details.
[03:16:41 PM] weblogic.application.ModuleException: Failed to load webapp: 'trellis-AppsInventoryManagerUi-context-root'
[03:16:41 PM] #### Deployment incomplete. ####
[03:16:41 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
I am getting above exception while i am trying to depoly the my ear. please see bold lines.
Please give me some guide line .
Regards,
Kiran.

Hi John,
Yes I have. I even tried on two seperate WebLogic installations. I noticed, even when I create just an ear file (not deploy to server), it gives me the same warnings about removing trinidad. Is there something i'm missing in JDeveloper?
For my installations:
On one Middleware home: I installed: WLS 10.3.5, ADF 11.1.1.5, then ADF 11.1.2 Patch 12611176. configured domain with all ADF/JRF libraries, followed by upgradeADF WLST command. I got same deployment issue.
On another middleware home: I even just installed JDeveloper 11.1.2, configured a new domain with all librearies. I got same deployment issue.
FYI: I also added the two Trinidad JSP Tag Libraries to my View Controller Project. I got same error.
Thank you,
Gavin
Edited by: GavinWoods on Feb 14, 2012 6:25 AM

Deployment issue: compatiblity issue with ODP, instant vs full client on PC

After a lot of deployment issues with full client, we thought we had the solution with Instant Client.
It worked great for a while, but now some of our users have full Oracle 11 client installed after installing our Instant Client because of other software that requires full client.
As soon as they install full client, our Instant Client breaks:
Exception has been thrown by the target of an invocation. (mscorlib)
The type initializer for 'Oracle.DataAccess.Client.OracleClientFactory' threw an exception.
The provider is not compatible with the version of Oracle client (Oracle Data Provider for .NET)
Our instant client is compiled with 2.111.6.20, the client is installing a different version (though I tried installing exactly same version does not seem to work either)
I've been experimenting to redirect the version to another assembly but no success.
How can I make Instant Client and Full client co-exist? The whole idea of using Instant was to be independent of other software who needs ODP.NET...
What do you do when 2 apps need different versions of ORacle ODP.NET (e.g. 2.111.6.0 vs. 2.112.1.0)?
Note that I don't have source code access to "our" app, so if it is at all possible through configuration, that is a prefered solution.
I also don't control our customers deployment strategy, they roll out apps over 1000's of PC's

According to documentation at [http://docs.oracle.com/cd/E20434_01/doc/win.112/e23174/featConfig.htm]
>
Configuration File Support
For customers who have numerous applications on a computer that depends on a single version of ODP.NET, the Windows Registry settings for a given version of ODP.NET may not necessarily be applicable for all applications that use that version of ODP.NET. To provide more granular control, ODP.NET Configuration File Support allows developers to specify ODP.NET configuration settings in an application config, web.config, or a machine.config file.
If a computer does not require granular control beyond configuration settings at the ODP.NET version level, there is no need to specify ODP.NET configuration settings through configuration files.
The following is an example of a web.config file for .NET Framework 2.0 and higher:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<oracle.dataaccess.client>
<settings>
<add name="DllPath" value="C:\oracle\bin"/>
<add name="FetchSize" value="131072"/>
<add name="PromotableTransaction" value="promotable"/>
<add name="StatementCacheSize" value="10"/>
<add name="TraceFileName" value="C:\odpnet2.trc"/>
<add name="TraceLevel" value="63"/>
<add name="TraceOption" value="1"/>
</settings>
</oracle.dataaccess.client>
</configuration>

EJB deployment issue in websphere

EJB deployment issue in websphere
I have created an EJB project in eclipse and created a stateless session bean successfully.
I created Enterprise application project and added the EJB project.
I tried to check it using Universal test client.
When I click the JNDI explorer>>sample.HelloWorldEJBHome
I get error IWAD0401E Unknown type of JNDI object
But when I install an EJB jar using administrator console after exporting the jar file for the EJB project
It is working file
I like to reduce the number of steps by right clicking the server publish and test.
Do any one have come across the same issue please help me
Thanks in advance.

Hi,
i have not done any changes to any process. I have created new DC and created new process.
new DC is not getting deployed with error "Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration". If you will check error log above then you will find it their.

Weblogic deploy issue

Hello,
I try to deploy a web application compiled with NetBeans to WebLogic Server Version: 10.3.0.0 (AIX) and I receive an error.
The application can be deployed without any problems to WebLogic Server Version: 10.3.1.0.
The application is the most simple thing possible, consisting in just a JSP page.
Do you have any idea where is the problem?
I've added some details bellow.
Thank you,
Adrian
Messages
     Unable to access the selected application.
     Exception in AppMerge flows' progression
     Exception in AppMerge flows' progression
     Unmarshaller failed
My WAR file looks like that:
└───APP
    ├───META-INF
        └───MANIFEST.MF
    ├───WEB-INF
        ├───classes
        ├───web.xml
        └───weblogic.xml
    └───index.jsp
MANIFEST.MF
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.9.0
Created-By: 1.7.0_21-b11 (Oracle Corporation)
web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    <session-config>
        <session-timeout>
            30
        </session-timeout>
    </session-config>
    <welcome-file-list>
        <welcome-file>index.jsp</welcome-file>
    </welcome-file-list>
</web-app>
weblogic.xml
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd">
<jsp-descriptor>
    <keepgenerated>true</keepgenerated>
    <debug>true</debug>
</jsp-descriptor>
<context-root>/ESPASExtractorWS_FN</context-root>
</weblogic-web-app>
index.jsp
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE html>
<html>
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
        <title>JSP Page</title>
    </head>
    <body>
        <h1>Hello World!</h1>
    </body>
</html>

This appears to occur when Weblogic attempts to parse the env-entry entries when web.xml is defined with an older namespace declaration. In this case, the servlet 2.4 schema was used.
Solution:
Updating the web.xml namespace declaration resolved the issue.
See document http://docs.oracle.com/cd/E21764_01/web.1111/e13712/web_xml.htm#i1039990http://docs.oracle.com/cd/E21764_01/web.1111/e13712/web_xml.htm#i1039990
Reference:
Deployment errors with "Exception in AppMerge flows' progression" with env-entry (Doc ID 1507765.1)

Deployment Issue With NetBeans4.1Beta

Ok Here is the issue...
I'm running SAS8 & NB4.1B on a windows server 2003 machine, j2se version is J2sdk1.4.2_07
I have been trying to build and deploy a simple hello world application with a single JSP file. I can do this no problems with the bundled Tomcat However SAS8PE throws the following error:
Here is step by step what I do...
File > NewProject > Web > Web Application
give it a unique project name, leave source structure as java BluePrints, leave server as SAS8PE, leave J2EE version as 1.4, leave context path as "/$projectname", leave set as main project checked...
click finish...
Build the project by Build>Build Main Project
This completes successfully (Just built an empty project with no coding...should return the empty standard jsp file when run)
And then I run the project by Run > Run Main Project and I get the deployment error on deployment processor monitor message box with the following info:
Deployment error: null. See the messages.log file for details.
Here is the contents of my output window after the error:
init:
deps-module-jar:
deps-ear-jar:
deps-jar:
library-inclusion-in-archive:
library-inclusion-in-manifest:
compile:
compile-jsps:
do-dist:
dist:
run-deploy:
Deployment error: null. See the messages.log file for details.
C:\java\nbprojectfolder\nb41Beta\deneme\nbproject\build-impl.xml:355: Deployment error: null. See the messages.log file for details.
BUILD FAILED (total time: 2 seconds
When I click the hyperlink to the build-impl.xml file I get the red line at precisely the following message:
<target name="run-deploy" depends="init,compile,compile-jsps,-do-compile-single-jsp,dist">
<nbdeploy forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" debugmode="false"/>
</target>
By the way this is at the execution section of the build-impl.xml file
I have tried re-installing everything and I still get the same error... Shouldn't this be a straightforward with no hassles task? Anyone else had the same problem as I did? What do you suggest I do at this point?
Thanks...

Another issue is when I try to deploy the simple war file under /dist thru the admin console (web applications > deploy) I get the following error...
A "com.sun.enterprise.tools.guiframework.exception.FrameworkException" was caught. The message from the exception: "java.lang.reflect.InvocationTargetException while attempting to process a 'error' event for 'deployWebModule'."
The root cause is "javax.management.AttributeNotFoundException: id"
See the HTML source for more detailed (stack trace) information.
The stack trace is as follows

Adobe Creative Cloud Enterprise Deployment Issues using SCCM 2012 R2

Hi,
I have been trying to deploy Adobe Creative Cloud Enterprise to Windows 8.1 machines that are identical, using SCCM 2012 R2.
The Adobe package seems fine, because it seems to deploy successfully to some machines. And SCCM 2012 R2 has been configured correctly, as I can deploy other software using it, and again, it deploys Adobe CC successfully to some of the machines.
I have tried comparing the package that is downloaded on the test machine/client machine, with the original package on the distribution point, using Beyond Compare, and there are no differences.
I have contacted Adobe Enterprise Support, and they asked me to send to them log files from Event Viewer, the msi installer, and other Adobe logs, from the machine that failed the deployment. However, after Adobe studying them, they told me that they could not identify any problems... Strange, because I could have sworn that I saw error 1603 pop up over 20 times on different machines indicating that the 'Set-up.dat' file had a problem with it.
After all the testing on over 20 identical machines (same hardware/same software), using different configurations on SCCM 2012 R2 and the client machines, I still can't seem to have a reliable solution to deploying Adobe CC.
The fact that it deploys successfully on one machine and fails on another, or sometimes deploy to two machines and fail on another (simultaneously), is something that I don't understand.
Another thing is that, if I retry the deployment 10-15 times after it failed the first time, it might go through...
Adobe Enterprise Support asked me if they could remote into a machine that failed the deployment to have a look at it and I agreed to that option, but it seems like my issue has been ignored because they never got back to me.
Has anyone had this kind of problem or anything similar before?
I need to be able to deploy this remotely to 100+ machines. So installing manually is not an option.
Any help is appreciated.
This was posted in the wrong section a few days ago. I'm hoping I can get some help here.
Case Number: 1862659812
UPDATE: I spoke to Adobe Customer Support and after 1.5 hours on the phone with a remote session going on, problem was still not solved or identified. Additional log files have been sent and now I'm waiting for a call back.

Hi Robert,
We seem to be having a very similar issue. Our installs would randomly fail with error code 1603 and an error message about a fault in Set-up.dat. Failure rate was near 95% on our 900 machines. Adobe Support and Karl having been looking into our issues but so far no solution has been found.
Having done a lot of investigating we've managed to deploy our package using a schedule task running as a domain admin. This is a nasty solution and we don't intend on using this permanently, but we needed to get the package out.
Are you seeing any of the following:
Entries in PDApp.log:
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The Bootstrapper Process is (5).Stopping the installation process.
[FATAL] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | The return code from the Adobe Installer Process is (33).Stopping the uninstallation process.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to find the pdb database.
[WARN] | | ASU | DeploymentManager | DeploymentManager | | | 2900 | Failed to get the local payload database handle.
Event Log:
Faulting application name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Faulting module name: Set-up.dat, version: 2.9.1.474, time stamp: 0x54e11f94
Exception code: 0xc0000005
Fault offset: 0x000d7c52
Faulting process id: 0xb40
Faulting application start time: 0x01d072a073861622
Faulting application path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Faulting module path: \\server.name.path\Adobe CC\FullPackage\Build\ASU\Set-up.dat
Report Id: c86d9216-de93-11e4-8284-782bcb99e284
Faulting package full name:
Faulting package-relative application ID:
Installer Log
Indicates it can't find the Media_db. We noticed that the folder C:\Program Files (x86)\Common Files\Adobe\caps doesn't get created on the machines were the install fails, so error message is correct in that there isn't a Media_db.db. Sysinterals Process Monitor seems to show that the setup tried to create the folder/files but they don't actually get created. Copying a Media_db into the folder from another machine seems to allow the installation to almost finish, but unsurprisingly you end up with problems later on.

Deployment Issues with Custom TS variables set for client

Good Day folks!
I have come across an interesting issue that I have not been able to find a quick fix as such I am looking for some ideas where to trouble shoot my issue moving forwards.
So the Issue:
I have a TS that deploys a Windows 8.1 SOE image, this is done first by using a PXE boot PE image for an “unknown” systems to load a Custom HTA. This HTA allows me manually add the system to SCCM and add it to a required deployments collection that has the
8.1 SOE deployed to it.
The HTA also sets a few custom variables for the system resource things like system location, Machine Domain etc.
Once the HTA has run the system then has a delay to allow for the resource to show up tin the 8.1 deployment collection and then closes.
Now all this appears to work fine, the system is added to the collection, reboots and the deployment runs from start to finish without error.
I can also check the system resource and the variables are present.
The problem I have found is that the custom variables for this resource are not being used by the TS after reboot.. upon further investigation I found that these variables are not even being retrieved ( ran a VB script to save all the variables from the
TS to a txt file to check this ) Because of this the TS is bypassing some needed TS Tasks.
A few interesting things to note:
System appears to be added again when AD discovery is run…. So it causes a Duplicate.
Client Dose connect to SCCM server after deployment but is not receiving deployments ( is getting some policy )
Worked with SCCM 2012 but not 2012 R2
So it appears that when the system reboots from the HTA PE step it has identified itself as an unknown system again…. Even though it has been manually added…
I am interested to know if first of all if others would agree with this and second how SCCM while running a TS matches itself up to a system to retrieve the custom set variables before client install etc... Or a good place to start looking
to dig up more information! Or anything else!
Thanks
Stuart.

Have you taken a look at this hotfix?
http://support.microsoft.com/kb/2907591
We had to apply it in order for our variables to be seen.
joeblow

SCCM Policies and SCEP Deployment Issues

I'm having several issues with SCCM 2012 R2.
I have inherited an existing SCCM 2012 R2 installation. The company does not want me to rebuild it from the ground using best practices, so I'm doing what I can with it.
Issue #1: SCEP does not auto deploy to new systems;
Issue #2: Client policies do not update;
Issue #3: Anti-malware policies do not update.
Starting out, I guess I need to look at issue #2 before I look at the others.
The client is auto-deploying as far as I can tell. I do not have any GPO’s that push the software to the clients, so it appears that the system wide deployment of the client is working correctly.
As for the policies not being updated, I have created a new policy that is assigned to newly defined device collections.
I have check the membership of the collections and it is populating/selecting the assets correctly.
I have picked a handful of computers out of the collection to use for information gathering.
Looking at the log files, it shows that it is applying policies, but it does not identify which policy from the SCCM server.
With the new policies that I’ve created, I’ve enabled ‘Endpoint Proection’, ‘Hardware Inventory’, ‘Power Management’, ‘Remote Tools’, ‘Software Deployment’, ‘Software Metering’, and ‘User and Device Affinity’.
After 13 days, the options within the policy have not taken effect as I have check the clients and the settings from the ‘Remote Tools’ and ‘Power Management’ haven’t been applied. I waited this long since several of the settings were set at 7 days before
re-evaluation.
I’m not sure where to go next on this issue.
On the issue #1 & 3, the computers that did get the initial config push and SCEP install, before I came on, are operating and reporting back to the SCCM manager that they are in a managed state, which is fine, but they are not applying any newly defined
policies. Checking the logs on the clients show that they are applying the Default Client Settings and not any of the other policies that are set to deploy to All systems or any other collection I’ve defined.
Also checking the anti-malware policy logs on the clients, they are also still applying the Default Client Antimalware Policy, not any of the custom policies, just like the SCCM client issue. In the EndpointProtectionAgent.log, i have several lines
showing "Deployment WMI is NOT ready." The same is in several of the other log files, so I've check that all the WMI services are running and I have tested management with the PoshCat utility and all of the commands are working in there and
the output reports all seem to be reporting correctly.
Any pointers or starting points would be greatly appreciated.

For the 'Client Settings', I have 4 listed. Default Client Settings, EP Settings (existing that I have set to deploy to a group that only has 1 computer left in it), Server Policy, and Workstation Policy (applies to all clients that have 'workstation'
in the version name).
For SCEP, just 2. Default Client and Custom SCEP.
The inventory and software distribution... let's look at the inventory function. I have nothing showing in '\Assets and compliance\Overview\Asset Intelligence\Inventoried Software'.
As for software distribution, I am not sure how to check that -- I haven't set up any deployed software packages yet... but the SCEP and Windows Updates are the only things showing up. SCEP is not deploying to any new workstations, but it appears all
the Windows Updates are deploying correctly to all the workstations.
I just checked the SrcUpdateMgr.log on a client and I've found several lines of 'Instance of CCM_SourceUpdateClientConfig doesn't exist in WMI'
Checking the SoftwareCatalogUpdateEndpoint.log file, I have several lines that just repeat...
Software catalog update endpoint is starting
Logo event received
Logon user SID: [...]
Retrieving URL for software Catalog
Software Catalog update endpoint is loading
Received notification for client agent setting or portal information change
Retrieving URL for Softwware Catalog
Making call to determin whether catalog Url should be added to the trusted sites zone
Updating the registry for Software Catalog for user '[...]'
Notification system applicaton: C:\Windows\CCM\UpdateTrustedSites.exe
Started UpdateTrustedSites process
Making call to determine whether keys to enable Silverlight elevated trust should be added
Enable elevated trust is set to false. Setting the keys to 0
CSoftwareCatalogUpdateHandler::UpdateSilverlightRegistry: Successfully set elevated trust on this client for Silverlight
CSoftwareCatalogUpdateHandler::UpdateSilverlightRegistry: Successfully set elevated trust on this client for Silverlight
CSoftwareCatalogUpdateHandler::UpdateSilverlightRegistry: Successfully set elevated trust on this client for Silverlight
Received notification for client agent setting or portal information change
and it does show the Silverlight lines 3 times each time in the repeats. The repeat time stamp looks like it happens alternating 20 minutes, then 2 hours, then 20 minutes, then 2 hours, etc.
KW

Netbeans Deployment issues

Similar Messages

Maybe you are looking for