Ashserv.exe - application error {fixed}

system · 2007-09-14T21:02:22.000Z

I did it the other way around. The smaller one first but I still get the error.

Lisandro · 2007-09-14T21:23:28.000Z

Please, answer Vlk’s question:

Vlk post:10:

Do you get the same message when you run (or restart) the avast service manually? (Control Panel → Administrative Tools → Services).

It’s difficult to guess where the problem could be… maybe troubleshooting route must include disabling providers (one by one) and see if it works… Isn’t anything related into Windows Events or anything more in avast logs?

system · 2007-09-14T21:29:51.000Z

Nothing in my log or anything. I might have to uninstall avast and install avg or something. Thanks

Lisandro · 2007-09-14T21:39:38.000Z

Nogard post:15:

Nothing in my log or anything. I might have to uninstall avast and install avg or something. Thanks

It’s a pity… but I can’t guess what’s wrong…
Please, post the last 100-150 lines of avast log: C:\Program Files\Alwil Software\Avast4\DATA\log\Setup.log

system · 2007-09-14T21:47:56.000Z

Lisandro · 2007-09-14T22:50:25.000Z

Nogard post:17:

14:48:25 vrb/gen License key generated Demo

How many times did you install the Trial version?
How long are you using it?

system · 2007-09-14T23:11:56.000Z

I uninstalled Avast a few times and reinstalled it. I never put in my Registration yet.

I never used the demo version that long. Before I update to the latest version, I didn’t even use the demo when I installed it a 4 weeks ago. I registered it and had no problem. I get message through Avast update that there was a new version out. I tried to update through the updating tool but it wouldn’t let me for some reason. So I down loaded a new version, uninstalled the old version, reboot, cleaned up what was left, reboot and re-installed the new version I started to get the error message.

Lisandro · 2007-09-15T13:56:24.000Z

Nogard post:19:

I didn’t even use the demo when I installed it a 4 weeks ago.

It does not matter if you use (on-demand scanning) but the installation itself is considered as an use (on-access). If you install / uninstall / install again, you will have only 6 days of trial period.
Can you add your Home registration key and see if you can update?

system · 2007-09-15T14:03:55.000Z

Tech™ post:20:

Nogard post:19:

I didn’t even use the demo when I installed it a 4 weeks ago.

It does not matter if you use (on-demand scanning) but the installation itself is considered as an use (on-access). If you install / uninstall / install again, you will have only 6 days of trial period.
Can you add your Home registration key and see if you can update?

Yeah I can update with the key in, it’s asking me to reboot after the update though. I’m going to reboot and see what happens.

Lisandro · 2007-09-15T14:06:25.000Z

Nogard post:21:

Yeah I can update with the key in, it’s asking me to reboot after the update though. I’m going to reboot and see what happens.

Indeed, this should happen after first update…

system · 2007-09-15T14:17:43.000Z

OK, I rebooted and I still get the error message.

Lisandro · 2007-09-15T14:40:03.000Z

Strange… Is there any other security program that could be interfering?
Firewall? HIPS protection?
It could sound stupid, but can’t you try an installation from the scratch:

Uninstall avast from Control Panel first.
Boot.
Use Avast Uninstall for complete uninstallation.
Boot.
Install again the last version.
Boot.
Check and post the results.

system · 2007-09-15T14:46:22.000Z

I have Outpost firewall installed. Should I try shutting that down while I do an install? I got xpsmoker installed along with Spybot s&d, but they don’t run in the background.

Lisandro · 2007-09-15T15:36:00.000Z

Nogard post:25:

I have Outpost firewall installed. Should I try shutting that down while I do an install? I got xpsmoker installed along with Spybot s&d, but they don’t run in the background.

XPSmoker is a tweaker tool, isn’t it?
It won’t be bad if you disable Outpost firewall and test… but, for sure, something is blocking low level activity of avast and you’re receiving an error. The difficult for us is to guess what is doing that…

system · 2007-09-15T15:51:48.000Z

I did all that was said to do in the other post you posted. I even went as far as disabling outpost on startup and I still get the error.

Yes XP Smoker is a tweaking tool. But I have nothing else that is running that could mess with it. I don’t know what it could be.

system · 2007-09-15T21:09:41.000Z

Anyone know if it’s a registry thing? If so what kind? I scanned through what I have running in the background and all I have is Outpost firewall running.

DavidR · 2007-09-15T21:21:11.000Z

Did you try the troubleshooting option I suggested way back when.

DavidR post:7:

Edit: Something I just thought of, that light bulb moment. If you can get in and open the Program Settings, Troubleshooting, check the 'Delay loading of avast services after other system services' and see if that has any effect.

system · 2007-09-15T23:24:22.000Z

DavidR post:29:

Did you try the troubleshooting option I suggested way back when.

DavidR post:7:

Edit: Something I just thought of, that light bulb moment. If you can get in and open the Program Settings, Troubleshooting, check the 'Delay loading of avast services after other system services' and see if that has any effect.

I did that, I still get the error message at the log in screen. But after check marking that, I get to keep avast opened but still not resident though. It has a little red circle with a line through it at the bottom left corner.

DavidR · 2007-09-15T23:57:03.000Z

This is very strange and the first case I have seen on the forums where the usual culprit another AV once removed resolves the issue. For it to also effect other AVs I’m really baffled as to what it could be.

Whilst I have had no issue with outpost pro, that really is the only common denominator other than your OS. Are you using the anti-spyware plug-in in OP Pro, if so I would suggest you disable it and see if that makes any difference.

Before you posted the windows event log entry for this, if you can go to the latest one and see if clicking the for more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp link and see if it does produce more and perhaps more helpful information.

system · 2007-09-16T02:53:27.000Z

DavidR post:31:

This is very strange and the first case I have seen on the forums where the usual culprit another AV once removed resolves the issue. For it to also effect other AVs I’m really baffled as to what it could be.

Whilst I have had no issue with outpost pro, that really is the only common denominator other than your OS. Are you using the anti-spyware plug-in in OP Pro, if so I would suggest you disable it and see if that makes any difference.

Before you posted the windows event log entry for this, if you can go to the latest one and see if clicking the for more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp link and see if it does produce more and perhaps more helpful information.

I turned off the anti spyware program for outpost and still have the error. I clicked on the link in the event veiwer and got this:

Details
Product: Windows Operating System
ID: 7034
Source: Service Control Manager
Version: 5.2
Symbolic Name: EVENT_SERVICE_CRASH_NO_ACTION
Message: The %1 service terminated unexpectedly. It has done this %2 time(s).

Explanation
The specified service could not continue. This service is configured to report the number of failures and, after a specific number of failures are reported, the Service Control Manager will perform the recovery action configured for the specified service.

User Action
For information that can help you identify possible causes for this error, view the WIN32_EXIT_CODE error that SCM encountered. To view the error, at the command prompt, type
sc query service name

I did what it said to do but I get an error saying " the specified services does not exist as a service."

Announcements