Error 101

  • Thread starter Thread starter Anne
  • Start date Start date
A

Anne

Hi--I've been scrolling (no "search"--bummer) through
the install newsgroup discussions and don't see anything
later than July 13 on this error. And I can't find any
clear recommended fix. The beta software was working
GREAT until the upgrade. Since then, I've tried
uninstalling and reinstalling, but no go--same error
101. I'm running XP Pro.

I'm reluctant to "try" some of the "maybe" fixes because
I've already got other problems coming up, for example
RealOne player error messages that I'd never seen before
today.

Hope to hear from someone soon. (One of the July 12 posts
suggested writing directly to Jeff Dillon who is working
on this--done that.) If there's no fix available yet, is
there someway to reinstall the older version? Thanks.
 
I posted the following on July 20 that may help.
It's a workaround until a permanent solution is available
but it works for me.

--------

Hi all,

This may help tackling the error 101 problem and is a
temporary workaround to get the latest build going.
It works on my system, which is running XP Pro SP2.

1) Uninstall build 614 by RMB clicking on the (latest)
MAS MSI file located in <systemdrive:>\Windows\Downloaded
Installations\<MAS dir>
and choosing Uninstall from the menu.
2) Delete any MAS files and directories that remain,
including the MSI files located in
<systemdrive:>\Windows\Downloaded Installations\<MAS dir>
and the gcUncompress.dll file in Windows\System32.
3) Reboot
4) Download the latest build (615) and install it the
usual way.
5) Reboot
6) Run MAS - Error 101 appears
7) Repair build 615 by RMB clicking on the new MAS MSI
file located in <systemdrive:>\Windows\Downloaded
Installations\<MAS dir>
and choosing Repair from the menu.
8) DO NOT reboot when asked
9) Running MAS now works fine (at least it does here)

When you reboot the error 101 problem is back again.
Workaround at this point is following step 7-9 again.

HTH at least some people!

Ron
 
The message to Jeff Dillon was meant to provide data only--replies weren't
provided, I'm afraid.

There are two fixes that I've seen that have sufficient weight behind them
that I'd try each of them. One is from Steve Dodson, Microsoft:
--------------------------------------------------
We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

Please provide feedback if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
----------------------------------------------------------------------------------------
The other is from another forum and has mostly been quoted by plun.

If you can find plun's posts on the subject, that's the best reference, I'm
not spotting them at the moment, and offer this one as perhaps the same
recipe:
http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html





--
 
Bill,

As outlined earlier, both fixes don't work for me.
All my systems running XP work fine with MAS except for
one. The only thing that works is the workaround outlined
in this thread.
Before re-booting all is okay, after re-booting there's
Error 101 until doing a RMB menu > Repair install on the
MAS MSI and without re-booting afterwards.

Also like to note that any build prior to 614/615 worked
without problems.

I am willing to work with MS if I can to solve the issue
as it is currently driving me nuts!
And let's face it, MAS - when running - is quite good!

Ron

-----Original Message-----
The message to Jeff Dillon was meant to provide data only--replies weren't
provided, I'm afraid.

There are two fixes that I've seen that have sufficient weight behind them
that I'd try each of them. One is from Steve Dodson, Microsoft:
--------------------------------------------------
We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

Please provide feedback if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
--------------------------------------------------------- -------------------------------
The other is from another forum and has mostly been quoted by plun.

If you can find plun's posts on the subject, that's the best reference, I'm
not spotting them at the moment, and offer this one as perhaps the same
recipe:
http://castlecops.com/t120958- NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005
..html





--

Hi--I've been scrolling (no "search"--bummer) through
the install newsgroup discussions and don't see anything
later than July 13 on this error. And I can't find any
clear recommended fix. The beta software was working
GREAT until the upgrade. Since then, I've tried
uninstalling and reinstalling, but no go--same error
101. I'm running XP Pro.

I'm reluctant to "try" some of the "maybe" fixes because
I've already got other problems coming up, for example
RealOne player error messages that I'd never seen before
today.

Hope to hear from someone soon. (One of the July 12 posts
suggested writing directly to Jeff Dillon who is working
on this--done that.) If there's no fix available yet, is
there someway to reinstall the older version? Thanks.
Click to expand...


.
Click to expand...
 
I hear you--but I'm not sure Anne has the same precise issue as you.

I also hear you on working with MS. I'll see if they feel they need more
input on this issue--the unusual nature of this beta may mitigate against
that, though.
--

Ron said:
Bill,

As outlined earlier, both fixes don't work for me.
All my systems running XP work fine with MAS except for
one. The only thing that works is the workaround outlined
in this thread.
Before re-booting all is okay, after re-booting there's
Error 101 until doing a RMB menu > Repair install on the
MAS MSI and without re-booting afterwards.

Also like to note that any build prior to 614/615 worked
without problems.

I am willing to work with MS if I can to solve the issue
as it is currently driving me nuts!
And let's face it, MAS - when running - is quite good!

Ron

-----Original Message-----
The message to Jeff Dillon was meant to provide data only--replies weren't
provided, I'm afraid.

There are two fixes that I've seen that have sufficient weight behind them
that I'd try each of them. One is from Steve Dodson, Microsoft:
--------------------------------------------------
We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

Please provide feedback if this is working.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
--------------------------------------------------------- -------------------------------
The other is from another forum and has mostly been quoted by plun.

If you can find plun's posts on the subject, that's the best reference, I'm
not spotting them at the moment, and offer this one as perhaps the same
recipe:
http://castlecops.com/t120958- NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005
.html





--

Hi--I've been scrolling (no "search"--bummer) through
the install newsgroup discussions and don't see anything
later than July 13 on this error. And I can't find any
clear recommended fix. The beta software was working
GREAT until the upgrade. Since then, I've tried
uninstalling and reinstalling, but no go--same error
101. I'm running XP Pro.

I'm reluctant to "try" some of the "maybe" fixes because
I've already got other problems coming up, for example
RealOne player error messages that I'd never seen before
today.

Hope to hear from someone soon. (One of the July 12 posts
suggested writing directly to Jeff Dillon who is working
on this--done that.) If there's no fix available yet, is
there someway to reinstall the older version? Thanks.
Click to expand...


.
Click to expand...
Click to expand...
 
Tried your fix it solution and no go. Still continues to
be functional on husbands start up page but not mine.
Also had multiple "error 1904.module ......." to about 5
to 6 different .dll files. what else is there to do? Help.
 
Back
Top