Develop Bugs

Outlook.exe "sticking" during ActiveSync

I just noticed this problem today - though I think it may have been happening for a few days.
OE & IE have been hanging a lot (most unusal for my PC). So I had a good clearout & spy/adaware/antivirus blitz too - nothing! When I checked my process list I discovered OUTLOOK.EXE running happily away. Initially I thought I had a worm but it looks like it only kicks in when ActiveSync is running and then I have to manually delete the process afterwards.
Around the time this all started I upgraded to the latest ROM etc and setup bluetooth on my PC and PDA. All eventually worked ok - after I removed 17 virtual COM ports from my device manager! I can now sync & surf via bluetooth if I need to - first choice is WIFI though.
Any comments would be appreciated - more concerned that whatever it is, is hanging OE & IE from time to time. If need be I'll remove the bluetooth on my PC and see if that makes any difference.

Have you installed activesync v4?

Hi Swoopster.
No I haven't - read conflicting reports online - admittedly didn't look into it very far but decided to stick with 3.8.0
Do you think I should try ver. 4?
Cheers

I installed one of the original activesync 4 betas and had the odd few issues with that. I found that it partially removed the issues with outlook locking up.
Moving to the released version of activesync 4 and my outlook issues have disappeared. Outlook remains open whenever the xda is syncing (and when i'm using it), otherwise it just closes it down and removes it whenever you remove your xda.
There is a clean way of shutting down a locked office app as well... In 2003 you have the microsoft application recovery tool which will force shut down the apps for you.
Cheers.

Outlook sticking and Activesync
Ihave the same problem with Outlook "sticking" and I have to end task when I want to back up my .pst file.
It happened with Activesync 3.8 and still with 4.0.
I could not downgrade Activesync back to 3.8 (by uninstalling 4.0 and reinstalling 3.8)- may just be me though !!!!

Sync problems - Activesync does not detect device (XDAIIs)

Dear All
Please help: I have an O2 XDA IIs which MS Activesync 4.1 does not detect, despite all my efforts during the last few days (I also have an old iPAQ 1940 which Activesync detects fine).
The XDA is from work, so could it be that it is somehow locked, and if so, how can I unlock it?
Also, as an alternative, can I sync the XDA with my PC via Bluetooth through the iPAQ's?
Any ideas will be gratefully received!
Many thanks in advance,
L

Hi there,
I've Looked through hundreds of forums and although I have seem similiar I haven't found a resolution to my exact problem.
Due to the fact that I've been trying to resolve this issue on and off all day it's probably something really simple... :roll:
HISTORY
PDA
Was running WM2003SE on a Xda IIS.
PC
ActiveSync 3.8 on Laptop with Windows 2000 SP4 and all updates. Laptop on a home LAN with router. No firewall software and have since removed all Spyware removal software, (after doing one last scan).
My Task \ Issue \ Problem
I wanted to to the upgrade to WM2005 and followed all the usual procedures. The one mistake I may have made was to install the very very latest 4.1 Activesync without removing 3.8. However at this stage my XDA was still on 2003SE and synced perfectly with 4.1 Activesync.
I performed the upgrade to WM2005 including patches and as far as the XDA is concerned everything appears to be working.
Activesync however doesn't work. Via the USB cradle Windows 2000 detected a device and under device properties it's was listed as Generic RNDIS, it's now listed as a windows mobile based-device. I don't have an entry in my network connections, although I think this only happens with Windows XP. I've tried uninstalling Activesync, removing the rapi.dll file, reinstalling etc, I even did the former and removed entries within the registry and running a registry fixer but to no avail.
I then decided the Bluetooth route but cannot sync via this method either. I can actually succesfully connect from PC to XDA and vice versa but cannot use these connections for Activesync.
I have another Hard Drive for this Laptop which I use for testing. I can simply shut down, swap drives and boot again to another build. The other build is also Windows 2000 with SP4 and pretty much nothing else. I've installed Activesync 4.1 onto this machine, plugged in the cradle and everything works fine.
So..... I know the XDA is fine, The cradle's okay and Activesync 4.1 actually works with my XDA OS. The problem is it doesn't work on one particular build. I believe this is actually a Activesync issue but due to some form of conflict with my build. It's currently out of the question for me to rebuild so my mission is to find out what's conflicting.
Just to summarise though..... Activesync 4.1 was working fine, I upgraded XDA to WM2003 to WM2005 and then it stopped. The other harddisk proves that Activesync does actually work with my XDA.
Pheeeew...... I hope somebody doesn't suggest lack of information.... :lol: :lol:
So the reason for the post?? Well if anybody else is having frustrations, (which I'm sure I'm not the only one judging my my searching), your not alone.
I think a lot of people's problems have actually been resolved by the latest version of Activesync, (4.1), and other people have resolved by sorting out the main culprit of firewalls.
For me though I'll keep searching..... if any of you can think of any other ideas I can use for diagnosing the problem I'll appreciate it.
Thanks in advance..... sorry for the waffle.....

RESOLVED
Okay.... During further searching I noticed people mentioning VPN clients interfering.
I did have SecureRemote VPN installed which I use for work purposes.
I uninstalled SecureRemote but had to uninstall & re-install Activesync again. This time it's working.....
I will, (but not tonight), re-install the VPN client and see what happens. If Activesync countinues to work then, apart from being happy, it's worth making a note of.
If it doesn't work then I'll start to investigate why...... I know the new active sync does some form of IP connection but I cannot accept that it won't work with VPN's installed.

use windows XP (SP2) ...
first install the activesyn and then restart your computer.
then attach your pocket pc with usb cable.
and try to connect.
its works for me...

Cannot sync via bluetooth (WIDCOMM BT driver)

I tried several times but I cannot sync my new XDA Orbit via Bluetooh. ActiveSync does not find my device although I did it the help-file told (choose the right COM-port). Could the reason be that I am using the WIDCOMM BT driver instead of the pre-installed standard Win XP-driver?

Same problem
Hi all. A have the samу problem with connection activesybc via bluetooth. When a want o connect my device say me that is no partnership to connect. What a reason. No posts about this a find
P.S. Sorry for my bad english

http://www.europe.htc.com/support/faq.html?id=167
awell done. synced

Hi.
May I know where you got your Widcomm BT stack for the Artemis?
Thanks

no. my artemis has a standard build in bluetooth drivers but for the first time i had aproblem whit them

I had this problem trying to sync with my Dell PC using its built in bluetooth hardware and the Widcomm stack. No luck at first, but I solved it by uninstalling the Widcomm stack in device manager, then allowing XP to re-discover the hardware and to install the alternative Microsoft stack. (XP SP2 only).
With XP handling the bluetooth, I had no problem pairing with the Artemis using instructions from here - http://www.geekzone.co.nz/content.asp?contentid=3163 .
Syncing is now straightforward.
F.

Okay, I've scanned the entire website and visited your links, I still cannot set up a bluetooth partnership with my P3300 and my laptop.
I'm using D-link DBT-122.. and it just doesnt connect.
What am I missing?

No one has any ideas?

Had to bump it because its frustrating to not be able to sync via bluetooth.
Anyone wid ANY ideas whatsoever?

I just managed to advance a bit on this path:
Thanx to a Hazymat over on xda-dev I managed to get it all working, his guide, for anyone else finding this:-
1) On your computer, go into bluetooth settings. Check bluetooth is ON and set to discoverable. Add an incoming COM port, eg. COM5.
2) On ActiveSync on your computer, go into connection settings. Tick all the boxes. If the COM port is greyed out, untick it, close the settings box, go back in, now tick it and set the COM port to eg. COM5.
3) On the K Jam go into bluetooth settings, and remove the connection to your computer.
4) On your K Jam go into ActiveSync, click 'menu' > 'connect via bluetooth' then you should see a message saying 'cannot find an existing bluetooth partnership with a PC that supports ActiveSync. Would you like to set up a partnership now?'
5) Click YES - you are taken to the Bluetooth settings screen.
6) Now click 'new partnership. As soon as you do this, the K Jam will search, and as long as your computer has bluetooth discoverable turned on, your computer will eventually be displayed. Check the computer name showing on the K Jam is the same as the name you gave the bluetooth profile on your computer.
7) On K Jam, click your computer name then NEXT.
Now enter a passcode - any four digit number (remember it) then next
9) When you do this, your computer will pop up with a message saying "a bluetooth device is requesting authorisation". Open this message and type in the code that you gave the K Jam. The next screen on the computer will tell you that it was successful - click FINISH.
10) Back on the K Jam, the screen will now be showing the services available. AS LONG AS YOU FOLLOWED STEP 1 and 2, ActiveSync will be an option, and you need to tick this and press FINISH on the K Jam.
11) Close bluetooth settings, now in ActiveSync screen click MENU > Connect via bluetooth. Your ActiveSync program on the computer should eventually pop up and connect.
The only port you worry about is the incoming pc one. Active Synch does the rest. You must see acitivesync as a service when you connect. I did not see it until I updated my Toshiba Bluetooth stack from thier website. Creating other ports can stop the synch from working.
Click to expand...
Click to collapse
(http://discussion.treocentral.com/wm-synchronization/104553-bluetooth-activesync.html)
The PC has an adapter managed by Widcomm stack (5.5.0.3200, latest so far). Only the "ActiveSync" service is set up as "Automatic", therefore immediately available. ActiveSync is version 4.5.
I do everything anew as instructed, my Hermes sees only the "ActiveSync" remote service. Sometimes it may stubbornly offer the "Serial Port" instead but after a few retries (yes, everything anew!) the correct service is seen. So far so good.
Then I create an outgoing port with same name as on PC. COM5 is apparently optimal at both sides. The PDA begins synchronization, the "Connected" sound is heard from PC... and almost immediately is followed by the "Disconnected" sound. The PDA additionally explains: "port is not available".
If I now refresh services visible via this partnership, the "ActiveSync" is replaced by "Wireless Stereo", "Serial Port" (checked), "Dialup Networking" and "Headset". This is a dead end. The stack on the PC somehow remembers this state and the correct choice of services won't be available anymore.
From now on I can do everything anew repeatedly, and if succeeded, all I get is that quick disconnection.
After installing the older v5.1.0.5600 stack the behaviour changed a bit. Instead of connecting/disconnecting an error message appears: "Synchronization cannot be completed successfully". Reinstalled the newer one, the appropriate behaviour returned.
Had no luck with the M$ stack altogether. The laptop manufacturer doesn't offer the Q323183 separately. Even if it is already included in SP2, I still must provide the kernel-mode drivers. The older Widcomm stack has them in a separate directory but they fail to install. Moreover I read somewhere that the M$ stack allegedly supports ActiveSync at a cost of absent RFCOMM support, and the latter is of paramount importance for me. Perhaps I'm destined to use cable (no problems with it).
Someone at experts-exchange.com states:
There are 2 major issues with activesync 4.x
1 - You cannot sync wirelessly
2 - You cannot sync via cable/cradle when the wifi card is active. If you are connected to a wireless network I would suggest you delete the connection and then try re-syncing.
If you do not need the latest version I would suggest you rollback to version 3.8 unless the above limitations dont affect you or you absolutely need the latest version.
Click to expand...
Click to collapse
If that only were an official M$ statement... And regarding older ActiveSync versions, those didn't work at all for me, as far as I remember.

User Observations: BT, Activesync, Vista and Dash

First let me apologize for spamming the forums with some similar threads... each time I overcame a hurdle and a new one presented itself, I just began a new thread to discuss that. From now on I will append the initial thread... thanks for your patience.
1. WM6.1 and WMDC 6.1 (vista x64) are not too friendly... as the interface, though designed to be intuitive.... is anything but. I am sure it will get worked out in the future... but now it is one tough SOB to conquer
2. From doing enough reading on the web, though recently updated (12-17-07)... the Toshiba BT stack also does not play nicely with WM6.1 ... as numerous smartphone and PPC users are experiencing issues across multiple mobile platforms.
3. In Vista x64 (this is my personal experience) the only way for me to sync via bluetooth is to drop the Toshiba BT stack and use the generic M$ drivers. However... doing so I lose the stereo and serial port services
4. For whatever reason, it seems that activesync locks up STK (R08). When I disable STK, I can establish a connection infintely quicker. Alternatively... when I have activesync disabled, STK is much snappier and its failure/crash rate drops substantially
If anyone has had similar and/or different/"better" experiences with similar hardware... I'd love to hear about it
OS: Vista ultimate x64
ROM: Kavana/Rickwyatt .18
BT adapter: Kensington Micro USB (toshiba rebadge)
HTC: s620

Poser said:
First let me apologize for spamming the forums with some similar threads... each time I overcame a hurdle and a new one presented itself, I just began a new thread to discuss that. From now on I will append the initial thread... thanks for your patience.
1. WM6.1 and WMDC 6.1 (vista x64) are not too friendly... as the interface, though designed to be intuitive.... is anything but. I am sure it will get worked out in the future... but now it is one tough SOB to conquer
2. From doing enough reading on the web, though recently updated (12-17-07)... the Toshiba BT stack also does not play nicely with WM6.1 ... as numerous smartphone and PPC users are experiencing issues across multiple mobile platforms.
3. In Vista x64 (this is my personal experience) the only way for me to sync via bluetooth is to drop the Toshiba BT stack and use the generic M$ drivers. However... doing so I lose the stereo and serial port services
4. For whatever reason, it seems that activesync locks up STK (R08). When I disable STK, I can establish a connection infintely quicker. Alternatively... when I have activesync disabled, STK is much snappier and its failure/crash rate drops substantially
If anyone has had similar and/or different/"better" experiences with similar hardware... I'd love to hear about it
OS: Vista ultimate x64
ROM: Kavana/Rickwyatt .18
BT adapter: Kensington Micro USB (toshiba rebadge)
HTC: s620
Click to expand...
Click to collapse
Never thought of STK being the culprit of activesync issues. Since i didnt have these issues with WM 6.0 . Now i also use the toshiba bluetooth stack but i use winXP and there was a way that i could get activesync to work. (not sure how this would translate to WMDC) here it goes. Basically i created another bluetooth COM port with the toshiba BT configurator. then made sure that COM port # was selected in connection settings under activesync then i opened activesnc on my phone searched for new bluetooth devices and when it found my PC and connected, activesync was one of the options. Trying to go the other way around by pairing the phone starting with toshibas program did not yield the same results, in fact i could never get it to paired the other way around.

very interesting...
I will try the technique with today... usually my issue comes about when the devices cant exchange passkeys... although they are identical.

pudge.... should I set the com port as server or client?

Poser said:
pudge.... should I set the com port as server or client?
Click to expand...
Click to collapse
Do what? the com port needs to be a serial COM port. not a bluetooth DUN or PAN com port

pudgedaddy said:
Do what? the com port needs to be a serial COM port. not a bluetooth DUN or PAN com port
Click to expand...
Click to collapse
I gotcha... when I use the BT com port utility it asks whether I want to create a client-side or server-side port
since its serial it needs to be "server" side...
I tried, but still no luck, it pairs.... lists stereo and activesync in the services, but then refuses to sync
I think this is a flaw in WMDC 6.1

Poser said:
I gotcha... when I use the BT com port utility it asks whether I want to create a client-side or server-side port
since its serial it needs to be "server" side...
I tried, but still no luck, it pairs.... lists stereo and activesync in the services, but then refuses to sync
I think this is a flaw in WMDC 6.1
Click to expand...
Click to collapse
the only other thing you might try is in bluetooth settings -->security on your device. disable (temporarily) the OBEX security option and try again.
You can also try and create a COM port on your device. When you're on the screen where you add a new bluetooth device. press right soft key and select COM ports. right soft key again and then select new outgoing port. then select your PC (or laptop) on the list of devices that shows up. then add a com port . and it will let you pick com 6 or com 7. Then try again

pudgedaddy said:
the only other thing you might try is in bluetooth settings -->security on your device. disable (temporarily) the OBEX security option and try again.
You can also try and create a COM port on your device. When you're on the screen where you add a new bluetooth device. press right soft key and select COM ports. right soft key again and then select new outgoing port. then select your PC (or laptop) on the list of devices that shows up. then add a com port . and it will let you pick com 6 or com 7. Then try again
Click to expand...
Click to collapse
already been down that road, trying to set up a new outgoing com port (6,7) no dice.
I think the deal is WMDC6.1 ... it makes me sad

Poser said:
already been down that road, trying to set up a new outgoing com port (6,7) no dice.
I think the deal is WMDC6.1 ... it makes me sad
Click to expand...
Click to collapse
sorry to hear that. Well since i have the same drivers, i will not be using vista anytime soon (not that i needed this as an excuse to begin with)

I was thinking of perhaps looking for some compatable drivers to replace the Toshiba stack. The generic MS drivers allow me to connect via activesync... but thats all, I lose all serial services (including object push, file transfer, stereo etc....)
I'll be honest though, I have been an XP guy for a long time... but after learning how to tweak, hack and optimize my vista install, I love it.

TP2 Activesync won't recognize outlook - WM6.5 problem??

I have just moved from a T-Mobile TouchPro2 (US Model) to an Orange TouchPro 2 (UK Model).
The T-Mobile was WM6.1 and the Orange is WM6.5 and both ROM's are stock.
On the T-Mobile ROM I was able to sync my Contacts & Calender with my works issue XP laptop running Outlook 2007.
When I set up my new Orange TP2 on the same laptop everything worked fine for about 3 days. Now when I connect I get a message saying I will only be able to view files etc. No sync is available and the message goes on to advise me to install MS Outlook. Of course Oulook has not been removed.
I deleted the sync partnership on the TP2 and tried again with no success. I re-installed activesysnc and this worked but only for about 5 connections. I now get the same message.
I still have my T-Mobil TP2 and did some testing with that but I can not get it to fail. When I retest with the Orange TP2 it fails within 5 syncs attempts.
Is this a known bug in WM6.5? I have searched the forums and there is a lot of info regarding problems syncing to Exchange (Push mail) but I do not use that service or connect in that way.
Any help appriciated.

does no one else see this problem?

I've noticed a similar issue when connecting my Tilt2 to my Windows 7 laptop. It will sometimes only connect once per boot. In other words I can plug it in and it will connect. But when I unplug and replug, it will make the little "USB Connect" sound but not actually connect. After rebooting, it will connect again.
Windows Vista and 7 use a slightly different method of syncing than XP (Windows Mobile Device Center). I've noticed that if I set up a named partnership in WMDC it seems to give more reliable connections.
I'm not sure that really helps your situation but at least know that you're not alone in sync wonkiness.

Similar problem running Activesync 4.5 on old Windows 2000 work laptop (don't ask ) Current ROM NRGY Phoenix 2 16 Jan 21889 Titanium build. Seems to be specific to some ROMs, but cannot for sure say which branch works better for Activesync.

It doesn't appear to be a common problem. But since I had never seen it before I started using WM6.5 I was sure it was a bug in the ROM. It's a real pain in the ass when it happens as you have to delete the sync partnership on the phone before it will reconnect. Then you have to set up all your favorite contacts and speed dials all over agin. I have just started a new job here and I am adding 3 or 4 new conacts every day at the moment so couldn't have happened at worse time. Might be time to try a cooked ROM.

TP2 Activesunc won't recognize Outlook - WM6.5
Have had this same problem now for over a month. Have been syncing Activesync v4.5 with WM6.5 on TP2 for over a year previously. Transitioned from MSO-2003 to MSO-2007 with no sync issues. Fresh install of MSO-2010 and TP2 will mo longer recognize that my computer has MS-Office installed. have not found solution anywhere to date. Appreciate any updates from other with any solutions ....
Regards,