Activesync fails to sync after installing vers. 4.0

Hello to all,
I have upgrade activesync from version 3.7.1 to 4.0 in order to deploy my application in VS2005 beta2 to the device. After doing that, activesync stops to work: although the AS icon show connection (green) when the PDA is in the cradle, is is not possible to get the main screen of activesync; and, when trying to explore the device, I get the following error window:
"Critical communications services have failed to start. Try resetting the mobile device, and then connect again".
To get worse, I have uninstalled AS 4.0 and went back to version 3.7.1. The problem still is there! In fact, I have tried (with no success) to:
- install activesync 3.8 , then 4.0 again, then back to 3.7.1
- uninstall the whole VS 2005 beta2 package.
- Connect to another PDA (a brand new acer n50 with WM 2003 SE in its factory default, with no previous sync)
- fully disable the firewall
- resetting the TCP/IP stack to the factory default ("netsh int ip reset")
- uninstalling the "Virtual machine network services" and "deterministic network enhancer" from the network cards (just in case, i'm not sure why are there :)
- do a repair installation of windows XP SP2

It is very dissapointing to see that there is no single mention to the "critical services..." error in the MS knowledge base, and the very few posts found with the same problem only have got one answer: to format the hard disk and do a fresh installation of Windows!

I would appreciate any help to track this problem. It seems that activesync have a (cryptic) log file, but I cannot find it. Any idea of which those "critical services" are
Any help will be appreciated. Many thanks in advance,
Adolfo.

Answer this question

Activesync fails to sync after installing vers. 4.0

ZhangHua
Thanks a lot for the information. After I tried to go back from 4.0 to 3.8, I had exactly the same problem, and I found the same warning messages in the log file. I had to remove these and more files from C:\Program Files\Common Files\Microsoft Shared\NoteSync Forms directory and reinstall 3.8 to get it working. Thanks again for saving a lot of time for me.

Hari
Tony_Rodriguez

Christoffee:

If you are still checking in, try some of the troubleshooting suggestions at this link:

http://www.pocketpcfaq.com/faqs/t-shootactivesync.htm

Blessings to you,

Doc
prash123
Hi,
the files RAPI.DLL and CEUTILS.DLL are located only in \windows\system32 in my system.
looking for problems in the log files of activesync in the %temp% directory, as Ken suggested, I have found the found the following lines in the WCESETUP.LOG file:

rpai.dll - WARNING: not copied (old ver = 4.0.4343.0, source ver = 3.8.0.5004)
ceutils.dll - WARNING: not copied (old ver = 4.0.4343.0, source ver = 3.8.0.5004)
So i deleted both files (always in the system32 directory) and reinstalled activesync 3.8. It worked for me. However, I haven't tried to install again AS 4.0, problably this new version still doesn't work in my computer.

Hope that helps.
regards,
Adolfo.
RA-SJD
Ken,
thank you very much for your answer. it actually solved the problem!
there was an entry in the setup log files complaining about the incorrect version of rapi.dll and ceutils.dll .
Thanks,
Adolfo.
Moses

Well! Never mind - you guys are great. I followed your steps and it works!

I went to the wcesetup.log by typing %temp% in the Run box

I saw the version conflicts saying it didn't copy the RAPI.DLL and CEUTIL.DLL file due to it being a newer version. So I searched for those two files and renamed them with the prefix "old" like oldrapi.dll (It wouldn't let me delete them for some reason)

Then I reinstalled ActiveSync 3.7 and I'm in business!

Yahoo!

Thanks very much. Happy New Year!
Jonathan Clark

I stumbled on this thread and it exactly describes my situation. I had AS3.7 and upgraded to AS4.0 and need to go back. I uninstalled AS/40 and reinstalled AS3.7 and when I cradle the device, the AS tray icon lights up and swirls for a while but AS never opens. Can't open AS at all, even without device in cradle. I am not as tech saavy as you guys. If I right-click tray icon and choose Explore, I get the same message listed above - Critical communication services have failed to start......

Is there any hope for me to get back my ability to sync

I can follow directions pretty well if they are spelled out, and I am not afraid to try. I know my way around my system pretty well, just can't quite follow your posts above. Can someone help

Jeff
knuckle05
Hey guys,

Check out the WcesView.log (found in the same subdirectory as the other logs). This log captures information whenever you attempt to explore the PDA through ActiveSync. I am able to explore my PDA with no problem so I include an extract of my log from a recent session that you can compare your logs against.

