error 101

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

I am getting an error 101. I have tried to reinstall the
software and was unable to fix the problem. i have tried
to repair it and still unable to resolve the issues. The
problem I keep getting is it is unable to register the
dll's. It wont do it during install, uninstall or
activation. I have looked through the newsgroup, however
without a search feature it makes it very difficult and
time consuming. If someone could help me with this issue
it would be greatly apprecitaed. I do like the software
very much so.
 
Paul said:
I am getting an error 101. I have tried to reinstall the
software and was unable to fix the problem. i have tried
to repair it and still unable to resolve the issues. The
problem I keep getting is it is unable to register the
dll's. It wont do it during install, uninstall or
activation. I have looked through the newsgroup, however
without a search feature it makes it very difficult and
time consuming. If someone could help me with this issue
it would be greatly apprecitaed. I do like the software
very much so.
Click to expand...

If you were to subscribe to the newsgroup using OE or the news
reader of your choice, you would have the search facility inherent
in that news reader.

Server:
privatenews.microsoft.com

Account Name:
privatenews\spyware

Password:
spyware

Since you haven't supplied much information we can only make wild
guesses about your problem, so here's my wild guess.<g> Are you
running with Administrator privileges?

Bob Vanderveen
 
I am also getting an "error 101". Since I can't open the
program, I can only give you the version number out of
the main EXE (which is 1.0.0.509) and what I have found
in the error log (shown below).

462::ln 15:The remote server machine does not exist or is
unavailable::GIANTAntiSpywareMain:modMain:Main::05/07/2005
11:21:08 AM:XP:1.0.509
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::05/07/2005
11:21:08 AM:XP:1.0.509
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::05/07/2005
11:21:08 AM:XP:1.0.509
0::ln 0::gcasDtServ not
Authorized.::GIANTAntiSpywareMain:modMain:Main::05/07/2005
11:21:08 AM:XP:1.0.509
462::ln 15:The remote server machine does not exist or is
unavailable::GIANTAntiSpywareMain:modMain:Main::05/07/2005
11:21:10 AM:XP:1.0.509
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::05/07/2005
11:21:10 AM:XP:1.0.509
91::ln 15:Object variable or With block variable not
set::GIANTAntiSpywareMain:modMain:Main::05/07/2005
11:21:10 AM:XP:1.0.509
0::ln 0::gcasDtServ not Authorized, 2nd
try.::GIANTAntiSpywareMain:modMain:Main::05/07/2005
11:21:10 AM:XP:1.0.509

I'm sorry that the post is so big, but I thought that the
contents of the log would help. Also this error only
occured after my computer decided to disable a whole
bunch of serveices on me (which I still haven't figured
out yet). I am logged into the Administrator account
(with full privelages), running Microsoft Windows
Profession (Service Pack 2). Sorry I can't be more
specific with the Windows version, but msinfo won't start
(something to do with the services on my computer).
 
Try this:

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
 
Try downloading the current build .614 from:

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

If that doesn't resolve it, try this fix:

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



--
 
Back
Top