Message store

Hi,
I have a code which calls standard function module. The standard function module outputs messages using the message statement. So, if an error occurs in the function module, it does not return me back anything through the program, but just gives out an error message, which I would not be aware of through my program.
Is there a way to activate any memory log, so that whenever such error/ warning messages happen in the standard function module, then message will be sent to the log, and when the control returns to my program, I can read the message log, and call the appropriate handler from my code.
Thanks,
Juwin

The function module just does not throw any exception. It gives out an error message and stops right there. I would rather prefer the function module to throw an exception and let me handle the error in my own way.
The code I am using is:
FORM create_to .
  CLEAR v_tanum.
  CALL FUNCTION 'L_TO_CREATE_SINGLE'
    EXPORTING
      i_lgnum               = v_0200data-lgnum
      i_bwlvs               = v_0200data-bwlvs
      i_matnr               = v_0200data-matnr
      i_werks               = v_0200data-werks
      i_lgort               = v_0200data-lgort
      i_anfme               = v_0200data-qnty
      i_altme               = v_0200data-uom
      i_squit               = 'X'
      i_wempf               = v_0200data-recipient
      i_vlenr               = v_storageunit
      i_nltyp               = v_0200data-sttype
      i_nlpla               = v_0200data-destbin
      i_update_task         = 'X'
      i_commit_work         = space
    IMPORTING
      e_tanum               = v_tanum
    EXCEPTIONS
      no_to_created         = 1
      bwlvs_wrong           = 2
      betyp_wrong           = 3
      benum_missing         = 4
      betyp_missing         = 5
      foreign_lock          = 6
      vltyp_wrong           = 7
      vlpla_wrong           = 8
      vltyp_missing         = 9
      nltyp_wrong           = 10
      nlpla_wrong           = 11
      nltyp_missing         = 12
      rltyp_wrong           = 13
      rlpla_wrong           = 14
      rltyp_missing         = 15
      squit_forbidden       = 16
      manual_to_forbidden   = 17
      letyp_wrong           = 18
      vlpla_missing         = 19
      nlpla_missing         = 20
      sobkz_wrong           = 21
      sobkz_missing         = 22
      sonum_missing         = 23
      bestq_wrong           = 24
      lgber_wrong           = 25
      xfeld_wrong           = 26
      date_wrong            = 27
      drukz_wrong           = 28
      ldest_wrong           = 29
      update_without_commit = 30
      no_authority          = 31
      material_not_found    = 32
      lenum_wrong           = 33
      OTHERS                = 34.
  IF sy-subrc <> 0.
    PERFORM err_message USING 7.
  ELSE.
    IF v_tanum IS NOT INITIAL.
      COMMIT WORK AND WAIT.
      PERFORM err_message USING 8.
    ENDIF.
  ENDIF.
  LEAVE TO TRANSACTION sy-tcode.
ENDFORM.                    " create_to

