TROUBLESHOOTING TEAM PROJECTS

(SVN METHOD)

OVERVIEW

Technical problems with team projects are rare, but they do happen. Here’s a collection of known issues along with any information we have about how to fix them.


Problems with setting up new SVN team projects are usually related to user account permissions or server configuration. Problems with previously-working projects can almost always be solved by getting a new local copy and then importing any changes.


(Note that you can also try hosting your team project on Axure Share. Learn about creating team projects, including on Axure Share, in this article.)


The Axure help desk is always happy to assist with troubleshooting. Just send an email to support@axure.com.

© 2002-2016 Axure Software Solutions, Inc. All rights reserved. Axure ® is a registered trademark of Axure Software Solutions, Inc.

86% OF THE FORTUNE 100

USE AXURE RP

AXURE

RESOURCES

LEGAL

CONNECT

EMAIL

COMMON PROBLEMS

CAN'T CREATE A TEAM PROJECT

If you’re getting stuck during the process of creating a new team project, these steps may help.

1. MAKE SURE YOU CAN CONNECT TO THE NETWORK DRIVE OR SVN SERVER

If you’re trying to create your team project on a network drive, see if you can browse to the team directory using your file browser (File Explorer or Finder). If you’re using an SVN server instead of a network drive, try navigating to the team directory using your web browser (Chrome, Firefox, etc.). If you can’t see the team directory after navigating to it, check your user account permissions for the network drive or server.

2. CHECK YOUR PERMISSIONS

For a network drive, verify that you have read, write, and modify permissions for the team directory. For an SVN server, verify that you have full access to the repository. You may need to work with your IT team to get help changing your account permissions.

3. MAKE SURE THE TEAM DIRECTORY YOU’VE CHOSEN EXISTS ON THE SVN SERVER

If you’re using an SVN server, the team directory you specify must already exist on the server. Axure RP will then add a directory beneath that one with the project name. For example, if you specify a team directory location of <svn://svnserver/OurProjects>, the "OurProjects" folder must already exist on the server.

CAN'T GET AND OPEN A TEAM PROJECT (GET LOCAL COPY)

If you’re having trouble downloading your own local copy of a team project that already exists—for example, if you’re seeing a "can’t connect to server" message—try these steps.

1. MAKE SURE YOU CAN CONNECT TO THE NETWORK DRIVE OR SVN SERVER

If your team project is located on a network drive, see if you can browse to the team directory using your file browser (File Explorer or Finder). If the project is on an SVN server instead of a network drive, try navigating to the team directory using your web browser (Chrome, Firefox, etc.). If you can’t see the team directory after navigating to it, check your user account permissions for the network drive or server. Sometimes just browsing to the directory re-establishes the connection, so you may want to try getting the project again after this step.

2. CHECK YOUR READ, WRITE, AND MODIFY PERMISSIONS

For a network drive, verify that you have read, write, and modify permissions for the team directory. You can do this from your file browser by right-clicking the directory and selecting "Properties" or "Get Info". For an SVN server, verify that you have full access to the repository. You may need to work with your IT team to get help changing your account permissions.

3. MAKE SURE THE DIRECTORY YOU’VE SPECIFIED IS THE FULL TEAM DIRECTORY

A full team directory file path will end with the project name. For example, if the project is called "MyProject", the team directory might look like <svn://svnserver/OurProjects/MyProject>. If you aren’t sure what the full team directory might be, and if you have a colleague who already has a local copy of the team project, ask them to open the project and go to "Team > Browse Team Project History". The team directory is in the text field at the top of that dialog.


Spaces and special characters are generally acceptable in the team directory file path, but we've had some customers report that they need to replace spaces with "%20" for the path to work.

CHECK-IN AND CHECK-OUT ARE SLOW

1. NETWORK DRIVE AND VPN

The most common scenario for slow check-ins and check-outs is when the team directory is located on a network drive AND the computer is connecting to the network drive over VPN. This combination should be avoided if possible, and a team directory location other than a network drive should be used instead if VPN access is necessary.

2. CONNECTION SPEED

How’s your intranet or internet connection? If it’s slow or intermittent, the speed of your check-ins and check-outs will be affected.

3. PROJECT SIZE

The RP project file size does affect check-in and check-out speed, though only by a small amount. To test whether the slowness is project-specific, try creating a new team project with just a few small pages on the same network drive or server.

CAN'T CHECK OUT

1. CHECK YOUR PERMISSIONS

