New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Using the ForgeUsing the ForgePotential Error When Committing Changes To CodePlex RepositoriesPotential Error When Committing Changes To CodePlex Repositories
New Post
8/3/2010 9:57 PM
This afternoon and evening I received the following error when attempting to commit a number of changes to the CodePlex repository for the DotNetNuke Feedback module ( project:

Commit failed (details follow):
Repository UUID '142e9c35-602f-4880-9f37-ec48a24daa6a' doesn't match expected
UUID '5ff7c347-ad56-4c35-b696-ccb81de16e03'

As the commit operation had worked fine several weeks ago I began looking through the CodePlex discussion forum and issue tracker for recent changes/issues and immediately found that other project users had begun experiencing the same issue beginning a few of days earlier. I also found the following on the CodePlex webblog:

The information in this entry applies to project coordinators and developers that are using TFS with the Team Explorer client. If you are using Mercurial or a Subversion client, then nothing will change for you.

During the upcoming weeks we will be migrating all of the CodePlex TFS projects onto our new TFS 2010 servers. This upgrade will allow us to support new TFS features and provide increased server performance and reliability. The move will happen on a server by server basis . . .

Since I was using Tortoise SVN as my subversion client, I did not at first think that this was related even though the TFS server for the DNN Feedback project was migrated on August 2nd. However, it appears that the migration did cause the UUID of each TFS repository to change thus causing a mismatch between the new repository UUID and that stored in the entries file in each project folder's hidden .svn folder. According to a CodePlex discussion thread of today's date, the mismatch can be corrected by first doing a clean checkout of the projects root folder. However, in my case, I already had made modifications to 6 files and made two file additions and two file deletions due to renames of version specific release notes and test cases text files so I wanted to avoid doing a clean checkout if possible. I also discovered that the Checkout option was not available on the Tortoise SVN context menu so could not have done so even if I wanted to.

The following blog post of today's date on Gut Instinct (of all places) finally led me in the right direction to manually update the entries files in each .svn folder:

Here are a few notes on the manual update process:

  1. In Windows folder options under Advanced Settings/Hidden Files and Folders select "Show Hidden Files, Folders and Drives"
  2. In each .svn folder which will reside in each folder of your project, locate the entries file and in its properties uncheck "Read Only"
  3. In the text editor of your choice open the entries file (note that the filename has no file extension) and do a find/replace to replace the old UUID (actually a GUID) which will the the last or "expected" UUID in the above error message with the new  UUID which will be the first or "repository" UUID in the error message.
  4. Save the modified entries file.
  5. Now when you attempt to commit your changes to the repository, no errors should be noted and all changes will be successfully made.

Hopefully my experience will save other Forge project contributors using subversion clients from the same aggravation!

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
New Post
8/3/2010 11:22 PM
Great post!  Thanks for sharing this with everyone, and being our "guinea pig."  :)

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
New Post
1/5/2011 8:03 AM
I agree with will, Great post!  Thanks a lot !
HomeHomeDNN Open Source...DNN Open Source...Using the ForgeUsing the ForgePotential Error When Committing Changes To CodePlex RepositoriesPotential Error When Committing Changes To CodePlex Repositories

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out