Similar Messages

  • Backing Up and Restoring the Message Store v.s. the queue

    Hello,
    We are running iPlanet 5.2 Messaging Server and need to migrate to another (duplicate) 5.2 Messaging Server. We have all the software installed and the LDAP user accounts created. Now we just need to move the existing mail from one server to the other.
    I found the Backing Up and Restoring the Message Store section in the Admin Guide says to back up and restore your data, Messaging Server provides the imsbackup and imsrestore utilities.
    However I am wondering about the Queue?
    Under <instance>/imta/queue
    What is the difference between the Message Store
    and the Queue? Can I just backup and restore the Queue using tar or cpio?
    Thanks in advance for any advice.
    Regards,
    Tim

    Hello,
    We are running iPlanet 5.2 Messaging Server and need
    to migrate to another (duplicate) 5.2 Messaging
    Server. We have all the software installed and the
    LDAP user accounts created. Now we just need to move
    the existing mail from one server to the other.
    I found the Backing Up and Restoring the Message
    Store section in the Admin Guide says to back up and
    restore your data, Messaging Server provides the
    imsbackup and imsrestore utilities.
    However I am wondering about the Queue?
    Under <instance>/imta/queue
    What is the difference between the Message Store
    and the Queue? The Message Store is where messages get delivered to, so you can read them.'
    The queue is where messages are temporarily stored, pending delivery to wherever they go.
    You can use tar, cpio, or what have you for the queue. Stop the server first. . .
    You then just restore the files to the new server. No need to restart or anything like that. Just dump the files in, and run
    imsimta cache -sync
    to tell the MTA to re-read the queue.
    Can I just backup and restore the
    Queue using tar or cpio?
    Thanks in advance for any advice.
    Regards,
    Tim

  • Berkeley DB XML as Message Store

    Hi,
    I need to build a 'Message Store' (as referred to in 'Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions') for our SOA. Components of the SOA are coupled by JMS / sockets and send XML messages to each other. The central message store would consume all messages and so provide a message history and allow comparison of messages for support, performance measurement, troubleshooting, etc.
    One approach which occured to me would be lightweight Java framework on top of Berkeley DB XML, which would handle connectivity to all integration points.
    All of our messages are small (< 5K) but some types are high frequency (say 2K/s).
    Can anyone comment on this approach pls or share experiences pls?
    Many thanks!
    Pete

    The short answer is that you need to shut down the FastCGI Perl script before you copy the files over, and then re-start it once the file copy is complete. Basically, what's happening is that FastCGI Perl script has cached data in file-system backed shared memory. When you replace the underlying files via an file system copy "under the covers" so to speak, the in-memory and on-disk data becomes out of sync. Subsequent access to the repository can fail in many ways, a core dump is often going to be the result.
    If you don't want to shut down the FastCGI Perl script during the copy, there are several other options that you could consider.
    1) Copy the new files into a new/alternate directory location, stop/re-start the FastCGI Perl script when the copy is complete, pointing to the new location. That minimizes the "downtime" or,
    2) Delete and insert documents one at a time through the API or,
    3) Update documents one at a time through the API or,
    4) Truncate the container and insert the documents.
    Options 2, 3 & 4 will allow the FastCGI Perl script to keep on running, but will probably take more time and may result in larger database files.
    Replication really won't help much if your goal is to completely replace the repository once every 24 hours. The same action would have to be applied to the master and replicated to the other repository locations. The same action of "replace everything" is still occurring.
    I hope that this helps.
    Regards,
    Dave

  • Where does Messages store attachments on the iPad?

    Where does Messages store attachments on the iPad?
    some photos are quite large, so it would be good to know where they go, and how to manage the app.... ;)

    Managing memory usage is not possible because the user does not have access to the file structure (unless you have jail broken your iPad that is).

  • Exchange Server 2010 Move mailbox to database but display MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)

    I have 2 exchange server "A" and "B". Server "A" have "Test1" database and Server "B" have "Test2" database. I tried move some mailboxes from "Test1" to "Test2"
    but sometimes mailboxes cannot finished and display below error.  I used Domain administrator to move mailboxes and grant "Manage full access permission" to these mailboxes but still failed. Finally, I clear the failed move request
    and repeat the move mailboxes action several times.  Then, the move request completed without error. Have any suggestion? Please help. Thank you!
    Mailbox move for 'xxx.com/xxx/xxx/xxx - Users/xxx/Peter' (331d5b4e-0bd1-428a-ae28-d97581ae0d7f) has failed.
    Error code: -2147024891
    MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
    Diagnostic context:
        Lid: 18969   EcDoRpcExt2 called [length=132]
        Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
        Lid: 32881   StoreEc: 0x80070005
        Lid: 50035 
        Lid: 64625   StoreEc: 0x80070005
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 56503 
        Lid: 12716   StoreEc: 0x80070005
        Lid: 20794 
        Lid: 28474   StoreEc: 0x80070005
        Lid: 22330   dwParam: 0x0        Msg: 14.03.0123.002:NHK-S08-MBD02
        Lid: 1750    ---- Remote Context End ----
        Lid: 23354   StoreEc: 0x80070005
        Lid: 25913 
        Lid: 21817   ROP Failure: 0x80070005
        Lid: 26297 
        Lid: 16585   StoreEc: 0x80070005
        Lid: 32441 
        Lid: 1706    StoreEc: 0x80070005
        Lid: 24761 
        Lid: 20665   StoreEc: 0x80070005
        Lid: 25785 
        Lid: 29881   StoreEc: 0x80070005
    Context:
    Mailbox: Primary (331d5b4e-0bd1-428a-ae28-d97581ae0d7f)

    Hi Gordon 
    This could happen if there is any mailbox which has occupied more space than its normal quota allocated.
    As suggested by geo try to clean all the DB's first 
    You can probably run Get-Mailboxdatabase | Clean-Mailboxdatabase which will clean all of your DB's wait for some time until it gets completed
    Also try running the command with the MRS server parameter switch and specify a CAS FQDN and see the results if it gets succeded
    Get-Mailbox -Database 'DBNAME'| New-MoveRequest -TargetDatabase DBNAME -BatchName "BATCHNAME" -BadItemLimit 100 -AcceptLargeDataLoss -MRSserver CAS server FQDN Good Luck !!Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
    Regards,
    Sathish

  • Error Message when Trying to Sync to MS Outlook 2010, "No Available Message Stores"

    Hi,
    I am trying to Sync My blackberry 8330 Phone with MS Outlook 2010 Beta.
    I can not Sync to any part of MS Outlook (Calendar, E-Mail, etc)  I always get the same error message "No available Message Stores".  Does anyone know what is causing this or how to fix it.
    Specs:
    Windows 7 64 bit
    MS Outlook 2010 Beta 32 bit
    Default Profile
    Blackberry OS V5.0
    Latest BlackBerry Desktop Manager.
    Thanks to anyone who can help.
    -Scoobs
    Solved!
    Go to Solution.

    Hi and welcome to the forums!
    A couple of places for you to visit: Blackberry 101   Tips & Tricks
    Take a look at this link:  No available msg stores
    Happy to have you here!
    IrwinII
    Please remember to "Accept as Solution" the post which solved your thread. If I or someone else have helped you, please tell us you "Like" what we had to say at the bottom right of the post.

  • Sun Messaging Server message-store inside zone (container)

    Hi Guys,
    i'm running Sun Messaging Server 7.3-11.01 (64bit, sparc).
    Do you now if message-store inside a zone is supported?
    Thank's in advance!
    Caius

    Yes, it is supported. For more info see [Installing Communications Suite on Solaris Zones|http://wikis.sun.com/display/CommSuite7/Installing+Communications+Suite+on+Solaris+Zones].

  • Assign a message store partition using delegated administrator

    Hi!
    i'm using messaging server and delegated administrator that comes in the JES Q5 2005 i'd like to assing the message store partition to the user when i create their account but i can't see any option to do that using delegated administration console. Is there a way to do that.?
    In older delegated administrator versions i could do that.
    Thanks in advance

    It does appear that the current DA does not have this capability. There is a RFE for it in place.
    At present, the only options you have are to:
    1. Use comm-admin to change the partition
    or
    2. Use ldapmodify or Console to make the change in Directory.

  • Best Practice - Message Store size

    Is there a recommended max size for the message store?
    iplanet 5.2

    The offical recommendatin is mostly, "that depends" . . .
    If you intend to do backups, then store partition size depends on backup parallelism and how long you will tolerate backups running.
    If you're talking about maximum size of the store itself, there's no hard limit, only performance limits.
    We have seen large systems, with up to 500,000 users on single boxes, with many hundreds of gigs of store, split up into 40 or 50 partitions work very successfully. On large boxes.
    Better to give us some idea of your needs, and perhaps we can offer advice.

  • Mailbox restore - MapiExceptionNotFound: Unable to open message store. (hr=0x8004010f, ec=-2147221233)

    Hi All,
    Help please!
    I have an Exch 2010 SP2.
    I restored "application" from Windows backup -> successful. And I created recovery database (RecoveryDB), and mounted -> successfull.
    I could not restore mailbox from RecoveryDB.
    I want to restore "kmc250sza" mailbox from RecoveryDB, but I have an error:
    Couldn't connect to the source mailbox.
    + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxRestoreRequest], RemotePermanentException
    + FullyQualifiedErrorId : F6FB8A18,Microsoft.Exchange.Management.RecipientTasks.NewMailboxRestoreRequest
    The command:
    New-MailboxRestoreRequest -SourceStoreMailbox fbc2acd5-31b8-48e9-88f4-564ea2cb81ca -SourceDatab
    ase "RecoveryDB" -targetmailbox admincspeto -AllowLegacyDNMismatch -verbose
    Detail log with verbose switch:
    VERBOSE: [07:24:41.926 GMT] New-MailboxRestoreRequest : Active Directory session settings for
    'New-MailboxRestoreRequest' are: View Entire Forest: 'False', Default Scope: 'bxxut.hu', Configuration Domain
    Controller: 'bxxdc2.bxxut.hu', Preferred Global Catalog: 'bxxdc2.bxxut.hu', Preferred Domain Controllers: '{
    bxxdc2.bxxut.hu }'
    VERBOSE: [07:24:41.942 GMT] New-MailboxRestoreRequest : Runspace context: Executing user:
    bxxut.hu/bxx_Admin_Users/Administrators/PCs administrator, Executing user organization: , Current
    organization: , RBAC-enabled: Enabled.
    VERBOSE: [07:24:41.942 GMT] New-MailboxRestoreRequest : Beginning processing &
    VERBOSE: [07:24:41.942 GMT] New-MailboxRestoreRequest : Instantiating handler with index 0 for cmdlet extension agent
    "Admin Audit Log Agent".
    VERBOSE: [07:24:41.958 GMT] New-MailboxRestoreRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient
    Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient
    Scope(s): {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [07:24:41.958 GMT] New-MailboxRestoreRequest : Searching objects "admincspeto" of type "ADUser" under the root
     "$null".
    VERBOSE: [07:24:41.989 GMT] New-MailboxRestoreRequest : Previous operation run on domain controller
    'bxxdc2.bxxut.hu'.
    VERBOSE: [07:24:41.989 GMT] New-MailboxRestoreRequest : Searching objects "RecoveryDB" of type "MailboxDatabase" under
    the root "$null".
    VERBOSE: [07:24:41.989 GMT] New-MailboxRestoreRequest : Previous operation run on domain controller
    'bxxdc2.bxxut.hu'.
    VERBOSE: [07:24:42.020 GMT] New-MailboxRestoreRequest : Searching objects "fbc2acd5-31b8-48e9-88f4-564ea2cb81ca" of
    type "MailboxStatistics" under the root "RecoveryDB".
    VERBOSE: [07:24:42.020 GMT] New-MailboxRestoreRequest : Previous operation that ran on: 'srv-xch.bxxut.hu'.
    VERBOSE: [07:24:42.020 GMT] New-MailboxRestoreRequest : Searching objects "DB1" of type "MailboxDatabase" under the
    root "$null".
    VERBOSE: [07:24:42.036 GMT] New-MailboxRestoreRequest : Previous operation run on domain controller
    'bxxdc2.bxxut.hu'.
    VERBOSE: [07:24:42.083 GMT] New-MailboxRestoreRequest : [DEBUG] MDB 0bd9ecdf-f085-441a-8738-20a5f587acea found to
    belong to Site: bxxut.hu/Configuration/Sites/Kozpont
    VERBOSE: [07:24:42.098 GMT] New-MailboxRestoreRequest : [DEBUG] MRSClient: attempting to connect to
    'SRV-XCH.bxxut.hu'
    VERBOSE: [07:24:43.380 GMT] New-MailboxRestoreRequest : [DEBUG] MRSClient: connected to 'SRV-XCH.bxxut.hu', version
    14.2.341.0 caps:07
    VERBOSE: [07:24:43.380 GMT] New-MailboxRestoreRequest : Processing object "RequestGuid
    (e6b67a4c-3aa9-4ca6-970c-525967a7c677), RequestQueue: (0bd9ecdf-f085-441a-8738-20a5f587acea)".
    VERBOSE: [07:24:43.567 GMT] New-MailboxRestoreRequest : Couldn't connect to the source mailbox. -->
    MapiExceptionNotFound: Unable to open message store. (hr=0x8004010f, ec=-2147221233)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=132]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=472][latency=15]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x8004010F
        Lid: 26937
        Lid: 21921   StoreEc: 0x8004010F
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 1238    Remote Context Overflow
        Lid: 22957   Error: 0x0
        Lid: 19693   Error: 0x0
        Lid: 17917   Error: 0x0
        Lid: 16893   Error: 0x0
        Lid: 28877   Error: 0x0
        Lid: 14312   StoreEc: 0x8004010F
        Lid: 25516   StoreEc: 0x8004010F
        Lid: 25805   Error: 0x0
        Lid: 8936    StoreEc: 0x8004010F
        Lid: 28877   Error: 0x0
        Lid: 14312   StoreEc: 0x8004010F
        Lid: 25516   StoreEc: 0x8004010F
        Lid: 21970   StoreEc: 0x8004010F PropTag: 0x680C0040
        Lid: 44743
        Lid: 2055    StoreEc: 0x80070005
        Lid: 25805   Error: 0x0
        Lid: 8936    StoreEc: 0x8004010F
        Lid: 28877   Error: 0x0
        Lid: 14312   StoreEc: 0x8004010F
        Lid: 25516   StoreEc: 0x8004010F
        Lid: 25805   Error: 0x0
        Lid: 8936    StoreEc: 0x8004010F
        Lid: 8936    StoreEc: 0x8004010F
        Lid: 41823
        Lid: 25805   Error: 0x0
        Lid: 8936    StoreEc: 0x8004010F
        Lid: 8936    StoreEc: 0x8004010F
        Lid: 48223   StoreEc: 0x8004010F
        Lid: 17097   StoreEc: 0x8004010F
        Lid: 8620    StoreEc: 0x8004010F
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849
        Lid: 21817   ROP Failure: 0x8004010F
        Lid: 26297
        Lid: 16585   StoreEc: 0x8004010F
        Lid: 32441
        Lid: 1706    StoreEc: 0x8004010F
        Lid: 24761
        Lid: 20665   StoreEc: 0x8004010F
        Lid: 25785
        Lid: 29881   StoreEc: 0x8004010F
    VERBOSE: [07:24:43.567 GMT] New-MailboxRestoreRequest : Admin Audit Log: Entered Handler:OnComplete.
    Couldn't connect to the source mailbox.
    + CategoryInfo          : NotSpecified: (0:Int32) [New-MailboxRestoreRequest], RemotePermanentException
    + FullyQualifiedErrorId : F6FB8A18,Microsoft.Exchange.Management.RecipientTasks.NewMailboxRestoreRequest
    VERBOSE: [07:24:43.583 GMT] New-MailboxRestoreRequest : Ending processing &
    The "kmc250sza" mailbox in the RecoveryDB:
    Get-MailboxStatistics -database RecoveryDB | ?{$_.displayname -eq "kmc250sza"} | fl *
    PSComputerName          : srv-xch.bxxut.hu
    RunspaceId              : 752e23df-4e42-43f1-82c9-ec018ca796b3
    AssociatedItemCount     : 5
    DeletedItemCount        : 0
    DisconnectDate          :
    DisconnectReason        :
    DisplayName             : kmc250sza
    ItemCount               : 133
    LastLoggedOnUserAccount : BXXUT\kmc250sza
    LastLogoffTime          : 2013.03.11. 13:50:28
    LastLogonTime           : 2013.03.11. 13:25:26
    LegacyDN                : /O=FIRST ORGANIZATION/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=KMC250SZA
    MailboxGuid             : fbc2acd5-31b8-48e9-88f4-564ea2cb81ca
    ObjectClass             : Mailbox
    StorageLimitStatus      : BelowLimit
    TotalDeletedItemSize    : 0 B (0 bytes)
    TotalItemSize           : 164.6 KB (168,588 bytes)
    MailboxTableIdentifier  : 2A0F-1673D
    Database                : RecoveryDB
    ServerName              : SRV-XCH
    DatabaseName            : RecoveryDB
    MoveHistory             :
    IsQuarantined           : False
    IsArchiveMailbox        : False
    Identity                : fbc2acd5-31b8-48e9-88f4-564ea2cb81ca
    MapiIdentity            : fbc2acd5-31b8-48e9-88f4-564ea2cb81ca
    OriginatingServer       : srv-xch.BXXut.hu
    IsValid                 : True
    The Restore-Mailbox command also come with error.
    Many thanks,
    Csabi

    Hi
    Yes:
    Get-MailboxStatistics -database RecoveryDB
    | ?{$_.displayname -eq "kmc250sza"} | fl *
    PSComputerName          : srv-xch.bxxut.hu
    RunspaceId              : 752e23df-4e42-43f1-82c9-ec018ca796b3
    AssociatedItemCount     : 5
    DeletedItemCount        : 0
    DisconnectDate          :
    DisconnectReason        :
    DisplayName             : kmc250sza
    ItemCount               : 133
    LastLoggedOnUserAccount : BXXUT\kmc250sza
    LastLogoffTime          : 2013.03.11. 13:50:28
    LastLogonTime           : 2013.03.11. 13:25:26
    LegacyDN                : /O=FIRST ORGANIZATION/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=KMC250SZA
    MailboxGuid             : fbc2acd5-31b8-48e9-88f4-564ea2cb81ca
    ObjectClass             : Mailbox
    StorageLimitStatus      : BelowLimit
    TotalDeletedItemSize    : 0 B (0 bytes)
    TotalItemSize           : 164.6 KB (168,588 bytes)
    MailboxTableIdentifier  : 2A0F-1673D
    Database                : RecoveryDB
    ServerName              : SRV-XCH
    DatabaseName            : RecoveryDB
    MoveHistory             :
    IsQuarantined           : False
    IsArchiveMailbox        : False
    Identity                : fbc2acd5-31b8-48e9-88f4-564ea2cb81ca
    MapiIdentity            : fbc2acd5-31b8-48e9-88f4-564ea2cb81ca
    OriginatingServer       : srv-xch.BXXut.hu
    IsValid                 : True

  • Can't Move Mailbox Exchange 2010: MapiExceptionMailboxSoftDeleted: Unable to open message store

    Hi All,
    I've this issues and I'll be gland if some one can assist me to fix it:
    I can't move mailbox form one DB1 to DB2, When I run the Move request on EMC i got this error:Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:03
    Allan Past
    Failed
    Error:
    MapiExceptionMailboxSoftDeleted: Unable to open message store. (hr=0x80004005, ec=2635)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=205]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=264][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0xA4B     
        Lid: 26937  
        Lid: 21921   StoreEc: 0xA4B     
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 22787   Error: 0x0
        Lid: 13032   StoreEc: 0x8004010F
        Lid: 25848  
        Lid: 7588    StoreEc: 0x8004010F
        Lid: 25840  
        Lid: 6564    StoreEc: 0x8004010F
        Lid: 50999  
        Lid: 2567    StoreEc: 0xA4B     
        Lid: 19452  
        Lid: 2199    StoreEc: 0xA4B     
        Lid: 56415  
        Lid: 48223   StoreEc: 0xA4B     
        Lid: 17097   StoreEc: 0xA4B     
        Lid: 8620    StoreEc: 0xA4B     
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0xA4B     
        Lid: 26297  
        Lid: 16585   StoreEc: 0xA4B     
        Lid: 32441  
        Lid: 1706    StoreEc: 0xA4B     
        Lid: 24761  
        Lid: 20665   StoreEc: 0xA4B     
        Lid: 25785  
        Lid: 29881   StoreEc: 0xA4B     
    Exchange Management Shell command attempted:
    'domain.com/Sites/Neles/Allan Past' | New-MoveRequest -TargetDatabase 'Mailbox DB2'
    Elapsed Time: 00:00:02
    Francis B.

    Hi
    How about run the New-MailboxRepairRequest to Test
    http://technet.microsoft.com/en-us/library/ff625226.aspx
    Cheers
    Zi Feng
    TechNet Community Support

  • Measure daily message store usage in Unity 7.0

    Does anyone know a way to measure the daily message voulme in minutes or daily message store storage usage?

    If you're looking for a Unity tool, then the best one I can think of is Message Store Manager.  You can find it here:
    http://www.ciscounitytools.com/Applications/Unity/MSM/MSM.html
    The help file will detail the info you can get from the tool such as the Subscriber Message Store Status Dump which  generates a CSV file with data about each included subscriber’s mailbox.  This data is extensive and detailed and is intended for analysis using a  tool like Microsoft Excel or a database management tool.
    Outside of that, you'd have to look into some Exchange-based tools which in a Unified Messaging setup probably won't be the most accurate (MSM may even be skewed a bit).
    In general, if you use G.711 then a 1 minute message = 480k.  The industry average for a message is typically said to be 30 to 90 seconds so most folks go with the easy 1 minute rule if they are trying to determine the impact on the message store prior to deployment.  The other thing to consider that is not as easy to determine is the impact on Exchange transaction logs (i.e., message drop, message delete, etc - these types of transactions that can happens 100's or even 1000's of times a day depending on the size of deployment).
    Hailey
    Please rate helpful posts!

  • Message store migration question

    Howdy. We are currently testing migration methods between a currently running 5.2 Messaging Server (iPlanet Messaging Server 5.2 HotFix 2.18) to a newly installed 6.3 Messaging Server (Sun Java(tm) System Messaging Server 6.3-0.15).
    We are not running a front end Message Multiplexer so we will suffer some downtime when switching from the old hardware to the new hardware.
    In order to minimize the downtime, we thought that the quickest approach would be to rsync the 5.2 message store onto the 6.3 machine. Due to the fact that the old machine has 8 message store partitions and the new machine has 20 message store partitions, we are doing rsyncs at the user level of the message store (i.e. users end up in different partitions on the new server). Because of this, we cannot migrate the message store databases.
    It appears to us that the message store itself is capable of holding all necessary flags/states/etc. and that we only need to reconstruct on the new system. However, it also appears that stored is "lazy" about updating new data in the databases out to the "store.sub,store.usr,etc." files. When we do our final shutdown of the 5.2 system, we would obviously want the store.* files updated so as to be consistent with the data in the message store databases so that our final rync copies complete consistent data.
    We are at a loss as to how to cause stored to flush/backup/whatever its database information out to the store.* files.
    Is there some way to do this or is our whole migration strategy bogus?
    Vern Gerein
    Senior Systems Administrator
    Server & Database Services
    University of Saskatchewan
    Great White North

    trepan wrote:
    If you are migrating I would highly recommend that the newly installed machine be at the latest patch release. 120228-28 is available on sunsolve.We were waiting for the latest from sun support but they didn't toss it our direction yet. I'll get a co-worker that has an account to grab it from sunsolve.You should be able to access it using the same login as you are using to post to this forum. It is a publicly available patch.
    How large a move are we talking here (size/messages/users)? Also are you using messaging express or just IMAP/POP access?1.4 TB / 35 Million messages / 85,000 users. We are using messaging express and IMAP/POP on the old hardware. We will only be using IMAP/POP on the new hardware (no messaging express).
    Expect to see an increase in overall disk usage due to single-message-copy links being expanded with the increased number of partitions.Our first test rsync from a live system went from 1.4 TB on the old system to 1.6 TB on the new. It is no worse than we expected. I was assuming we'd get a bit of that back if we ran a relink step after the migration.Correct -- the relinker will help to recover some space.
    If I was in your position (and I used to be), I would be looking to add an MMP into the equation so that you could perform user-by-user migrations. This would > allow slower/online migrations which will reduce risk of something going wrong in the move. You can gradually increase the load on the MS6.3 system.We love the idea of being able to do a slower/online migration as you suggest. We had thought about this already be we foresaw one problem with this approach:
    Our current email machine (mail.usask.ca) is used by a LOT of clients so we cannot just deploy a new MMP front end and then ask our client base to now point to that. The only way for us to deploy a MMP front end would be to have it named mail.usask.ca and to change the name of the current 5.2 box to something else. Actually there is another approach that you may not have considered.
    1. Install a 5.2 MMP on the current email machine and reconfigure the existing server to listen on another port for IMAP/POP e.g. 1143 for IMAP and thenn specify the backend port with the MMP so mail.usask.ca:143 (MMP) goes to mail.usask.ca:1143 (backend) for example.
    2. Install and configure new system with a different hostname e.g. mail-server1.usask.ca and configure to listen on the same ports as used in (1)
    3. To migrate the accounts, use the MoveUser utility, this will change the mailhost so email will be redirected and client connections will go mail.usask.ca:143 -> mail-server1.usask.ca:1143
    4. Once all users are migrated, assign the IP for mail.usask.ca to a new MMP frontend server running MS6.3 MMP and MS6.3 MTA.
    NOTE: Step (3) WILL break Messenger Express access but as you said there was no plans on providing ME access on the MS6.3 server this shouldn't be an issue.
    Alas, I don't know of any way to quickly rename an existing Messaging Server (the host name etc. is embedded everywhere, LDAP, configuration files, etc.). The only way I can think of is to reinstall the software. And even if one managed to rename the box, what would it then do with messages that are still in the queues? Of course, I could be missing something simple/obvious.It is possible to do this and requires a lot of planning and testing. Basically the idea is to configure messaging server to recognise itself as two names (mail.usask.ca and mail-server1.usask.ca) and then slowly change the various settings (e.g. users mailhosts: value) from the old hostname to the new hostname. Eventually you work through all the settings till only the clients themselves are actively using mail.usask.ca at which point you assign the IP to a new MMP. If there is a problem you assign the IP back, fix the issue then try again.
    When migrating from Netscape 4.15 to iMS5.2 I had the exact same issue but it was further complicated due to the use of Messenger Express. Since you are not planning on using this going forth this makes things much easier.
    Is there a easy/quick/utterly-and-completely-safe way to rename an existing production 5.2 Messaging Server?Easy, no. Quick, no. Utterly-and-completely-safe, no. But with time, planning and testing it can be achieved.
    Or am I thinking about this in a completely wrong way?There are two approaches mentioned above. I suggest you think which one is going to work for you. In my case I was told in no uncertain terms, the 'migration' must be flawless (i.e. completely transparent to the end-user). It was -- from planning/(re)testing/debugging/customisation/integration to completion took me 12 months (albeit elapsed not effort time).
    Regards,
    Shane.

  • How to restart clustered message store

    Hello all,
    I'm sure this is a newbie question, but what is the recommended procedure for making configuration changes to a clustered deployment of message store?
    I've inherited admin duties for two servers running iMS 6.2. Each server is assigned a portion of the user population with fail-over to the other server. I have some experience with iMS but not with cluster.
    If I wanted to make a configuration change (e.g. change the http port), I would normally use the configutil command, then stop and restart iMS to activate the changes.
    But what is the proper way to do this when you have multiple servers in a cluster?
    Thank you,
    BJ

    Messaging 6 is FAR better to work with in Cluster than 5.x was. In cluster, to do what you need:
    run configutil to make the change.
    stop-msg http
    start-msg http
    done.
    yes, even in cluster, this is all you have to do. the start/stop script actually works with the Watcher process, and it's watcher that tells cluste when failover is needed. Since Watcher is doing the stop/start stuff, it knows it means to do that, and doesn't bother the Cluster with it.

  • Connector error message stores

    I recently upgraded computers and now have Outlook 2010 and Windows 7. Haven't been able to sync Curve to Outlook since. Getting message "Microsoft Outlook Connector Error" as title and then "No Available Message Stores". Any ideas on how to solve this? Thanks much!

    Hi and Welcome to the Forums!
    Here is a KB that discusses that error:
    KB15564"No available message stores" appears when configuring synchronization settings in BlackBerry Desktop Software
    Hopefully it contains something useful!
    Good luck and let us know!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • After adding a new message store partition

    First , our version is:
    Sun Java(tm) System Messaging Server 6.3-6.03
    (built Mar 14 2008; 32bit)
    libimta.so 6.3-6.03 (built 17:12:37, Mar 14 2008; 32bit)
    I have a question about the behaviour of users whose
    mailbox are in a newly created message store partition
    , which I call its nickname as mailvol2
    These were what I did:
    I created the new partition using the command
    configutil -o store.partition.mailvol2.path -v /newdisk/par
    (then restarted the JSMS)
    I tried to test it first on an existing user
    (whose mails are still in the default primary partition)
    and I added the "mailMessageStore" attribute to
    his Ldap entry, with the value mailvol2
    Now I tried sending him new mails.
    The mail could be read. But it seems that they
    went to the primary mailstore partition as I
    could not see any subdirectories under the path
    /newdisk/par
    (I expected there is a subdirectory called
    ==user under there)
    Is this normal ? In other words, only newly created
    users (with the mailMessageStore= mailvol2 attribute)
    will have their mails under there.
    For the old user, I must use the
    mboxutil -r ..........
    command to move his old mailbox first in order for his
    new mails being housed in the new partition ?

    mboxutil -r should change the mailMessageStore attribute on the user.
    It is important that the mailMessageStore attribute on the user be correct. This is not for the normal functioning of access to the folder on a day-to-day basis, but for recovery purposes.
    For normal functioning, access to the folder occurs via the folder DB. The folder DB record includes the name of the partition on which the folder resides and the file system path to the folder.
    But if folder DB information has been lost, the store access code looks for the folder on the partition specified by the user's mailMessageStore attribute. If it exists, the folder is added to the folder DB. This allows the store to recover dynamically. If the user does not have a mailMessageStore attribute, then the default partition is assumed. The reconstruct -m command will search all the partitions and work this out, but the dynamic recovery requires the mailMessageStore attribute to be correct and assumes the user is on the default partition if the does not have a mailMessageStore attribute.
    This is mentioned in [To Change the Default Message Store Partition|http://wikis.sun.com/display/CommSuite/Managing+Message+Store+Partitions+and+Adding+Storage#ManagingMessageStorePartitionsandAddingStorage-ToChangetheDefaultMessageStorePartition] in the Admin Guide.

Maybe you are looking for