Error in TFS Release Management Server after Upgrading to Update 3

Some weird and unexplained error logged in InRelease aka (Release Management) server event log after upgrading Release Management Update 1 to update 3.
Below error started getting logged only after upgrading to Update 3.
Even though we started the Inrelease Server and all agents but no luck.
Any immediate help would be much helpful.
----------------------------------- EVENT LOG ERROR ------------------------------------
Timestamp: 12/15/2014 10:22:18 AM
Message: 'LambdaValue>' is not of type 'ServerActivity'. When loading this instance you must ensure that the activity with name 'LambdaValue>' implements
'ServerActivity'.: \r\n\r\n at
System.Activities.ActivityInstance.System.Activities.Runtime.ActivityInstanceMap.IActivityReference.Load(Activity activity, ActivityInstanceMap instanceMap) at System.Activities.Runtime.ActivityInstanceMap.InstanceList.Load(Activity activity, ActivityInstanceMap
instanceMap) at System.Activities.Runtime.ActivityInstanceMap.LoadActivityTree(Activity rootActivity, ActivityInstance rootInstance, List1
secondaryRootInstances, ActivityExecutor executor) at System.Activities.Runtime.ActivityExecutor.OnDeserialized(Activity workflow, WorkflowInstance workflowInstance) at System.Activities.Hosting.WorkflowInstance.InitializeCore(IDictionary2 workflowArgumentValues,
IList1
workflowExecutionProperties) at System.Activities.Hosting.WorkflowInstance.Initialize(Object deserializedRuntimeState, DynamicUpdateMap updateMap) at System.Activities.WorkflowApplication.LoadCore(DynamicUpdateMap updateMap, TimeoutHelper timeoutHelper, Boolean
loadAny, IDictionary2 values) at System.Activities.WorkflowApplication.Load(Guid instanceId, TimeSpan timeout) at System.Activities.WorkflowApplication.Load(Guid instanceId) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCacheSingleton.<.cctor>b__1(WorkflowApplication
app, Guid id) at
Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCache.CreateApplicationInCache(CreateParameters createParameters, Guid id) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.WorkflowInstanceCache.GetInstance(CreateParameters
createParameters, Guid id) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.WorkflowInstance.CachedWorkflowInstanceLoader.GetInstance(DeploymentLog log, CreateParameters createParams) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.DeploymentControllerServiceProcessor.ContinueDeploymentWithFinalComponentState(DeploymentLog
log) at Microsoft.TeamFoundation.Release.ServiceProcessor.Processor.DeploymentControllerServiceProcessor.ContinueDeployment(String log)
Category: General
Priority: -1
EventId: 0
Severity: Error
Title:
Machine: **********
Application Domain: /LM/W3SVC/1/ROOT-1-130630102320068767
Process Id: 6628
Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Win32 Thread Id: 1344
Thread Name:
Extended Properties:

Dear Charles-Li,
Thank you so much for your reply.
we started using  Release Management Update 1  and it was worked perfectly fine.  then we move to upgrade existing Release Management(server,
Database and agent) with Update 3, which we did, and its working fine  except lots of error as mentioned in above thread, are getting logged in server event log at regular interval till now(3-4 errors every second).
even though lots of error are getting logged but we are not facing any issue while using Release Management with update 3.
But i am bit curious to know out reason for getting those error.
<<clean
the cache folder and restrat Release Management and try again>>
already tried but no luck.
Thanks!!

