Error 101

  • Thread starter Thread starter Jacques
  • Start date Start date
J

Jacques

I'am also fighting against Error 101. Solved for a few
days by running setup one more time (Add/Remove + update
does'nt solve anything).
Is there any body who knows how to trap this error and
submit a report to MS?
 
If you run gcasdtserv.exe /register the error should go
away. This is the same error you get when trying to roll
out the application via the MSI package.
 
Hmm - I believe the standard prescription is change, update, and, if that
fails, uninstall, reinstall.

So you just ran setup another time, and installed over the existing app and
that fixed it?

I want to know what is breaking it for all these folks. I tend to suspect
multi-user issues, but nobody is giving steps that caused it to break.
 
Thanks, it seems to work.
But I don't anderstand why MSAS de-register and how to submit the problem to
MS with all the context in order to fix it.
 
Hi,

Happy if I could help solving this issue.
Some details about my computer: XP-home SP2 with all updates (incuding a lot
of optionals). 5 accounts (std) + mine (with admin rights).
Every night, I stop the computer and restart it (usually with my account).
If it's open with my wife's account, nothing wrong appens. I would suspect
update process as the issue is after a lot of days without anything new
(except AV manual update and XP & MSAS auto updates)

My question is "what to do" in order to help if a new crash appens.
 
Here's what to do:

Send an email to (e-mail address removed).

That should reach Jeff Dillon who is actively investigating the Error 101
issue.

He may ask you to send him a log from your machine.

Describe your experience with this issue as you have here.
 
Back
Top