3/24/2006 12:10:17 PM - Entering connect threadproc
3/24/2006 12:10:17 PM - OnLogActive
3/24/2006 12:10:17 PM - ThreadProc: dwContext = 228568
3/24/2006 12:10:17 PM - CConnectThread::ThreadProc: Calling CeRapiInitEx().
3/24/2006 12:10:17 PM - CConnectThread::ThreadProc: ri.heRapiInit = 0x1030, m_hrInit = 0x0.
3/24/2006 12:10:17 PM - OnLogIpAddrEx
3/24/2006 12:10:17 PM - CDevicesConn::OnLogIpAddrEx: 175589284
3/24/2006 12:10:34 PM - CConnectThread::Term - Inform backgroun thread to quit.
3/24/2006 12:10:34 PM - CConnectThread::ThreadProc() Calling CeRapiUninit.
3/24/2006 12:10:34 PM - CConnectThread::Term: Before WaitForSingleObject().
3/24/2006 12:10:34 PM - CConnectThread::Term: Before WaitForSingleObject().
3/24/2006 12:10:34 PM - CConnectThread::Term: After WaitForSingleObject().
3/24/2006 12:11:51 PM - Entering connect threadproc
3/24/2006 12:11:51 PM - OnLogActive
3/24/2006 12:11:51 PM - ThreadProc: dwContext = 226432
3/24/2006 12:11:51 PM - CConnectThread::ThreadProc: Calling CeRapiInitEx().
3/24/2006 12:11:51 PM - CConnectThread::ThreadProc: ri.heRapiInit = 0xD34, m_hrInit = 0x0.
3/24/2006 12:11:51 PM - OnLogIpAddrEx
3/24/2006 12:11:51 PM - CDevicesConn::OnLogIpAddrEx: 175683409
3/24/2006 12:12:22 PM - CConnectThread::Term - Inform backgroun thread to quit.
3/24/2006 12:12:22 PM - CConnectThread::ThreadProc() Calling CeRapiUninit.
3/24/2006 12:12:22 PM - CConnectThread::Term: Before WaitForSingleObject().
3/24/2006 12:12:22 PM - Leaving connect threadproc 0x800704C7
3/24/2006 12:12:22 PM - CConnectThread::Term: After WaitForSingleObject().
Gena
I had the exact same problems as above, but tried everything to try to fix this, and now I just can't explore my "Mobile Device" in Windows Explorer. I have tried more than one PPC too, same problem. However, I can connect to the PPC through EVC++ and debug on the device just fine. Here's everything I did:

- Used windows uninstaller to take out AS 3.8, then installed AS 4.0
- Found that it didn't work for anything, so i used windows uninstaller to remove AS 4 and reinstalled AS 3.8.
- Followed all instructions and suggestions from several online forums, including this one which was the most informative.
- Removed rapi.dll from Windows/system32/ (there is no ceutils.dll on my computer, i searched for it), and there was no rapi.dll in my ActiveSync folder.
- Turned off windows firewall to make sure it wasn't blocking any connections (i'm behind a firewall at work, so i'm not too worried about it for the time being).
- Looked at the wcescomm.log file and here are the lines that concern the issue:

11/03/2005 12:49:32.711 - TCP: ...R.., 192.168.55.101(1055) => 172.16.70.201(1052) Seq=1617643764-1617643764 Ack=3125063 Win=0 Len=40
11/03/2005 12:49:32.971 - CesProxy: recv failed on PPP socket 1052, err = 10054

If you have any info on how to explore mobile devices in windows explorer again, I'd be very grateful.

thanks very much in advance,
kurt
Grey Properjohn
It wasn't the solution to the same problem on my computer. In fact, there was no rapi.dll in my c:\program files\active sync map and copying the one from the system map didn't help. Any other sugestion
Luca Giuffrida
Adolfo, thanks for your reaction.

This is in mine WCESETUP.LOG

Copying static files to C:\WINDOWS\System32\
ceutil.dll - refreshed (ver = 3.8.0.5004)
rapi.dll - refreshed (ver = 3.8.0.5004)

So that’s seems to be OK. I can’t find another problem in this file else then I described before. < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

So I still can use some help
Dj. Benlahrech

I am having the same problem, but it occurred first in AS 3.8. I upgraded to AS 4.0. Unisntalled, reisntalled and the problem went away for about 5 syncs. Uninstalled, reinstalled 4.0 and it wwent away again for about 5 syncs. I do not have the rapi.dll or ceutils.dll under \system32, and copying version 4.1.4841.0 from %temp% to \system32 had no effect.

Below are a couple of excerts from WCSELog.log with the pertinent info:

