Original destination for messages redelivered to error destination

          Hi,
          I'm writing an admin interface for our system and one part of it needs to manage
          redelivery of messages. We have multiple destinations, and I have configured
          one queue to act as an error queue for them all. My plan had been to allow users
          to resubmit messages to their original destination - but I dont have that information.
          Message.getDestination() returns my error queue, which makes sense. I was hoping
          there'd be a header I could extract that might contain the name for of the original
          destination, but I dont seem to be able to find it.
          The only thing I can think of is to have a separate error queue for each destination,
          this would allow me to assume that all messages were initially sent to the corresponding
          queue - but it seems a little heavy handed... does anyone else have a better solution?
          cheers
          dim
          

Sorry Dmitri, I mixed up names here.
          "Adarsh Dattani" <[email protected]> wrote in message
          news:[email protected]...
          > Terrence,
          >
          > Check out the "Error Destination Manager" sample app at
          > http://dev2dev.bea.com before you write a lot of code. I have already the
          > built the admin facility that you are talking about and have also included
          > the source code and documentation with it. Let me know if you need any
          help
          > with it.
          >
          > AD
          >
          > "Dmitri Colebatch" <[email protected]> wrote in
          message
          > news:[email protected]...
          >
          > >
          > > Hi,
          > >
          > > I'm writing an admin interface for our system and one part of it needs
          to
          > manage
          > > redelivery of messages. We have multiple destinations, and I have
          > configured
          > > one queue to act as an error queue for them all. My plan had been to
          > allow users
          > > to resubmit messages to their original destination - but I dont have
          that
          > information.
          > > Message.getDestination() returns my error queue, which makes sense. I
          > was hoping
          > > there'd be a header I could extract that might contain the name for of
          the
          > original
          > > destination, but I dont seem to be able to find it.
          > >
          > > The only thing I can think of is to have a separate error queue for each
          > destination,
          > > this would allow me to assume that all messages were initially sent to
          the
          > corresponding
          > > queue - but it seems a little heavy handed... does anyone else have a
          > better solution?
          > >
          > > cheers
          > > dim
          > >
          >
          >
          

