ActiveSync Issues/Questions

---

I have the following problem every few days when I try to sync my phone (T-Mobile Dash but it also happened with my old MDA) I got the following error: "Synchronization cannot be completed successfully. Reconnect your device and try again. If the problem persists, see the Microsoft ActiveSync Troubleshooter in Microsoft ActiveSync Help on your desktop computer."

I can click 'Explore' through ActiveSync and see my device. It just won't synchronize.

The workaround that I found for this problem is to delete the partnership and then recreate it again, then it starts synchronizing but few days later I get the same error message again.

I'm using ActiveSync 4.5 (final not the beta) but got the same error with 4.2.

I've run the troubleshooter which told me to check Zone Alarm. I followed that guide. I've done a soft reset. The same problem.

I found an advice in other forum about cleaning the Windows/Temp but that directory doesn't exists in my device

I would really like to resolve this problem without doing a hard reset or recreate the partnership every 3 days.

try opening outlook and then syncing. when i upgraded to outlook 2007, i had the same issue. i just had to run outlook to sync up all the software with the device.

if that doesn't work, you might want to try uninstalling activesync completely, and then reinstalling 4.2. I've found that 4.5 is a bit too buggy for me.

I have outlook open when I sync. I just moved back to 4.2 but not sure how long it will take before I get the error message again.

ActiveSync not Syncing?

---

Noticed the last week or so, my phone is refusing to sync up. I uninstalled and reinstalled AS... rebooted... powered down the phone... everything that the "troubleshooter" told me to do.

It's also telling me Outlook is not my default email client (it is), though I do use Mozilla Thunderbird regularly. Could this be my problem?

Here is the detailed log...

ActiveSync Troubleshooting Utility version: 4.5.5096.0
Date/Time: 2007/05/31-21:21:44.640
Analysis started
Operating system has been qualified as Windows XP (Home or Professional) SP1 or greater
Current operating system is supported
Current version of IE is supported
ActiveSync version found is 4.5.5096
Outlook XP found
Current version of Outlook is supported
Exchange server not found in Outlook profile
PC is not qualified
SerialUSB driver has been detected.
Net start - %s
Net start - These Windows services are started:

Net start -

Net start - Application Layer Gateway Service

Net start - Automatic Updates

Net start - Background Intelligent Transfer Service

Net start - COM+ Event System

Net start - COM+ System Application

Net start - Computer Browser

Net start - Cryptographic Services

Net start - DCOM Server Process Launcher

Net start - DHCP Client

Net start - Distributed Link Tracking Client

Net start - DNS Client

Net start - DVD-RAM_Service

Net start - Event Log

Net start - Fast User Switching Compatibility

Net start - Help and Support

Net start - HID Input Service

Net start - IPSEC Services

Net start - Logical Disk Manager

Net start - McAfee E-mail Proxy

Net start - McAfee HackerWatch Service

Net start - McAfee Network Agent

Net start - McAfee Protection Manager

Net start - McAfee Real-time Scanner

Net start - McAfee Redirector Service

Net start - McAfee Scanner

Net start - McAfee Services

Net start - McAfee SystemGuards

Net start - Media Center Extender Service

Net start - Media Center Receiver Service

Net start - Media Center Scheduler Service

Net start - Network Connections

Net start - Network Location Awareness (NLA)

Net start - Plug and Play

Net start - Print Spooler

Net start - Protected Storage

Net start - Remote Access Auto Connection Manager

Net start - Remote Access Connection Manager

Net start - Remote Procedure Call (RPC)

Net start - Remote Registry

Net start - Secondary Logon

Net start - Security Accounts Manager

Net start - Security Center

Net start - Server

Net start - Shell Hardware Detection

Net start - SSDP Discovery Service

Net start - System Event Notification

Net start - Task Scheduler

Net start - TCP/IP NetBIOS Helper

Net start - Telephony

Net start - Terminal Services

Net start - Themes

Net start - WebClient

Net start - Windows Audio

Net start - Windows Firewall/Internet Connection Sharing (ICS)

Net start - Windows Image Acquisition (WIA)

Net start - Windows Management Instrumentation

Net start - Windows Time

Net start - Wireless Zero Configuration

Net start - Workstation

Net start -

Net start - The command completed successfully.

Net start -

Route - ================================================== =========================

Dumping Route information
Route - Interface List

Route - 0x1 ........................... MS TCP Loopback interface
Route - 0x2 ...00 13 02 a4 90 88 ...... Intel(R) PRO/Wireless 3945ABG Network Connection - Packet Scheduler Miniport
Route - 0x3 ...00 16 36 63 7a e4 ...... Intel(R) PRO/100 VE Network Connection - Packet Scheduler Miniport
Route - ================================================== =========================

Route - ================================================== =========================

Route - Active Routes:

Route - Network Destination Netmask Gateway Interface Metric

Route - 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.100 25

Route - 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

Route - 192.168.1.0 255.255.255.0 192.168.1.100 192.168.1.100 25

