Still no access - any updates on when we could expect access again?

Regards,

Erik

I can't access the downloads... any idea what's going on?

Nuking my cookies seems to have taken care of it and I'm able to log into my MVLS account and DL files now.

However- this is very frustrating because the error gives no technical detail and I presumed that there was a temporary outage in the login server and waited around for several days...

When you have something that is a *subscription* for a period of time, and there is an outage for *weeks*, that sounds like stealing to me.

I'm tired of waiting for this to work.

It persists. And no one  answered what does it mean. Who knows what is hidden behind the Error 11008? I guess it showld mean something (somebody numbered it keeping some sence in mind). Idiotical advices "to delete all tmp files and cookis" dont play! The same abote "updates".

It is weeks now since I can access MSDN downloads.  And will there be no recourse?  We have paid our thousands.  I do expect that we should have an extension to our subscription or a refund.  I wish to call the question publicly whether Microsoft will provide what we have paid for or make it right.  And I agree that telling us to delete all temp files, when we have already tried that along with updates and reboots on our own is stalling.  I expect a refund or an extension.

When you pay for something and are then locked out for WEEKS you are indeed WAY... past the point of apologies and pleading for patience.

Everyone here know about bugs and upset customers. We know sometimes problems are part of the game but we also know that at some point you have to move past just saying "sorry."

It is time for work around downloads for those who NEED them to make a living. It is time for refunds and extensions and gifts. You are screwing the folks you should treat the best.

It is also time to give folks subscribing to get access to OSes from MS to get every OS: - LIKE HOME SERVER!

If MS wonders why more are developing for Linux this sort of ting is why. We are entering the defining of THEFT here! We are paying for *this*?

More pathetic than MS Bob!

I just got this error and a Google got me here.

The cookie removal solved it for me.

Thanks to this thread I only experienced about 10 minutes inconvenience.  Thanks especially to b/Bob.