Big problem!

[Helge]

I have a big problem with Msas.
When I open the main program the System Summery
says 'protected' but all the checkpoints further down
shows only questionmarks.

Last Spyware Scan -> You have not run a scan yet!
Last Spyware Scan results -> You have not run a scan yet!
Spyware Scan Schedule -> Jan. 1, 2004 12:00:00 AM
Realtime protection -> Active
Spyware Definitions -> 00/00/0000 (version 12)
AntiSpyware AutoUptater -> Active

The message center has this important message: |b|MCText.
If I click on the link below a blank page shows.

All the checkpoints in the summary list have question
marks in front of them, even the ones that says active.

If I try to check my agents it says on some that they are
inactive but if I try to activate it the program just
stops working. Pluss the list of agents is not showing
anything.


Here is what I have tried:

1. Ran Virusscans with latest defs. Tried several
different online scans plus Symantec Corporate 9.0 with
definition file version 10.02.2005 rev. 8.
--Nothing showed up

2. Ran "The cleaner" troyan scanner with the latest defs.
--Nothing showed up

3. Ran spyboot and Lavasoft Ad-aware.
--Only Cookies were detected.

4. Uninstalled MSAS from "Add/remove" program. Deleted
every file on my harddrive I could find that was related
to MSAS even the .msi file. Removed all referenses to
MSAS in the register using the search strings 'antis' -
'giant' and 'gcAS'

5. Restarted my computer and downloaded a new fresh
installation file from Microsoft and even scanned it for
virus. Installed it.

When I open the main program again it is the same:-(

My scheduled scan seems to be working.

Anyone that can help me with this?

Thank you!

 

[Bill Sanderson]

In the folder where Microsoft Antispyware is installed is a log
file--errors.log.

Sometimes, this log file contains lines referencing a particular .DLL or
..OCX file which isn't getting registered correctly. Do you see such
references in this file?

If so--post just those bits of the file.

 

[Helge]

This is the error log
----
48::ln 5:Error in loading
DLL::GIANTAntiSpywareMain:frmStartupWizard:LoadStep::13.02
..2005 13:31:00:XP:1.0.501
48::ln 5:Error in loading
DLL::GIANTAntiSpywareMain:frmStartupWizard:LoadStep::13.02
..2005 13:31:01:XP:1.0.501
48::ln 5:Error in loading
DLL::GIANTAntiSpywareMain:frmStartupWizard:LoadStep::13.02
..2005 13:31:01:XP:1.0.501
48::ln 0:Error in loading
DLL::gcasServ:modMain:Main::13.02.2005 13:31:02:1.0.501
48::ln 20:Error in loading
DLL::GIANTAntiSpywareMain:frmStartupWizard:LoadStep::13.02
..2005 13:31:31:XP:1.0.501
91::ln 22:Object variable or With block variable not
set::GIANTAntiSpywareMain:frmStartupWizard:LoadStep::13.02
..2005 13:31:31:XP:1.0.501
91::ln 23:Object variable or With block variable not
set::GIANTAntiSpywareMain:frmStartupWizard:LoadStep::13.02
..2005 13:31:31:XP:1.0.501
48::ln 70:Error in loading
DLL::GIANTAntiSpywareMain:modMain:Main::13.02.2005
13:31:31:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlMain:LoadData::13.02.2005
13:31:32:XP:1.0.501
48::ln 70:Error in loading
DLL::GIANTAntiSpywareMain:modMain:Main::13.02.2005
13:32:52:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlMain:LoadData::13.02.2005
13:32:53:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlMain:LoadData::13.02.2005
13:33:31:XP:1.0.501
48::ln 70:Error in loading
DLL::GIANTAntiSpywareMain:modMain:Main::13.02.2005
13:41:45:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlMain:LoadData::13.02.2005
13:41:46:XP:1.0.501
48::ln 70:Error in loading
DLL::GIANTAntiSpywareMain:modMain:Main::13.02.2005
15:16:20:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlMain:LoadData::13.02.2005
15:16:20:XP:1.0.501
48::ln 0:Error in loading
DLL::gcasServ:modMain:Main::13.02.2005 16:47:52:1.0.501
48::ln 70:Error in loading
DLL::GIANTAntiSpywareMain:modMain:Main::13.02.2005
16:49:54:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlMain:LoadData::13.02.2005
16:49:55:XP:1.0.501
48::ln 0:Error in loading
DLL::gcasServ:modMain:Main::13.02.2005 16:57:53:1.0.501
48::ln 0:Error in loading
DLL::gcasServ:modMain:Main::13.02.2005 17:00:59:1.0.501
48::ln 0:Error in loading
DLL::gcasServ:modMain:Main::13.02.2005 17:11:36:1.0.501
48::ln 70:Error in loading
DLL::GIANTAntiSpywareMain:modMain:Main::13.02.2005
17:22:50:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlMain:LoadData::13.02.2005
17:22:51:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlIERestore:lnkChangeSetting_Cl
ick::13.02.2005 17:23:23:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlIERestore:lnkChangeSetting_Cl
ick::13.02.2005 17:23:33:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlIERestore:lnkRestore_Click::1
3.02.2005 17:23:37:XP:1.0.501
48::ln 0:Error in loading
DLL::GIANTAntiSpywareMain:ctlIERestore:lnkRestore_Click::1
3.02.2005 17:23:39:XP:1.0.501
----------

 

[Helge]

But there is no file--errors.log
Just errors.log

-----Original Message-----
In the folder where Microsoft Antispyware is installed is a log
file--errors.log.

Sometimes, this log file contains lines referencing a particular .DLL or
..OCX file which isn't getting registered correctly. Do you see such
references in this file?

If so--post just those bits of the file.
--
FAQ for Microsoft Antispyware:
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm




.

 

[Helge]

Should maybe also include that when I first was
installing MSas I had no problems with it.
I run XP SP2 with all newest patches.
Can't really say when the problem occured but the only
change I can remember doing was installing icq 5 (now
removed)

 

[Bill Sanderson]

I'm stumped I'm afraid (this is an American expression the origin of which
I'm having trouble imagining, but it means I don't have any idea what to
suggest to fix this!)

 

[Bill Sanderson]

So--today I'll give the knee-jerk respons of suggesting trying the new build
available at the download site, and seeing how effective that is.

I would recommend uninstalling, deleting the installation subdirectory, and,
in addition, stopping as many non-microsoft services as possible for the
duration of the install. And perhaps crossing fingers or whatever
appropriate good luck superstitions you'd care to throw in!