Cannot establish a connection ... anyone else having problems AFTER reinstalling everything?

[Joergen Bech]

Yes, I have read previous posts on the subject, MS knowledgebase
article, etc.

But even after reinstalling everything, I *still* cannot connect to
the device.

I uninstalled everything having anything to do with PocketPC and
VS.Net 2003, then reinstalled in this order:
- ActiveSync 3.7
- eMbedded Visual C++ 4.0 + SP2
- VS.Net 2003 (everything)
- PocketPC 2003 SDK
- MSDN Library April 2003 (everything)

but as I said, still no connection. Tried using a fixed IP address,
tried with and without loopback adapter: Nothing.

The ProxyPorts values in the registry match those of a working
installation on another machine.

Note: Yes, it did work at some point, then gave up the ghost after
upgrading ActiveSync (remove old + install new), so there is nothing
wrong with the hardware.

Q1: Has someone gathered a FAQ list concerning this problem?
I really don't feel like reinstalling the whole machine, but would
like to try out any suggestion I might have missed.

Q2: Has anyone else had to give up completely, even after reinstalling
VS.Net?

Q3: Anyone know if Microsoft is working on an official fix for this
problem? I am sure that they realize that reinstalling VS.Net is not a
satisfactory answer in the long run(?)

TIA,

Joergen Bech

 

[Shaun Wilde]

I had this yesterday with my 2003 and I rembered the trick of uninstalling
the smartdevices support in 2003 for C# and VB and then reinstalling
that did the trick

Shaun

 

[Joergen Bech]

Yes, I heard about that one too. But as I said, this was a complete
reinstallation.

But just for the sake of it, I removed and reinstalled smartdevice
support - again without luck.

Regards,

Joergen Bech

 

[Rick Winscot]

Joergen,

If you are using WM2003 and have installed an applications on your handheld
that uses the new VB Runtimes... VS .NET may not be able to connect to the
device. I have experienced this problem and can duplicate it reliably. The
only way that I can restore the connection to the device is to perform a
hard reset on your handheld.

Can you detail any other software that is installed on your handheld?

Rick Winscot
rickly@zyche dot com

 

[jose baldner [Msft]]

Hi Joergen,

1 - Did Active Sync still works?
2 - Your Os is PPC 2003, What's your device Ipaq?
3 - Could you check if after you try to connect you get
conmanclient.exe present on the device's \Windows folder?

Thanks,
Jose Baldner [MS]

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Rick Winscot" <[email protected]>
| References: <[email protected]>
| Subject: Re: Cannot establish a connection ... anyone else having
problems AFTER reinstalling everything?
| Date: Mon, 25 Aug 2003 10:25:21 -0600
| Lines: 60
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: 205.127.17.116
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:31895
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| Joergen,
|
| If you are using WM2003 and have installed an applications on your
handheld
| that uses the new VB Runtimes... VS .NET may not be able to connect to the
| device. I have experienced this problem and can duplicate it reliably.
The
| only way that I can restore the connection to the device is to perform a
| hard reset on your handheld.
|
| Can you detail any other software that is installed on your handheld?
|
| Rick Winscot
| rickly@zyche dot com
|
|
| "Joergen Bech @ post1.tele.dk>" <jbech<NOSPAMNOSPAM> wrote in message
| | >
| > Yes, I have read previous posts on the subject, MS knowledgebase
| > article, etc.
| >
| > But even after reinstalling everything, I *still* cannot connect to
| > the device.
| >
| > I uninstalled everything having anything to do with PocketPC and
| > VS.Net 2003, then reinstalled in this order:
| > - ActiveSync 3.7
| > - eMbedded Visual C++ 4.0 + SP2
| > - VS.Net 2003 (everything)
| > - PocketPC 2003 SDK
| > - MSDN Library April 2003 (everything)
| >
| > but as I said, still no connection. Tried using a fixed IP address,
| > tried with and without loopback adapter: Nothing.
| >
| > The ProxyPorts values in the registry match those of a working
| > installation on another machine.
| >
| > Note: Yes, it did work at some point, then gave up the ghost after
| > upgrading ActiveSync (remove old + install new), so there is nothing
| > wrong with the hardware.
| >
| > Q1: Has someone gathered a FAQ list concerning this problem?
| > I really don't feel like reinstalling the whole machine, but would
| > like to try out any suggestion I might have missed.
| >
| > Q2: Has anyone else had to give up completely, even after reinstalling
| > VS.Net?
| >
| > Q3: Anyone know if Microsoft is working on an official fix for this
| > problem? I am sure that they realize that reinstalling VS.Net is not a
| > satisfactory answer in the long run(?)
| >
| > TIA,
| >
| > Joergen Bech
| >
| >
| >
|
|
|

 

