cant update expired version

[Guest]

Bill--

To answer you question, I saved the download to my desktop as suggested and
ran it from there. I have literally tried *everything* that was suggested in
this newsgroup without success. Is MS aware of this dilemma and where do I go
from here?

Frustrated to say the least,
--Alan

 

[Bill Sanderson]

I don't have any information about what Microsoft is aware of--they've got
quite a bit on their plate, in terms of anti-malware and security-related
issues at the moment, and I've not been bugging them. OTOH, one of their
primary recommendations about the current security issue is to use Microsoft
Antispyware, but they are providing no support for those with installation
issues.

I'm pretty much out of ideas on this one. I guess we could step back and
get precise sizes and checksums for both .615 downloads and .701 downloads
and make absolutely certain which one you have.

So--what you are saying is that you went to MajorGeeks--saw a web page which
had an appropriate date and mentioned build .701

http://www.majorgeeks.com/download4466.html

downloaded to the desktop. Ran that download--and didn't get a simple
upgrade message--followed through on the install and still have the old code
in place?

Maybe it is time to dig out all the old .MSI files from various beta
versions and blow them away.



--

 

[Bill Sanderson]

In another similar thread, a user reported success by switching to IE, when
he had been downloading via Firefox.

If you have an alternative browser available to you, or want to try this
route, it may be worth doing.

One thing that such a switch of browsers does is use a different local
Temporary Internet cache.

--

 

[Guest]

Bill,

Just thought to let you know that I managed to solve my problem by
uninstalling MSAS through Add/Remove programs in the Control Panel, then
deleting all traces of MSAS in Program Files.

I had previously uninstalled MSAS using the uninstaller in Program Files.
Using the Control Panel appears to work. It would appear that an alternative
solution is not to Upgrade or Update MSAS (both failed for me), but to
replace it in its entirety.

Andy

 

[Bill Sanderson]

Thanks!

So--perhaps some "failure to update" cases are akin to the situations in
which the first-run wizard appears with every run, or user settings don't
stick--i.e. some form of permission issue or corruption in the existing
install...

That's good news, I guess--this is a pretty easy prescription--maybe we've
been chasing up the wrong tree here....

--

 

[Bill Sanderson]

One other question:

after deleting the folder--did you use the same downloaded file which had
previously failed to update, or do a new download?

--

 

[Jupiter Jones [MVP]]

Bill;
I had this on a computer I was working on a few days ago.
The final solution for that computer:
Roll the date back before the expiration date.
Open MSAS.
Correct version and expiration date was shown.
Changed date to correct and MSAS worked OK after that.

 

[Guest]

I did a new download just to be sure.

One other question:

after deleting the folder--did you use the same downloaded file which had
previously failed to update, or do a new download?

 

[Bill Sanderson]

Very interesting. Seems to point in the same direction--some settings file
amongst the .GCD's that isn't getting updated correctly.

I'm wondering whether deleting the file--perhaps the gcUserData.gcd file
which has been fingered in the "initial setup wizard runs every startup"
syndrome--will be enough to do the trick. Blow it away and it should be
recreated by the .701 code and all should be well.

Running the date back may have undesirable side effects for some users--not
sure I can point to anything--but if you have date-sensitive betas of any
kind, you might invoke a timebomb.

 

[Bill Sanderson]

Nuts!--so in terms of straight logic I can't be sure that the new download
wasn't different from the previous one, and was what really fixed things.


However--with Jupiter Jones' input, I'm leaning towards this being an issue
with the old files left on the machine--perhaps specifically gcUserData.gcd.

I'd love to have someone who has hasn't resolved this problem yet try simply
deleting that file.


--

 

[Bill Sanderson]

Forgot to say:

Thanks! This, and Andy's experience as recounted here help point away from
the download system and towards something on the local system--which seems
more likely, and also a lot easier to fix.