Similar Messages

  • An error occured while creating the original attribute for message no26 296

    Hi All,
              I am new to DMS , we are trying to store PM documents on content server , created a storage category and while assigning files to storage category then on saving the document i get the below error :
    An error occured while creating the original attribute for
    Message no. 26 296
    Diagnosis
    An error occured while creating an original in the Knowledge Provider.
    System Response
    The original could not be created.
    Procedure
    Contact the systems administrator and check the log file (transaction Evaluate application log, object SDOK).
    Please let me know what configs i am missing ...
    Thanks in advance
    regrds
    pushpa

    Hi Pushpa,
    Which enhancement package are you on currently? This is observed in cases where originals in DIR's are invisible and sometimes error message 26296 occurs in transaction CV01n. Hence,please check your entries in the table SDOKPROP to avoid such a problem in your system.
    Further,suggest you explore if the below resolutions can be adopted in your case.
    http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=10321987
    http://wiki.sdn.sap.com/wiki/display/PLM/OriginalsinvisibleafterEHP3or+EHP4
    Regards,
    Pradeepkumar haragoldavar

  • Distinguishing between messages in the error destination

    Hi,
              First of all, I'm using Weblogic 8.1 SP4.
              I recognize that messages are delivered to the error destination if one of two situations occur:
              1) The message has reached the redelivery limit.
              2) The message has expired.
              In my message-driven bean that picks up messages from the error destination, I need to know the reason why a message ended up there. That is, I need to know whether it was expired or the redelivery limit was reached.
              Is this possible?
              Thanks in advance!
              Henrik Oddershede

    The JMS chapter of the book "Professional Oracle WebLogic Server" has a nice discussion of poison message handling.
    In your case, I'd recommend adding code to your inbound queue processing application to detect bad format messages and automatically redirect them to a separate queue for manual intervention. This would avoid mixing up the bad format messages with your automatically handled problem messages. You could then write a specialized application that your administrator can use to process the messages.
    Tom

  • [svn] 3897: BLZ-266: Ajax FABridge doesn' t pull in channel info for messaging destination

    Revision: 3897
    Author: [email protected]
    Date: 2008-10-26 17:10:00 -0700 (Sun, 26 Oct 2008)
    Log Message:
    BLZ-266: Ajax FABridge doesn't pull in channel info for messaging destination
    (merge branch changelist 3896 to mainline)
    qa: yes
    doc: no
    bug: BLZ-266
    checkintests: passed
    Details:
    /resources/fds-ajax-bridge/actionscript/FDMSBridge.as
    * need to initialize the parameters for the LoaderConfig
    Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-266
    http://bugs.adobe.com/jira/browse/BLZ-266
    Modified Paths:
    blazeds/trunk/resources/fds-ajax-bridge/actionscript/FDMSBridge.as

  • [svn] 3896: BLZ-266: Ajax FABridge doesn' t pull in channel info for messaging destination

    Revision: 3896
    Author: [email protected]
    Date: 2008-10-26 16:02:33 -0700 (Sun, 26 Oct 2008)
    Log Message:
    BLZ-266: Ajax FABridge doesn't pull in channel info for messaging destination
    qa: yes
    doc: no
    bug: BLZ-266
    checkintests: passed
    Details:
    /resources/fds-ajax-bridge/actionscript/FDMSBridge.as
    * need to initialize the parameters for the LoaderConfig
    Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-266
    http://bugs.adobe.com/jira/browse/BLZ-266
    Modified Paths:
    blazeds/branches/3.0.x/resources/fds-ajax-bridge/actionscript/FDMSBridge.as

  • No rfc destination defined for global trade services error while doing migo

    Hi all,
    Pls help me in fixing the following error..
    "no rfc destination defined for global trade services" error while doing migo

    i guess you will be getting dumps in the background in ST22. Can you please check this and post the details if there are any dumps?
    Meanwhile, check this note:
    Note 1098491 - MIGO:Termination MESSAGE_TYPE_X with IO 304 (subcontracting)
    Cheers,
    Jazz

  • I receive this error message "The operation cannot be completed because the original item for "backup" cannot be found.

    I performed a clean install of Lion, then upgraded to Yosemite. Now, i am trying to restore files and programs from my backup in my time capsule but when i connect to the backup folder i receive this error message "The operation cannot be completed because the original item for "backup" cannot be found.
    I previously had mavericks installed and was able to backup and restore just fine. I do believe that within the time since i last performed a backup or restore there was an update for the time capsule that i ran using my iPhone. I need a solution to this issue.

    Yosemite can take a very long time to index the backup.. and it seems to be impossible in my own testing to get back beyond the latest one.
    If you cannot manage a migration.. which I guess is what you are trying to do.. see if you can do a full restore to a USB drive plugged into your computer.

  • I updated my a friends iphone but failed. i was ask to restore to original software for which i did but a message pops up after unsuccessful restoration that 'an error occured' pls help me.

    i updated a friends iphone but it failed to update. i was as to restore to original software for which i did but it also failed. a message poped up that 'an error occured'. the phone is not responding. pls i need help

    What is the exact error and/or error code that it is displaying?

  • ERROR WHEN START ESR: Cannot activate endpoint for message-driven bean

    Hi Gurus,
    We just upgraded our PI 7.1 to SP11, and we have finished it successfully, then we go to the /rep/start/repository.jnlp to start the ESR but some error happens,while the ID,SLD and RWB works well, below is the detailed message:
    Application cannot be started!
    Details:     
    com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repository*xml|com.sap.xpi.ibrep.server.jar*xml|WorkspaceSyncMessageReciverMDB
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:893)
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:425)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:498)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3422)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3408)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:749)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:180)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:288)
         at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:103)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:250)
    Caused by: com.sap.engine.services.ejb3.container.ActionException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repository*xml|com.sap.xpi.ibrep.server.jar*xml|WorkspaceSyncMessageReciverMDB
         at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:103)
         at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
         at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:59)
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)
         ... 34 more
    Caused by: javax.resource.NotSupportedException: javax.resource.spi.UnavailableException: Could not activate endpoint for the configured number of attempts
         at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:113)
         at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:451)
         at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:154)
         at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:85)
         at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:58)
         at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:95)
         ... 37 more
    Caused by: javax.resource.spi.UnavailableException: Could not activate endpoint for the configured number of attempts
         at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:161)
         at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:101)
         ... 42 more
    Caused by: javax.resource.spi.UnavailableException: The destination jms/queue/xi/repository/SWCVSync cannot be looked up. Last attempt performed : jms_vendor_queues_global/jms/queue/xi/repository/SWCVSync
         at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:369)
         at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:128)
         ... 43 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of SWCVSync.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:367)
         ... 44 more
    how should we resolve this issue? does any one have such experience on this issue?
    thanks.

    Hi;
    As our Colleague said it would be good to create message to SAP.
    01 .Please check the cache,
    02. check the system users are  not locked.
    03. Re-initialization option in Java Web Start Administration (before using this please read the description carefully).
    04. try Full Cache Refresh.
    05. Check the Java run time version you are using.
    Regards,
    Prabhu Rajesh

  • Error when ESR starts - Cannot activate endpoint for message-driven bean

    Hi, as already posted on ERROR WHEN START ESR: Cannot activate endpoint for message-driven bean
    after an upgrade to PI 7.1 SP11, we got the following error when trying to start ESR, other applications work well:
    Application cannot be started!
    Details: com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|WorkspaceSyncMessageReciverMDB
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:893)
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:425)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:498)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3422)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3408)
         at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:749)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:180)
         at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:288)
         at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)
         at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:103)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
         at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
         at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
         at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
         at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
         at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:250)
    Caused by: com.sap.engine.services.ejb3.container.ActionException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repositoryxml|com.sap.xpi.ibrep.server.jarxml|WorkspaceSyncMessageReciverMDB
         at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:103)
         at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:81)
         at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:59)
         at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:887)
         ... 34 more
    Caused by: javax.resource.NotSupportedException: javax.resource.spi.UnavailableException: Could not activate endpoint for the configured number of attempts
         at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:113)
         at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:451)
         at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:154)
         at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:85)
         at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:58)
         at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:95)
         ... 37 more
    Caused by: javax.resource.spi.UnavailableException: Could not activate endpoint for the configured number of attempts
         at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:161)
         at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:101)
         ... 42 more
    Caused by: javax.resource.spi.UnavailableException: The destination jms/queue/xi/repository/SWCVSync cannot be looked up. Last attempt performed : jms_vendor_queues_global/jms/queue/xi/repository/SWCVSync
         at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:369)
         at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:128)
         ... 43 more
    Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of SWCVSync.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:367)
         ... 44 more
    Thanks.

    Guys,
    I have deployed the below components and after this repository could not be started which gives the below error.
    1000.7.11.10.18.20130529165100
    SAP AG
    sap.com
    SAP_XIAF
    1000.7.11.10.11.20130529165100
    SAP AG
    sap.com
    SAP_XIESR
    1000.7.11.10.15.20130529165100
    SAP AG
    sap.com
    SAP_XITOOL
    We have the same issue. Still the Restart did not solve ths issue.
    Can anybody help? We are not able to start the XI Repository.
    Our PI components are as below
    com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/com.sap.xi.repository; nested exception is: java.rmi.RemoteException: [ERROR
    CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:
            com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean sap.com/com.sap.xi.repository*xml|com.sap.xpi.ibrep.server.jar*xm
    l|CacheRefreshMDB^M
            at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)^M
            at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)^M
            at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)^M
    1000.7.11.10.6.20121015232500
    SAP AG
    sap.com
    MESSAGING
    Regards
    Omkar

  • Rules based on a nickname/original destination address

    We have a zentral post-Admin account which collect different
    email-destinations via nicknames (Fax@DNS, Bill@DNS, Sales@DNS, ..).
    Now we want to move incoming emails based on the original email-address,
    same as the used GW nickname, to different folders. Example is Fax@DNS
    should be moved to a folder Fax. We see the nickname in the incomming
    mail but we cannot find a working rule.

    Dear Danita,
    sorry holiday delayed my answer.
    I will try next day and response.
    Thanks,
    Bodo
    =============================ðWðWðWðWðWðWðW ðWðWðWðWðWðWðWðWð6ðWðWðWðWðWðWðWð WðWðWðWðWðWðWðWðMEBSware Informatik GmbHðWðWðWðWðWðWðWðWðWðWðWðWðWðWðW 6ðWðWðWðWðWðWðWðWðWðWðWðWðWðWðWðB odo SchulzðWðWðWðWðWðWðWðWðWðWðWðWðWðWð Wð6ðWðWðWðWðWðWðWðWðWðWðWðWðWðWðW ðWðWðWðWðWðWðWðWðWðWðWðWðWðWðWð6 WðWðWðWðWðWðWðWðWðWðWðWðWðWðWðBodo .[email protected]ðWðWðWðWðWðWðWðWðWðW WðWðWðWðWð6ðWðWðWðWðWðWðWðWðWðWðW ðWðWðWðWðwww.mebsware.deðWðWðWðWðWðWðW ðWðWðWðWðWðWðWðWð6ðWðWðWðWðWðWðWð WðWðWðWðWðWðWðWð========================== ===>>>
    Von: DZanre<[email protected]>
    An:novell.support.groupwise.2012.agents
    Datum: 16.01.2013 20:45
    Betreff: Re: rules based on a nickname/original destination address
    Bodo Schulz wrote:
    > Example is Fax@DNS
    > should be moved to a folder Fax.
    I actually have a lot of rules that work on nicknames. I realize that I'm
    coming to this message "late", but the easiest way to troubleshoot rules is to
    first just do a "filter" in the inbox to find what works.
    Do a find for "to: contains [email protected]" - do you get the results you
    expect? If so, then a rule on that query should also work.
    Danita
    Novell Knowledge Partner
    http://www.moveoutoftheoffice.com

  • My hard drive fried and had to be replaced. I'm trying to install CS4 from my original discs but keep getting this error message - "One or more of the required components of Adobe Creative Suite 4 Design Standard failed to install correctly". A customer s

    My hard drive fried and had to be replaced. I'm trying to install CS4 from my original discs but keep getting this error message - "One or more of the required components of Adobe Creative Suite 4 Design Standard failed to install correctly". A customer service rep gave me a link to download off the Adobe site, but when I try to open the file to run it, I get this error message - "A problem occurred extracting the archive".
    Can anyone help?

    Yep.  Nothing happens at all. Windows tries to execute the uninstaller, but I don't get any other screen and all activity stops for the MSI.  I monitored it in Process Monitor and the MSI executable appears, but is quickly ended, like it couldn't find anything or something.
    It's as if windows has a blank entry in Programs and Features, because it used to show the size of the Adobe application in the "Size" column.  Now it's just blank.  Link to screenshot below:
    http://img829.imageshack.us/img829/5006/screenshotcaf.jpg
    Note the install date.  That's when I was able to successfully reinstall it.  Now I can't even do that.  I should also mention I tried Revo Uninstaller.  It deleted one small registry key, but nothing changed.
    By the way, is the CS cleaner supposed to ask for a disc in the drive when you run it?  It refused to run unless I had one in it, so I used my install dvd.

  • Accessing the original message body in Error handler

    Hello everybody,
    The loanGatewy3 proxy service in the OSB tutorial uses a stage in the request pipeline for validation. If a validation error occurs the error handler reports the original body message using a reporting action.
    Now if an error happens inside the Routing node; and if an error handler is defined to report the original message ($body), the reporting action will report the error message not the original message. It seems that the $body variable contains the erroneous response instead of the original message. So is there a way to access the original request $body inside a node error handler?
    Best regards,
    Tarek

    you can always put the original message into a dummy variable $origMessage, then in the event of an error report on $origMessage not $body
    cheers
    James

  • Can anyone explain origination/destination on the billing summary?

    can anyone explain origination/destination on the billing summary?

    The destination of a call made by the cell phone is where billing is based, if you are calling them.
    For example, if I call my friend who has a NYC number and she is standing next to me here in GA and I have a MI number, The origination will show Podunk GA, but the destination will still show NYC.
    Now if she calls me from GA, on my bill it will Destination, Incoming Call
    Whether incoming or outgoing, on the bill, you, the line holder, are always the Origination.  Look at the pic below and look at the calls from 8.5. my friend from NYC, visiting Hiram, when calling her shows NYC. Yet when she called me, it is Incoming Call
    So basically, you never know WHERE the person on the other end actually is.
    Hoped this helps

  • An error occured while creating the original attribute for

    Hi All,
    We encounter  this error in  "An error occured while creating the original attribute for " DMS  very often when a user edits a file & tries to check in.
    I searched the forums & realized that this is caused by the inconsistencies in the KPRO & DMS server and removing these
    inconsistencies will repair this issue.
    I have been deleting the inconsistencies using DMS reports DMS_KPRO_READ & DMS_KPRO_CHECK1 and it resolves the error
    so the file is unlocked. But I haven't been able to figure out the ROOT cause of this issue.I couldn't find any information on the root cause of this issue. What can be done to fix this error permanently.
    Regards
    -Neha

    Hi Neha,
    Please go to transaction SE16 and enter 'SDOKPROP' as table. Then enter 'DMS*' in the field PROP_NAME and press F8. Now all DMS related entries should be displayed to you. Please compare them with the following entries displayed in the attached screenshot and maintain the missing entries.
    DMS_ACTIVE_VERSION 00 Active Version
    DMS_APPLICATION 00 Logical application
    DMS_CHECKOUT_USER 00 Checkout User
    DMS_CREATE_AUDIT 00 Generate new version of the original
    DMS_DEFAULT_LANGUAGE 00 Default Language
    DMS_DELETEABLE 00 PHIO deletable
    DMS_DOC_KEY 02 IWB_DMS01 DMS_DOCKEY Document info record
    DMS_DOC_VERSION 00 Version of relevant document
    DMS_DRAW_APPNR 00 Application number from DRAW
    DMS_DRAW_DTTRG 00 Data carrier from DRAW
    DMS_DRAW_FILEP 00 File name from DRAW
    DMS_FILE1 00 File name(firstpart)
    DMS_FILE2 00 File name(secondpart)
    DMS_FILE3 00 File name(thirdpart)
    DMS_FILE_ID 00 GUID that points to table DMS_PHIO2FILE
    DMS_FRMTXT 00 Format description, ID of additional file
    DMS_MUP_CAT 00 Markup category
    DMS_MUP_FLAG 00 Markup flag
    DMS_ORDER 00 Sequence of additional files
    DMS_STATUS 00 Document status
    DMS_STATUSNR 00 Number in status protocol
    DMS_STATUSNR_X 00 References to Status Log
    Please pay attention that all entries are typed well and that there are no spelling errors. If all these values are maintained correctly in table SDOKPROP the dump and the error message should no longer appear.
    For further information you can also see the corresponding SDN WIKI page under
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/plm/error26296in+CV01N
    Regards,
    Ravindra

Maybe you are looking for

  • How to Connect the Asha 205 to PC

    hi..... i have Nokia Asha 205 and i wanna to connect it with my Pc and it dont have connection port... so how will i connect it .... help pllzzzz Thanks Moderator's Note: The subject was amended as the post was moved to the appropriat board.

  • Select which users doesn't logged their work yesterday on MS Project 2013

    We use MS Project 2013 to control people work report. I wanna make a SQL query that will catch all users that doesn't set their work yesterday on WebProject App. My intention on that is to alert them by e-mail about this. If the user doesn't logged h

  • IMessage verification email not received

    I've seen this issue in other threads but it persists for me. I only have a single Apple ID and I've verified at appleid.apple.com that both my alternate email addresses show there as "verified". But when I attempt to use either of those addresses on

  • Where is the volume animator in GarageBand 10.0.2 like the earlier version?

    Is there a volume control animator for fine volume control in individual tracks like there was in the earlier version of GB? I can't seem to find it. Thanks for any support!

  • AS Logging

    In AS Performance Tuning, Oracle recommends disabling XLF logging at the server level and "enabling" the logging for each listener to enhance performance. I have done this for each of my listeners using the [ConnectionLogs] section of the svxxx.cfg c