Forum Discussion

Krister's avatar
Krister
Level 5
16 years ago
Solved

Unspecified error

Hi!

I´m running a rather large pst migaration issue and now and then I get the "Unspecified error" when trying to migrate the pst file.

I has been in contact with the Support and recived  a bunch of suggestion how to solve this. Sometime it works and sometime it doesent.

I wounder if someone has figured out a "best practice" how to handle or solve this?

/Krister
Enterprise Vault
Information Governance
Tip-How to
  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    16 years ago
    Yes and Yes.  You see it's the binaries we've changed on the server .. in the end all migrations go through the same binaries on the server.

    However, just skipping over corrupt items isn't really the end of it.  You should still investigate what's wrong with the particular messages.  If they are corrupt, there is little we can do about it, but if there a simple thing wrong with it, then we should handle that.    Here's a fake example or two :-

    Example 1
    The mail we are trying to migrate has an attachment, but opening the attachment crashes Outlook. 
    We can't do anything about that, and probably shouldn't!

    Example 2
    The mail we are trying to migrate has japanese characters in the subject.  Migration stops on this message.
    We should be able to handle that.  (And this is just an example, we do actually handle japanese characters in the subject of mails!)


13 Replies

  • Wayne_Humphrey's avatar
    Wayne_Humphrey
    Level 6
    16 years ago
    Hmmm,

    Add some more relent information.

    Where the logs?
    What have support done?
    What have support suggested?

    --wayne
  • Krister's avatar
    Krister
    Level 5
    16 years ago
    The support has looked into my logs, Dtrace, event and so on and came up with this tip/solution.
    It has worked on some and some not.


    1. Review technote http://support.veritas.com/docs/287829
    2. Run scanpst.exe on the affected PST file
    3. Ensure that the PST file is NOT being accessed at the time the migration is running
    4. Create a NEW PST file in Unicode format and export all items from Old PST to New PST and then run migration on newly created PST
  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    16 years ago
     What version of EV (and service pack) is this?

    Are you actually getting this error, or something else :

    Event Type: Error 
    Event Source: Enterprise Vault 
    Event Category: Migrator Server 
    Event ID: 6988 
    Date: 2/28/2007 
    Time: 5:28:11 PM 
    User: N/A 
    Computer: <EV server name>
    Description: 
    A PST failed to migrate because it is too full to process.  Split the PST and attempt to migrate in two parts

    Can you share your trace?
     
  • Krister's avatar
    Krister
    Level 5
    16 years ago

    The trace log was aprox 300Mb i think so it seems a little to big to attach.

    OS: W2008
    EV: 8 sp1
    Outlook 2003

    its a server driven migration

    This is a clip from the eventlog:

    namnlös1.JPG

  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    16 years ago
    Okay that helps ( a bit )...  It's right in the area of the code where we are changing the messages in the PST .. adding our attributes, like message class, archived date and the like.

    Can you look through the dtrace, and grab the 40-50 lines either side of the function called : 

    CMigrator::SetCustomMessageProps

    We should see an error being thrown with SCMP/SC in it, but also importanly we'll see a hex code which might tell us more about it.

    Can you also elaborate some more on :-

    * Type of PST Migration you're doing ... client side, server side etc.
    * For a PST that fails, if you copy it to a safe place, and try to import it through the Import functionality in the VAC, does it work?
    * What version (and service pack) of Outlook is installed on the EV server?

  • Krister's avatar
    Krister
    Level 5
    16 years ago
    Hi again!

    Couldent find the dtrace log for this file, maybe the support deleted it when they was done. Anyhow, I have another pst file with the same problem with a much smaller log fil, approx 5Mb. I try to attach that to the original post. There was more fileds with CMigrator::SetCustomMessageProps in the log file.

    The migration is server driven.
    Outlook on the EV server is OL2003 sp3 and also the client if it mather in this case...
    Have tried to do a manual import from the VAC but doesnt work.


    namnlös2.JPG
  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    16 years ago
    What version of Outlook is installed on the EV server?  And Service Pack, and hotfixes?

    From the trace it looks like you're getting some MAPI errors back when we're looking up attributes on messages :

    18727    13:20:23.816     [8080]    (MigratorServer)    <9476>    EV:M    CMAPISaveset::OpenSharedMessageOnIMsg (Exit). hr=<0x8004011b>
    18728    13:20:23.816     [8080]    (MigratorServer)    <9476>    EV:M    CMAPISaveset::OpenSharedMessage (Exit). hr=Success  [0]
    18729    13:20:23.816     [8080]    (MigratorServer)    <9476>    EV:M    CMAPISaveset::get__MAPIOBJECT (Exit). hr=Success  [0]
    18730    13:20:23.816     [8080]    (MigratorServer)    <9476>    EV:M    CMAPISaveset::get_OriginalMessageClass (Exit). hr=Success  [0]
    18731    13:20:23.816     [8080]    (MigratorServer)    <9476>    EV:H    CMAPISaveset2::get_OriginalMessageClass _com_error exception. hr=<0x8004011b>
    18732    13:20:23.816     [8080]    (MigratorServer)    <9476>    EV:M    CMAPISaveset2::get_OriginalMessageClass (Exit). hr=<0x8004011b>

    Also try looking in the PST for a message with a blank subject ...


    856    13:20:12.737     [8080]    (MigratorServer)    <9476>    EV:M    CMigrator::ProcessMessages|Processing messages|Folder: IN 2002
    857    13:20:12.768     [8080]    (MigratorServer)    <9476>    EV:L    CMigrator::ProcessChunkOfMessages (Entry) |
    858    13:20:12.784     [8080]    (MigratorServer)    <9476>    EV:L    CMigrator::CheckJobState (Entry) |
    859    13:20:12.784     [8080]    (MigratorServer)    <9476>    EV:M    CMigrator::CheckJobState (Exit) |
    860    13:20:12.784     [8080]    (MigratorServer)    <9476>    EV:L    CMigrator::isEligibleForArchive (Entry) |
    861    13:20:12.784     [8080]    (MigratorServer)    <9476>    EV:M    CMigrator::isEligibleForArchive (Exit) |
    862    13:20:12.784     [8080]    (MigratorServer)    <9476>    EV:M    CMigrator::ProcessChunkOfMessages|Processing item|Subject:


    The folder is called IN 2002, I think.

    If you can find that particular message, can  you open it?  Does it look okay?  Can you move it to a different folder?  I'm thinking that the message "might" be corrupt in some way.

    PSTs often have "strange" messages in them.  There is a post EV 8 SP 2 hotfix which changes the migrator so that if it encounters PSTs with a problem message, it logs the fact, and moves on to the next item.
  • Krister's avatar
    Krister
    Level 5
    16 years ago
    Hi!

    The Outlook on the EV server is 2003 with SP3 and some uppdates.

    The OS is 2008 SP1 with a number of hotfixes and uppdates.

    We also come to the folder IN 2002 but the user had a couple of thousand mail in that and to ask him to go through all thoose mail wasnt appriciated. The users are satisfied with the pst files and dont se the problems with it like the IT Department does. So there is a problem to make the users go throug ther pst files and look for corrupt messages.

    But what you say is that EV8 SP2 with hotfix could handle this problem and archive all other mail in the pst file except thoose that are corrupted?

    Regards
    Krister
  • Krister's avatar
    Krister
    Level 5
    16 years ago
    The EV8 SP2 with hotfix...

    Do that also solve the problem with migration from the VAC?
  • Rob_Wilcox1's avatar
    Rob_Wilcox1
    Level 6
    16 years ago
    Yes and Yes.  You see it's the binaries we've changed on the server .. in the end all migrations go through the same binaries on the server.

    However, just skipping over corrupt items isn't really the end of it.  You should still investigate what's wrong with the particular messages.  If they are corrupt, there is little we can do about it, but if there a simple thing wrong with it, then we should handle that.    Here's a fake example or two :-

    Example 1
    The mail we are trying to migrate has an attachment, but opening the attachment crashes Outlook. 
    We can't do anything about that, and probably shouldn't!

    Example 2
    The mail we are trying to migrate has japanese characters in the subject.  Migration stops on this message.
    We should be able to handle that.  (And this is just an example, we do actually handle japanese characters in the subject of mails!)