For a network drive, verify that you have read, write, and modify permissions for the team directory. For an SVN server, verify that you have full access to the repository.

2. CONFIRM SVN LOCKING IS ENABLED

In order for an Axure RP team project to work correctly with a team directory located on an SVN server, a feature of SVN called "locking" must be turned on. If this is your first time working with a particular SVN server, make sure that locking has been enabled on the server.

3. GET A NEW LOCAL COPY

If you've been able to check in and out in the past and then are suddenly no longer able to, the quickest fix is usually to get a new local copy. If you can check out from the new local copy, continue working from that new copy. You can delete the original local copy after any changes have been imported.

CAN'T CHECK IN

1. MAKE SURE YOU CAN CONNECT TO THE NETWORK DRIVE OR SVN SERVER

If your team project is located on a network drive, see if you can browse to the team directory using your file browser (File Explorer or Finder). If the project is on an SVN server instead of a network drive, try navigating to the team directory using your web browser (Chrome, Firefox, etc.). If you can’t see the team directory after navigating to it, check your user account permissions for the network drive or server. Sometimes just browsing to the directory re-establishes the connection, so you may want to try getting the project again after this step.

2. GET ALL CHANGES

Use the "Team > Get All Changes from Team Directory" menu command and then try to check in again.

3. GET A NEW LOCAL COPY

If the check-in still doesn’t work, you may need to get a new local copy. You can optionally import any changes you've made in the original local copy to the new one.


If this problem happens to you repeatedly, check whether you're running any programs that might be syncing the local directory with another drive (like Dropbox or a similar file-syncing program). If so, disabling the syncing may fix the problem.

PAGE SEEMS TO BE ALREADY CHECKED OUT

Check-outs in team projects are granted per local copy and not per user.


Imagine this: you have a local copy on your work computer and a second local copy on your home computer. You check out a page from your work computer, and then you go home and open up the local copy on your home computer. In this scenario, the page you checked out at work will not be checked out to you at home. Instead, the page will appear from your home computer to be checked out to another "you"—which is in fact the case.


If a local copy has been deleted while pages are still checked out to it, or if you’re seeing a warning message that a page is already checked out but the attributed user doesn't seem to have it checked out, you can perform what’s called a "steal" in order to get things back to normal. To steal a check-out, follow these steps:

1. CHECK OUT THE PAGE FROM YOUR CURRENT LOCAL COPY

A dialog will appear warning you that the page is already checked out. Click on the page or pages in question and click "Edit w/o Check Out". This will create an "unsafe checkout" of the page.

2. MAKE A CHANGE TO THE PAGE

You’ll need to make at least one change so that during the check-in you’ll have the option to steal the check-out.

3. CHECK IN

When checking in, if any changes have been made to the page, you will be asked to steal the check-out. Go ahead and steal the check-out and proceed with checking in. Your page or pages should now be back to normal.

CAN'T CHECK IN OR OUT AFTER MOVING THE TEAM DIRECTORY

After moving the team directory, you can repoint your local copy to the new team directory. Go to "Team > Repoint to Moved Team Directory…". Then enter or browse to the new team directory.


If this doesn't clear up the issue, get a new local copy from the new team directory.

TEAM DIRECTORY IS CORRUPT OR LOST

If the team directory has been corrupted or lost, you can export a standalone .rp file from your current local copy and then create a new team project from that file. (A drawback to remaking a team project in this way is that you’ll lose the project’s version history, normally available via the team project history browser. Make sure the team directory is definitely lost before you proceed.)

1. OPEN YOUR LOCAL COPY

(If you don’t have a working local copy, you can try using the "File > Recover File from Backup" menu command from the last computer able to edit the team project.)

2. EXPORT AN RP FILE

Export your local copy to a standalone .rp file using "File > Export Team Project to File".

3. CREATE THE NEW TEAM PROJECT

Open the .rp file and use "Team > Create Team Project from Current File" to create the new team project.

4. NEW LOCAL COPIES

Each person working on the project will need to get a new local copy from the new team directory. If they’d made changes to their old local copies that are not in the new project, they can export .rp files from their previous local copies and use "File > Import from RP File" to import the pages into their new local copies.

AUTHORIZATION FAILED / NEED TO RE-ENTER SVN PASSWORD

If you’re having trouble connecting to the SVN server—possibly because your SVN authorization details (like username or password) recently changed—it’s a good troubleshooting step to clear and re-enter your SVN authentication.


