- Confluence Docs 3.0 : _Troubleshooting Confluence while Running as a Windows Service This page last changed on Jul 26, 2009 by ggaskell. ## Troubleshooting Confluence while Running as a Windows Service When investigating memory issues or bugs, it may be useful to view information from Confluence's garbage collection. To turn on the verbose garbage collection, use the command:
      tomcat6 //US//Confluence ++JvmOptions="-Xloggc:<CONFLUENCE-INSTALL>\logs\atlassian-gc.log"
- If you are running 64-bit Windows, please note that Apache Tomcat cannot run as a Windows service if you are using a 64-bit JDK. Please ensure that you are using a 32-bit JDK. (If you used the automated Confluence Installer, you will not run into this problem because a 32-bit JDK has already been installed for you.) For more information, please refer to [CONF-12293|http://jira.atlassian.com/browse/CONF-12293] for a workaround if you intend to continue using the 64-bit JDK. Starting the service produces an error similar to `Failed creating java C:\jdk1.6.0_10\jre\bin\server\jvm.dll`. This is because Tomcat is looking for a `msvcr71.dll` file. Please refer to this Knowledge Base article. Unable to start Confluence as service after Allocating higher JVM Memory. Please refer to this Knowledge Base article. Confluence 2.9 Installer does not work when installed as service, due to missing semi-colon in `service.bat`. Please refer to reported issue CONF-12785. You can use a Sysinternals tool called `Procmon.exe` from the The Microsoft Windows Sysinternals Team, to check the error occured at the specific time when starting Confluence Service. You need to match the time when Tomcat failed captured by this tool against the time in Windows' `Event Viewer`.
  | Note that it is not recommended that you run this tool too long as it may disrupt other Atlassian applications. So once you have captured the required information you will need to press `Ctrl + E` to stop capturing.
## Check the Knowledge Base Articles
Unable to configure Confluence to run as a service on Tomcat
Unable to Install Service on Windows Vista
Could not Start Confluence as a Service After Allocating JVM Memory
Confluence does not Start due to Windows Firewall
Unable to change JVM memory when running Evaluation Installer as a Windows service
## Requesting Support If after you follow the troubleshooting guide above you still cannot make Confluence run as Windows Service or there is an error when setting the JVM configuration for the service, you can create a ticket in http://support.atlassian.com for help. Please provide the following information we need to assist you: Are you running a 32 bit or 64 bit Windows? Give us the result of running `java -version` from Windows command line console. A screen shot of your Windows Registry setting for Tomcat. If you have modified service.bat, please give us a copy of this file for review. What application server are you using? eg. Are you using the Confluence Standalone distribution? Your atlassian-confluence.log file. ##### RELATED TOPICS Start Confluence automatically on Windows as a Service

Document generated by Confluence on Nov 05, 2009 23:34