ADNM does not install on SBS 2003 SP1

Avast Business Avast Distributed Network Manager
1

Hello,

we had avast on a server for a few months… One day, we could connect to the administration console anymore. So, we decided to try to uninstall and then reinstall… Since that day, we cannot install ADNM anymore… The MSDE failed every time to install.

HELP :slight_smile:

2

Please stay in the same thread. No need to say it twice.

http://forum.avast.com/index.php?board=10;topic=22840.0#msg188682

3

Sorry but this is a different problem on a different computer that’s why I started a second thread…

4

Ok, my mistake. I though it was the same thing.
I’m not much into the server version, but I am sure someone will try to help you soon.

In the mean time, take care

Eddy

5

So, you’re now basically trying to install ADNM from scratch?

If so, please make sure there’re no remaints of the previous installation.

Namely, make sure to delete the following folders

C:\Program Files\ALWIL Software\Management Tools
C:\Program Files\Microsoft SQL Server

(well, delete the latter ONLY IF there’s no other instance of MS SQL Server (or MSDE) installed on that machine, that is, only if it contains just two subdirectories “80” and “MSSQL$AVAST”).

Thanks
Vlk

6

Thanks for your answer.
I allready tried to clean the directories concerning ADNM…
I cannot delete the sql server directory because this is a sbs server and there is many msde installed on it (WUS, Health, Sharepoint)…
Uninstalling all the MSDE is not an option because this is the production server of one of our customers.

I can install other products which come with MSDE, I think the problem is a conflict with the MSDE version that adnm deploy.
I also tried to install it on a sql server 2005 express edition with no result at all… It seems that this is not compatible…

What are the other options ? :slight_smile:

David

7
  1. Yeah, this has traditionally been pain in the a$$. MSDE seems to be quite sensitive about different versions installed at the same time. I was trying to solve a similar problem just a couple of weeks ago.

Do you have any idea which version(s) of MSDE there are, currently?

  1. SQL 2005 Express should work with ADNM. What exactly failed? How did you try to install it?

Thanks
Vlk

8

MSDE is with SP4a in it.

Concerning SQL 2005, avast didn’t see the server during install and I cannot deploy the database on the server.

9

SP4a? What is it? :slight_smile:

10

OK :slight_smile:
So how must I do to check the version number of my differents MSDE ?

11

Still no answer… :frowning:
So I repeat my question how do I check the different MSDE version allready installed on the system ?

Thanks for your help.
David

12

Try e.g. this: http://forums.seattletech.com/viewtopic.php?t=21&

Thanks
Vlk

13

Hello,

thanks for your help.

So the current versions are :
SBSMONITORING : 8.00.761 (SP3a)
SHAREPOINT : 8.00.1100 (SP4)

Sorry for the delay but the method you send me didn’t work since I don’t know the passwords on the different MSDE which are not in trusted mode…

Good thing to know is that the version number is in the registry key :
HKLM\Software\Microsoft\Microsoft SQL Server{$INSTANCE$}\MSSQLServer\CurrentVersion\CSDVersion

So now that we know the version, which one it is in Avast ? Because I think it’s not possible to install with a older MSDE version…

14

OK, I see, this is probably the culprit. I believe the ADNM installer contains SP3a, while you already have an instance with SP4 installed which makes the ADNM install fail.

Let’s try this:

  1. download MSDE with SP4 from this page http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5 - download “SQL2000.MSDE-KB884525-SP4-x86-ENU.EXE” (78.5MB)

  2. Start normal ADNM installation, and proceed to the stage where it asks you for SQL server details

  3. Search the system partition e.g. for file called “SqlRun01.msi”. The point here is to locate the TEMP folder where the ADNM installer stores the MSDE setup files. The MSDE install folder has a SETUP subfolder, and SqlRun01.msi resides in this subfolder.

  4. Replace the whole MSDE install folder with the SP4 one downloaded in step 1. (the file you download in step 1. is just a self-extracting archive that will create a folder structure similar to the one you’ll see in the TEMP folder).

  5. Proceed with the ADNM installation as normal.

Hope this will do the trick.

Meanwhile, we’ll try to embed MSDE SP4 install directly to the ADNM setup program so that this hack won’t be necessary starting with the next update.

Thanks
Vlk

15

Hello Vik,

thank you for your answer I just gave a try to your solution. Sorry, but it doesn’t work because avast extracts the setup files for msde after the step you described in the setup so, I cannot replace the files since the setup replace them during the install. Please, could you provide a version with the last msde SP4 included. I don’t think we can achieve this without the correct msde integrated in the installer or without modifying the install process.

Regards.

David

16

The MSDE installation is really extracted right before starting, so it can’t be replaced on the fly.
You can first install downloaded MSDE SP4, you should provide some commandline parameters.
Follow these steps:

  1. Run MSDE setup with commandline:
    setup.exe SAPWD=strong_pwd INSTANCENAME=avast SECURITYMODE=SQL COLLATION=Latin1_General_CI_AS DISABLENETWORKPROTOCOLS=1 REBOOT=ReallySuppress /wait /L*v “C:\msde.log”
    where strong_pwd is password containing both upper and lower-case letters and numbers

  2. When MSDE setup finishes, start MSSQL$AVAST service

  3. Run ADNM setup, follow wizard until SQL Server settings

  4. Select SQL Server, enter server’s address with instance name (e.g. COMPUTER\avast) and ‘sa’ user’s password

  5. Then proceed with installation

17

That said, we have verified that the ADNM package actually contains MSDE 2000 SP4 (version 8.00.2039) so it’s quite strange… I have no idea what is your SharePoint MSDE version (8.00.1100) - SP4 should indeed be 8.00.2039 (as documented here: http://support.microsoft.com/kb/321185 )

Thanks
Vlk