SVN keeps a cache of your login details at these locations:


Windows:

C:\Users\%USERNAME%\AppData\Roaming\Subversion\auth


Mac OS X (locate via Finder using the "Go > Go to Folder" menu command):

~/.subversion/auth/


Delete the contents of the "auth" folder to clear your cached authentication. Then, the next time you try to connect to the SVN server from Axure RP, you will be prompted to re-enter your authentication details.

ERRORS WHEN HOSTING A TEAM PROJECT ON DROPBOX, GOOGLE DRIVE, ETC.

Storing team projects on services like Dropbox, Google Drive, or OneDrive is not recommended. The rate at which these services sync is often not frequent enough for team projects with multiple users. If several people make changes to a repository before it has finished syncing any previous changes, then the repository can become corrupt.


Hosted SVN services like Unfuddle are a better solution for storing team projects. Another great option is to host your team project on Axure Share. Learn about creating Team Projects on Axure Share in this article.

CAN'T OPEN A LOCAL COPY

If for any reason your local copy of a team project becomes unusable or is lost, you can always get a new one. If you had any unsent changes, use the "File > Recover File from Backup" feature to retrieve a recent backup version of your project. You can then use the "File > Import from RP File" feature to bring those changes into your new local copy.

SVN ERROR MESSAGES

You may see any of these error messages indicating a problem. Steps for troubleshooting in response to some error messages are found below.

COMMIT FAILED

1. GET CHANGES

Try the "Team > Get All Changes from Team Directory" menu command and then check in again.

2. CHECK PERMISSIONS

If you haven't been able to check in to this project before, verify that you have full access to the team directory.  You may need to work with your IT team to get help changing your account permissions.

3. GET A NEW LOCAL COPY

If that doesn't work, get a new local copy and import any changes from the original local copy.

WORKING COPY LOCKED

This error usually occurs after a connection is interrupted during a check-in or check-out.

1. TRY AGAIN

If the error was the result of a momentary connection issue, simply checking in a second time might clear it up.

2. CLEAN UP LOCAL COPY

Try using the "Team > Clean Up Local Copy" feature.

3. GET A NEW LOCAL COPY

If that doesn't work, get a new local copy of the project.

YOUR .SVN/TMP DIRECTORY MAY BE MISSING OR CORRUPT;

RUN 'SVN CLEANUP' AND TRY AGAIN

1. CLEAN UP LOCAL COPY

Try using the "Team > Clean Up Local Copy" feature.

2. GET A NEW LOCAL COPY

If that doesn't work, get a new local copy of the project.

CAN'T MOVE 'PATH'

TURN OFF INDEXING

If you’re on Windows, go to "Indexing Options" in the Control Panel and exclude your local team projects folder from indexing. Sometimes indexing can interfere with check-ins and other operations.

CHECKSUM MISMATCH

GET A NEW LOCAL COPY

This seems to be a bad one. You can try to get a new local copy of the project. If that doesn’t work, it's likely that your team directory is lost or corrupt and will need to be created again.

UNABLE TO OPEN AN RA_LOCAL SESSION TO URL

LOOK FOR SPECIAL CHARACTERS

Try taking out any special characters or spaces in the team directory path or path to your local copy.

PROPFIND REQUEST FAILED

1. MAKE SURE YOU CAN CONNECT TO THE NETWORK DRIVE OR SVN SERVER

If your team project is located on a network drive, see if you can browse to the team directory using your file browser (File Explorer or Finder). If the project is on an SVN server instead of a network drive, try navigating to the team directory using your web browser (Chrome, Firefox, etc.). If you can’t see the team directory after navigating to it, check your user account permissions for the network drive or server. Sometimes just browsing to the directory re-establishes the connection, so you may want to try getting the project again after this step.

2. GET ALL CHANGES

Use the "Team > Get All Changes from Team Directory" menu command and then try again.

3. GET A NEW LOCAL COPY

If none of that works, try getting a new local copy of the project.

RESOURCE OUT OF DATE

1. GET CHANGES

Use the "Team > Get All Changes from Team Directory" menu command and then try again.

2. GET A NEW LOCAL COPY

If that doesn't work, get a new local copy of the project.

CAN'T PARSE LOCK/ENTRIES HASHFILE

1. GET CHANGES

Use the "Team > Get All Changes from Team Directory" menu command and then try again.

2. GET A NEW LOCAL COPY

If that doesn't work, get a new local copy of the project.

NO SUCH REVISION

