no synchronization definition was found
When trying to show synchronization history of a ClearCase Synchronization Stream, the following error was displayed. Not sure how it was deleted (if it was deleted). Is there any way to recover it or need to create a new one? Thanks.
"unable to display history because no synchronization definition was found; definition was most likely deleted by the user" |
7 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 01 '08, 2:23 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The most common way of getting this error is if you have not yet had a
successful sync of a stream (the sync definition gets created by the sync request, not when the sync stream is created). Have you had a successful synchronization of this stream yet? Cheers, Geoff gdang wrote: When trying to show synchronization history of a ClearCase |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 01 '08, 4:46 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
First, just to make sure that nothing funny has happened to your sync
stream, request a sync on that stream. If that sync is successfully started, and then successfully completes, try asking for the sync history again. If you get the same error message reported below, go to the Jazz Provider Properties of the sync stream, and find the value of the BUILD_ENGINE_NAME property. Then go the the Team Artifact Navigator view, open the project that contains the sync stream, and open the Build Engines folder. You should find a build engine there with the name specified in the BUILD_ENGINE_NAME property. Right click on that build engine, and select Show Build Activity. That should display the synchronization history. Let me know what happens when you try this sequence of steps. Cheers, Geoff gdang wrote: When trying to show synchronization history of a ClearCase |
Thanks, Geoff.
I was not able to request a sync on that stream. ==> the error shows "An error occurred while synchrionizating streams. Reason: Synchronization stream in use by other process". |
When the sync was working, the repository connection was https://localhost:443/...... Now I changed the URL to the IP of the jazz server. This seems contributed to the issue.
Synchronization.bat window shows the following message..... 2008-07-01 22:34:18 CRRTC3524W: Repository connection failed : CRJAZ0099I HTTP error "Connection refused: connect" accessing https://localhos t:443/jazz/service/com.ibm.team.repository.common.internal.IRepositoryRemoteServ ice. |
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 01 '08, 11:22 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Our code does not detect what is in effect a "move" of the repository to
a new URI. I'll add a workitem for us to do so. One simple thing to do in this case is just create a new sync stream on that ClearCase stream. If you want to keep using the existing sync stream, then you can just change the appropriate argument in the synchronization.bat script (you'll recognize it :-). Another way to get the script regenerated is to just change the sleep time of the synch engine by modifying the BUILD_ENGINE_SLEEP_TIME property of the Jazz Provider (this will automatically regen the synchronization.bat script, at which time it will pickup the new repository URI). Then execute the "restart sync engine" operation, and verify that the sync engine can successfully be started. Once you have a new or fixed sync stream, request a sync, and verify that the sync succeeds. (If the sync fails with "sync stream in use", "unlock" the sync stream from the ClearCase Provider Properties page, as described in a previous message, and then re-request the sync). And THEN you should have a sync history. Cheers, Geoff gdang wrote: When the sync was working, the repository connection was |
Thank you, Geoff, for your help. I need to get this project go alive this week. Therefore, I just recreated a new sync stream which is working fine. I will use a testing project later to play around synchronization settings later, if I see similar issues. Thanks.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.