Hi I am a new Desire user. I setup Exchange server sync on my desire with no problem on email. However the calendar syncing doesn't work. It always say "time out ...". I can't sync the calendar at all. Anyone has this problem and a solution?
mine syncs just fine.
i'm guessing that you didn't forget to check the calendar to be synced?
also try to set up a different exchange acc , like gmail and see if you have the same problem...just so you know if it's the phone of server error
mr.vandalay said:
mine syncs just fine.
i'm guessing that you didn't forget to check the calendar to be synced?
also try to set up a different exchange acc , like gmail and see if you have the same problem...just so you know if it's the phone of server error
Click to expand...
Click to collapse
Actually I did check it. The message is "Connection Socket Timeout" under "Sync calendar [X]".
If I can receive email that means I can connect to exchange server with no problem right? Then there should be no other special setting for calendar... strange...
YES, facing the same (exchange 2007 on sbs 2008 with htc desire)
mail & contacts are fine, calendar says "connection timeout".
logging on sbs says:
MS Exchange Active Sync 1008:
---
Ausnahme, die von Exchange ActiveSync behandelt wurde. Diese kann von einer veralteten oder fehlerhaften Exchange ActiveSync-Gerätepartnerschaft verursacht worden sein. Dieser Fall kann eintreten, wenn ein Benutzer versucht, das gleiche Element von mehreren Computern aus zu ändern. Wenn dies der Fall ist, erstellt Exchange ActiveSync die Partnerschaft mit dem Gerät erneut. Die Elemente werden bei der nächsten Synchronisierung aktualisiert.
(in english: exeption, activesync, mobile partnership failed. cause may be a user who tries to fetch the same element from different computers. activeync re-establishes partnerships and syncs the next time).
URL=/Microsoft-Server-ActiveSync/default.eas?Cmd=Sync&User=muser&DeviceId=HTCAnd2cf22b0d&DeviceType=htcbravo
--- Ausnahmebeginn ---
Ausnahmetyp: Microsoft.Exchange.Data.Storage.SyncStateNotFoundException
Ausnahmemeldung: Saving SyncState 37 failed because the file was deleted out from underneath the operation.
Ausnahmeebene: 0
Ausnahmestacktrace: bei Microsoft.Exchange.Data.Storage.SyncState.CreateSyncStateItemInFolder(SyncStateInfo syncStateInfo, Folder syncStateFolder, PropertyDefinition[] properties, Object[] values)
bei Microsoft.Exchange.Data.Storage.SyncState.Commit(PropertyDefinition[] properties, Object[] values, Int32[] sizes)
bei Microsoft.Exchange.AirSync.SyncCommand.SaveSyncStateAndDispose(SyncCollection collection)
bei Microsoft.Exchange.AirSync.SyncCommand.OnExecute()
bei Microsoft.Exchange.AirSync.SyncCommand.Execute()
bei Microsoft.Exchange.AirSync.Command.WorkerThread()
Die innere Ausnahme folgt...
Ausnahmetyp: Microsoft.Exchange.Data.Storage.ObjectNotFoundException
Ausnahmemeldung: Could not get properties.
Ausnahmeebene: 1
Ausnahmestacktrace: bei Microsoft.Exchange.Data.Storage.MapiPropertyBag.GetProperties(IList`1 propertyDefinitions)
bei Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.InternalLoad(PropertyDefinition[] properties, Boolean forceReload)
bei Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag..ctor(StoreSession session, MapiProp mapiProp, Origin origin, PropertyDefinition[] autoloadProperties, Boolean canSaveOrDisposeMapiProp)
bei Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag..ctor(StoreSession session, MapiProp mapiProp, Origin origin, PropertyDefinition[] autoloadProperties)
bei Microsoft.Exchange.Data.Storage.Folder.CreateMessageInternal(StoreSession session, MapiFolder mapiFolder, ItemQueryType type)
bei Microsoft.Exchange.Data.Storage.Folder.CreateMessageInternal(StoreSession session, StoreId folderId, ItemQueryType type)
bei Microsoft.Exchange.Data.Storage.MessageItem.InternalCreate(StoreSession session, StoreId destFolderId, ItemQueryType itemQueryType)
bei Microsoft.Exchange.Data.Storage.SyncState.CreateSyncStateItemInFolder(SyncStateInfo syncStateInfo, Folder syncStateFolder, PropertyDefinition[] properties, Object[] values)
Die innere Ausnahme folgt...
Ausnahmetyp: Microsoft.Mapi.MapiExceptionNotFound
Ausnahmemeldung: MapiExceptionNotFound: Unable to get properties on object. (hr=0x8004010f, ec=-2147221233)
Diagnostic context:
Lid: 18969 EcDoRpcExt2 called [length=474]
Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=156][latency=0]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropOpenFolder [2]
Lid: 17082 ROP Error: 0x8004010F
Lid: 21857
Lid: 21921 StoreEc: 0x8004010F
Lid: 27962 ROP: ropExtendedError [250]
Lid: 1494 ---- Remote Context Beg ----
Lid: 26426 ROP: ropOpenFolder [2]
Lid: 1750 ---- Remote Context End ----
Lid: 27962 ROP: ropCreateMessage [6]
Lid: 17082 ROP Error: 0x4B9
Lid: 24929
Lid: 21921 StoreEc: 0x4B9
Lid: 27962 ROP: ropExtendedError [250]
Lid: 1494 ---- Remote Context Beg ----
Lid: 26426 ROP: ropCreateMessage [6]
Lid: 1750 ---- Remote Context End ----
Lid: 27962 ROP: ropGetPropsSpecific [7]
Lid: 17082 ROP Error: 0x4B9
Lid: 26465
Lid: 21921 StoreEc: 0x4B9
Lid: 27962 ROP: ropExtendedError [250]
Lid: 1494 ---- Remote Context Beg ----
Lid: 26426 ROP: ropGetPropsSpecific [7]
Lid: 1750 ---- Remote Context End ----
Lid: 26849
Lid: 21817 ROP Failure: 0x4B9
Lid: 20385
Lid: 28577 StoreEc: 0x8004010F
Lid: 32001
Lid: 29953 StoreEc: 0x8004010F
Ausnahmeebene: 2
Ausnahmestacktrace: bei Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo)
bei Microsoft.Mapi.MapiProp.GetProps(PropTag[] propTagsRequested)
bei Microsoft.Exchange.Data.Storage.MapiPropertyBag.GetProperties(IList`1 propertyDefinitions)
--- Ausnahmeende ---.
So is this a bug or what? Do I have to wait for Android 2.2 ... ...? Or do I need to purchase touchdown??? *_*
Hi Folks!
Just delete all pairings with all (even old or other [windows phone] devices) in windows mobile device center and/or outlook web access.
Wait until all pairings completed successfully on active devices and create a new sync partnership with the desire.
To get those sync problems gone that should be the most clean way.
Synchronisation at all works in general against Exchange 2007 - do you have all ms server updates applied?
Greetings from Berlin/Germany
Ralf
Hi Ralf, the problem is actually not the sync between Outlook calendar saved on PC and my Desire. It is the sync between Exchange server and my Desire. When you say delete all the pairing you mean the pairing between ActiveSync installed on PC and the mobile phone right? Correct me if I am wrong.
Yes, I have the same problem ("Connection Socket Timeout") with my Desire and Exchange 2003. Email and contacts work like a charm, but not the calendar. However, with Touchdown everything works fine.
*edit*
I followed the instructions in a post by mattrog (search for "Exchange 2010 Sync Calendar Problem (solution!)" and you'll find the post) and it worked.
Yes!! It works!! Thanks NoNick2!
maxermaxer said:
Hi I am a new Desire user. I setup Exchange server sync on my desire with no problem on email. However the calendar syncing doesn't work. It always say "time out ...". I can't sync the calendar at all. Anyone has this problem and a solution?
Click to expand...
Click to collapse
I have errors from time to time but it is only a handful of connections that time out. Most work well.
in my case i had thousands of calender items, i just deleted the old years completely (do i need my calender items from 2001?) - then the desire could sync without problems.
have phun
Another fix
I have found another fix!
I tried backing up and deleting all calendar items from my Exchange 2007 calendar, I also tried deleting the ActiveSync relationships from within OWA. I then tried deleting the account on my phone (a HTC Desire running 2.2) and recreating it, but it kept failing to sync the calendar. I noticed that each time I tried, most (but not all) of the calendar items I had deleted from my calendar in Exchange came back, presumably from the phone! That made me realise that for some reason many of the Exchange calendar items had become local calendar items on the phone, hence they survived me deleting the Exchange account and they were getting synced back to Exchange each time I re-created the account on the phone.
So I then tried:
Settings > Applications > Manage applications > Calendar storage > Clear data
And set up the account again and all was OK
I don't know if deleting everything from the Exchange calendar or deleting and re-creating the account on the phone was required (but they definitely didn't fix it on their own) but I am sure clearing the local phone calendar was the crucial step in my case.
Issue: vbulletin: functional: URL parser malfunction or bad EH: ERR "Invalid File" on setting remote profile/avatar image
Affected:
CLIENT vbulletin (unknown version, year 2011)
with SERVER vBulletin Version 4.1.0 (Deutsch)
with Browser FF 3.6.18 ubuntu on debian stable.
Reproduction: INPUT 'http********/image.php?u=145501', profile.php?do=editprofilepic , 'Option 1'
Methods:
INPUT
CLIENT profile.php?do=updateprofilepic, profile.php?do=updateavatar
SERVER image.php?u=<uid>
OUTPUT:
CLIENT EH: "Invalid File"
SERVER EH: "HTTP/1.1 200 OK"
Pls forward to jelsoft bug tracker, thx.
in CM12.1 for Xiao mi Read Mi 1s, now I have the error as bllow:
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: out/host/linux-x86/obj32/SHARED_LIBRARIES/libjavacore_intermediates/luni/src/main/native/android_system_OsConstants.o: file is empty
libcore/luni/src/main/native/Register.cpp:36: error: undefined reference to 'register_android_system_OsConstants(_JNIEnv*)'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [out/host/linux-x86/obj32/lib/libjavacore.so] Error 1
who can help me?
Recommendation
Hello,
to get an answer you should at least:
Name the thread appropriately
Elaborate when you are getting this error - after which step and procedure
Put code into
Code:
environment
[/LIST]
jiang18109913 said:
in CM12.1 for Xiao mi Read Mi 1s, now I have the error as bllow:
prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.6//x86_64-linux/bin/ld: error: out/host/linux-x86/obj32/SHARED_LIBRARIES/libjavacore_intermediates/luni/src/main/native/android_system_OsConstants.o: file is empty
libcore/luni/src/main/native/Register.cpp:36: error: undefined reference to 'register_android_system_OsConstants(_JNIEnv*)'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [out/host/linux-x86/obj32/lib/libjavacore.so] Error 1
who can help me?
Click to expand...
Click to collapse
I think u might ve installed 64 bit os. I ve no idea. Just tell me when this error occur. Best way try changing ur rom. Thats it. This might be helpful
http://forum.xda-developers.com/redmi-1s/general/guide-unbricking-redmi-1s-bricked-t2905426
Is it resolved ? How ?
Hi,
Everything works fine on my S5, with LOS latest, except I can't send SMS.
I've tried switching to 3G only, and I've called my carrier as well. All settings seem fine.
Here are relevant log entries from logcat:
Code:
I MessagingAppDataModel: ResendMessageAction: Resending message 4; changed timestamp from 1513762391396 to 1513767602957
I MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages
I MessagingAppDataModel: ProcessPendingMessagesAction: Queueing message 4 for sending
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
I MessagingAppDataModel: SendMessageAction: Sending SMS message 4 in conversation 4
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
D MmsService: getAutoPersisting
E MessagingApp: SmsSender: failure in sending message part. requestId=content://sms/4 partId=0 resultCode=1 errorCode=0
E MessagingApp: MmsUtils: SMS permanent failure
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
I MessagingAppDataModel: ProcessSentMessageAction: Done sending SMS message 4 in conversation 4; status is MANUAL_RETRY
I MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages(message failed)
I art : Background partial concurrent mark sweep GC freed 19934(1446KB) AllocSpace objects, 21(1404KB) LOS objects, 40% free, 10MB/17MB, paused 1.800ms total 100.462ms
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
W IInputConnectionWrapper: finishComposingText on inactive InputConnection
I MessagingAppDataModel: SyncMessagesAction: Starting batch for messages from 1513767583980 to 1513767604615 (message update limit = 80, message scan limit = 4000)
I MessagingAppDataModel: SyncMessagesAction: All messages now in sync
I ActivityManager: START u0 {flg=0x4000000 cmp=com.android.messaging/.ui.conversation.ConversationActivity (has extras)} from uid 10072 on display 0
D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
D MessagingApp: DraftMessageData: loading for conversationId=3
D MessagingApp: ReadDraftMessage: created draft. conversationId=3 selfId=1
W ViewPager: Requested offscreen page limit 0 too small; defaulting to 1
W ViewPager: Requested offscreen page limit 0 too small; defaulting to 1
I MessagingAppDataModel: SyncMessagesAction: Starting batch for messages from 1513767604615 to 1513767605988 (message update limit = 80, message scan limit = 4000)
I ActivityManager: Displayed com.android.messaging/.ui.conversation.ConversationActivity: +243ms
D MessagingApp: DraftMessageData: draft loaded. conversationId=3 selfId=1
W SurfaceFlinger: couldn't log to binary event log: overflow.
I MessagingAppDataModel: SyncMessagesAction: All messages now in sync
D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
I MessagingAppDataModel: ResendMessageAction: Resending message 3; changed timestamp from 1513767392994 to 1513767606822
I MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages
I MessagingAppDataModel: ProcessPendingMessagesAction: Queueing message 3 for sending
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
I MessagingAppDataModel: SendMessageAction: Sending SMS message 3 in conversation 3
D MmsService: getAutoPersisting
E MessagingApp: SmsSender: failure in sending message part. requestId=content://sms/3 partId=0 resultCode=1 errorCode=0
E MessagingApp: MmsUtils: SMS permanent failure
I MessagingAppDataModel: ProcessSentMessageAction: Done sending SMS message 3 in conversation 3; status is MANUAL_RETRY
I MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages(message failed)
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
D audio_hw_primary: out_set_parameters: enter: usecase(1: low-latency-playback) kvpairs: routing=2
I MessagingAppDataModel: ResendMessageAction: Resending message 3; changed timestamp from 1513767606822 to 1513767608002
I MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages
I MessagingAppDataModel: ProcessPendingMessagesAction: Queueing message 3 for sending
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
I MessagingAppDataModel: SendMessageAction: Sending SMS message 3 in conversation 3
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
I Icing : IndexChimeraService.getServiceInterface callingPackage=com.google.android.gms componentName=null serviceId=36
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
I Icing : App usage reports: 15
I Icing : Usage reports ok 15, Failed Usage reports 0, indexed 0, rejected 0, imm upload false
D MmsService: getAutoPersisting
E MessagingApp: SmsSender: failure in sending message part. requestId=content://sms/3 partId=0 resultCode=1 errorCode=0
E MessagingApp: MmsUtils: SMS permanent failure
I MessagingAppDataModel: ProcessSentMessageAction: Done sending SMS message 3 in conversation 3; status is MANUAL_RETRY
I MessagingAppDataModel: ProcessPendingMessagesAction: Scheduling pending messages(message failed)
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
E AlarmManagerService: Unable to set alarm to 1513776840.000000000: Invalid argument
I art : Do partial code cache collection, code=95KB, data=125KB
I art : After code cache collection, code=94KB, data=124KB
I art : Increasing code cache capacity to 512KB
I MessagingAppDataModel: SyncMessagesAction: Starting batch for messages from 1513767605988 to 1513767609278 (message update limit = 80, message scan limit = 4000)
I Icing : Indexing AD3C28AE9B24B44E5BC318F612CE23D2357E78E1 from com.google.android.gms
I MessagingAppDataModel: SyncMessagesAction: All messages now in sync
I art : Starting a blocking GC Explicit
Any help highly appreciated.