Getting exception in msg splitting

lucaro · April 4, 2013, 8:19am

Hi,

I am trying to split msg mail, getting following error

<!–[if gte mso 9]>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-IN</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:DontVertAlignCellWithSp/>
<w:DontBreakConstrainedForcedTables/>
<w:DontVertAlignInTxbx/>
<w:Word11KerningPairs/>
<w:CachedColBalance/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
<m:mathPr>
<m:mathFont m:val=“Cambria Math”/>
<m:brkBin m:val=“before”/>
<m:brkBinSub m:val="–"/>
<m:smallFrac m:val=“off”/>
<m:dispDef/>
<m:lMargin m:val=“0”/>
<m:rMargin m:val=“0”/>
<m:defJc m:val=“centerGroup”/>
<m:wrapIndent m:val=“1440”/>
<m:intLim m:val=“subSup”/>
<m:naryLim m:val=“undOvr”/>
</m:mathPr></w:WordDocument>
<![endif]–>

java.lang.IllegalArgumentException: length

at com.aspose.email.ms.System.IO.f.a(Unknown Source)

at com.aspose.email.co.a(Unknown Source)

at com.aspose.email.co.(Unknown Source)

at com.aspose.email.MapiMessageReader.(Unknown Source)

at com.aspose.email.MapiMessage.a(Unknown Source)

at com.aspose.email.MapiMessage.fromStream(Unknown Source)

Sorry, due to proprietary reason, can not share the email.

Please let me know, what can cause this error.<!–[if gte mso 10]>

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

<![endif]–>

kashif.iqbal · April 4, 2013, 10:08am

Hi Sachin,

Could you please tell us what you wanted to achieve? Please share complete details of your issue along with some sample input files for further investigation at our end. Specifically, I would request you to please explain how are you trying to split the message.

lucaro · April 4, 2013, 11:48pm

Thanks for your quick reply.

In this call I am getting the above exception
MapiMessage.fromStream(inputStream);

kashif.iqbal · April 5, 2013, 12:20am

Hi Sachin,

Could you please post a sample file here for our reference? As this issue is not reproducible at my end, and seems specific to your input file, we need this file in order to reproduce the issue at our end and assist you further.

lucaro · April 5, 2013, 12:44am

I know that you are not able to produce it.

But, I can’t share the file - it’s confidential.

Please guide me what can be possible cause of problem<span style=“font-size:10.0pt;font-family:“Arial”,“sans-serif”;
mso-ansi-language:EN-US” lang=“EN-US”>
java.lang.IllegalArgumentException: length

at com.aspose.email.ms.System.IO.f.a(Unknown Source)

at com.aspose.email.co.a(Unknown Source)

at com.aspose.email.co.(Unknown Source)

at com.aspose.email.MapiMessageReader.(Unknown Source)

at com.aspose.email.MapiMessage.a(Unknown Source)

at com.aspose.email.MapiMessage.fromStream(Unknown Source)

in "MapiMessage.fromStream(inputStream);" call.

It may be not accurate, but will help in analyzing it better.

kashif.iqbal · April 5, 2013, 2:03am

Hi Sachin,

I am afraid but this seems to be a very general message that is dependent on the stream going to be loaded. As I mentioned earlier, we need some sample file to investigate this issue as this may be an internal parsing error in Aspose API. We appreciate your cooperation in this regard and looking forward to assist you further.

Ravinder61637 · April 12, 2013, 6:46am

Hi Kashif,

The issue is that when we are uploading the msg files they are getting failed with the following error however if we save the file and upload again it works fine.

Could you please share your thoughts on it.

java.lang.IllegalArgumentException: length

at com.aspose.email.ms.System.IO.f.a(Unknown Source)

at com.aspose.email.co.a(Unknown Source)

at com.aspose.email.co.(Unknown Source)

at com.aspose.email.MapiMessageReader.(Unknown Source)

at com.aspose.email.MapiMessage.a(Unknown Source)

at com.aspose.email.MapiMessage.fromStream(Unknown Source)

kashif.iqbal · April 13, 2013, 2:04am

Hi Sachin,

I am afraid to inform that I am unable to proceed without the sample file. Here at Aspose, only authorized users has access to the customer data. You may please change this thread to private and send us the sample mail file as it will help us to assist you as soon as possible.

We are sorry for the inconvenience caused to you.

Ravinder61637 · April 15, 2013, 6:06am

Hi,

We won't be able share the file. Is it possible to increase the logging further so that i can provide us the cause of this issue.

Regards,

Ravinder Kumar

kashif.iqbal · April 15, 2013, 10:43am

Hi Ravinder,

The exception you are mentioning may be a bug at Aspose.Email end and development team needs such sample file in order to test it in debug mode and rectify the issue in the API. In such a situation, I am afraid it’s not possible to identify the issue as there had been a number of same exception reported by other customers in past but each one had a different reason, and were fixed then.

We understand your concerns that the data file is confidential, and we do respect our customer’s privacy by using the test input file only for reproducing the issue. Therefore, in order to save your time so that the issue may be considered for possible rectification in the upcoming release, I would suggest you to provide us with the sample input file for our analysis, and appreciate your understanding in this regard. You can mark this thread as Private before uploading your file here.