|
Posted by Paul G. Tobey [eMVP] on February 6, 2006, 11:11 am
Please log in for more thread options Yes, I seem to have been less lucky than some, but luckier than others.
Best I can suggest is to capture the log files from both the device and the
desktop and call support. Tell them early that you have been working with
various MVPs via the newsgroups to fix the problem, that you have the log
files, etc. That may get you past the usual scripted dumb-user debugging
and into something deeper.
Good luck!
Paul T.
> Hi Paul,
>
> I've got the same problem and have followed your instructions to the
> letter
> but I keep loosing the association between my windows mob.5 device and a
> desktop and a laptop (using activesync 4.1).
>
> The problem appears to be that the device doesn't recognise the desktop
> computer when it is reintroduced after having been with the laptop (and
> vice
> versa). I've checked the device name as per your instructions. It seems
> though the that the device doesn't recognise the computer names.
>
> I've tried giving the computers new names, or rolled with the
> automatically
> ascribed ones, and neither works. If I use automatically ascribed names,
> when I return to "windows desktop 1" from laptop ("windows desktop 2") it
> invites me to delete an association - 'because the max number allowed is
> to
> two computers', and then it ascribes the name windows desktop 3 to my
> desktop, and so on and so on..
>
> Would love to see this working,
>
> Kind regards, Mark
>
> "Paul G. Tobey [eMVP]" wrote:
>
>> Yes, I've heard this before. Try the following:
>>
>> 1. Delete any and all partnerships on both PCs.
>>
>> 2. Start with PC #1. Connect the device and establish a partnership.
>>
>> 3. Disconnect device from PC #1. Go to Control Panel, About, the Device
>> ID
>> page. Set the name to something recognizable and *not* what AS has set
>> it
>> to for you. Don't use any punctuation, no spaces, etc. Try to make it
>> as
>> likely to work as possible.
>>
>> 4. Reconnect to PC #1. Make sure that you don't connect to PC #2. AS on
>> PC
>> #1 should recognize the device and should realize that its name has
>> changed
>> and show the new name as the device name. Synchronization should
>> proceed.
>>
>> 5. Disconnect from PC #1 and verify that the device name has not been
>> reset
>> by AS.
>>
>> 6. Connect to PC #2 and establish a partnership. My experience is that
>> AS
>> will again change the device name for you, but let it choose whatever it
>> wants and just roll with it for now.
>>
>> 7. Disconnect from PC #2 and rename the device, if necessary, as in step
>> 3.
>>
>> 8. Reconnect to PC #2 (again, don't connect to PC #1 in the middle), and
>> verify that the new name is recognized. Allow the device sync to
>> proceed.
>>
>> 9. I think that you should be able to connect to either PC now and have
>> it
>> recognize that it has seen the device before.
>>
>> If *any* of the intermediate steps fails, stop right there and report
>> back.
>> It may be something that I've listed wrong and that we can recover from,
>> but
>> if you try to keep going, you'll probably be back at step 1 pretty
>> quick...
>>
>> Paul T.
>>
>> > I'm using Activesync 4.1 and WM5 phone.
>> > I want to setup activesync to synchronise with two computers.
>> > I setup the partnership with the first and it works fine.
>> > I then setup the partnership with the second and it works fine.
>> > If I then go back to the first it doesn't find the partnership that was
>> > previously made and asks to delete one of the partnerships so that it
>> > can
>> > create a new one.
>> > If I delete the first partnership and create a new one it works.
>> > But then when I go back to the second PC again the same thing occurs
>> > and
>> > so on.
>> >
>> > I tried to re-create the problem on two other PC's but they work OK
>> > The main difference is that the two PC's with the problem previously
>> > had
>> > Activesync 3.8 Installed.
>> >
>> > If no one has any ideas (I'm hoping someone will) is there someway to
>> > completely remove all traces of Activesync to start again.
>> >
>>
>>
>>
| 
XML Sitemap