[Joergen Bech]

1. Yes, ActiveSync still works
2. iPaq 3870 running PocketPC 2002 (not 2003)
3. Yes, ConManClient.exe is present in the \Windows folder

I have tried a hard reset without luck.

No programs installed, except for some .Net test programs (not
running, though, - I have checked the memory). Oh, and a trial
version of SOTI PocketController.

It has to be said that if I move the iPaq+cradle to two other
machines running exactly (I suppose) the same development
tools (.Net 2003, etc), there are no problems whatsoever.
I installed those machines myself, so I know that the same
installers and install order was used.
But those machines are not permanently accessible to me
(dedicated to other uses/users). The problem seems to be
only with my development machine (Dell Inspiron 5000e).
I suppose I should get another development machine.
A PIII-600 really isn't that well suited for .Net development
of any kind (opinions, anyone?), but for now, I would like
to get the connection stuff to work. It will most likely be a
couple of months before I upgrade - and even then, I might
run into the same problem.

Regards,

Joergen Bech

Hi Joergen,

1 - Did Active Sync still works?
2 - Your Os is PPC 2003, What's your device Ipaq?
3 - Could you check if after you try to connect you get
conmanclient.exe present on the device's \Windows folder?

Thanks,
Jose Baldner [MS]

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Rick Winscot" <[email protected]>
| References: <[email protected]>
| Subject: Re: Cannot establish a connection ... anyone else having
problems AFTER reinstalling everything?
| Date: Mon, 25 Aug 2003 10:25:21 -0600
| Lines: 60
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: 205.127.17.116
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:31895
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| Joergen,
|
| If you are using WM2003 and have installed an applications on your
handheld
| that uses the new VB Runtimes... VS .NET may not be able to connect to the
| device. I have experienced this problem and can duplicate it reliably.
The
| only way that I can restore the connection to the device is to perform a
| hard reset on your handheld.
|
| Can you detail any other software that is installed on your handheld?
|
| Rick Winscot
| rickly@zyche dot com
|
|
| "Joergen Bech @ post1.tele.dk>" <jbech<NOSPAMNOSPAM> wrote in message
| | >
| > Yes, I have read previous posts on the subject, MS knowledgebase
| > article, etc.
| >
| > But even after reinstalling everything, I *still* cannot connect to
| > the device.
| >
| > I uninstalled everything having anything to do with PocketPC and
| > VS.Net 2003, then reinstalled in this order:
| > - ActiveSync 3.7
| > - eMbedded Visual C++ 4.0 + SP2
| > - VS.Net 2003 (everything)
| > - PocketPC 2003 SDK
| > - MSDN Library April 2003 (everything)
| >
| > but as I said, still no connection. Tried using a fixed IP address,
| > tried with and without loopback adapter: Nothing.
| >
| > The ProxyPorts values in the registry match those of a working
| > installation on another machine.
| >
| > Note: Yes, it did work at some point, then gave up the ghost after
| > upgrading ActiveSync (remove old + install new), so there is nothing
| > wrong with the hardware.
| >
| > Q1: Has someone gathered a FAQ list concerning this problem?
| > I really don't feel like reinstalling the whole machine, but would
| > like to try out any suggestion I might have missed.
| >
| > Q2: Has anyone else had to give up completely, even after reinstalling
| > VS.Net?
| >
| > Q3: Anyone know if Microsoft is working on an official fix for this
| > problem? I am sure that they realize that reinstalling VS.Net is not a
| > satisfactory answer in the long run(?)
| >
| > TIA,
| >
| > Joergen Bech
| >
| >
| >
|
|
|

 

