Paramont CMS AI 2.0 server

How to uninstall Paramont CMS AI 2.0 server from your PC

Paramont CMS AI 2.0 server is a Windows application. Read more about how to remove it from your PC. The Windows release was developed by chippoint. More information on chippoint can be found here. Further information about Paramont CMS AI 2.0 server can be seen at chippoint. Usually the Paramont CMS AI 2.0 server program is to be found in the C:\Program Files (x86)\Paramont CMS Server directory, depending on the user's option during install. You can remove Paramont CMS AI 2.0 server by clicking on the Start menu of Windows and pasting the command line C:\Program Files (x86)\InstallShield Installation Information\{92AF5D75-84A2-4E9F-9567-3FA294CBD551}\setup.exe. Note that you might be prompted for admin rights. ServerTrayUI.exe is the programs's main file and it takes around 589.50 KB (603648 bytes) on disk.

The executable files below are part of Paramont CMS AI 2.0 server. They occupy about 73.05 MB (76603032 bytes) on disk.

• AlarmServer.exe (208.00 KB)
• ApplicationServer.exe (208.50 KB)
• AuthenticationServer.exe (988.00 KB)
• ConfigServer.exe (4.10 MB)
• IntelligentAnalysisServer.exe (213.50 KB)
• JoinServer.exe (208.00 KB)
• MediaTransferServer.exe (212.00 KB)
• mysql.exe (4.90 MB)
• mysqldump.exe (4.88 MB)
• ServerTrayMgr.exe (440.00 KB)
• ServerTrayUI.exe (589.50 KB)
• StorageServer.exe (221.50 KB)
• TVWallServer.exe (213.50 KB)
• Tomcat9.exe (101.62 KB)
• appletviewer.exe (19.13 KB)
• extcheck.exe (19.13 KB)
• idlj.exe (19.13 KB)
• jabswitch.exe (35.63 KB)
• jar.exe (19.13 KB)
• jarsigner.exe (19.13 KB)
• java-rmi.exe (19.13 KB)
• java.exe (241.13 KB)
• javac.exe (19.13 KB)
• javadoc.exe (19.13 KB)
• javafxpackager.exe (126.13 KB)
• javah.exe (19.13 KB)
• javap.exe (19.13 KB)
• javapackager.exe (126.13 KB)
• javaw.exe (241.13 KB)
• javaws.exe (379.13 KB)
• jcmd.exe (19.13 KB)
• jconsole.exe (19.13 KB)
• jdb.exe (19.13 KB)
• jdeps.exe (19.13 KB)
• jhat.exe (19.13 KB)
• jinfo.exe (19.13 KB)
• jjs.exe (19.13 KB)
• jmap.exe (19.13 KB)
• jps.exe (19.13 KB)
• jrunscript.exe (19.13 KB)
• jsadebugd.exe (19.13 KB)
• jstack.exe (19.13 KB)
• jstat.exe (19.13 KB)
• jstatd.exe (19.13 KB)
• jvisualvm.exe (193.13 KB)
• keytool.exe (19.13 KB)
• kinit.exe (19.13 KB)
• klist.exe (19.13 KB)
• ktab.exe (19.13 KB)
• native2ascii.exe (19.13 KB)
• orbd.exe (19.13 KB)
• pack200.exe (19.13 KB)
• policytool.exe (19.13 KB)
• rmic.exe (19.13 KB)
• rmid.exe (19.13 KB)
• rmiregistry.exe (19.13 KB)
• schemagen.exe (19.13 KB)
• serialver.exe (19.13 KB)
• servertool.exe (19.13 KB)
• tnameserv.exe (19.13 KB)
• unpack200.exe (170.63 KB)
• wsgen.exe (19.13 KB)
• wsimport.exe (19.13 KB)
• xjc.exe (19.13 KB)
• jabswitch.exe (35.63 KB)
• java-rmi.exe (19.13 KB)
• java.exe (241.13 KB)
• javacpl.exe (89.13 KB)
• javaw.exe (241.13 KB)
• javaws.exe (379.13 KB)
• jjs.exe (19.13 KB)
• jp2launcher.exe (114.63 KB)
• keytool.exe (19.13 KB)
• kinit.exe (19.13 KB)
• klist.exe (19.13 KB)
• ktab.exe (19.13 KB)
• orbd.exe (19.13 KB)
• pack200.exe (19.13 KB)
• policytool.exe (19.13 KB)
• rmid.exe (19.13 KB)
• rmiregistry.exe (19.13 KB)
• servertool.exe (19.13 KB)
• ssvagent.exe (79.13 KB)
• tnameserv.exe (19.13 KB)
• unpack200.exe (170.63 KB)
• nbexec.exe (155.63 KB)
• nbexec64.exe (212.63 KB)
• WebClient5000_VPPlugin.exe (51.47 MB)

...click to view all...

The information on this page is only about version 2.1.2.10922 of Paramont CMS AI 2.0 server. Click on the links below for other Paramont CMS AI 2.0 server versions:

• 2.1.3.20527

Following the uninstall process, the application leaves some files behind on the computer. Some of these are shown below.

Directories found on disk:

• C:\Program Files (x86)\Paramont CMS Server

The files below are left behind on your disk when you remove Paramont CMS AI 2.0 server:

