No connection could be made because the target machine actively refused it.

ugh. I’ve had Avast’s ADNM working fine on this network for about 6 months now, maybe longer. Today, I was going to see if I could force the newest update out to a few computers so the kids don’t get confused, and ADNM wouldn’t let me login.

It’s installed on a Windows 2000 Advanced server box (SP4).

In the AMS Maintenance Tool, the SQL Connection test works fine (test says, “Database connection OK!”), the license file is set to expire on May 26, 2010 (issued Mar 26, 2008), and the certificate expires 3/31/2010.

I’ve tried to recopy my license.dat file from a backup folder, and that didn’t help.

My “Avast Management Server” service is running and set to automatic, although I do have a problem when I try to stop or restart that service. It gets stuck on, “Stopping Service.” Then I have to use process explorer to kill it, or reboot the server to get it started again.

I’ve had this event in my log, but I don’t know if it’s related:

Event Type: Warning
Event Source: SQLBrowser
Event Category: None
Event ID: 3
Date: 1/7/2009
Time: 2:33:37 PM
User: N/A
Computer: SERVER1
Description:
The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.

This is the only even I’ve seen in the log that has anything to do with avast:

Event Type: Information
Event Source: SQLAgent$AVAST
Event Category: Service Control
Event ID: 101
Date: 1/7/2009
Time: 2:33:53 PM
User: N/A
Computer: SERVER1
Description:
SQLServerAgent service successfully started.

I don’t know where to look for more logs.

Can anyone point me to the next step?

Well, I was looking around some more, and under “C:\Program Files\Microsoft SQL Server\MSSQL$AVAST\LOG” I have this error file:

2009-01-07 12:38:23.10 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)

2009-01-07 12:38:23.14 server Copyright (C) 1988-2002 Microsoft Corporation.
2009-01-07 12:38:23.14 server All rights reserved.
2009-01-07 12:38:23.14 server Server Process ID is 1088.
2009-01-07 12:38:23.14 server Logging SQL Server messages in file ‘C:\Program Files\Microsoft SQL Server\MSSQL$AVAST\LOG\ERRORLOG’.
2009-01-07 12:38:23.29 server SQL Server is starting at priority class ‘normal’(2 CPUs detected).
2009-01-07 12:38:24.76 server SQL Server configured for thread mode processing.
2009-01-07 12:38:24.87 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2009-01-07 12:38:25.75 spid2 Starting up database ‘master’.
2009-01-07 12:38:27.81 server Using ‘SSNETLIB.DLL’ version ‘8.0.2039’.
2009-01-07 12:38:27.81 spid5 Starting up database ‘model’.
2009-01-07 12:38:27.90 spid2 Server name is ‘SERVER1\AVAST’.
2009-01-07 12:38:27.90 spid2 Skipping startup of clean database id 4
2009-01-07 12:38:27.90 spid2 Skipping startup of clean database id 5
2009-01-07 12:38:28.53 spid5 Clearing tempdb database.
2009-01-07 12:38:28.56 server SQL server listening on Shared Memory.
2009-01-07 12:38:28.56 server SQL Server is ready for client connections
2009-01-07 12:38:33.81 spid5 Starting up database ‘tempdb’.
2009-01-07 12:38:36.79 spid2 Recovery complete.
2009-01-07 12:38:36.79 spid2 SQL global counter collection task is created.
2009-01-07 12:38:40.84 spid51 Starting up database ‘msdb’.
2009-01-07 12:38:51.84 spid51 Using ‘xpsqlbot.dll’ version ‘2000.80.2039’ to execute extended stored procedure ‘xp_qv’.
2009-01-07 12:39:09.70 spid52 Starting up database ‘avast’.
2009-01-07 12:39:11.67 spid52 Starting up database ‘avast’.
2009-01-07 12:39:14.04 spid52 Starting up database ‘avast’.
2009-01-07 14:27:42.39 server SQL Server terminating because of system shutdown.

I’m wondering about the “Skipping startup of clean database #” part. Then it starts up a temp db, and says recovery complete.

I’m a MySQL kinda guy, and don’t really mess with SQL very much, so I don’t know what programs I can use to look at the database and see if there are any other errors.

Does it sound like my database is screwed? Is there a way to repair it, or should I just delete the database and re-configure?

I’m still having this problem. :frowning:

I think I’m going to delete the database and reinstall adnm, because I need to get this up and running, and I have no idea what to do next.

I’ll at least let everyone know how it turned out.

I tried to delete the database and start over. After deleting the database, it said that the service had to be restarted, so I let the AMS Tool try to do that. Of course, it stayed in “Stopping” for quite some time, so I just used process explorer to kill the process. I then created a new database, and attempted to login after making sure that the process was started. It wouldn’t let me log in.

So, I just uninstalled ADNM completely, along with MSDE, and rebooted the server. I’m in the process of re-installing the newest version of ADNM now and it’s updating the mirrors as I type this. Hopefully, I’ll be able to login after this!

Yep, working now.

I’d really like to know why it didn’t let me log in before though…