[Joergen Bech]

1. VS.Net 2003 Final (from MSDN subscription download)

2. "Cannot establish a connection. Be sure the device is physically
connected to the development computer."

3. Tried a hard reset. Still no change. I can browse the device using
"Explore" in ActiveSync 3.7 - and I can browse the Internet on the
device through my notebook internet connection (device connected
to notebook using USB)

4. The registry keys/values specified are present.

Is there anything I can do to provide you with more information? Any
tools I can use to monitor/analyze the traffic between ActiveSync and
the device?

As I said in an earlier post, I can take the cradle/device to another
machine and everything works fine (hard reset or no hard reset), so
I have the opportunity to compare a working system with a non-working
one, provided I know what to look for.

Regards,

Joergen Bech

 

[Joergen Bech]

1. Yes, it says "Deploying to Pocket PC Device using TCP Connect
Transport", the statusbar says "Establishing connection", and then it
fails. F5 and CTRL-F5 both. On the working VS.Net 2K3 installations
I often get a deployment error the first time I press F5, but then I
(always) just need to press F5 again, and everything works the second
time around. I usually set the main form MinimizeBox property to False
in order not to have a previous build running when I try to deploy a
new one.

2. ConManClient.exe seems to have gone AWOL since the last hard reset
of the device (it was definitely there before, and as I said, the
device
worked perfectly when connected to two other machines).
Connecting it to a working .Net 2K3 installation and deploying a
small test project to it brought conmanclient.exe back - though this
did not make the device work on the "broken" installation

When I click conmanclient.exe, I am presented with two dropdown
boxes: One containing a single (non-editable) "TCP_ACCEPT__"
entry, the other an editable "5656" port.

3. Device Name = Pocket PC Device
Transport = TCP Connect Transport
- [ ] Use fixed port number (disabled)
- (*) Obtain an IP address automatically using ActiveSync
Startup server = ActiveSync Startup Provider

(same as the working installation)

Regards,

Joergen Bech

 

[Peter Woerner]

Hi Joergen,

did you get your problem solved in the meantime?
I am having the same problem and start getting crazy...

TIA
Peter

 

[Joergen Bech]

The registry settings are fine. As for the device /windows directory,
I presume this is okay too as the device works on another development
system. Only thing I haven't tried is a full reinstall with ActiveSync
3.5 instead of 3.7. Maybe I'll try that, but it really ought not to be
necessary.

Good to hear that you got it up and running.

Regards,

Joergen Bech

 

[Carl Dumas]

Hi Joergen,
I'm having exactly the same problem, its the second time its happened.
The first time I had to reinstall the entire os to get it to work
again. Now I'm under the gun and have to get a project done by friday
and this happens again.

have you made any progress with the problem, have you heard back from
MS.
thanks,
carl

 

[Joergen Bech]

Joergen,
Could you run this tool and send me the outputs?
See datails on the readme file
Thanks,
Jose Baldner [MS]

My humble apologies. I gave up on the machine (for the time being) and
had not seen your post until now, as I have not been monitoring this
group/thread for a week or so. I thought the thread had died.

But since you went to all this trouble, here are the results (below).

I noticed this line in the dbmon.exe output:
"You may need to run DelDesktopCryptKey to fix the problem."
and a couple of lines before:
"System.Net.Sockets.SocketException: A non-blocking socket operation
could not be completed immediately"
which seems to be the first problem it runs into.
I can see from this recent post
http://groups.google.dk/[email protected]&rnum=1
that some people (at least/last) are getting nearer a solution.

Regards,

Joergen Bech

