ADNM service will not start on Server 2008 R2 x64 - error %%42000 - SOLVED

I’ve installed ADNM on a Server 2008 Standard R2 x64 machine. I’ve got SQL Server Express 2005 x64 w/SP3 set up and have created an avast user.

During the installer, I specify my SQL server instance and user/pass, and it connects and creates the Avast database successfully. I can see the tables and information in my SQL server manager. The SQL service is running and the Avast user can connect and run SQL commands.

However, I can’t start the ADNM service. Or, rather, it will start, and then fail within seconds with error %%42000.

If I open the AMS maintenance tool, all functions fail with an “unable to locate database - error 42000” except the one to change DB credentials, which ALWAYS shows up blank with no information pre-populated, but when I put in the connection details it successfully connects.

It appears that it is not properly saving the database login information. I’ve contacted support but they’re not responding to tickets, and the support-for-paid-products line is disconnected and out of service. Free support has NO idea what I’m talking about, and redirected me to Element5 Billing Support.

I see a lot of people having similar-but-not-identical issues, and a number of solutions that don’t quite match my configuration and don’t work for me regardless. Any suggestions?

EDIT August 19 2010: Problem is solved, thanks to user “edj”. My solution: Uninstall ADNM and AMS Tools and delete the database. Run the installer again using right-click “Run As Administrator”, not simply with an Administrator-privileged account. Use the same DB server and credentials, it will create the same DB, but now the service starts and ADNM is working for me.

Can you test to run the AMS Maintenance Tools as “Administrator”?

Running the AMS tools as admin didn’t work, but:

I checked the setup.log file, and it told me the installer reported it could not create the database, despite the fact that it DID create the database.
I uninstalled the program and told it to delete the database, and it told me it could not delete the database - and then DID delete the database.

I re-ran the installer using right-click “Run As Administrator” instead of simply running it with my administrator-privileged login account, and it accepted the exact same server information, DB user, DB password, and created the same database with the same lack of error messages - but the service started.

The new setup.log is the same as the old one, except it says “database successfully created”

It appears that my problem is solved. Thank you very much.

Good news!

:wink:

good to hear its solved :smiley:

so what did u learn?? :D:D
correct: when your installing programs on a 2008 server or vista or win7 always run it as administrator… even tho you are logged in as administrator the rights of the account are limited :slight_smile: