Errors with MS Antispyware Beta 1

H

Herschel

Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?
 
B

Bill Sanderson

Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--
 
H

Herschel Hochman

No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.
 
B

Bill Sanderson

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
..614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

My guess from your original message is that you are on .614, but perhaps I'm
mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.
 
B

Bill Sanderson

Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

Bill Sanderson said:
Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

My guess from your original message is that you are on .614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.
 
H

Herschel

Yes, I am on build .614. I'll try the links you provided
and let you know.
Thanks

-------------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

My guess from your original message is that you are on ..614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.


.
 
G

Guest

Neither of these links helped. I tried them both together
and separately twice.


-----------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

My guess from your original message is that you are on ..614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.


.
 
B

Bill Sanderson

We're in uncharted waters now. Andre DaCosta has been posting what
information is in the program help file--you might look at that--

Open help, click on the search tab, and put "known issues" in the keyword
slot and hit List Topics.

double-click on "Release Notes"--and dig through there.

If uninstalling the program, and deleting the installation folder and all
subfolders, followed by a reboot, login as an administrator, and
reinstallation of the newest build from scratch doen't do the job, I'm at a
loss.
--


Neither of these links helped. I tried them both together
and separately twice.


-----------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

My guess from your original message is that you are on ..614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.


.
 
S

Steve Dodson [MSFT]

How did you install the previous build? What build were you running
previously? Was the install for the previous build automated, was it
installed through a script? Are all users admins on the box?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

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.
Bill Sanderson said:
We're in uncharted waters now. Andre DaCosta has been posting what
information is in the program help file--you might look at that--

Open help, click on the search tab, and put "known issues" in the keyword
slot and hit List Topics.

double-click on "Release Notes"--and dig through there.

If uninstalling the program, and deleting the installation folder and all
subfolders, followed by a reboot, login as an administrator, and
reinstallation of the newest build from scratch doen't do the job, I'm at
a loss.
--


Neither of these links helped. I tried them both together
and separately twice.


-----------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

My guess from your original message is that you are on .614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to
sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

message
Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.


.
 
H

Herschel

Under "Known Issues", the Error 101 is mentioned. I will
try to uninstall and reinstall later this evening and let
you know the results.
Thanks for all your help.

================================
-----Original Message-----
We're in uncharted waters now. Andre DaCosta has been posting what
information is in the program help file--you might look at that--

Open help, click on the search tab, and put "known issues" in the keyword
slot and hit List Topics.

double-click on "Release Notes"--and dig through there.

If uninstalling the program, and deleting the installation folder and all
subfolders, followed by a reboot, login as an administrator, and
reinstallation of the newest build from scratch doen't do the job, I'm at a
loss.
--


Neither of these links helped. I tried them both together
and separately twice.


-----------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test..html


--

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

My guess from your original message is that you are on ..614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to
sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

message
Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.


.


.
 
H

Herschel

I installed the previous build when I received notification
that there was an update. I don't remember if it updated
automatically or whether I went to MS website. Under any
circumstances, if I had to use a website, it would have
been Microsoft. I am sure it was automated. Also, I am the
user and administator for this system.

Is there any suggestion as to the exact location to make
the reinstall?

Thanks

===================================
-----Original Message-----
How did you install the previous build? What build were you running
previously? Was the install for the previous build automated, was it
installed through a script? Are all users admins on the box?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

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.
We're in uncharted waters now. Andre DaCosta has been posting what
information is in the program help file--you might look at that--

Open help, click on the search tab, and put "known issues" in the keyword
slot and hit List Topics.

double-click on "Release Notes"--and dig through there.

If uninstalling the program, and deleting the installation folder and all
subfolders, followed by a reboot, login as an administrator, and
reinstallation of the newest build from scratch doen't do the job, I'm at
a loss.
--


Neither of these links helped. I tried them both together
and separately twice.


-----------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en
My guess from your original message is that you are on .614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to
sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

message
Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.





.


.
 
H

Herschel

Well, I finally solved the problem, at least for myself. No
more Error 101, error.logs and no more delay. I hope it
stays that way.

Apparently, it is not enough to remove the MS Antispyware
program through Add/Remove. I found 123 additional items in
the registry. After removing all traces of MS Antispyware
AND GiantAntispyware, I then reinstalled the program from
the Microsoft website. So far everything works fine.

Thanks for all everyones help.


============================================
-----Original Message-----
How did you install the previous build? What build were you running
previously? Was the install for the previous build automated, was it
installed through a script? Are all users admins on the box?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

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.
We're in uncharted waters now. Andre DaCosta has been posting what
information is in the program help file--you might look at that--

Open help, click on the search tab, and put "known issues" in the keyword
slot and hit List Topics.

double-click on "Release Notes"--and dig through there.

If uninstalling the program, and deleting the installation folder and all
subfolders, followed by a reboot, login as an administrator, and
reinstallation of the newest build from scratch doen't do the job, I'm at
a loss.
--


Neither of these links helped. I tried them both together
and separately twice.


-----------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en
My guess from your original message is that you are on .614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to
sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

message
Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.





.


.
 
B

Bill Sanderson

I've got mixed feelings.

I'm glad you solved your problem, but this is the first such issue that I've
seen that required messing about in the registry at all. I've so far
completely ignored Microsoft Antispyware's registry footprint, and
successfully, I think.

I can't just tell the average user of this forum to root stuff out of the
registry, that's a recipe for disaster.

