[jcifs] How to solve "The parameter is incorrect." Exception

Michael B Allen ioplex at gmail.com
Thu Mar 5 22:35:33 GMT 2009

On Thu, Mar 5, 2009 at 4:50 PM, Marco Nelissen <marco.nelissen at gmail.com> wrote:
> I had the exact same problem when trying to use JCIFS on the Android
> platform. The problem turned out to be that JCIFS uses the
> "UnicodeLittleUnmarked" encoding instead of the more standard "UTF-16LE".
> They're equivalent, but the latter is required for VMs to implement, while
> the former is not.
> Replacing all instances of "UnicodeLittleUnmarked" with "UTF-16LE" made it
> work, but it seems like it would be better for JCIFS to use UTF-16LE
> instead, because then I could just include the official prebuilt jar in my
> app.

There was a time when some VMs did not support "UTF-16LE" and so we
had to use Java's "UnicodeLittleUnmarked". But I think we're probably
beyond that at this point so I think it would be safe to move to
"UTF-16LE". I have added this to the TODO for further investigation.


> On Mon, Mar 2, 2009 at 7:03 PM, JUNJIE HOU <junjie.hou at gmail.com> wrote:
>> Hello there,
>>     I am using jCIFS in embeded platforms. I always got a "The parameter
>> is incorrect." exception (caused by a timeout operation). I am using jcifs
>> 1.3.3.
>>    Can anyone help? Or can I change the timeout value?
>>    Thanks!
>> --
>> Best regards,
>> Junjie Hou

Michael B Allen
Java Active Directory Integration

More information about the jcifs mailing list