Route - 192.168.1.100 255.255.255.255 127.0.0.1 127.0.0.1 25

Route - 192.168.1.255 255.255.255.255 192.168.1.100 192.168.1.100 25

Route - 224.0.0.0 240.0.0.0 192.168.1.100 192.168.1.100 25

Route - 255.255.255.255 255.255.255.255 192.168.1.100 3 1

Route - 255.255.255.255 255.255.255.255 192.168.1.100 192.168.1.100 1

Route - Default Gateway: 192.168.1.1

Route - ================================================== =========================

Route - Persistent Routes:

Route - None

Dumping Ipconfig information
Dumping LSPs information
LSP - MSAFD Tcpip [TCP/IP]
LSP - MSAFD Tcpip [UDP/IP]
LSP - MSAFD Tcpip [RAW/IP]
LSP - RSVP UDP Service Provider
LSP - RSVP TCP Service Provider
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{197CB53D-D5AD-4329-8E5B-84E11FAB702F}] SEQPACKET 9
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{197CB53D-D5AD-4329-8E5B-84E11FAB702F}] DATAGRAM 9
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{0D439983-D266-4054-9EC8-2052A9BA615E}] SEQPACKET 3
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{0D439983-D266-4054-9EC8-2052A9BA615E}] DATAGRAM 3
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{2BF0B2E8-B041-4C21-B9A3-B1C182EEDE19}] SEQPACKET 5
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{2BF0B2E8-B041-4C21-B9A3-B1C182EEDE19}] DATAGRAM 5
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{FAF5FECE-EB9E-4EED-9AB6-741CBF5B2CD3}] SEQPACKET 7
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{FAF5FECE-EB9E-4EED-9AB6-741CBF5B2CD3}] DATAGRAM 7
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{1D62C6C2-D3E1-406B-BC4B-F53DDD8F9B44}] SEQPACKET 6
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{1D62C6C2-D3E1-406B-BC4B-F53DDD8F9B44}] DATAGRAM 6
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{02344484-60AB-49E6-BAF2-31F0BB3AB133}] SEQPACKET 4
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{02344484-60AB-49E6-BAF2-31F0BB3AB133}] DATAGRAM 4
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{148B6D3A-EF7A-400C-AC7D-3CD28DF2AFA9}] SEQPACKET 0
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{148B6D3A-EF7A-400C-AC7D-3CD28DF2AFA9}] DATAGRAM 0
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{EAE03E08-3A4F-4FBF-9991-2B6FDB5BF352}] SEQPACKET 1
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{EAE03E08-3A4F-4FBF-9991-2B6FDB5BF352}] DATAGRAM 1
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{D711002D-7ECF-417F-9ABB-B43FFFCBFB57}] SEQPACKET 2
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{D711002D-7ECF-417F-9ABB-B43FFFCBFB57}] DATAGRAM 2
Dumping NSPs information
NSP - Tcpip
NSP - NTDS
NSP - Network Location Awareness (NLA) Namespace
Dumping NDIS information