FWIW, Steve Dodson posted today the the current build shouldn't let the
errors.log file grow beyond 20 megs which is good to hear.

--


Well, I finally solved the problem, at least for myself. No
more Error 101, error.logs and no more delay. I hope it
stays that way.

Apparently, it is not enough to remove the MS Antispyware
program through Add/Remove. I found 123 additional items in
the registry. After removing all traces of MS Antispyware
AND GiantAntispyware, I then reinstalled the program from
the Microsoft website. So far everything works fine.

Thanks for all everyones help.


============================================
-----Original Message-----
How did you install the previous build? What build were you running
previously? Was the install for the previous build automated, was it
installed through a script? Are all users admins on the box?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

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.
We're in uncharted waters now. Andre DaCosta has been posting what
information is in the program help file--you might look at that--

Open help, click on the search tab, and put "known issues" in the keyword
slot and hit List Topics.

double-click on "Release Notes"--and dig through there.

If uninstalling the program, and deleting the installation folder and all
subfolders, followed by a reboot, login as an administrator, and
reinstallation of the newest build from scratch doen't do the job, I'm at
a loss.
--


Neither of these links helped. I tried them both together
and separately twice.


-----------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download and install build
.614 from here:
http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en
My guess from your original message is that you are on .614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't have a link to at
hand--I'll go look for that and post it to this thread.

--


No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to
sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

message
Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.





.


.
 
H

Herschel

I completely agree with your assessment. Without
understanding the Registry, it could become a disaster. I
have found many situations over the years where
reinstalling an earlier registry or manually deleting
certain files would correct a situation. This is especially
true when an update or upgrade was done. It has even
happened in other Microsoft updates. It might be worth
while considering a Restore to an earlier date when things
were going well. When I used the Win98, I would always
export the registry and save it when I knew everything was
working properly. This saved me any number of times.

Thanks
Herschel

======================================
-----Original Message-----
I've got mixed feelings.

I'm glad you solved your problem, but this is the first such issue that I've
seen that required messing about in the registry at all. I've so far
completely ignored Microsoft Antispyware's registry footprint, and
successfully, I think.

I can't just tell the average user of this forum to root stuff out of the
registry, that's a recipe for disaster.

FWIW, Steve Dodson posted today the the current build shouldn't let the
errors.log file grow beyond 20 megs which is good to hear.

--


Well, I finally solved the problem, at least for myself. No
more Error 101, error.logs and no more delay. I hope it
stays that way.

Apparently, it is not enough to remove the MS Antispyware
program through Add/Remove. I found 123 additional items in
the registry. After removing all traces of MS Antispyware
AND GiantAntispyware, I then reinstalled the program from
the Microsoft website. So far everything works fine.

Thanks for all everyones help.


============================================
-----Original Message-----
How did you install the previous build? What build were you running
previously? Was the install for the previous build automated, was it
installed through a script? Are all users admins on the box?

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

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.
We're in uncharted waters now. Andre DaCosta has been posting what
information is in the program help file--you might look at that--

Open help, click on the search tab, and put "known issues" in the keyword
slot and hit List Topics.

double-click on "Release Notes"--and dig through there.

If uninstalling the program, and deleting the installation folder and all
subfolders, followed by a reboot, login as an administrator, and
reinstallation of the newest build from scratch doen't do the job, I'm at
a loss.
--


Neither of these links helped. I tried them both together
and separately twice.


-----------------------------------
-----Original Message-----
Try these, courtesy of plun.

Let me know what works--I don't want to be posting the old
link if one of
these is more effective.

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

http://castlecops.com/t119717-Error_101_Possible_Workaround_Please_Test.html


--

in message
Are you on build .614?

(see help, about.)

If not, I would uninstall the current build and download
and install build
.614 from here:

http://www.microsoft.com/downloads/...A2-6A57-4C57-A8BD-DBF62EDA9671&displaylang=en

My guess from your original message is that you are on
.614, but perhaps
I'm mistaken.

There's a third-party fix for this issue that I don't
have a link to at
hand--I'll go look for that and post it to this thread.

--

"Herschel Hochman" <[email protected]>
wrote in message

No, this did not work. There is no change. Ignoring the log
file which is an annoyance, the splash screen of Beta 1 MS
Antispyware comes up and indicates "Loading", followed by
"Starting Engine" and remains on the screen for many
minutes. This is followed by the Error 101 message.

Checking the Administrative tool change, it is now
"Administrators Group".

I have XP Professional.

Where do I go from here?

==========================================
-----Original Message-----
Try this fix for Error 101.

Please ignore the log file, unless it grows quickly to
sizes in the
megabytes to gigabytes range.
--------------------------------------------------------------------------
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.




--

message
Ever since upgrading, I have had a problem with the
Microsoft AntiSpyware Beta 1. Each time I start up my
Windows XP PC, it takes forever for the MS AntiSpyware
program to load and start. Sometimes, it never completes
the Start process. I always receive an error message that
says "encountered Error 101". In addition, I always
receive
an errors.log on notepad similar to the following:

429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:07:09
AM:XP:1.0.501
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:07:09 AM:XP:1.0.501
429::ln 15:ActiveX component can't create
object::GIANTAntiSpywareMain:modMain:Main::7/9/2005
7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::7/9/2005 7:09:11
AM:XP:1.0.501


Can anyony tell me how to solve this problem?


.





.


.


.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top