12/15/2005 08:09:18.363 p(2108) t(2720) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:09:19.719 p(2224) t(1484) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:10:06.586 p(2108) t(4068) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:10:07.194 p(2224) t(1484) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:11:29.581 p(2108) t(3552) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:11:30.392 p(2224) t(1484) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:11:56.373 p(2108) t(2820) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:11:56.732 p(2224) t(1484) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:28:38.803 p(2108) t(3812) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)
12/15/2005 08:28:39.473 p(2224) t(1484) TraceToFile -> ERROR in CRAPIDesktop::EnumDevices : hr = 0x800706ba - RAPIDesktop.cpp(601)

And from WCSECOMM.LOG:

Seq=72182312-72182312 Ack=280465397 Win=0 Len=40
12/15/2005 08:28:40.969 - CesProxy: recv failed on Win socket 990, err = 10054
12/15/2005 08:28:40.969 - CesProxy: Close Win socket 990
12/15/2005 08:28:40.969 - CesProxy: Close PPP socket 990
12/15/2005 08:28:40.969 - TCP: ...R.., 192.168.55.100(1040) => 192.168.55.101(990) Seq=73188547-73188547 Ack=280465397 Win=0 Len=40

Just out of curiosity, what version of rapi.dll are you guys showing Has anyone figured this out yet

Thanks!
OBeckles
the critical services error probably refers to RAPI. Verify the version of RAPI.dll in the windows\system32 directory matches the version in the \program files\Microsoft activesync directory. With the installs, and uninstalls done these may have gotten mixed up.

Also the log files are written to your %temp% directory. Click Start | Run and type %temp% in the run dialog. The files are wcesmgr.log and wcescomm.log.
requiem001
Just happened on this thread and I'm having the same problem. I've tried everything in this thread and still can't explore my mobile device.

Here's a little background as to what I've done so far. Upgraded from AS 3.8 to 4.1. Discovered incompatibility between the old Avantgo client (Pocket IE based) and 4.1 so downgraded back to 3.8 by uninstalling 4.1, manually deleting ceutil.dll and rapi.dll from c:\windows\system32. Resintalled As 3.8. Syncing works fine but I cann't explore. I get to no errors messages. When I click on the Explore button in AS I get the hour glass cursor for a second and then it goes away but no Mobile Device explorer window opens. I looked in the .log files under %temp% and nothing is getting updated in there after the window fails to open.
Rogier van de Roer
Hi People,

Its really Quite interesting readng this thread, it's been by far the most useful so far in troubleshooting the problem i'm having with my PDA. I think I may have a slightly different problem though. I am using active sync 3.8 and can sync with the PDA, but get the error message whenever I try to explore it and cannot install prgrams to the PDA.

There are no error messages in wcesmgr.log but the error message shown in wcesview.log when i try to explore is the following

01/03/2006 16:22:38 - CConnectThread::ThreadProc: Calling CeRapiInitEx().
01/03/2006 16:22:38 - CConnectThread::ThreadProc: ri.heRapiInit = 0x570, m_hrInit = 0x80004005.
01/03/2006 16:22:38 - CConnectThread::ThreadProc() !m_bRPCInited. Calling CeRapiUninit.
01/03/2006 16:22:38 - Connect threadproc retry init RAPI (2) 0x80004005
01/03/2006 16:22:38 - CConnectThread::ThreadProc: Calling CeRapiInitEx().
01/03/2006 16:22:38 - CConnectThread::ThreadProc: ri.heRapiInit = 0x580, m_hrInit = 0x80004005.
01/03/2006 16:22:38 - CConnectThread::ThreadProc() !m_bRPCInited. Calling CeRapiUninit.
01/03/2006 16:22:38 - Connect threadproc retry init RAPI (1) 0x80004005
01/03/2006 16:22:38 - CConnectThread::ThreadProc: Calling CeRapiInitEx().
01/03/2006 16:22:38 - CConnectThread::ThreadProc: ri.heRapiInit = 0xC, m_hrInit = 0x80004005.
01/03/2006 16:22:38 - CConnectThread::ThreadProc() !m_bRPCInited. Calling CeRapiUninit.
01/03/2006 16:22:38 - Connect threadproc failed to init RAPI after several retries 0x80004005
01/03/2006 16:22:38 - Connect threadproc CeRapiInitEx failed 0x80004005
01/03/2006 16:22:43 - Leaving connect threadproc 0x80004005

Obviouly a problem with RAPI somewhere but I have tried deleting the rapi.dll and ceutil.dll and reinstalling to no avail, I have tried disabling the firewall everything I can think of and posts I can find but to no avail. Anyone got any further ideas

Cheers,
Activesync fails to sync after installing vers. 4.0

Answer this question