Re: Remote Call Profiler not connecting
- From: "M@ Johnson" <mattj@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 18 Apr 2005 10:07:57 -0700
Hmmm,
Since your other tools connect just fine to the image and just Remote
Call Profiler and Remote Kernel Tracker are affected. It sounds like
perhaps there is some problem with the tools accessing the Event Tracking
sub system (celog). I have a couple of questions to narrow
this down a bit.
Does RCP still connect to which ever Default SDK that is installed with EVC?
Do you have any other tools that are using celog, that perhaps are not
releasing it correctly?
Could you try building your image and turning on profiling on by setting the
env variable IMGPROFILER=1 before building. Then boot the device and check
that celog.clg is put into the flat release directory. This would tell us
if the event tracking subsystem is working or not.
~Thanks,
~M@ J.
--
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only
This posting is provided "AS IS" with no warranties, and confers no rights
"Oskar" <Oskar@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5998146B-6677-4D70-BD4B-61CCC332077F@xxxxxxxxxxxxxxxx
> Hi Matt,
>
> Thanks for the suggestion but corestra is already in the OS. Just in case,
> I've tried deleting it and adding it again but apparently there's a
> dependency with some other(unspecified) component that prevents me from
> removing it.
>
> Anyway, I've done a clean build but the problem remains.
>
> Is there any other component that I should check that it's included in the
> image? Anything else I might try?
>
> Thanks in advance.
>
> Rgds
> Oskar
>
> "M@ Johnson" wrote:
>
>> Hey Oskar,
>>
>> The most common problems with the Remote Call Profiler and headless
>> devices are that the OS Design does not include the string handling
>> corestra
>> component.
>>
>> check out:
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcedebug5/html/wce50conRemoteCallProfiler.asp
>>
>> ~Thanks,
>> ~M@ J.
>>
>> --
>> Please do not send e-mail directly to this alias. This alias is for
>> newsgroup purposes only
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights
>> "Oskar" <oberreteaga@xxxxxxxxxx> wrote in message
>> news:4711023b.0504132314.64400603@xxxxxxxxxxxxxxxxxxxxx
>> > Hi,
>> >
>> > I already posted this on microsoft.public.windowsce.embedded.vc but I
>> > got no anwers since it might have to do with the OS and not with eVC.
>> > In any case, sorry for the crosstalk.
>> >
>> > I'm trying to use Remote Call Profiler (RCF) with eVC 4.0 SP2. The
>> > target device is running a headless 4.20 retail image on an x86 CPU.
>> > However,
>> > when I try to connect, I get the following message:
>> >
>> > "Remote Call Profiler cannot connect to the target device because
>> > ConPMon.exe did not launch correctly on the target device.
>> > Verify that ConPMon.exe downloaded successfully, and then connect to
>> > the target device."
>> >
>> > I've double checked that ConPMon.exe is on the device using Remote
>> > File Viewer (by the way, other remote tools work fine except Remote
>> > Kernel Tracker which cannot connect either). I've also tried RCF on a
>> > different box with eVC 4.0 SP4 and same message appears. I guess it
>> > may
>> > have something to do with the OS image and some missing component but
>> > I
>> > can't imagine which one it is. Also tried release and debug images
>> > with profiling enabled but with no luck.
>> >
>> > I've reviewed the 'WinCe Log' branch in the Event Viewer and, among
>> > the info, three errors appear when launching RCF:
>> >
>> > 12/04/2005 15:20:07 cemgr Error None 1 Not available 2105-11-OSKAR
>> > Process Id: 2368 Thread Id: 2692 Source: Message: No matching files
>> > found for package ObjSvr.exe
>> >
>> > 12/04/2005 15:20:27 CECap Error None 1 Not available 2105-11-OSKAR
>> > Process Id: 3372 Thread Id: 3260 Source: Message: CDevice.Launch
>> > failed trying to launch \windows\ConPMon.exe.
>> > hr=0x80040002
>> >
>> > 12/04/2005 15:20:29 tltcpip Error None 1 Not available 2105-11-OSKAR
>> > Process Id: 2368 Thread Id: 3440 Source: Message: -ReadBytes Error
>> > reading packet size. recvsize() returned nRecv=-1 Last socket
>> > Error=10004. Returning hr=80040004
>> >
>> > I can post the full log if you want me to.
>> >
>> > Any help will be appreciated.
>> >
>> > Regards
>> > Oskar
>>
>>
>>
.
- Follow-Ups:
- Re: Remote Call Profiler not connecting
- From: Oskar
- Re: Remote Call Profiler not connecting
- References:
- Remote Call Profiler not connecting
- From: Oskar
- Re: Remote Call Profiler not connecting
- From: M@ Johnson
- Re: Remote Call Profiler not connecting
- From: Oskar
- Remote Call Profiler not connecting
- Prev by Date: USB RNDIS Function Driver-XP-.inf file and name of .sys Drivers
- Next by Date: Re: RNDIS Questions?
- Previous by thread: Re: Remote Call Profiler not connecting
- Next by thread: Re: Remote Call Profiler not connecting
- Index(es):
Relevant Pages
|