Similar Messages

  • Deployer Installation: Failed to validate Release Management Server for Team Foundation Server 2013

    Attempting to install the deployer on a machine and getting the below error.  Not sure what that means, out of turn error or what actually occurs at this step, validating release management server,  during the configuration piece.  The user,
    that we set for the service was validated fine.  The user is an service account in the TFS RM Server, is  an admin on the local box as well.
    I am able to get into the TFS RM Server through the client just fine. I can hit the TFS RM UI just fine as well.
    Curious what would not allow the deployer to complete as mentioned below.
    Any help is appreciated.
    I, 2013/12/16, 14:46:26.521, Validated account to use as identity for Release Management Services.
    I, 2013/12/16, 14:46:26.521, Validating Release Management Server for Team Foundation Server 2013...
    E, 2013/12/16, 14:46:30.905, Received Exception : Microsoft.TeamFoundation.Release.CommonConfiguration.ConfigurationException: Failed to validate Release Management Server for Team Foundation Server 2013.
       at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateServerUrl()
       at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateAndConfigure(DeployerConfigUpdatePack updatePack, DelegateStatusUpdate statusListener)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
    I, 2013/12/16, 14:46:30.905, Work completed for GetConfiguration() call : got out of turn error
    E, 2013/12/16, 14:46:30.905, Failed to validate Release Management Server for Team Foundation Server 2013.

    Hi Kpdn, 
    Thanks for your post.
    All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
    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.
    Click
    HERE to participate the survey.

  • Release Management Server/Client clarification

    Hi there,
    I am using TFS 2010 and i would like some assistance in regards to what i would like to do please.
    At my place of work we have a Build server, call it Server A which has a controller and 2 build agents. It builds my projects and outputs them in a drop folder on that server.
    Firstly, can i use my existing custom build template to allow others to trigger a build via the Release Management Client tool?
    The existing custom template i am using builds all the projects in the solution and then generates several *.MSI files at the end. I use this template in all of my Build Definitions.
    Secondly, Do i have to install the Release Management Client tool and Deployment Agent on the Build server as well?Correct me if i am wrong because i read that if you want to do automated deployment i have to do this.
    Thirdly, am i allowed to use custom scripts, executable side by side with the Deployment Agent. The reason i ask that is at some point i would like to extend the process so that once the build has finished, i can install it on Server B. Is this possible?
    Lastly, do i have to install Visual Studio 2013 on the build server for Release Management Server to work correctly?
    If you have any questions on the above please let me know.
    Thanks,

    Hi IndusKing,  
    Thanks for your reply.
    If your build definition using the ReleaseDefaultTemplate.xaml template, and you want only to build the solution(needn’t to trigger release template), you can set the
    Release Build = False in build definition>>Process>>Release.
    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.
    Click
    HERE to participate the survey.
    So if i understand correctly i can either use the ReleaseDefaultTemplate.xaml in all my build definitions or i can modify my existing template to use the Release Template functionality e.g Release Build = False.
    As far as I know RM Client not support trigger TFS build definition. You can install the VS on your RM Client machine, then trigger build definition in Team Explorer, or trigger the build definition by execute TfsBuild
    Start command line.
    Are you saying that RM client can only deploy finished finished builds?

  • Error while starting weblogic Managed Server

    Hi ,
    I am new to SOA 11g. I installled the latest version(11.1.1.4) of all the components.I started web logic and able to login into Admin Console but I have a problem
    while starting Managed Server.It gives me an error saying
    <Feb 2, 2011 2:01:29 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 17.0-b17
    from Sun Microsystems Inc.>
    <Feb 2, 2011 2:01:30 PM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: Unable to obtain lock on C:\Oracle\Middleware\user_projects\domains\fmw_domain\servers\AdminServer\tmp\AdminServer.lok.
    Server may already be running
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:159)
    at weblogic.management.internal.ServerLocks.getServerLock(ServerLocks.java:58)
    at weblogic.management.internal.DomainDirectoryService.start(DomainDirectoryService.java:74)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:879)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:566)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:467)
    at weblogic.Server.main(Server.java:71)>
    <Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Feb 2, 2011 2:01:30 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Feb 2, 2011 2:01:30 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Can anyone help ?
    Regards,
    Vikas Manchanda
    Edited by: 829347 on Feb 2, 2011 12:48 AM

    How are you starting the managed server? Is it a new install? The error suggests that the managed server is already running. You could check the windows task manager to see if there is a Java process running (or two if managed and admin server is on the same machine)
    Damien

  • Nodemanager does not restart managed server after Linux OS reboot

    Running Linux 2.6.18, Sun JDK 1.6.0_14, and WebLogic 10.3, we have a correctly functioning nodemanager watching a single managed server. If I kill -9 the managed server, the nodemanager fires up a new one immediately. If, however, we reboot the box, the nodemanager will start cleanly and will not start the managed server. It appears to believe the node should remain down and reports its status as UNKNOWN.
    I've seen where this is a known problem on Windows boxes, easily gotten around by supplying the -Xrs parameter to the startup parms for the managed server. (Section 5 of the general nodemanager config doc.) I don't see, however, where there's an equally clean solution for Linux.
    Things I've tried:
    + When I set the server to DEBUG, it shows zero sign of receiving a shutdown signal. It's dumping loads of cluster messages, etc, into the log and then suddenly the log just ends so it's dying via kill -9. If the nodemanager is still running at that time, it might try to restart the managed server and log it somewhere as permanently failed.
    + The nodemanager only logs to INFO level, and logs no evidence of deciding to leave the node down. (DEBUG is an invalid LogLevel, so that's all I've got.)
    + A restart signal sent from our AdminServer (on another Linux box) successfully starts the managed node through the nodemanager. Nothing unusual occurs or is logged.
    Things I'm curious about:
    + Is there some way to see in what state the nodemanager believes the managed server to be?
    + Is there some value in some doc somewhere that might say the server should not be restarted?
    + Is there not a log of NodeManager client actions? I don't see anything in domain.log or AdminServer.log except when the NM is down.
    Thanks,
    Kevin
    ListenPort=5556
    ListenBacklog=50
    SecureListener=true
    AuthenticationEnabled=true
    NativeVersionEnabled=false
    CrashRecoveryEnabled=true
    JavaHome=/appl/java/jre
    StartScriptEnabled=false
    StopScriptEnabled=false
    StartScriptName=startWebLogic.sh
    StopScriptName=
    LogFile=/appl/bea/wlserver_10.3/common/nodemanager/logs/nodemanager.log
    LogLevel=INFO
    LogLimit=0
    LogCount=1

    can you set NativeVersionEnabled to true. We have faced this in windows which was fixed by changing this property. Some notes from that issue:
    Faced this interesting issue in Windows 2008 environment. Managed Servers were started by node manager and it was expected that on a system restart after a crash, the node manager will restore the state of the managed servers to the state it was before the crash. Node Manger was configured to run as a windows service. Hence it started after the server restart. But the individual managed servers were not getting started. Interestingly, for the managed servers started by the node manager there were no <Managed_Server_Name>.lck file in the <Server>/data/NodeManger folder.
    To fix this always set the following properties in the nodemanager.properties on the node maager home directory.
    CrashRecoveryEnabled=true /* This by default is set to false. This needs to be turned for auto restart after crash to work */
    NativeVersionEnabled=true /* This is by default set to true and it should be set as such. If you turn this off on platforms for which weblogic provide native JNI libraries ( e.g. as in Windows 2008) then this wont create the .lck file and hence node manager wont restart the managed server after the crash.
    Note: As per official documentation .lck files are required for weblogic node managers to do auto restart after system crash
    From Official documentation:
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.
    If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    After the system is restarted, Node Manager checks each managed domain specified in the nodemanager.domains file to determine if there are any server instances that were not cleanly shutdown. This is determined by the presence of any lock files which are created by Node Manager when a WebLogic Server process is created. This lock file contains the process identifier for WebLogic Server startup script. If the lock file exists, but the process ID is not running, Node Manager will attempt to automatically restart the server.If the process is running, Node Manager performs an additional check to access the management servlet running in the process to verify that the process corresponding to the process ID is a WebLogic Server instance.
    */

  • Error while running the Managed server

    Hi
    i am getting the below error while running the Managed server.
    java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050633> <BEA-149059> <Module dms.war of application DMS Application [Version=11.1.1.1.0] is transitioning from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
    ####<Dec 6, 2011 7:47:30 PM IST> <Info> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050711> <BEA-149060> <Module dms.war of application DMS Application [Version=11.1.1.1.0] successfully transitioned from STATE_ADMIN to STATE_PREPARED on server managed_server1.>
    ####<Dec 6, 2011 7:47:30 PM IST> <Error> <Deployer> <01hw198371> <managed_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JGJiy3T5EgGqywAhMG1ErYE5000002> <1323181050726> <BEA-149231> <Unable to set the activation state to true for the application 'DMS Application [Version=11.1.1.1.0]'.
    weblogic.application.ModuleException: [HTTP:101216]Servlet: "Spy" failed to preload on startup in Web application: "dms.war".
    java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: java.lang.IllegalArgumentException: config=oracle.dms.config.DumpConfig@186793e logDir=null agency=oracle.dms.reporter.SpyAgency@181f91a dmsTimer=java.util.concurrent.ScheduledThreadPoolExecutor@95b5c
         at oracle.dms.impl.producer.Dumper.<init>(Dumper.java:100)
         at oracle.dms.app.ServerInitializer.init(ServerInitializer.java:136)
         at oracle.dms.app.BaseInitializer.getInitializer(BaseInitializer.java:360)
         at oracle.dms.app.DmsSpy.init(DmsSpy.java:210)
         at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
         at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
         at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    can anyone help

    Srinath is 100% correct.
    If the deployment failed, then there will very likely be some mention in the log.
    You state that you checked the log, but you didn't mention whether you found an error, no error, a successful startup, etc. you are providing painfully few details to assist.
    I would bet if you posted your .log and .out logs to Pastebin.com - #1 paste tool since 2002 and provided us links, We would be able to point out the error.
    Lacking that information, my best advice would be to re-install and double-check you're completing all steps in the correct order.
    Also, be sure to always search the product documentation first, the search this forum. For basic issues (e.g., standard installation), there is a high probability that someone else has asked that question.
    I hope that helps,
    -ryan

  • Error while starting the managed server using nodemanager

    HI ,
    I am getting the below error while starting the managed server from the Admin console. All the serverstart and the node manager proeprties looks fine.
    Below is the error in the managed server log,
    startWebLogic.sh: grep: not found
    startWebLogic.sh: uname: not found
    startWebLogic.sh: test: argument expected
    can you help me to solve the problem please. i am using weblogic 10.3.3
    thanks
    Arun

    I think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?

  • SAP B1 APPLICATION IS RUNNING SLOW IN SERVER AFTER UPGRADE

    Hi,
    The sap application is running slow in server after upgrading it from 9.0 to 9.1 it's taking 5-10 secs to open a document after clicking it and its taking more time in client system.
    what are the steps to be taken so that the application will run without any delay.
    Regards,
    Karthik B

    hi please check bellow thread ,it may help you
    Client Machines Logon to SAP Server is Very Slow
    update the status
    regards
    AKR

  • WLST - error when i start managed server using nmstart() command.

    i am receiving an error when start the managed server using nmstart(). Please advise.
    Do I have add any parameter to nodemanager.properties file?
    Thankyou
    pasted below is the error message i am receiving when i start managed server.
    Starting server hssclient ...This Exception occured at Thu Mar 19 10:30:02 EDT 2
    009.
    java.lang.IllegalArgumentException: Invalid host name: Null or empty
    at weblogic.nodemanager.client.NMClient.checkNullOrEmpty(NMClient.java:7
    2)
    at weblogic.nodemanager.client.NMClient.setHost(NMClient.java:79)
    at weblogic.nodemanager.mbean.NodeManagerRuntime.getNMClient(NodeManager
    Runtime.java:527)
    at weblogic.nodemanager.mbean.NodeManagerRuntime.getNMClient(NodeManager
    Runtime.java:565)
    at weblogic.nodemanager.mbean.NodeManagerRuntime.start(NodeManagerRuntim
    e.java:188)
    at weblogic.server.ServerLifeCycleRuntime.startServer(ServerLifeCycleRun
    time.java:439)
    at weblogic.server.ServerLifeCycleRuntime.start(ServerLifeCycleRuntime.j
    ava:124)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean
    .java:428)
    at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImp
    l.java:213)
    at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultM
    BeanServerInterceptor.java:815)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784
    at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBea
    nServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:248)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.
    run(WLSMBeanServerInterceptorBase.java:443)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
    oke(WLSMBeanServerInterceptorBase.java:441)
    at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterce
    ptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:63)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.
    run(WLSMBeanServerInterceptorBase.java:443)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.inv
    oke(WLSMBeanServerInterceptorBase.java:441)
    at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(
    SecurityInterceptor.java:426)
    at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
    ptor$10$1.run(AuthenticatedSubjectInterceptor.java:582)
    at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
    ptor$10.run(AuthenticatedSubjectInterceptor.java:580)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterce
    ptor.invoke(AuthenticatedSubjectInterceptor.java:573)
    at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanSer
    ver.java:310)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnecti
    onImpl.java:1410)
    at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectio
    nImpl.java:81)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run
    (RMIConnectionImpl.java:1247)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(R
    MIConnectionImpl.java:1350)
    at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImp
    l.java:784)
    at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown S
    ource)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
    147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
    a:439)
    at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:6
    1)
    at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicSer
    verRef.java:983)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    Hi I am getting below exception, is nmStart only start AdminServer ????
    There are 1 nested errors:
    weblogic.management.ManagementException: Booting as admin server, but servername, MS1, does not match the admin server name, AdminServer
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:803)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:493)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
    at weblogic.Server.main(Server.java:67)
    >
    <Feb 10, 2010 1:45:17 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Feb 10, 2010 1:45:17 PM UTC> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Feb 10, 2010 1:45:17 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <Feb 10, 2010 1:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 8275>
    <Feb 10, 2010 1:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Feb 10, 2010 1:45:17 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    ~

  • An unknown error occurred (-42110) when opening itunes after upgrading

    when opening itunes i get "an unknown error occurred (-42110) when opening itunes after upgrading to latest version.

    Try the following user tip:
    iTunes for Windows 11.0.2.25 and 11.0.2.26: "Unknown error -42110" messages when launching iTunes

  • Mavericks Mail not working properly with Exchange server after upgrade from Lion

    Mail will no longer maintain a stable connection to my company's Exchange server after upgrading to Mavericks from Lion.  Nothing has been changed on the Exchange server.  It has only partially downloaded the messages that are on the server.  It seems to download current messages when they hit the server.  It has difficulty sending messages.  When I send a message, it gets stuck in the Outbox.  It is constantly losing the connection to the server.  The problem is only occuring with Exchange email.  My iCloud email works properly as well as a POP3 account.

    No shortage of pre-existing threads on Mavericks mail issues...
    https://discussions.apple.com/message/23706759#23706759
    https://discussions.apple.com/message/23469853#23469853
    https://discussions.apple.com/message/24277596#24277596
    https://discussions.apple.com/message/23769976#23769976
    https://discussions.apple.com/message/19077388#19077388
    https://discussions.apple.com/message/24170482#24170482
    https://discussions.apple.com/message/24483692#24483692

  • HT4623 iPhone 4s will not register with server after iOS 6 update

    My iPhone 4s will not register with server after iOS 6 update.  Does anyone has similar problem?

    Obviously since you have iOS 7 you're a developer.  As a developer, you signed a NDA with Apple not to discuss the iOS on a public forum.  Please log in to the Developer Forum using your credentials and ask for help there, lest you risk having your credentials terminated.
    Thanks, and best of luck to you.
    GDG

  • Disks Not Displayed in Server Manager 2012 After Upgrade

    I have two identical IBM x3650 M3 servers with the M5014 RAID controller installed. The internal SAS drives are configured with three RAID 5 logical drives, basically a C:, D:, and E:. They also have an external eSATA drive with a Silicon Image eSATA
    card installed that is used for backup. Both servers were upgraded from Server 2008R2 to 2012R2. Both of the server's firmware was updated prior to the upgrade and are using the same versions.
    On the first server, all of the RAID controller's logical drives are displayed under Server Manger > File and Storage Services > Volumes > Disks. All of the volumes on these drives and the eSATA drive are displayed correctly under Server
    Manger > File and Storage Services > Volumes.
    On the second server, all of the volumes correctly displayed under Server Manger > File and Storage Services > Volumes. However, only the first logical drive is displayed under Server Manger > File and Storage Services > Volumes
    > Disks. The other two logical drives are not displayed. The drives show up correctly under Disk Management and Device Manager. All of the data and shares are accessable and the server functions like it did before the upgrade. While it doesn't seem
    critical at the moment, I would like to find out why the logical drives are not being displayed.

    Hi,
    Did you have a failover cluster with a highly available storage solution that uses LSI MegaRAID controllers and use Server Manager to manage the storage using the LSI SMI-S storage provider? If so, the associated physical disks may not appear correctly in Server
    Manager when you create storage pools or virtual disks from the storage pools. 
    To work around this issue, run the following Windows PowerShell cmdlet on all nodes, and then refresh the Server Manager UI: 
    Update-StorageProviderCache –DiscoveryLevel Full
    For more detailed information, please refer to the article below:
    Known Issues: File and Storage Services in Windows Server 2012
    http://social.technet.microsoft.com/wiki/contents/articles/13392.known-issues-file-and-storage-services-in-windows-server-2012.aspx
    Best Regards,
    Mandy 
    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.

  • User Management problem after upgrade of SAP DB/Database Studio

    Hi,
    after upgrading SAP DB to 7.8.02.21 and Database Studio to the same version (this is on Windows 7 64 bit professional) I experience that starting DB Studio as a normal user fails with a message regarding not being able to execute (?) User Management. To start the program I have to run it as administrator. Once I do this it will, afterwards, work fine for a normal user, too, but only for one day (or possibly one logon to Windows 7).
    (The error message does not even contain a hint to that solution)
    In previous versions it was necessary to run DB Studio once (after installation) as an adminstrator. After that it would work all the same for normal users.
    Is there a way to fix this? The desired behaviour being the one from previous versions that after one administrator run it can be started by my normal Windows user? It's, of course, not serious and I do know a workaround, but it's a bit annoying nonetheless.
    (And yes, I do know that Windows 7 is not an officially supported platform. I'm just shyly asking).
    Best regards,
    Thomas

    Hi Thomas,
    due to the changes in the security concept in Windows 7 it's now required to be admin when you want to start or stop a service or to create 'global objects' like the shared memory files that are used to communicate between DBM-client, server and database kernel.
    Since the user management of MaxDB Studio actually is just a small MaxDB instance, the service for this must be running.
    To start the service and to create the shared memory the admin privilege is necessary on Windows 7.
    What you may do is to flag the dbstudio.exe as "execute as administrator" - that will give you a pop-up warning every time you run the program but it will work.
    I assume that is the workaround that you're already using and it's the one I use as well.
    AFAIK the colleagues in Berlin are working on a version that doesn't require a MaxDB instance for local user management - that should remove this kind of problem as well.
    regards,
    Lars

  • Office Professional Plus 2010 - Fails to Install - Error 25004 - "System error: -1073418209" - Microsoft Key Management Server

    I am receiving an error when attempting to install a site license copy of Microsoft Office Professional Plus 2010. The enterprise environment that I am in is using a Microsoft Key Management Server for the authentication of all Office 2010 and Windows 7
    installations. The error that I receive at the end of the installation is: "Error 25004. The product key you entered cannot be used on this machine. This is most likely due to previous Office 2010 trials being installed. (System error: -1073418209)".
    I have never installed a trial of Office 2010, nor did I ever install the beta of Office 2010. I do have a copy of Microsoft Office Projects 2010 installed. Before attempting to install Office 2010, I had Office 2007 installed. I used the Upgrade option
    to install 2010, instead of removing 2007 (which apparently I should have done instead) first. I have tried using the Microsoft FixIt tool to remove both Office 2007 AND Office 2010. Neither of those tools has fixed my problem. Office 2010 also does not show
    up in my Add/Remove Programs list.
    Any ideas on how to fix this? I do not have time to reformat until after the Holiday seasons, and need to have Office working!

    Hi,
    The full error text is as follows: Error 25004: The product key you entered cannot be used on this machine. 
    This is most likely due to previous Office 2010 trials being installed. (System error: 1073422308)
    The key you are currently trying to install with, is an Office Professional Plus Trial key. A machine will allow one Professional Plus Trial key installed on it ever. Meaning you can
    install a trial on a machine, used it for some time, uninstall Office. When you go back to the Microsoft website and get a new key, the second installation will be rejected with the above error message.
    If this is not the situation, try to completely uninstall all the versions of the Office programs from control panel, and then use the suggestions in this KB
    article to uninstall it:
    How do I uninstall Office 2003, Office 2007 or Office 2010 suites if I cannot uninstall it from Control Panel?
    http://support.microsoft.com/kb/290301
    Then, reinstall the Office 2010 program.
    Best Regards,
    Sally Tang

Maybe you are looking for

  • Find all tables used in a stored procedure

    Hi, I have a requirement where i have to find all the tables used in a stored procedures from different  databases. Ex: i have a stored procedure where i use few tables from MASTER database and some from STAGE database.When i have written a query to

  • Document JavaScript tool is missing

    Hello I've found this old discussion (see below) - seems like it never came to a solution. I have the same problem. I can't find the Document JavaScript tool in my Acrobat Pro X. It should be in the Tools menu. But this is all there is: The installed

  • How to assign NULL value to an ITEM in Forms Personalization?

    Hi, how to assign NULL value to an ITEM in Forms Personalization? please suggest me. Thanks

  • Discrepancy between the confirmation & deletion of qRFC - LUWs

    Hi Guys, when I load master data  load in delta, the load gets terminated & its throughing Application log, where I can see this error message: When the datawas confirmed & deleted in the qRFC queue, the system found the discrepancy between the numbe

  • Best way to handle gifs in an app

    Hello, I have been playing around with project siena for a week or so now, and I am very impressed with its capabilities. I have a requirement to display a gif image on an app, this gif is about 5 MB in size and a new one is uploaded daily so I canno