Results:
--------------------------------------------
1. Output from dbmon.exe:
---snip---
176: Checking: C:\Documents and Settings\jbe\Local
Settings\Application Data\Mic
rosoft\VisualStudio\devices\7.1\conman_ds_platform.xsl
176: Checking: C:\Documents and Settings\jbe\Local
Settings\Application Data\Mic
rosoft\VisualStudio\devices\7.1\conman_ds_package.xsl
176: Checking: C:\Documents and Settings\jbe\Local
Settings\Application Data\Mic
rosoft\VisualStudio\devices\7.1\conman_ds_transport.xsl
176: Checking: C:\Documents and Settings\jbe\Local
Settings\Application Data\Mic
rosoft\VisualStudio\devices\7.1\conman_ds_startup.xsl
176: Versions OK.
176: server version : 7.10.3088.0
176: PublicTransport.Initialize() entered
176: rapiinit returned success.
176: System.Net.Sockets.SocketException: A non-blocking socket
operation could n
ot be completed immediately
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at PublicTransport.EstablishConnection()
176: Could not create a new key container.
176: *** You may need to run DelDesktopCryptKey to fix the problem.
176: GetUserMachineName:
176: jbe, jbe.JB
176: rapiinit returned success.
176: PublicStartupProvider.lookupCurrentTransport - entering ...
176: PublicStartupProvider.lookupCurrentTransport -
CurrentTransport=tcp_connect

176: PublicStartupProvider.lookupCurrentTransport - exiting
176: looking for : {\Windows\ConManClient.exe}
176: looking for : {C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFr
ameworkSDK\ConnectionManager\Target\wce300\ARM\ConManClient.exe}
176: looking for : {\windows\cmtnpt_tcpaccept.dll}
176: looking for : {C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFr
ameworkSDK\ConnectionManager\Target\wce300\ARM\cmtnpt_tcpaccept.dll}
176: Could not create a new key container.
176: *** You may need to run DelDesktopCryptKey to fix the problem.
176: ERROR DOING Wrap_GetExchangeKey! Analysis:
176: ERROR_INVALID_PARAMETER
176: randomSeed was: 1063619458
176: DropPublicKeyAndUserMachineInfoToFile failure doing
CryptExportKey! Details
follow...
176: ERROR_INVALID_PARAMETER
176: PublicStartupProvider.copyToDevice - copy C:\Documents and
Settings\jbe\Loc
al Settings\Application Data\PubKey.blb to PubKey.blb
176: Caught a bad exception: System.Exception: Error trying to write
PREP inform
ation to device: System.IO.FileNotFoundException: Could not find file
"C:\Docume
nts and Settings\jbe\Local Settings\Application Data\PubKey.blb".
File name: "C:\Documents and Settings\jbe\Local Settings\Application
Data\PubKey
..blb"
at System.IO.__Error.WinIOError(Int32 errorCode, String str)
at System.IO.FileStream..ctor(String path, FileMode mode,
FileAccess access,
FileShare share, Int32 bufferSize, Boolean useAsync, String msgPath,
Boolean bFr
omProxy)
at System.IO.FileStream..ctor(String path, FileMode mode,
FileAccess access)
at PublicStartupProvider.copyToDevice(String localFileName, String
remoteFile
Name)
at PublicStartupProvider.Init(IDevice device, ITransport transport,
IStartup
startupConfig, ITypeToArchitectureMap cpuMap)
at PublicStartupProvider.Init(IDevice device, ITransport transport,
IStartup
startupConfig, ITypeToArchitectureMap cpuMap)
at
Microsoft.VisualStudio.DeviceConnectivity.ConnectionManagerServer.startup(
StartupCheckOption check)
176: finalizing ConnectionManagerServer.
176: disposing server.
176: out: Hangup
176: disposing PublicTransport.
---snip---

2. Output from VSDConnTest.exe:
---snip---
VSDConnTest - Current device is Pocket PC Device
VSDConnTest - Device name is Pocket PC Device
VSDConnTest - Device connection failed
---snip---

3.
- No conmanclient.exe
- No Cmtnpt_TcpAccept.dll
- No \windows\NETCFKEYS\<UserName>.<MachineName>.blb folder/file
(I deleted the whole folder before running the test, as there was only
a single file in it originally)

 

[Joergen Bech]

Running DelDesktopCryptKey.exe (posted in a later thread)
finally fixed the problem.

Regards,

Joergen Bech

---snip---

Joergen,
Could you run this tool and send me the outputs?
See datails on the readme file
Thanks,
Jose Baldner [MS]

---snip---
"You may need to run DelDesktopCryptKey to fix the problem."

---sniiiiip---