BirdieSync

hello,

i've tried birdiesync's test version and now it is exspired.

I uninstalled birdie sync and followed all recommended steps.

so far so good. now the sync via active sync is not possible anymore, because my pocket pc is first recognized but then the connection shuts down after 5 sec and an error occurs that "a file can't be located"!

Has anybody had the same problem and a solution? I tried to reinstall active sync but without success!

thanx
Tobias

Hello,

Could you tell me how this error is displayed ? Is it an alert raising from the task bar ? A pop up window ? What is the exact message ?
Did you remove BirdieSync on the mobile too ?
Did you try to delete ActiveSync partnership ?
Thanks.

hello birdy,

well I uninstalles Birdiesync on my pc after I unchecked the thunderbird mail, contacts ... in activesync.
then launched thunderbird > birdiesync was gone.
then removed birdiesync on pocketpc by "add/remove program" function

then tried a sync with active sync and the connection between pc and pocketpc is established for 3-5 sec and then the connection is not working anymore.

The error message is coming from a software which tries to update while syncing because the connection is established only for 3-5 sec and then the green activesync logo is gray again.

I have no idea how to fix it!

Could you give me the exact error message ?

the error message is in german (I'm german :-))

Das Sytem kann die angegebene Datei nicht finden.

and a 2nd one afterwards:

error: der Vorgang wurde erfolgreich beendet!

that's weird.

I've tried both activesync 4.2 and 4.5.
I've runned the troubleshooter of activesync 4.2 and the log-file is the following:

ActiveSync Troubleshooting Utility version: 4.2.4876.0
Date/Time: 2007/09/12-18:44:58.187
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.2.4876
Outlook 2003 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 - Folgende Windows-Dienste sind gestartet:

Net start -

Net start - Ad-Aware 2007 Service

Net start - AntiVir PersonalEdition Classic Guard

Net start - AntiVir PersonalEdition Classic Planer

Net start - Anwendungsverwaltung

Net start - Apple Mobile Device

Net start - Arbeitsstationsdienst

Net start - Automatische Updates

Net start - Bluetooth Service

Net start - COM+-Ereignissystem

Net start - DCOM-Server-Prozessstart

Net start - Designs

Net start - DHCP-Client

Net start - Distributed Transaction Coordinator

Net start - DNS-Client

Net start - Druckwarteschlange

Net start - Ereignisprotokoll

Net start - Fehlerberichterstattungsdienst

Net start - Gatewaydienst auf Anwendungsebene

Net start - Gesch�tzter Speicher

Net start - Hilfe und Support

Net start - hpqwmiex

Net start - Indexdienst

Net start - IPSEC-Dienste

Net start - IPv6-Hilfsdienst

Net start - Konfigurationsfreie drahtlose Verbindung

Net start - Kryptografiedienste

Net start - LightScribeService Direct Disc Labeling Service

Net start - Logitech Process Monitor

Net start - Lokaler Verbindungskanal

Net start - Message Queuing

Net start - Message Queuing Triggers

Net start - Netzwerkverbindungen

Net start - NLA (Network Location Awareness)

Net start - NT-LM-Sicherheitsdienst

Net start - Plug & Play

Net start - RAS-Verbindungsverwaltung

Net start - Remote-Registrierung

Net start - Remoteprozeduraufruf (RPC)

Net start - Server

Net start - Shellhardwareerkennung

Net start - Sicherheitskontenverwaltung

Net start - Systemereignisbenachrichtigung

Net start - Systemwiederherstellungsdienst

Net start - Taskplaner

Net start - Telefonie

Net start - Terminaldienste

Net start - TuneUp Designerweiterung

Net start - Verwaltung logischer Datentr„ger

Net start - WebClient

Net start - Windows Audio

Net start - Windows Installer

Net start - Windows-Bilderfassung (WIA)

Net start - Windows-Firewall/Gemeinsame Nutzung der Internetverbindung

Net start - Windows-Verwaltungsinstrumentation

Net start - Windows-Zeitgeber

Net start -

Net start - Der Befehl wurde erfolgreich ausgef�hrt.

Net start -

Dumping Route information
Route - ===========================================================================

Route - Schnittstellenliste

Route - 0x1 ........................... MS TCP Loopback interface
Route - 0x2 ...00 18 de bc 7a 17 ...... Intel(R) PRO/Wireless 3945ABG Network Connection - Paketplaner-Miniport
Route - ===========================================================================

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

Route - Aktive Routen:

Route - Netzwerkziel Netzwerkmaske Gateway Schnittstelle Anzahl

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 192.168.1.100 1

Route - Standardgateway: 192.168.1.1

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

Route - St„ndige Routen:

Route - Keine

LSP - MSAFD Tcpip [TCP/IP]
Dumping Ipconfig information
Dumping LSPs information
LSP - MSAFD Tcpip [UDP/IP]
LSP - MSAFD Tcpip [RAW/IP]
LSP - RSVP UDP Service Provider
LSP - RSVP TCP Service Provider
LSP - MSAFD Pgm (RDM)
LSP - MSAFD Pgm (Stream)
LSP - MSAFD Tcpip [TCP/IPv6]
LSP - MSAFD Tcpip [UDP/IPv6]
LSP - MSAFD Tcpip [RAW/IPv6]
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{A989772F-73CD-41FA-8F3F-D5F87101E92D}] SEQPACKET 12
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{A989772F-73CD-41FA-8F3F-D5F87101E92D}] DATAGRAM 12
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{DC10D101-3068-403F-9652-31F2ED53B3EC}] SEQPACKET 8
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{DC10D101-3068-403F-9652-31F2ED53B3EC}] DATAGRAM 8
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{BEF0BEF2-0790-4134-8CF8-079D07585612}] SEQPACKET 9
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{BEF0BEF2-0790-4134-8CF8-079D07585612}] DATAGRAM 9
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{EEF70A16-B80F-49B7-B40B-9BF5A3C9B7EE}] SEQPACKET 10
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{EEF70A16-B80F-49B7-B40B-9BF5A3C9B7EE}] DATAGRAM 10
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{46EDEB7A-DBCC-431C-A766-3613F97FB049}] SEQPACKET 11
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip6_{46EDEB7A-DBCC-431C-A766-3613F97FB049}] DATAGRAM 11
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{A989772F-73CD-41FA-8F3F-D5F87101E92D}] SEQPACKET 13
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{A989772F-73CD-41FA-8F3F-D5F87101E92D}] DATAGRAM 13
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{EEF70A16-B80F-49B7-B40B-9BF5A3C9B7EE}] SEQPACKET 7
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{EEF70A16-B80F-49B7-B40B-9BF5A3C9B7EE}] DATAGRAM 7
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{32EAFB3B-F6AF-436E-82E0-605EAB258822}] SEQPACKET 4
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{32EAFB3B-F6AF-436E-82E0-605EAB258822}] DATAGRAM 4
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{BEF0BEF2-0790-4134-8CF8-079D07585612}] SEQPACKET 3
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{BEF0BEF2-0790-4134-8CF8-079D07585612}] DATAGRAM 3
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{DC10D101-3068-403F-9652-31F2ED53B3EC}] SEQPACKET 0
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{DC10D101-3068-403F-9652-31F2ED53B3EC}] DATAGRAM 0
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{72106479-D40F-44D1-A94F-86B304D7C75F}] SEQPACKET 1
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{72106479-D40F-44D1-A94F-86B304D7C75F}] DATAGRAM 1
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{2162A4B8-8860-40B1-B505-764E7B6B23CB}] SEQPACKET 2
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{2162A4B8-8860-40B1-B505-764E7B6B23CB}] DATAGRAM 2
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{30625B7E-0F8E-4E34-8BDD-07450CFCD52A}] SEQPACKET 5
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{30625B7E-0F8E-4E34-8BDD-07450CFCD52A}] DATAGRAM 5
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{C9B08A63-8325-47C3-81C2-0903ED242350}] SEQPACKET 6
LSP - MSAFD NetBIOS [\Device\NetBT_Tcpip_{C9B08A63-8325-47C3-81C2-0903ED242350}] DATAGRAM 6
Dumping NSPs information
NSP - TCP/IP
NSP - NTDS
NSP - NLA-Namespace
Dumping NDIS information
Listing Network Protocols
---Microsoft TCP/IP Version 6
------Binding Path 1
---------Microsoft TV-/Videoverbindung
------Binding Path 2
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 3
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 4
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 5
---------Microsoft Tun-Miniportadapter
---PPP (Point to Point-Protokoll) mit Ethernet
------Binding Path 1
---------Microsoft TV-/Videoverbindung
------Binding Path 2
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 3
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 4
---------Broadcom 440x 10/100 Integrated Controller
---Point to Point Tunneling-Protokoll (PPTP)
---Layer 2-Tunnelingprotokoll
---RAS-NDIS-WAN-Treiber
------Binding Path 1
---------Parallelanschluss (direkt)
------Binding Path 2
---------WAN-Miniport (PPPOE)
------Binding Path 3
---------WAN-Miniport (PPTP)
------Binding Path 4
---------WAN-Miniport (L2TP)
------Binding Path 5
---------Asynchroner RAS-Adapter
---NDIS-Benutzermodus-E/A-Protokoll
------Binding Path 1
---------Microsoft TV-/Videoverbindung
------Binding Path 2
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 3
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 4
---------Broadcom 440x 10/100 Integrated Controller
---Nachrichtorientiertes TCP/IP-Protokoll (SMB-Sitzung)
---Protokoll für WINS-Client (TCP/IP)
------Binding Path 1
---------Microsoft TCP/IP Version 6
---------Microsoft TV-/Videoverbindung
------Binding Path 2
---------Microsoft TCP/IP Version 6
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 3
---------Microsoft TCP/IP Version 6
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 4
---------Microsoft TCP/IP Version 6
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 5
---------Microsoft TCP/IP Version 6
---------Microsoft Tun-Miniportadapter
------Binding Path 6
---------Internetprotokoll (TCP/IP)
---------Microsoft TV-/Videoverbindung
------Binding Path 7
---------Internetprotokoll (TCP/IP)
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 8
---------Internetprotokoll (TCP/IP)
---------1394-Netzwerkadapter
------Binding Path 9
---------Internetprotokoll (TCP/IP)
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 10
---------Internetprotokoll (TCP/IP)
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 11
---------Internetprotokoll (TCP/IP)
---------WAN-Miniport (IP)
---Internetprotokoll (TCP/IP)
------Binding Path 1
---------Microsoft TV-/Videoverbindung
------Binding Path 2
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 3
---------1394-Netzwerkadapter
------Binding Path 4
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 5
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 6
---------WAN-Miniport (IP)
---Konfigurationsfreie drahtlose Verbindung
Listing Network Services
---Steelhead
---DFÜ-Server
---RAS-Verbindungsverwaltung
---DFÜ-Client
---Datei- und Druckerfreigabe für Microsoft-Netzwerke
------Binding Path 1
---------Nachrichtorientiertes TCP/IP-Protokoll (SMB-Sitzung)
------Binding Path 2
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Microsoft TV-/Videoverbindung
------Binding Path 3
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 4
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 5
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 6
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Microsoft Tun-Miniportadapter
------Binding Path 7
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------Microsoft TV-/Videoverbindung
------Binding Path 8
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 9
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------1394-Netzwerkadapter
------Binding Path 10
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 11
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 12
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------WAN-Miniport (IP)
---QoS-Paketplaner
------Binding Path 1
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 2
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 3
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 4
---------WAN-Miniport (IP)
---Standardpaketklassifizierung
---Gateway auf Anwendungsebene
---NetBIOS-Schnittstelle
------Binding Path 1
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Microsoft TV-/Videoverbindung
------Binding Path 2
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 3
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 4
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 5
---------Protokoll für WINS-Client (TCP/IP)
---------Microsoft TCP/IP Version 6
---------Microsoft Tun-Miniportadapter
------Binding Path 6
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------Microsoft TV-/Videoverbindung
------Binding Path 7
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------Treiber für Bluetooth-LAN-Zugangsserver
------Binding Path 8
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------1394-Netzwerkadapter
------Binding Path 9
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------Intel(R) PRO/Wireless 3945ABG Network Connection
------Binding Path 10
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (TCP/IP)
---------Broadcom 440x 10/100 Integrated Controller
------Binding Path 11
---------Protokoll für WINS-Client (TCP/IP)
---------Internetprotokoll (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
Es konnte keine Verbindung zwischen dem PC und dem Gerät hergestellt werden. Aktuelle Lösungen für häufig auftretende Verbindungsprobleme erhalten Sie auf der Microsoft-Website. Klicken Sie hierzu auf folgenden Link:
http://go.microsoft.com/fwlink/?LinkId=65257
Die Verbindung zum Gerät ist anscheinend getrennt. Verbinden Sie das Gerät mit dem PC.
ActiveSync is performing a sync, please wait......
ActiveSync-Protokolldatei wird durchsucht
No errors found in ActiveSync log file
Exiting

the other thing is, that in the active sync window first is said:

connected

and then after 5 sec

error while synchronizing

First you could try to delete ActivSync partnership (ActiveSync window, Menu Toold/Delete mobile Device). Then reconnect your mobile.

If it still doesn't work, you could try to install BirdieSync 1.6.0.1 and then uninstall it (on the mobile too). There were some improvements in the mobile uninstallation in this new version.

I did delete the partnership > doesn't work!

And I can't install Birdiesync again because the pocketpc needs to be connected via activesync but since this connection is disrupted after 5 sec there is no way to install birdiesync again!

Any other ideas?

Even if the connection seems disrupted can you still access to your mobile folders with Windows file explorer (sometimes you can) ?

what exactly do you mean?

I don't see the folders of my mobile device in windows explorer because it is not CONNECTED! after uninstallation of birdiesync the connection gets disrupted after 5 sec!

I understood. But I know some cases where it is still possible to access to the mobile folders even if the mobile appears disconnected (especially after a "synchronization error")...

Could you send to support(at)birdiesync.com the file WCESMgr.log located in C:\Documents and Settings\<user name>\Local Settings\Temp ?
Thanks.

I've just sent it ....

The same happened to me. I suspected other reasons and have meanwhile uninstalled ActiveSync 4.5 and reinstalled again.
Any idea?

Did you uninstall BirdieSync on the mobile ?

As previously, could you send to support(at)birdiesync.com the file WCESMgr.log located in C:\Documents and Settings\<user name>\Local Settings\Temp ?
Thanks.