1. VERIFY THE TEAM DIRECTORY PATH

Check to see if the team directory was moved.

2. TEAM DIRECTORY ON A FILE SYNCING SERVICE?

If you’re using Dropbox, Google Drive, or another file syncing service for your team directory location, that might be the problem. Please consider an alternative team directory location.

3. GET A NEW LOCAL COPY

If none of the above applies, you can always get a new local copy of the project.

THIS CLIENT IS TOO OLD TO WORK WITH WORKING COPY

This error can happen after you use a third-party SVN client like TortoiseSVN to view or manage the local copy of the team project. If this happens, you’ll need to get a new local copy.

GETTING A NEW LOCAL COPY

1. CREATE A BACKUP RP FILE

First, open your current local copy and use the "File > Export Team Project to File" feature to create a standalone .rp version.


If you can't open your local copy, try recovering an auto-saved backup via the "File > Recover File from Backup" feature. Then skip to step (4) below.

2. DON'T OPEN THE RP FILE

When asked whether you want to open the exported file, choose "no"—it isn't necessary at this point.

3. GET THE PATH TO THE TEAM DIRECTORY

If you already know the path to the team directory, you can skip this step. Don't forget that the project name needs to be at the end of the path.


To look up the path if you don't know it, open the team project history browser via the "Team > Browse Team Project History" menu command and copy the path from the "Team Directory" field. Then close the dialog.


If you don't have the path and can't open your local copy to check, you'll need to have a colleague get into the team project history browser from their local copy and grab it for you.

4. GET THE NEW LOCAL COPY

Now that you have the team directory path, get a new local copy of the team project via the "Team > Get and Open Team Project" dialog.

5. CHOOSE A NEW LOCAL DIRECTORY

While you're getting the new local copy, you'll need to choose a location on your computer where you want to put it. Because you created or retrieved a backup of your current local copy in step (1), one option is to delete your current local copy in order to get your new local copy to the same location if you wish. (If you want to do it this way, you'll need to use your operating system's file browser to navigate to and delete the old local copy—or else Axure RP won't let you specify that location for the new one.)


Alternatively, you can plan to save your new local copy to a new location. One way to keep your files organized in this scenario is to store the new local copy in a subfolder adjacent to the old local copy folder and append something to the folder name to remind you which one's which (e.g. call it something like "ProjectName_NewLocal1").

6. IMPORT ANY CHANGES FROM THE BACKUP

If there were changes you'd like to import from the old local copy, you can do that now.


Use the "File > Import From RP File" wizard to import any items featuring changes from your backup .rp file.


Since these items will most likely be still checked out to your previous local copy, you will need to choose to the "Edit All w/o Check Out" option when warned that the pages are already checked out. After importing the pages and checking in, you will be asked to steal the check out from the other local copy. Do that by selecting the pages in the warning dialog and clicking "Steal Check Out". (Read more about stealing a checkout above.)


After the "steal" step, all of your changes should be committed to the team directory and the project's check-outs should be back to normal. Nice work!

UPGRADING A TEAM PROJECT TO RP 8 FROM AN

EARLIER VERSION OF AXURE RP

Team projects from Axure RP 7 can be opened directly in RP 8 (build 8.0.0.3302 or higher).


A team project created in any earlier major release of Axure RP (6.5, etc.) will need to be exported to a regular .rp file and then recreated as a team project in RP 8. We recommend that you open and resave your .rp file in each successive major release when upgrading across multiple versions. You can download earlier versions of Axure RP from <www.axure.com/previous>. Follow the steps below if you are upgrading across multiple major releases.

1. CHECK IN EVERYTHING

Ask everyone working in the project to use the earlier version of RP to check in all of their changes.

2. GET ALL CHANGES

Using the earlier version of RP, sync your local copy with the team directory using the "Team > Get All Changes from Team Directory" menu command.

3. EXPORT AN RP FILE

Still in the earlier version of RP, export a standalone .rp file using the "File > Export File from Team Project" menu command.

4. CREATE THE NEW PROJECT

Open the exported standalone .rp file in RP 8 and use the "Team > Create Team Project from Current File" menu command to recreate your team project.

5. NEW LOCAL COPIES

Each person working on the project will need to get a new local copy in RP 8.

COMMON PROBLEMS

SVN ERROR MESSAGES

4. OPEN AND SAVE IN INTERMEDIARY VERSIONS

Open the standalone .rp file in any intermediary versions, e.g. Axure RP 7. Save the file and close it.