Database is in Use after re-installing TeamCity

Hello,

I recently logged into my TeamCity webUI after not logging into it for a while and found that it had an error along the lines of a second teamcity installation was detected and an administrator token was needed to fix it. I could not figure out what the administrator token was so I decided to reinstall team city. After re-installaing TeamCity I am greeted by the screenshot below telling me that the Database is in Use. I have been unable to find a solution to this issue online. After coming across this screen shot, I deleted the directory that I installed Team City to, I also deleted the C:\ProgramData\JetBrains directory, and then re-installed Team City (again) only to find that the same issue still exists.

Below is my teamcity-server.log after going through the process.

[2017-11-28 16:42:06,902]   INFO -  jetbrains.buildServer.STARTUP - Path to the startup configuration file: C:\TeamCity\bin\..\conf\teamcity-startup.properties
[2017-11-28 16:42:07,036]   INFO -  jetbrains.buildServer.STARTUP -

[2017-11-28 16:42:07,037]   INFO -  jetbrains.buildServer.STARTUP - ===========================================================
[2017-11-28 16:42:07,038]   INFO -  jetbrains.buildServer.STARTUP - Starting TeamCity server
[2017-11-28 16:42:07,527]   INFO -  jetbrains.buildServer.STARTUP - TeamCity version: 2017.2 (build 50574), data format version 829
[2017-11-28 16:42:07,538]   INFO -  jetbrains.buildServer.STARTUP - OS: Windows 10, version 10.0, x86, Current user: MAXWELLPLT$, Time zone: CST (UTC-06:00)
[2017-11-28 16:42:07,538]   INFO -  jetbrains.buildServer.STARTUP - Java: 1.8.0_151, Java HotSpot(TM) Server VM (32 bit) (25.151-b12, mixed mode), Java(TM) SE Runtime Environment (1.8.0_151-b12), Oracle Corporation; JVM parameters: -Djava.util.logging.config.file=C:\TeamCity\bin\..\conf\logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Xrs -Xmx512m -Dteamcity.configuration.path=../conf/teamcity-startup.properties -Dlog4j.configuration=file:../conf/teamcity-server-log4j.xml -Dteamcity_logs=C:\TeamCity\bin\..\logs -Dcatalina.base=C:\TeamCity\bin\.. -Dcatalina.home=C:\TeamCity\bin\.. -Djava.io.tmpdir=C:\TeamCity\bin\..\temp
[2017-11-28 16:42:07,540]   INFO -  jetbrains.buildServer.STARTUP - Garbage collection: PS Scavenge, PS MarkSweep
[2017-11-28 16:42:07,540]   INFO -  jetbrains.buildServer.STARTUP - Web server version: Apache Tomcat/8.5.23
[2017-11-28 16:42:07,546]   INFO -  jetbrains.buildServer.STARTUP - Server IP address: 192.168.1.88
[2017-11-28 16:42:07,549]   INFO -  jetbrains.buildServer.STARTUP - Web server ports: 2021 (protocol: HTTP/1.1, scheme: http), 8105 (shutdown port)
[2017-11-28 16:42:07,550]   INFO -  jetbrains.buildServer.STARTUP - Context path: "/", servlet real path: "C:\TeamCity\webapps\ROOT"
[2017-11-28 16:42:07,557]   INFO -  jetbrains.buildServer.STARTUP - TeamCity distribution type: exe
[2017-11-28 16:42:07,557]   INFO -  jetbrains.buildServer.STARTUP - TeamCity server work mode: Main TeamCity Server
[2017-11-28 16:42:07,588]   INFO - rocesses.ProcessTreeTerminator - Using jetbrains.buildServer.processes.ProcessTreeTerminatorWindows
[2017-11-28 16:42:07,694]   INFO - .ProcessTreeTerminatorImplBase - Will use command 'C:\TeamCity\temp\TeamCity6560755873145761213ps\JetBrains.TeamCity.ps.x86.exe ps'.
[2017-11-28 16:42:07,819]   INFO -  jetbrains.buildServer.STARTUP - TeamCity server process ID (10048) stored in: C:\TeamCity\logs\teamcity.pid
[2017-11-28 16:42:07,837]   INFO -  jetbrains.buildServer.STARTUP - Version file lock was successfully obtained: C:\TeamCity\webapps\ROOT\BUILD_50574
[2017-11-28 16:42:07,865]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Looking for the TeamCity Data Directory
[2017-11-28 16:42:07,865]   INFO -  jetbrains.buildServer.STARTUP - The TeamCity Data Directory path is determined using the user home directory
[2017-11-28 16:42:07,938]   INFO -  jetbrains.buildServer.STARTUP - The TeamCity Data Directory "C:\Windows\System32\config\systemprofile\.BuildServer" doesn't exist
[2017-11-28 16:42:07,938]   INFO -  jetbrains.buildServer.STARTUP - Asking user to select the TeamCity Data Directory path from UI
[2017-11-28 16:42:07,938]   INFO -  jetbrains.buildServer.STARTUP - Startup confirmation is required. Open TeamCity web page in the browser. Server is running at http://localhost:2021
[2017-11-28 16:42:07,938]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Confirming TeamCity first start (administrator login is required to proceed)
[2017-11-28 16:42:16,477]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Initializing the TeamCity Data Directory
[2017-11-28 16:42:16,477]   INFO -  jetbrains.buildServer.STARTUP - The TeamCity Data Directory path configured by the user from the UI: 'C:\ProgramData\JetBrains\TeamCity'
[2017-11-28 16:42:16,488]   INFO -  jetbrains.buildServer.STARTUP - The main configuration file "C:\ProgramData\JetBrains\TeamCity\config\main-config.xml" exists
[2017-11-28 16:42:16,488]   INFO -  jetbrains.buildServer.STARTUP - The database properties file "C:\ProgramData\JetBrains\TeamCity\config\database.properties" exists
[2017-11-28 16:42:16,488]   INFO -  jetbrains.buildServer.STARTUP - The internal database data file "C:\ProgramData\JetBrains\TeamCity\system\buildserver.data" exists
[2017-11-28 16:42:16,496]   INFO -  jetbrains.buildServer.STARTUP - Data Directory version: 812
[2017-11-28 16:42:16,497]   INFO -  jetbrains.buildServer.STARTUP - Startup configuration file is created: C:\TeamCity\bin\..\conf\teamcity-startup.properties
[2017-11-28 16:42:16,503]   INFO -  jetbrains.buildServer.STARTUP - The TeamCity Data Directory path 'C:\ProgramData\JetBrains\TeamCity' is stored in 'C:\TeamCity\conf\teamcity-startup.properties'
[2017-11-28 16:42:16,503]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Looking for the database configuration
[2017-11-28 16:42:16,504]   INFO -  jetbrains.buildServer.STARTUP - Database properties file "C:\ProgramData\JetBrains\TeamCity\config\database.properties" exists
[2017-11-28 16:42:16,504]   INFO -  jetbrains.buildServer.STARTUP - Internal HSQL database file (C:\ProgramData\JetBrains\TeamCity\system\buildserver.data) exists, version: 2.3.2
[2017-11-28 16:42:16,504]   INFO -  jetbrains.buildServer.STARTUP - Database connection URL: jdbc:hsqldb:file:$TEAMCITY_SYSTEM_PATH/buildserver
[2017-11-28 16:42:16,506]   INFO -  jetbrains.buildServer.STARTUP - Using database connection URL from the database properties file. The URL is: jdbc:hsqldb:file:$TEAMCITY_SYSTEM_PATH/buildserver
[2017-11-28 16:42:16,507]   INFO -  jetbrains.buildServer.STARTUP - Using internal (HSQL) database
[2017-11-28 16:42:16,507]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Connecting to the database
[2017-11-28 16:44:00,015]   INFO -  jetbrains.buildServer.STARTUP - HSQL database opened (in-process) by another application.
 
[2017-11-28 16:44:00,015]   INFO -  jetbrains.buildServer.STARTUP - Current stage: Second TeamCity instance detected (administrator login is required to proceed)

Any suggestions on how to fix this issue would be much appreciated.