The patch requires the Black Berry Enterprise Server to provide a sequence number.Since the Black Berry Enterprise Server does not use this property, it does not have any data to supply for it and the property is instead set to 0.
The file does not require the use of this sequence number, so the Black Berry Enterprise Server does not normally set it.
Nothing works, what are the specifics on the issues?
All this worked fine when BES was installed on our Exchange server.
This is acceptable to Microsoft Outlook as if there is no sequence number available then it assumes the response is to the most recent instance of the meeting.
The patch mentioned above makes some slight changes to how the sequence number is set.