Cisco Messaging Interface down

Hi all,
I'm having an issue on a CUCM machine running 6.0.1.2112-1. If I run the RTMT I get to see numerous of alerts saying:
'Service status is DOWN.
Cisco Messaging Interface...'
The alert keeps popping up every 30 seconds.
Can anyone tell me what the cause of this alert could be, and how it can be solved?
With kind regards,
Paul van den IJssel
Digacom, The Netherlands

Hello Paul --
I assume that you are using Cisco Unity/Unity Connection/Unity Express for the voicemail platform. If so, you will not need the Cisco Messaging Interface service and you can deactivate it from the serviceability pages. The service is only needed for external voicemail systems that are not Cisco.
Please let me know if you have any other questions. I hope this helps. Please rate helpful posts.
Thanks,
Ohamien

Similar Messages

  • Cisco Messaging Interface-Not Running

    Hi All,
    On the UCM 6.0 the Cisco Messaging Interface service is activated and when i check the status in 'control center feature services' it shows 'Not Running' and 'Activated'. If i start and refresh the page it again shows as 'Not Running'

    Hi Vineet,
    This interface is only used in CCM to Legacy VM integrations (via SMDI) if you are not setup that way this is why you are seeing this :)
    Cisco Messaging Interface Service
    The Cisco Messaging Interface allows you to connect a simplified message desk interface (SMDI)-compliant external **Third Party** voice-mail system with the Cisco CallManager. The CMI service provides the communication between the voice-mail system and Cisco CallManager. The SMDI defines a way for a phone system to provide a voice-mail system with the information needed to intelligently process incoming calls.
    Genrally the Cisco Messaging Interface (CMI) is a Cisco CallManager service that should be run only on the publisher server. This service intercepts calls destined for voicemail and generates appropriate SMDI messages, which are then delivered to one of the server's Component Object Model (COM) ports.
    From this doc;
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a008037e2f3.html#wp1024396
    Hope this helps!
    Rob

  • Sdlc interface down very often

    Hello,
    In my customer site, SDLC device connect to 2600. IOS version is 12.0.7T. Then access AS400 through DLSW function. We showed log and found the connected interface down very often. show log as below.
    We checked AS400 log and didn't find the SDLC device inactive ever. And we check SDLC device, the device work well, user didn't find any problem??
    We don't know why always log of message showed the interface down.
    Anyone can help me??
    .Jun 23 08:29:56 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:29:57 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:30:01 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:30:02 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:33:06 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:33:07 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:33:11 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:33:12 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:36:16 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:36:17 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:36:21 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:36:22 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    .Jun 23 08:39:25 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to down
    .Jun 23 08:39:26 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to down
    .Jun 23 08:39:30 Taiwan: %LINK-3-UPDOWN: Interface Serial1/0, changed state to up
    .Jun 23 08:39:31 Taiwan: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1/0, changed state to up
    JSB025a#sh inter se 1/0
    Serial1/0 is up, line protocol is up
    Hardware is CD2430 in sync mode
    Description: connect to SNA pu2.1
    MTU 1500 bytes, BW 128 Kbit, DLY 20000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation SDLC, loopback not set
    Half-duplex enabled.
    cts-delay 0 milliseconds
    dcd-txstart-delay 100 milliseconds
    dcd-drop-delay 100 milliseconds
    transmit-delay 0 milliseconds
    Errors - 0 half duplex violation
    Router link station role: PRIMARY (DCE)
    Router link station metrics:
    slow-poll 10 seconds
    T1 (reply time out) 3000 milliseconds
    N1 (max frame size) 12016 bits
    N2 (retry count) 20
    poll-pause-timer 10 milliseconds
    poll-limit-value 1
    k (windowsize) 7
    modulo 8
    sdlc vmac: 4000.2625.01--
    sdlc addr 01 state is CONNECT (xid-poll)
    cls_state is CLS_IN_SESSION
    VS 5, VR 0, Remote VR 5, Current retransmit count 0
    Hold queue: 0/200 IFRAMEs 116636/58170
    TESTs 0/0 XIDs 40235/14460, DMs 6784/6736 FRMRs 0/0
    RNRs 7/0 SNRMs 9757/0 DISC/RDs 9733/0 REJs 0/0
    Poll: clear, Poll count: 0, ready for poll, chain: 01/01
    Last input 00:00:00, output 00:00:00, output hang never
    Last clearing of "show interface" counters 9w3d
    Queueing strategy: fifo
    Output queue 0/40, 0 drops; input queue 0/75, 0 drops
    5 minute input rate 0 bits/sec, 50 packets/sec
    5 minute output rate 0 bits/sec, 0 packets/sec
    156063821 packets input, 318338246 bytes, 0 no buffer
    Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
    11 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 11 abort
    155708948 packets output, 337016303 bytes, 0 underruns
    0 output errors, 0 collisions, 43092 interface resets
    0 output buffer failures, 0 output buffers swapped out
    106807 carrier transitions
    DCD=up DSR=up DTR=up RTS=down CTS=down

    Hi,
    I believe that your line keeps bouncing due to Data
    Carrier Detect(DCD) going down. I didn't see a copy
    of the interface config but do you have the following
    command under your interface?
    half-duplex controlled-carrier
    This in conjunction with the dcd-txstart-delay and
    dcd-drop-delay settings will cause the DCE to drop
    DCD frequently.
    These are for very specialized environments which
    probably are not what you have.
    What is your environment, with respect to the
    connection to the AS/400? Is it just a Cisco DCE
    cable connected to an AS/400 cable? Or are there
    other cables/switches/modems involved?
    If you just have the Cisco DCE cable connected to
    the AS/400's cable then you do not need that command.
    Otherwise, it is possible you have a cable or
    physical interface problem.
    Please include your interface's config if this
    information wasn't enough to resolve the problem.
    Thanks and regards,
    Ed Mazurek

  • Error message when opening Outlook: The operation failed. The messaging interfaces have returned an unknown error. If the problem persists, restart Outlook.

    In an Exchange 2010 server/Outlook 2013 environment, one of our users is getting an error message every time they start Outlook. The error message says: "The operation failed. The messaging interfaces have returned an unknown error. If the problem
    persists, restart Outlook."
    The error log message details are as follow:
    System
    Provider
    [ Name]
    Microsoft Office 15 Alerts
    EventID
    300
    [ Qualifiers]
    0
    Level
    4
    Task
    0
    Keywords
    0x80000000000000
    TimeCreated
    [ SystemTime]
    2013-01-08T15:54:49.000000000Z
    EventRecordID
    655
    Channel
    OAlerts
    Computer
    Computer-Name.domain.local
    Security
    EventData
    Microsoft Outlook
    The operation failed. The messaging interfaces have returned an unknown error. If the problem persists, restart Outlook.
    301670
    15.0.4420.1017
    xyfc
    0x8004011B
    The system is as follows:
    Size of .pst file: 2.3 GB (Unicode format so there should be plenty of space left)
    OS: Windows 7 (64-Bit)
    Application: Outlook 2013 (32-Bit)
    The user upgraded from Outlook 2010 a few months ago and the error message has only recently started appearing on startup. I thought it was a corrupt mail profile, so I have already tried creating a new mail profile, as well as the repairing tool in Outlook.
    I even tested another email account and that worked just fine. So apparently it is something wrong with the specific user's account/profile and not something wrong with the computer - since my email account worked fine on his computer.
    Any help would be greatly appreciated.

    I had the same error message, only in my situation Outlook would only open successfully every 4 or 5 attempts. When Outlook would open (versus just hanging at the splash screen), I would get two dialog boxes with the warning/error message. 
    After I clicked okay I could get into Outlook.
    Previously I experienced this problem running my Office 2010 client with my Exchange 2007 mailbox on my old laptop.  The problem followed my mailbox through an Exchange 2010 migration (so new Exchange org), client upgrade to Outlook 2013, and a new
    laptop (so I knew it wasn't a corrupt profile).  This led me to the conclusion that it was a corrupt item(s) in my mailbox.
    To resolve the issue, I archived *everything* in my mailbox to a PST file, ran SCANPST to fix the corruption, and then uploaded everything back into my Exchange mailbox one folder at a time, stopping after each folder to close and restart Outlook so I could
    narrow down which folder had the corrupt item if the problem recurred.  I'm happy to say my issue is now resolved.

  • Outlook 2010 ...messaging interfaces returned unknown error... cannot resolve recipient. When replying

    There is a link with someone else who was receiving the same error, but i believe for different reasons.
    http://social.technet.microsoft.com/Forums/en-US/outlook/thread/43221dbf-60e1-4afb-8c25-f23f06deed3e
    I just performed an upgrade from office 2007 enterprise to office professional plus 2010 today (I am running Windows 7) and I keep getting this error:
    Microsoft Outlook
    The operation failed.  The messaging interfaces have returned an unknown error. If the problem persists, restart Outlook. Cannot resolve recipient.
    P1: 300531
    P2: 14.0.4763.1000
    P3: 6xk3
    P4: 0x80040700
    It happens when I reply to an email.  The addresses are in the format which outlook 2003 and 2007 have been using
    Webb, Sydney A <[email protected]>
    I notice that if I simply type the address:
    [email protected]
    it will send fine.
    I also notice, the format for contacts has changed to Webb, Sydney A ([email protected])
    () instead of <>
    i assume that is what is causing the issue, but all of my incoming emails are marked with the old style, so when I hit reply I have to retype the addresses every time(even for the same contact on following email replies).  I am sending via POP3(gmail
    account in PST is default), but I do have an exchange account configured which I occasionally connect to.
    any ideas on how to change the incoming format of messages so the sender's address is in the new format?
    I would greatly appreciate any help.
    Christopher Webb http://christophermichaelwebb.com

    I too updated from 2007 to 2010 and couldn't send group emails.  After reading many of the suggestions here, I discovered a simple solution. I simply clicked on the outlook contact, opened up the file in the address book, and changed the display name.
     I had some addresses that were listed under "display" like this:  John Doe ([email protected]). I changed each of those in the display field to read either John Doe or Doe, John.  I saved the contact and continued.
    Note:  I discovered this problem in sending out group emails.  So I opened the groups one by one.  Then I scanned down the list of displayed names, and clicked on any with the combination of name and address to them as an outlook address card.
     In the card, I changed the display name, and then clicked "update" to update the list with the new listing.  Sometimes after updating, the display name had not changed.  Hmmm... I noticed that there were two kinds of card icons to
    the far left of the displayed name.  With the lighter-appearing icon, changing did not work.  I had to delete the individual person in the group, and then re-add them by clicking "add member." Now they had disappeared in the listing.  So
    I clicked "advanced find."  There I put in their names or a portion of the email address, and found them quickly.  Then I double clicked on the correct listing to add the person back into the group.  
    At that point, the icon to the left of the displayed names had changed to a darker icon like the majority of my members, and clicking on the name to open the file worked, as did changing the display name.  Then when I clicked "update", I had
    the correct display name.  The changes stuck.  I think perhaps the lighter-appearing icon were adds to the group that I had not added to my outlook address book, but only to the group email.  It was so long ago that I added these members originally
    that I have no idea any more. 
    So now we know two things:  Display the name only, or display the email address only.  Both work.  Just don't display the combination with parentheses.  I wondered if perhaps the Outlook 2010 couldn't find that kind of listing referenced
    in the outlook address book, and that's what is causing this hangup?
    I hope this helps someone save a lot of time and irritation.  It was a fairly easy fix.

  • Unidentified traps and interface down alerts LMS 4.2

    Hi all,
    Sometimes we have unidentified traps in our log, we don't know where they come from.
    In high severity faults we see an active alert with device name “Unidentified” event name unresponsive but with a certain ip address.
    What are these alerts about? Can I filter them?
    A second issue I have is that I get interface down alerts. But when we log on to the device, there is no interface down at all. We can also ping the device from the lms server at that time. I have been told that the admin state and operational state has to be up.
    Thanks,
    Best Regards,
    Joris

    Hi Joris,
    Generic trap support is a new feature introduced in LMS 4.2 release. look at the below
    document also.
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.2/user/guide/lms_monitor/TrapFwd.html#wpxref13049
    LMS 4.2 release onwards DFM will display any unprocessed traps comming from device in
    fault monitor screen as unidentified trap under Inform alarm.
    For the other issue , it could be a DFM database issue , try to REDISCOVER those devices in
    DFM and see how it works
    Thanks
    Afroz

  • Intermittant radio interface down on 1130 APs

    I am having unified wireless installation, with WiSM on 6500 at central site and around 90 nos of 1130 APs located at remote locations ( over WAN) as well as some APs locate in the same location.
    The APs are configured in WCS, using default AP template.
    Alsomot all APs are showing minor alarms saying " radio interface threshold violated".
    In addition, a major alarm posted frequently on WCS saying "radion interface down".
    Cleints are complaining that they are loosing connectkion momentarily but connected again automatically wo WLAN. But they will have to log in to application programs in such cases.
    a.Does anybody have similar experience, and
    b. What are the best settings for 1130 APs trhat we have to do explicitly in setting up the WCS template ?
    Thanks ,

    Might be due to interference and the fact that RRM is enalbled and the ap's are changing channels causing the radios to shut down temporarily. Either set the channel or try to change the threshold.
    Here is the error info:
    http://www.cisco.com/en/US/docs/wireless/wcs/4.2/configuration/guide/wcsevent.html#wp1139158

  • VIF Bound Physcial Interface Down

    Hi Guys!
    We are trying to connect FI 6248 (UCSM 2.1.1a) to Brocade 6510 swtich(One FI to one of the two Brocade switches separately). The ports are configured as FC Uplink port and the FI's work in End-host mode. We created the service profile. After associating the SP to one of the blades the two errors occurs immediately:
    VIF <number> Bound Physical Interface Down
    VIF <number> Bound Physical Interface Down
    and this relates to the 2 vHBAs created in SP. Is this normal situation if OS isn't already installed on the host? We can't configure SAN zone from the brocade side because we don't see any WWPNs of the configured vHBAs in the SP. We see only FI's WWPNs(as I think). NPIV mode is enabled from the Brocade side. 
    Can someone explain what can cause this problem?

    Sergey,
    This is expected if there is no OS installed yet, see the possible reasons for the VIF down in this bug:
    https://tools.cisco.com/bugsearch/bug/CSCul99847
    Rate ALL helpful answers.
    -Kenny

  • Force dialer interface down

    Can I force dialer interface down until some one dials in?
    Sent from Cisco Technical Support iPhone App

    The router is configured as a hub VPN sever for my mobiles users.
    I don't have the option for dynamic routing due to the remote end.
    Primary connection is ip for mobile users. But if they can't use ip for any reason I want them to come in via Isdn.
    The hub needs to route ip unless it sees that the remote has come in via Isdn. I have considered a gre tunnel on the Isdn but that's over heads I'd prefer to avoid.
    Sent from Cisco Technical Support iPhone App

  • F0283 VIF 1 / 2 B-42/44 down, reason: Bound Physical Interface Down

    Hi
    I have some issues after migrate from CX4 SAN to VNX SAN. Everything is moved from CX4 to VNX and I have disabled FC Uplink port that is connected to CX4. Both my FI's is only connected to VNX.
    We want SAN boot on our ESXi host, and some of them is install on a boot LUN on VNX, and some other is install local at the Blade.
    My issue is that all my host shall boot from SAN. But suddenly this fails.
    I zones the host on our MDS switches, and does everything in VNX, so the host shall see its boot LUN. SAN Boot Target is changed so it sees the VNX SAN.
    In the install I see my boot LUN, and install ESXi without any issues. Remove the installation media and reboots the server.
    When it shall boot back up, it says:
    Reboot and Select proper Boot device
    or Insert Boot Media in selected Boot device and press a key.
    And i gets 8 major error messages like this:
    VIF 1 / 2 B-42/44 down, reason: Bound  Physical Interface Down
    What is wrong. I do the same thing now, as I did when I installed the hosts that is working.

    Can you try to re-ack the Server the Profile is associated to.  The error you're seeing usually means the host Iniitator interface (VIF) is down because it has no uplink to correclty pin to.  You said you shut down the ports the CX4 was previously connected to by disabling it.  Can you re-ack the blade which should re-pinn to the new/remaining uplink.
    If that doesn't correct the problem I'd look into your boot policy.  Double and triple check the boot targets entered in the profile and make sure they match the targets on the VNX, and that each one is online and logged into the MDS ("zone flogi database").  The symptoms you're seeing used to be common with Clariion arrays as they are Active/Passive.  During the installation any available path has access to the LUN for the installation, but they rebooting required the first listed target in the boot policy to be the "owner" of the LUN.  This was easily fixed by trespassing the LUN to the other Storage Processor on the array.  With VNX I'm pretty sure they are Active/Active arrays so this shouldn't matter.
    Regards,
    Robert

  • Message Interface no longer exist in Integartion Repository

    Hi,
         I am working on a IDOC to file case, in which I want to determine the receiver at runtime using a value in IDOC, with the help of Context objects/ XPATH. In Receiver determination of ID, after selecting Sender and Sender Interface, when I try to select Receiver, it's giving message "Message Interface no longer exist in Integration Repository" and I am not able to see the Sender IDOC in the conditions field before the Receiver selection. Anybody having any idea why I am getting that error message.

    hi,
    check if the system that you're using has this message interfaces in sender/receiver tab (double click on the
    system in directory)
    if not maybe the you need to add dependencies
    to the software object (product/software component) which has this message interface - this idoc
    (if you do remember to refresh sld cache) 
    /people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Problem with internet. When i open System preferences, Network, message drops down: 'your network settings have been changed by another application'. I click OK, but it drops a message again and again, preventing me to do anything about the setting.

    Problem with internet. When i open System preferences, Network, message drops down: 'your network settings have been changed by another application'. I click OK, but it dropps the message again and again, preventing me to do anything about the setting.

    A Fix for "Your network preferences have been changed by another application" Error 
    In the Library/Preferences/SystemConfiguration/ folder delete the following:
    com.apple.airport.preferences.plist
    NetworkInterfaces.plist
    preferences.plist
    com.apple.nat.plist
    You will have to re-configure all your network settings since deleting.
    (10.4.10)
    Use Software Update to update your OS to last version of Tiger.  Install all the other updates that goes along w/it.

  • Using one Message Interface for all mappings

    Hi Folks,
    I am using a BPM in which i m getting a file from file system which have system ID in it.
    I am having three send Synchronous step following that.
    What i need is to use the Message interface for file to be used for receiver determination based on system id in case of Synchronous interfaces.
    DO i need to include this File msg. interface in each mapping, if i do so will it be possible to send req. and get response for synchronous call.
    OR is there any way to to use the file msg. interface for each mapping.
    we are on SP17,I also tried Extended mapping but i am having SYNCHRONOUS send steps.
    Plz help me out
    Sachin

    Bhavesh
    <i>1. You receiver a file in your BPM . This has a field called SYSTEM ID?
    2. On the basis of the System ID field you need to determine the Receiver to which the Synchronous Request message has to be sent?</i>
    Sorry for that...because I was confused with jai's ans.. that's why said like that
    <b>You are absolutely correct</b>
    This is what i want to do.
    i can't use switch step here.  my BPM looks like this
    RecFile->sync send->transformation1->transformation2->sync send2->transformation3->BLOCK
    in BLOCK
    Sync Send3->transformation4 and so on...
    I am using three different Sync ABS Interface for each Sync send steps.
    In receiver determination i want to get the data from respective R/3 system based on system ID i.e. logical system in File MI.
    Say if it T90CLNT90 then get data from BS_SAPR3_4.6 else from BS_4.7
    Sachin
    Message was edited by:
            Sachin Dhingra

  • Message interface with two types of message types

    Hi experts,
    I am having problem that a proxy cannot be generated because  of the (mixed) types of the message types that the interface is using.
    The first message type is defined in the repository and another is defined as an external definition, imported in from an outside source.
    Here is the SAP message I received when I tried to generate the proxy for this interface.
    +++++++++++++++++++++++++++++++++++++++++++++
    Interface uses external and internal message definitions
    Message no. SPRX122
    Diagnosis
    In a message interface you can use messages from different sources:
    1. Message types and fault message types edited in the Integration Repository
    2. Messages imported into the Integration Repository (external definitions, RFC, IDoc)
    In the current message interface, message types from different sources have been used.
    Since messages from these different sources must be handled differently during proxy generation, such a mixture of messages within a message interface is not possible.
    System Response
    The interface cannot be generated.
    Procedure
    Change the interface definition accordingly in the Integration Repository.
    ++++++++++++++++++++++++++++++++++++++++++
    The imported xsd is quite large and also contain many large includes. I don't have the option of creating the message type manually.
    Any suggestions?
    Thank you,
    -michelle

    Hi all,
    I tried several things and the problem is still not resolved. This is what I learned.
    First of all, I believed the SAP message about mixing of internal and external message is misleading or even wrong. I tried with both message types being external but I still get the same message that the interface has one internal and the other external message type.
    Secondly, since Arvind suggested that I might have used an xml element that is not currently supported by ABAP proxy, I then change to another definition with the most simplest elements. I then attached this other definition to the interface and tried generating the proxy again. I still get the same system message that I am using mixing of message types in one interface.
    My conclusion is XI still is not capable of generating ABAP proxy from external definition.
    Does anyone have any comments/suggestion/experience on this issue?
    Best regards,
    -michelle

  • Message Interface does not exist in IR u0096 but it does!

    Hi, well again i have a problem. I am still trying to get the XI-demo Checkflight…. to run but there are some obstacles on my way.
    I just wanted to check a MI given in the ID to check the attributes and picked it in the ID to get linked to the IR but a pop-up appears saying
    “Message Interface does not exists in Integration Repository”
    What’s the reason for this because obviously it is there, still existing.
    I tried to refresh the cache of all XI-components, did a server restart but nothing seems to be working.
    On the other hand I have some other questions:
    -     Why is it not possible to delete an object (business system) from the ID? I know because of the dependencies of the different channels but it should be possible because of re-generation of the communication-channels (this was also my approach for solving the problem mentioned above!)
    -     When do I have to refresh the cache in general? Is it indefinite whenever I want to or it seems to be the right time because something is not running the way it should and it seems a little odd

    Hi Carsten Heinrich,
    This will help you,
    1)     Cache Connectivity Test
    In RWB component monitoring, we now have the option of checking whether the cache-connectivity is functioning correctly. This is useful when we are experiencing problems when updating the runtime cache. The system displays a separate window in which we perform the test. If no previous tests have been performed, the system displays a corresponding message. Otherwise, the system shows when and by whom the last test run was started, together with the result of this test.
      To start a new test run, choose Start Test.
    The system displays the first results of the test run. Since the whole test takes some time, we can update the displayed results if necessary.
    To Update the displayed results, choose Refresh Display.
    The overall result for each component is displayed as a green, yellow, red, or gray symbol. A green symbol is only displayed if both update steps for the runtime cache were successful, that is, they both have a green symbol.
    2)     Cache notification status
    a)     Start the Integration Repository.
    b)     Select Environment ® Cache notification.
    c)   Have a look at the entries for the relevant user and date.
    d)   Have a look at the entries for the relevant cache instance, user and date.
                   3)    Cache update and resend the message
    a)Start transaction SXI_CACHE.
    b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
    c)     Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.        
             4)     Deleting the SLD Cache
      Many actions require  to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
    However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
    To clear the SLD cache, from the Integration Builder main menu, choose Environment  ®  Delete Cache for SLD Data.
    Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
    Regards
    Agasthuri Doss

Maybe you are looking for