Problem with socket on N70

Hi all, 

I have a problem with my N70 phone. 

I have developed an application that connects to a server, so it makes login. It
works fine for the 6630 and 6680 devices, but while trying to run it on a N70
phone, the pone gives a panic -14, "object in use". I have the same
problem when I run the sockets example in the sdk, so I am quite puzzled :-(

Any idea?

Thanks in advance,

Marta



-- 
 

Are you getting a KErrInUse (-14) leave or a XXXX-XXXX 14 panic?

If it is a leave you need to locate where and determine when it is 
generated.

The documentation has many panics with id 14 so you need to identify its 
category before going further. Some possible candidates:
	- ESock 14 - Descriptor parameter error
	- User 14 - This panic is raised when expanding or contracting an 
HBufC16 buffer using the ReAlloc() or ReAllocL() descriptor member 
functions. Specifically, the panic occurs if the new length being 
specified is too small to contain the data.
	- E32User-CBase 14 - This panic is raised by the Delete(), Ptr(), 
BackPtr() member functions of a segmented dynamic buffer (a CBufSeg); 
the panic can also be raised by InsertL() and ExpandL(). It is caused 
when the position value passed to these functions is either negative or 
represents a position beyond the end of the current buffer.



Marta wrote:
> Hi all,
>  
> I have a problem with my N70 phone.
>  
> I have developed an application that connects to a server, so it makes 
> login. It works fine for the 6630 and 6680 devices, but while trying to 
> run it on a N70 phone, the pone gives a panic -14, "object in
use". I 
> have the same problem when I run the sockets example in the sdk, so I am 
> quite puzzled :-(
>  
> Any idea?
>  
> Thanks in advance,
>  
> Marta
>  
>  
> 
> -- 

> I have developed an application that connects to a server, so it makes 
> login. It works fine for the 6630 and 6680 devices,
> but while trying to run it on a N70 phone, the pone gives a panic -14, 
> "object in use". I have the same problem when I run
> the sockets example in the sdk, so I am quite puzzled :-(

I presume you're referring to ESock_client category, is this correct?
I've seen these a couple of times, but only in emulator (3rd ed). Upgrading 
the sdk (they were beta releases) solved the problem (Probably not your case 
anyway)
Maybe posting some snippet of the problematic code would help.

Regards,
David.-