Sublime Subversion

The Sublime Service Account is used to run the Sublime web application.  You define the account when first installing Sublime.  To change this account, execute the following steps on your Sublime server:

1. Add the new service account to the local Administrator’s group
2. Add the new service account to the local IIS Worker Process group (IIS_WPG for Windows Server 2003, IIS_USRS for Windows Server 2008).
3. Change the Identity of the SublimeAppPool application pool
   • Open the Internet Information Services (IIS) Manager from Administrative Tools
   • Expand the Application Pools folder, right-click SublimeAppPool and choose Properties
   • Click the Identity tab
   • Enter the username and password for the new service account
   • Click OK
4. Recycle the SublimeAppPool application pool, or perform an IIS Reset.

If you downloaded yesterday’s build of Sublime 0.7 you will need to perform the following steps to fix a small bug.

Problem

When clicking on a group in Sublime to view the group membership, you receive the following error: “The group membership could not be retrieved.”

Applies To

All servers running Sublime 0.7.0.917 (released 7/15/2009)

Steps to Fix

This issue has been corrected in a new build posted 7/16/2009.  You may download Sublime and re-install to correct this issue, or you can follow the steps below.

1. From the server, open the Sublime web.config file in notepad.  The web.config file will be located beneath your Sublime installation directory in the Web folder (i.e. c:\program files\sublime\web\web.config).
2. Locate the <system.web> line.  Insert a new line below <system.web> and enter the following text:
   <webServices>
  <protocols>
    <add name="HttpPost"/>
  </protocols>
</webServices>

   The text should now look like this:

   ... snip ...
<appSettings/>
<connectionStrings/>
<system.web>
  <webServices>
    <protocols>
      <add name="HttpPost"/>
    </protocols>
  </webServices>
<compilation debug="true" />
<authentication mode="Forms">
... snip ...

3. Save the web.config file.

Problem:

If you have installed Sublime using the default SlikSVN Subversion install, your users may receive the following error when attempting to access repositories:

svn: Can't connect to host '192.168.1.14': A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.


or

svn: Can't connect to host '192.168.1.14': No connection could be made because the target machine actively refused it.


Applies To:

• Windows Server 2008 (32 bit and 64 bit)
• Windows Vista (32 bit and 64 bit)
• SlikSVN 1.5.5 and SlikSVN 1.5.6
• Servers running Subversion Authentication with SVNSERVER (Apache servers are not impacted)

Resolution:

This is a known issue and will be fixed in the next release of Sublime.  In the mean time you can use the workaround below as a temporary solution.

Steps to Fix:

FIRST: Ensure that your firewall is configured correctly. Port 3690 must be open for the SVN protocol. If your firewall is configured correctly and you still receive these errors, proceed with the following steps:

1. Open the Sublime website and navigate to the Administration home page.
2. In the Repository Status section, take the svnserve service offline by clicking “Take Offline”
3. Connect to your server via Remote Desktop
4. Download the 1.5.5 Subversion binaries from http://subversion.tigris.org/files/documents/15/44589/svn-win32-1.5.5.zip
5. Unzip the files to a temporary folder on your server.
6. Open the location where you unzipped the files and navigate to the “bin” folder.
7. Copy the entire contents of this folder (including all dll and exe files)
8. Navigate to the location where your Subversion binaries are installed. By default this will be C:\Program Files\Subversion\bin
9. Paste all copied files in this location over-writing any duplicates.
10. Back in Sublime on the Administration home page, click “Bring Online”, and then click the “Bring Online” button to re-start the svnserve service.

Your users should now be able to access repositories.