Microsoft Discussion Groups

[pcastric]

During the past month or so, I have logged into the Microsoft Discussion Groups website Welcome to Microsoft Discussion Groups which lists various discussion groups.

When I click English>Windows>Windows Update (as an example), I get "Service Temporarily Unavailable - We apologize for this inconvenience, Please try again later" message" which I have done and have received the same error message.

Has anyone heard what is going on with these discussion pages???

Pierre

 

[Anak]

It must be low priority at MS, It seems that it has been going on for quite a while.
This post is from 2009 Error Message - Service Temporarily Unavailable

Check Clif McIrvin's work-around in the last post.

 

[z3r010]

Those pages look like they are from the Microsoft newsgroups which Microsoft closed down over a year ago.

 

[pcastric]

If they closed it down someone at MS should change the message to note that site is closed and therefore not accessible anymore instead of saying check later.

Pierre

 

[niemiro]

If they closed it down someone at MS should change the message to note that site is closed and therefore not accessible anymore instead of saying check later.

Pierre

Yeah, they probably should. Looking at your thread history, I see you have an error 1935 error code. I would definitely put that in the top 3 hardest error codes to solve. Without a shadow of a doubt. Even with a computer in front of them, a lot of VC++/Windows Update experts can't fix that error code.

One of the problems is that that error code has a lot of different sub error codes (1935.1, 1935.2, 1935.3, etc. etc.) all extremely different, with all extremely different solutions. Some of those sub error codes have touch and go solutions, but many have no publically known solution, hence a low success rate.

Bad news, I am afraid!

Richard

 

[pcastric]

Thank you Richard for your comments which the average "joe" can comprehend. For the past month or so, trying to find a solution to my problem has been very very very frustrating. I now realize trying to find a solution would require a programmer/developer to debug the code in order to figure out that is going on which I do not believe can be done remotely.

Because users can utilize the previous version of the blackberry desktop manager, the problem is not a "show stopper" and therefore solving the problem is of a low priority.

Hopefully, the folks at Research in Motion will try to come up with a workaround whereby the next version of the blackberry desktop manager will no longer require the 2008 version of MS Visual C++.

Thank you once again Richard.

Cheers

Pierre