I have encountered this weird error on our server. The application was not running this morning. When I tried to start it it went into a starting loop. When trying to start the app on the server via the service 1.07 i get an error message saying: LogSubscriber LogFile already exists When trying to delete the log I get a meesage saying that some other process or program is using it. How do I find out what, the application is in production and it is critical to have it up and running asap. Something seems to be trying to establish a connection to the database in a constant loop - how do I stop it? The service is stopped. 2011-06-27 12:03:10.025 WARNING - ConnectionBus: Cannot create database connection. 2011-06-27 12:03:34.509 WARNING - ConnectionBus: Database connections: 0 active, 0 idle. 2011-06-27 12:03:34.509 ERROR - ConnectionBus: Opening JDBC connection failed with SQLState: 08S01 Message: The TCP/IP connection to the host nlbmrasql2, port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.". Retrying...(1/3) 2011-06-27 12:03:50.915 WARNING - ConnectionBus: Database connections: 0 active, 0 idle. 2011-06-27 12:03:50.915 ERROR - ConnectionBus: Opening JDBC connection failed with SQLState: 08S01 Message: The TCP/IP connection to the host nlbmrasql2, port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.". Retrying...(2/3) 2011-06-27 12:04:07.758 WARNING - ConnectionBus: Database connections: 0 active, 0 idle. 2011-06-27 12:04:07.758 ERROR - ConnectionBus: Opening JDBC connection failed with SQLState: 08S01 Message: The TCP/IP connection to the host nlbmrasql2, port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port."., giving up...(3/3) Thanks