• C:\Program Files (x86)\Paramont CMS Server\AlarmServer_log\AlarmServer.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid12100.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid15204.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid154892.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid16892.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid20988.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid22200.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid22600.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid27448.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid37460.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid41912.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid45912.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid45956.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid52284.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid54340.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid61004.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid64488.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid79396.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid87352.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid96328.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\hs_err_pid98508.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\jdk\jre\lib\deploy\ffjcext.zip
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\jdk\jre\lib\deploy\splash.gif
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\jdk\readme.html
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2024-11-13.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2024-11-20.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2024-12-10.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2024-12-11.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2024-12-23.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2025-01-07.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2025-01-13.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2025-01-27.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2025-01-28.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2025-01-29.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2025-01-30.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2025-02-05.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\catalina.2025-02-10.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-03-10.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-03-14.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-03-15.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-04-13.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-04-14.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-04-20.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-04-22.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-04-27.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-04-28.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-05-04.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-05-07.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-05-08.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-05-24.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-06-08.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-06-15.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-06-21.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-06-24.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-06-28.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-07-02.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-07-18.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-08-01.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-08-11.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-08-20.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-08-22.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-08-31.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-09-13.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-09-15.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-09-16.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-09-19.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-09-26.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-10-05.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-10-21.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-10-24.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-10-27.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-11-08.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-11-09.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-11-14.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-11-17.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-11-18.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-11-23.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-12-08.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2022-12-21.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-01-04.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-01-10.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-02-08.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-02-09.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-02-10.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-02-12.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-02-13.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-02-27.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-02-28.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-03-02.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-03-13.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-03-21.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-04-11.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-04-28.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-05-02.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-05-16.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-05-30.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-06-08.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-06-30.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-07-03.log
• C:\Program Files (x86)\Paramont CMS Server\apache-tomcat\logs\commons-daemon.2023-07-19.log

Registry keys:

• HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\8014A81B3426D354098AE0C33CA2DFF0
• HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield_{92AF5D75-84A2-4E9F-9567-3FA294CBD551}

Use regedit.exe to remove the following additional values from the Windows Registry:

• HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\8014A81B3426D354098AE0C33CA2DFF0\ProductName

How to remove Paramont CMS AI 2.0 server from your computer with Advanced Uninstaller PRO

Paramont CMS AI 2.0 server is an application by chippoint. Frequently, people try to remove this program. Sometimes this is easier said than done because doing this by hand takes some skill regarding Windows internal functioning. The best EASY approach to remove Paramont CMS AI 2.0 server is to use Advanced Uninstaller PRO. Here is how to do this:





1. If you don't have Advanced Uninstaller PRO already installed on your PC, add it. This is a good step because Advanced Uninstaller PRO is a very useful uninstaller and general utility to clean your PC.

DOWNLOAD NOW

• go to Download Link
• download the program by pressing the DOWNLOAD NOW button
• set up Advanced Uninstaller PRO

2. Start Advanced Uninstaller PRO. It's recommended to take your time to get familiar with Advanced Uninstaller PRO's design and wealth of functions available. Advanced Uninstaller PRO is a powerful PC management program.

3. Click on the General Tools category


4. Click on the Uninstall Programs tool


5. A list of the programs existing on the PC will appear

6. Scroll the list of programs until you locate Paramont CMS AI 2.0 server or simply activate the Search feature and type in "Paramont CMS AI 2.0 server". The Paramont CMS AI 2.0 server application will be found very quickly. When you select Paramont CMS AI 2.0 server in the list of applications, the following data regarding the application is made available to you:

• Safety rating (in the lower left corner). This explains the opinion other users have regarding Paramont CMS AI 2.0 server, ranging from "Highly recommended" to "Very dangerous".
• Reviews by other users - Click on the Read reviews button.
• Details regarding the program you want to uninstall, by pressing the Properties button.

For instance you can see that for Paramont CMS AI 2.0 server:

• The web site of the program is: chippoint
• The uninstall string is: C:\Program Files (x86)\InstallShield Installation Information\{92AF5D75-84A2-4E9F-9567-3FA294CBD551}\setup.exe

7. Click the Uninstall button. A window asking you to confirm will appear. accept the uninstall by pressing the Uninstall button. Advanced Uninstaller PRO will automatically remove Paramont CMS AI 2.0 server.


8. After uninstalling Paramont CMS AI 2.0 server, Advanced Uninstaller PRO will offer to run an additional cleanup. Click Next to perform the cleanup. All the items of Paramont CMS AI 2.0 server that have been left behind will be detected and you will be asked if you want to delete them. By removing Paramont CMS AI 2.0 server using Advanced Uninstaller PRO, you can be sure that no Windows registry items, files or folders are left behind on your computer.

Your Windows PC will remain clean, speedy and ready to take on new tasks.

Disclaimer

This page is not a recommendation to remove Paramont CMS AI 2.0 server by chippoint from your PC, we are not saying that Paramont CMS AI 2.0 server by chippoint is not a good application. This page simply contains detailed instructions on how to remove Paramont CMS AI 2.0 server in case you want to. Here you can find registry and disk entries that our application Advanced Uninstaller PRO discovered and classified as "leftovers" on other users' computers.