SyncML-Nokia reports error 0xD0 ( internal server error )...help required

[sripathitk]

Hello group,

I am trying to develop a SyncML client that interoperates with Nokia 6680. My client is based on OBEX over Bluetooth.

I am able to make an OBEX connection to the SyncML service. But when I send my initialization package via a PUT request it reports the error 0xD0 or internal server error. I hv tried all possible combination to send the PUT requests. But it reports the same error everytime. I even tried sending the same request as that of Nokia itself which I had captured using a logger. This too did not help.

I hv not been able to proceed a step further than this. Shall appreciate a great deal if anyone cud shed some light on this.

Thanks in advance,

Sripathi

[wingslee]

I just meet the same difficult problem.

[traud]

http://www.traud.de/gsm/SyncML.htm

[wingslee]

http://www.traud.de/gsm/SyncML.htm

Hi, traud
I had visited your site, but....I am still puzzled....can you explain a little?

[traud]

You have to tell us which service (UUID) you connect to, what data you send (WBXML) and how your OBEX packet flow looks-a-like.

[wingslee]

Thanks for your reply.

Now I am trying to send a OBEX PUT request to the Nokia 7610. Of course the fields is as following:
OpCode - 0x82
Packet Length
Connection ID
Type
Packet Length
End of Body

and I got the response code 0xD0(Internal Server Error).

Then I found your suggestion in this post:
http://discussion.forum.nokia.com/fo...ad.php?t=44303
I send the PUT request as you said:
OpCode - 0x02
Packet Length
Connection ID
Type
Packet Length

and I got the response code 0x90(Continue),and then I send
OpCode - 0x82
End of Body

Still got the 0xD0, I gonna be crazy...

Could you point me in the right direction about this

Thanks a lot.

Victor.

[traud]

Ahh, I understand, you should know, an OBEX error in SyncML (real) world does not mean you have an error on the OBEX layer. Often it is one in the WBXML, SyncML or even the OMA DS layer.

So, we need at least your WBXML and please provide your raw OBEX. Your information is near to NULL. Now, I still do not know, if your OBEX is correct either. Do not be so shy and hide your data, we want to help but need all the input you have.

[wingslee]

Thanks a lot. I checked my wbxml and found the error. Now the PUT request got the success response.

Now goes to the GET reponse with package #1, I send connection ID and type header, got the code 0xC3(Forbidden - operation is understood but refused).

I am confused by the Opcode for GET(0x03 or 0x83), The client prompts "system error". I have already set the local maximum packet size to 0x2000, so I used 0x83. Is that right?

Below is my Server Alert code

<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<!DOCTYPE SyncML PUBLIC
			'-//OMA//DTD SYNCML 1.1//EN'
			'http://www.openmobilealliance.org/DTD/OMA-SyncML-RepPro-DTD-V1_1_2-20030505-D.dtd'
>
<!--
	see SyncML Sync Protocol, version 1.1.2; chapter 13.1 Sync Alert
-->
<SyncML xmlns='SYNCML:SYNCML1.1'>
	<SyncHdr>
		<VerDTD>1.1</VerDTD>
		<VerProto>SyncML/1.1</VerProto>
		<SessionID>1</SessionID>
		<MsgID>1</MsgID>
		<Target>
			<LocURI>IMEI:</LocURI>
		</Target>
		<Source>
			<LocURI>PC Suite</LocURI>
		</Source>
	</SyncHdr>
	<SyncBody>
		<Alert>
			<CmdID>1</CmdID>
			<Data>206</Data>
			<Item>
				<Source>
					<LocURI>Contacts</LocURI>
				</Source>
				<Meta>
					<Type xmlns='syncml:metinf'>text/x-vcard</Type>
				</Meta>
			</Item>
		</Alert>
		<Final/>
	</SyncBody>
</SyncML>

I do appreciate your help regarding this.

[traud]

Now, you have an OBEX error. Please read the OBEX specification again or have a look at the very good examples in the SyncML OBEX binding document. Your code should adapt to the maximum OBEX size automatically, furthermore, after looking at these specifications and their examples, the use of the final bit in GET should be clear: You send 0x83 all the time, because it is your final command.

[wingslee]

The OBEX connection has been established successfully, and also the PUT request got the SUCCESS response, so I wonder if I've missed something in the XML or my wbxml parser has errors. I send wbxml with hexadecimal format.

0x03, 0x9F, 0x53, 0x6A, 0x00, 0x6D, 0x6C, 0x71, 0x03, 0x31, 0x2E, 0x31, 0x00, 0x01, 0x72, 0x03, 
0x53, 0x79, 0x6E, 0x63, 0x4D, 0x4C, 0x2F, 0x31, 0x2E, 0x31, 0x00, 0x01, 0x65, 0x03, 0x31, 0x00,
0x01, 0x5B, 0x03, 0x31, 0x00, 0x01, 0x6E, 0x57, 0x03, 0x49, 0x4D, 0x45, 0x49, 0x3A, 0x33, 0x35,
0x33, 0x33, 0x38, 0x38, 0x30, 0x30, 0x31, 0x31, 0x36, 0x34, 0x33, 0x30, 0x32, 0x00, 0x01, 0x01,
0x67, 0x57, 0x03, 0x50, 0x43, 0x20, 0x53, 0x75, 0x69, 0x74, 0x65, 0x00, 0x01, 0x01, 0x01, 0x6B,
0x46, 0x4B, 0x03, 0x31, 0x00, 0x01, 0x4F, 0x03, 0x32, 0x30, 0x36, 0x00, 0x01, 0x54, 0x67, 0x57,
0x03, 0x43, 0x6F, 0x6E, 0x74, 0x61, 0x63, 0x74, 0x73, 0x00, 0x01, 0x01, 0x5A, 0x00, 0x01, 0x53,
0x03, 0x74, 0x65, 0x78, 0x74, 0x2F, 0x78, 0x2D, 0x76, 0x63, 0x61, 0x72, 0x64, 0x00, 0x01, 0x01,
0x01, 0x01, 0x00, 0x00, 0x12, 0x01, 0x01

Are there anything wrong with my wbxml code?


Thanks.

[traud]

Did you not state, you have problems with GET? That is a pure OBEX problem of yours now. Why do you hide information all the time. When I say, it is OBEX you give me WBXML. I am confused.

Why do you not use my Alert? For example you use WBXML 1.3 which makes trouble with Sony Ericsson requiring WBXML 1.2.

[wingslee]

Yes, so sorry for that. I send the GET request like this:

0x83(Opcode Get Last)
0x00, 0x27(packet length, updated at the final)
0xcb(Opcode Connection Header)
0xC3, 0xF, 0xA5, 0x96(Connection ID I got from the OBEX server)
0x42(Opcode Type Header)
0x00, 0x1F(type length)
application/vnd.syncml+wbxml(Type header for syncml)

then I got the 0xC3 response. the phone prompted "system error".

Regarding the OBEX, the RFCOMM channel which the SyncML service used was connected successfully. So I doubted it's my fault with wbxml.

I also used your alert code, but got the same result.

Hope it's useful. I was stuck with it now..


Thanks.

[traud]

Please re-read the OBEX specification chapter 2.2.3. Where is the NULL? Again, when you would look at the SyncML OBEX binding examples, you can notice this without the OBEX specification.

Nevertheless, the OBEX status returned by the Nokia OBEX server could be better.

[wingslee]

Hi, Traud

I really appreciate your help. I had found the problem because I send the error size of wbxml with PUT request.

Thanks, I learned a lot from your fore post


Victor.