Outlook Connectory - Synch Error Messages

[Guest]

Hello,

We are frustrated enough at this point that we have quit using Outlook.
We're moving on to Thunderbird to avoid the hassles of Outllok 2007 with
Vista and Outlook Connector.

Does anyone in Microsoft Land actually know whats going on out on the web
relative to these problems? Go to Google and type in "Folder Collection Sync
Key" and see whats going on.

We use Vista, Outlook 2007, Outlook Connector, OfficeLive and since August
14 we have registered 4,571 errors messages that look like this:

The following issues occured while synchronizing with the server:
Folder Collection Sync Key: 0{8098095B-A7A2-464A-9476-79DD312D1011}11
Message Collection Sync Key: 0{FE957736-1BE7-4089-BE52-7B6C03960004}11
Network operation failed

We run into problems with the connector loosing its connection and requiring
repeated logins over and over again. Sometimes all at the same time in a
matter of seconds. If you lose the connection re-establish it when I'm ready
or figure out why the connection keeps timing out. We're not the only ones
with this connector problem.

The folks at OfficeLive are useless, Micro$oft wants money each time you
call them for anything, the problems are mounting in the market and there
doesn't seem to be any end in sight.

We'll come back to OfficeLive, Outlook 2007 and Vista in a couple of years
when the problems are better worked out.....probably just in time for
something new to the market again. Meantime, we'll fuss with Firefox,
Thunderbird and the MAC.

Later.

 

[F. H. Muffman]

Hello,

We are frustrated enough at this point that we have quit using Outlook.
We're moving on to Thunderbird to avoid the hassles of Outllok 2007 with
Vista and Outlook Connector.

Does anyone in Microsoft Land actually know whats going on out on the web
relative to these problems? Go to Google and type in "Folder Collection
Sync
Key" and see whats going on.

We use Vista, Outlook 2007, Outlook Connector, OfficeLive and since August
14 we have registered 4,571 errors messages that look like this:

The following issues occured while synchronizing with the server:
Folder Collection Sync Key: 0{8098095B-A7A2-464A-9476-79DD312D1011}11
Message Collection Sync Key: 0{FE957736-1BE7-4089-BE52-7B6C03960004}11
Network operation failed

We run into problems with the connector loosing its connection and
requiring
repeated logins over and over again. Sometimes all at the same time in a
matter of seconds. If you lose the connection re-establish it when I'm
ready
or figure out why the connection keeps timing out. We're not the only
ones
with this connector problem.

The folks at OfficeLive are useless, Micro$oft wants money each time you
call them for anything, the problems are mounting in the market and there
doesn't seem to be any end in sight.

We'll come back to OfficeLive, Outlook 2007 and Vista in a couple of years
when the problems are better worked out.....probably just in time for
something new to the market again. Meantime, we'll fuss with Firefox,
Thunderbird and the MAC.

Later.

Pardon me for sounding rude, but, are you actually looking for help or just
venting?

I mean when you start off with 'We've stopped using Outlook', I don't know
why I'd bother reading anything else.

 

[Guest]

This response is a bit of everything. Its venting because of all the
frustrations involved:
- the man-power/labor that goes into trying to figure all this out that
helps to fix these problems that Microsoft does not pay for - yet they will
charge for their time!

- its the fact that a product(s) is put to market that requires all this
fixing and doesn't work

- its trying to make someone at Microsoft aware of this issue that seems to
be prevalent if you just do a simple search at Google.

- its looking for someone that may by the off chance have seen this problems
and knows how to fix it.

What is overall amazing to me is anytime there is a problem with a Microsoft
product, if you do a search on the web you will find forums upon forums of
people identifying their problems, working together to find a solution, and
if you consider the man-power that goes into these problems you just want to
scream at Microsoft. it is impossible to think that this sort of software
development can continue into the future.

 

[F. H. Muffman]

This response is a bit of everything. Its venting because of all the
frustrations involved:
- the man-power/labor that goes into trying to figure all this out that
helps to fix these problems that Microsoft does not pay for - yet they
will
charge for their time!

- its the fact that a product(s) is put to market that requires all this
fixing and doesn't work

a) It works for me.
b) No matter how much you test a piece of software, it will have bugs.
Deal with it. Stop letting it bug you quite so much.

- its trying to make someone at Microsoft aware of this issue that seems
to
be prevalent if you just do a simple search at Google.

As I say below, I wouldn't trust what you see on Google to be an accurate
count as to how prevalent an issue is.

- its looking for someone that may by the off chance have seen this
problems
and knows how to fix it.

What is overall amazing to me is anytime there is a problem with a
Microsoft
product, if you do a search on the web you will find forums upon forums of
people identifying their problems, working together to find a solution,
and
if you consider the man-power that goes into these problems you just want
to
scream at Microsoft. it is impossible to think that this sort of software
development can continue into the future.

Well, on the one hand, no one posts to say 'Hey, everyting is working fine.'

And, on the other hand, note that many forums slurp from USENET. So, this
one post to this newsgroup might come up as 10 pages of Google hits.

As for 'Micro$oft' wanting money every time you call, no they don't. Ask
for a case number. Tell them you have an existing case and give them the
number.