| LINKS |
|
ApexSQL Knowledgebase Tips and How-to Articles for ApexSQL Tools How to uninstall the ApexSqlConnection Monitor.exe process and other server-side components APPLIES TO ApexSQL Log 2008.06 and below SUMMARY This article explains how to uninstall ApexSQL server-side components, as uninstalling Log client components doesn't uninstall ApexSQL Log server-side components. The server-side components are removed together with the client, only when installed WITH the client-side components during setup. 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 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. If the server-side components are installed WITH the client-side components during setup, uninstalling the client-side components also removes the server-side components. This whole approach may be changed in future versions of ApexSQL Log to avoid confusion. For now, the following procedure will uninstall the server-side components of ApexSQL Log: ApexSQL Log 2005 1. Download and execute the 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: 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 the 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. 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: 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 the server-side components have been split to 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 the resources. 2. On the command line of your server, go to the SQL Server's Binn directory and execute the following command: ApexSqlLog2008ServerHelper /unload 3. Delete all binaries that start with ApexSqlLog* 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. To do so, right click the server you want the server-side components to be uninstalled from, and click Uninstall Server Components on the context menu. This uninstalls all of the 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 SEE ALSO ApexSQL Log Pre-Installation Notes POSTED BY Dmitriy Dyubchenko LAST UPDATED May 5, 2010 Labels: ApexSQL Log |