Listing Network Protocols
---Point to Point Protocol Over Ethernet
------Binding Path 1
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 2
---------Intel(R) PRO/100 VE Network Connection
------Binding Path 3
---------D-Link WNA-1330 Notebook Adapter
------Binding Path 4
---------Microsoft TV/Video Connection
------Binding Path 5
---------Intel(R) PRO/1000 PL Network Connection
---Point to Point Tunneling Protocol
---Layer 2 Tunneling Protocol
---Remote Access NDIS WAN Driver
------Binding Path 1
---------Direct Parallel
------Binding Path 2
---------WAN Miniport (PPPOE)
------Binding Path 3
---------WAN Miniport (PPTP)
------Binding Path 4
---------WAN Miniport (L2TP)
------Binding Path 5
---------RAS Async Adapter
---NDIS Usermode I/O Protocol
------Binding Path 1
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 2
---------Intel(R) PRO/100 VE Network Connection
------Binding Path 3
---------D-Link WNA-1330 Notebook Adapter
------Binding Path 4
---------Microsoft TV/Video Connection
------Binding Path 5
---------Intel(R) PRO/1000 PL Network Connection
---Message-oriented TCP/IP Protocol (SMB session)
---WINS Client(TCP/IP) Protocol
------Binding Path 1
---------Internet Protocol (TCP/IP)
---------Windows Mobile-based Device #2
------Binding Path 2
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 3
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/100 VE Network Connection
------Binding Path 4
---------Internet Protocol (TCP/IP)
---------D-Link WNA-1330 Notebook Adapter
------Binding Path 5
---------Internet Protocol (TCP/IP)
---------Microsoft TV/Video Connection
------Binding Path 6
---------Internet Protocol (TCP/IP)
---------1394 Net Adapter
------Binding Path 7
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/1000 PL Network Connection
------Binding Path 8
---------Internet Protocol (TCP/IP)
---------WAN Miniport (IP)
---Internet Protocol (TCP/IP)
------Binding Path 1
---------Windows Mobile-based Device #2
------Binding Path 2
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 3
---------Intel(R) PRO/100 VE Network Connection
------Binding Path 4
---------D-Link WNA-1330 Notebook Adapter
------Binding Path 5
---------Microsoft TV/Video Connection
------Binding Path 6
---------1394 Net Adapter
------Binding Path 7
---------Intel(R) PRO/1000 PL Network Connection
------Binding Path 8
---------WAN Miniport (IP)
Listing Network Services
---Wireless Zero Configuration
---Steelhead
---Dial-Up Server
---Remote Access Connection Manager
---Dial-Up Client
---File and Printer Sharing for Microsoft Networks
------Binding Path 1
---------Message-oriented TCP/IP Protocol (SMB session)
------Binding Path 2
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Windows Mobile-based Device #2
------Binding Path 3
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 4
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/100 VE Network Connection
------Binding Path 5
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------D-Link WNA-1330 Notebook Adapter
------Binding Path 6
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Microsoft TV/Video Connection
------Binding Path 7
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------1394 Net Adapter
------Binding Path 8
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/1000 PL Network Connection
------Binding Path 9
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------WAN Miniport (IP)
---QoS Packet Scheduler
------Binding Path 1
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 2
---------Intel(R) PRO/100 VE Network Connection
------Binding Path 3
---------D-Link WNA-1330 Notebook Adapter
------Binding Path 4
---------Intel(R) PRO/1000 PL Network Connection
------Binding Path 5
---------WAN Miniport (IP)
---Generic Packet Classifier
---Application Layer Gateway
---NetBIOS Interface
------Binding Path 1
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Windows Mobile-based Device #2
------Binding Path 2
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 3
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/100 VE Network Connection
------Binding Path 4
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------D-Link WNA-1330 Notebook Adapter
------Binding Path 5
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Microsoft TV/Video Connection
------Binding Path 6
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------1394 Net Adapter
------Binding Path 7
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------Intel(R) PRO/1000 PL Network Connection
------Binding Path 8
---------WINS Client(TCP/IP) Protocol
---------Internet Protocol (TCP/IP)
---------WAN Miniport (IP)
---QoS RSVP
Pinging Desktop gateway 192.168.1.1 started
Ping echoed successfully
The IP address of device is unknown
Unable to establish a connection between the PC and the device. Get up-to-date solutions to common connection problems. Please click the following link:
http://go.microsoft.com/fwlink/?LinkId=65257
The device appears to be disconnected. Please connect your device to the PC
ActiveSync is performing a sync, please wait......
Searching ActiveSync log file
No errors found in ActiveSync log file
Exiting

Originally Posted by freyes01

I have outlook open when I sync. I just moved back to 4.2 but not sure how long it will take before I get the error message again.

I'm having exactly the same experience as you. Can you tell me if moving back to 4.2 solved your problems? If so, is 4.2 still available to download?

Anyone!? Still can't connect

I saw McAfee in your list there ... perhaps it is blocking the ActiveSync somehow ... see this for configuration to let it through !!

http://www.microsoft.com/windowsmobile/help/activesync/mcafee.mspx

another thing is ... WM5 you can use Activesync 4.2 ... but for WM6 you will required Activesync v4.5

Outlook is not required if you are not syncing emails ... I don't even have outlook on my desktop ... things run fine ... I also use McAfee and syncing is fine.

and then there's Vista ... that's another story ... will requires "Windows Mobile Device Center Driver for Windows Vista"

Originally Posted by UnicornKaz

I saw McAfee in your list there ... perhaps it is blocking the ActiveSync somehow ... see this for configuration to let it through !!

http://www.microsoft.com/windowsmobile/help/activesync/mcafee.mspx

another thing is ... WM5 you can use Activesync 4.2 ... but for WM6 you will required Activesync v4.5

Outlook is not required if you are not syncing emails ... I don't even have outlook on my desktop ... things run fine ... I also use McAfee and syncing is fine.

and then there's Vista ... that's another story ... will requires "Windows Mobile Device Center Driver for Windows Vista"

Sorry, should have said. Running XP with all hotfixes/SPs. Running WM6 with ActiveSync 4.5. I'll give the virus scan passthrough a go, but can't see that being it since I have no software firewall. It just keeps spinning in the tray and is forever "connecting"


OK.... like I said, no firewall, and appears McAfee has nothing to do with it since I even shut down the service completely and no change. (Yes... Windows firewall is off as well).

Also tried two different USB cables, shutting off the request for Email syncing on the phone, and uninstalled/reinstalled again..... nadda

how can you say that when clearly your first post have "McAfee" written allover it ???



BTW ... you have to configure like that link I gave you ... you cannot just boot up windows already and then stop the service ...etc ... it won't work that way.

other then that ... I don't know what else to say ... I have XP + McAfee ... had the same Activesync problem WAYYYY back ... ( owned an Axim X51V also ) .... ever since I got the info a few years back ... been configuring the same route and never have problem using activesync ever again ..