Unsolved
This post is more than 5 years old
2 Posts
1
1785
January 27th, 2012 04:00
EMC SourceOne event viewer errors
we are in process of PST migration and we are troubled by the fact that these errors are occuring often in our EMC logs ..
What is the root of the problem here?
why is this happening?
any solutions or updates to fix this problem?
We are using MSExchange only environment.
System call failed. (0x86040100) [ExContainerMigrationJBC, CExContainerMigrationThread.cpp(180).CExContainerMigrationThread::MigrateMessage]
>System call failed. (0x86040100) [ExContainerMigrationJBC, CoExExchProvider.cpp(1277).CoExExchProvider::ShortcutDoc]
>System call failed. (0x86040100) Catastrophic failure (0x8000FFFF) [ExContainerMigrationJBC, CoExExchShortcut.cpp(287).CoExExchMsg::ShortcutMessage]
>Failed to Extract MAPI Properties from MsgId: (0x86040C02) [ExContainerMigrationJBC, CoExExchMsgProps.cpp(551).CoExExchMsg::CacheProps]
>Failed to Extract MAPI Properties from MsgId: (0x86040C02) Not enough storage is available to complete this operation. (0x8007000E) [ExContainerMigrationJBC, CoExExchMsgProps.cpp(551).CoExExchMsg::CacheProps]
Job Id : 10726
Activity Name : PST Migrate 4GB ERROR test MSEXC OK
Activity Id : 387
Activity Type : 20
RKatwal
2 Intern
•
600 Posts
0
January 29th, 2012 17:00
Greetings,
There are few things to watch for:
1. Exchange has hard coded limit of how many objtMsg and objtFolder can be open in one mapi session. SourceOne is multithread application and it had potential to reach that limit sometime quickly. Engineering has done a lot of work to make sure we do not go above the limits(it depends on what version you are running). If the limit is reached you are meant to see failing activities with such errors because Exchange terminated the connection once limit was reached. Sometimes you might have to increase the limit on Exchange side. There are technet articles available to explain you why, how and what impact it will have.
2. You might be picking up some of these error messages from the ExContainerMigrationJBC log file. There is a lot of information in these logs which is for support and engineering team. Unless errors are coming in the EMC event log, many times these errors could be ignored.
3. You might also want to make sure that when you are processing these PST files then no one has these open because a PST can be open by one outlook profile at a time. When SourceOne processes the PST files its mounting the PST into the MAPI profile (temporarily) for processing.
If you continue to see the issue with PST migration, please open support ticket with EMC Support.
Regards,
Rajan
RKatwal
2 Intern
•
600 Posts
0
January 29th, 2012 22:00
Greetings,
I were referring to the verbosity logs instead of event logs. If you see errors in verbose logging but not in event logs those are extra errors that are printed and handles by a process. If there is something of concern that will be logged into event log. As I mentioned earlier verbose logging prints a lot more info which is for support and engineering team for analysis.
I would encourage you to engage support so that they can have a look at the issue when it occurs and collect information needed for them to analyse.
Regards,
Rajan
kocmur
2 Posts
0
January 29th, 2012 22:00
1. i know the objtMsg and objetFolder limits on exchange and we have raised the limits to 1000
2. i am viewing the errors in EMC event log
3.we are extra careful about that..and are moving the PST from employee so he could not use it and closing them in outlook
why do you think the messages in EMC event log could be ignored?