ApexSQL Knowledgebase: How to uninstall the ApexSqlConnection Monitor.exe process and other server-side components

SITE FEED

Site Feed

Support Forum

The fastest and most effective to get answers to your questions quickly.

FAQs

Quick answers to common questions.

Troubleshooting

Known issues and basic troubleshooting techniques for problems or unexpected behaviors.

Knowledgebase

Technical tips, How-to articles, and other tutorials about ApexSQL Tools.

Online Documentation

All of our help files for download or convenient viewing online.

Videos

Watch product demos, training videos, or tutorials of our products' main features.

ApexSQL Knowledgebase

Tips and How-to Articles for Apex SQL Tools

How to uninstall the ApexSqlConnection Monitor.exe process and other server-side components

DESCRIPTION
Uninstalling ApexSQL Log client components doesn't uninstall ApexSQL Log server-side components . ApexSQL Log is licensed per server thus, server-side components can only be installed on one machine while the client-side components can be installed on as many machines as the user wants.It is by design then that server-side components are not uninstalled when client-side components are uninstalled. The exception is when the server-side components are installed WITH the client-side components during setup.

SOLUTION
In this case, uninstalling the client-side components also removes the server-side components. More information about server-side components, processes and extended procedures created on SQL Server can be found here. This whole approach may be changed in future versions of ApexSQL Log to avoid confusion. For now though, the following procedure will uninstall the server-side components of ApexSQL Log:

ApexSQL Log 2005
1. Download and execute sql script on your server from here
2. On the command line of your server, go to the SQL Server's Binn directory and execute the following command from : ApexSqlServerHelper /unload
3. Delete all binaries that start with ApexSql* from SQL Server's Binn folder.
4. Drop msdb.dbo.APEXSQL_LOG_LOGIN table if you don't need data that's stored in it (it's your login data - that's why we don't drop it automatically)

ApexSQL Log 2008.01 - 2008.03 versions
1. 1. Download and execute sql script on your server from here
2. On the command line of your server, go to the SQL Server's Binn directory and execute the following command from : ApexSqlServerHelper2008 /unload
3. Delete all binaries that start with ApexSql* from SQL Server's Binn folder.
4. Drop msdb.dbo.APEXSQL_LOG_LOGIN table if you don't need data that's stored in it (it's your login data - that's why we don't drop it automatically)

Starting from the ApexSQL Log 2008.05 server-side components have been split on ApexSQL Log and ApexSQL Recover and extended stored procedures have been renamed, please download and execute the following script to delete stored procedures and release resources.
2. On the command line of your server, go to the SQL Server's Binn directory and execute the following command from : ApexSqlLog2008ServerHelper /unload
3. Delete all binaries that start with ApexSql* from SQL Server's Binn folder.
4. Drop msdb.dbo.APEXSQL_LOG_LOGIN table if you don't need data that's stored in it (it's your login data - that's why we don't drop it automatically)

Alternatively, the server-side components can also be uninstalled from the ApexSQL Log client.

This uninstalls all server-side components as well as the Connection monitor.

If all of the above fail to kill the ApexSQL Connection Monitor process, please try the following:

1) Go to your SQL Server's binn directory (e.g. C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn)
2) Rename ApexSqlConnectionMonitor2008.exe (for ApexSQL Log 2008.01 - 2008.03) and ApexSqlLog2008ConnectionMonitor.exe (for ApexSQL Log 2008.05) to another name.
3) Go to Task Manager and kill the ApexSqlConnectionMonitor2008.exe process
4) Delete the (renamed) file

AUTHOR
Dmitriy Dyubchenko

LAST REVIEW DATE
09 December 2009

Labels: ApexSQL Log

posted by Janice Lee on Thursday, August 09, 2007

0 Comments: