Error occured while importing a transaction

[kha]

I used Import/Export tool comes with the Vault Client installation. I used this tool to export folder from one repository and also used it to then imported the exported folder to different repository. I got this error:

An error occurred while importing a transaction for (TxID: 5364 on 2007-11-07 11:46 AM by <username> [12]). The import cannot continue

I tried it with other exported folders, same error happen with some (not all) of those folders while importing\. The "txID:" numbers are different for each error occurrence.

Can anyone tell me what really happened? What is the cause? I got no error at all when I exported those folders.

[lbauer]

We'd need more information before we can determine why the import didn't work. We'd like to see the Vault import log files, plus the Vault server log for the same time period. The Vault server log is sgvault.log and is in %windir%\temp\sgvault on the server machine. If you have the export logs, those might be userful, too.

Send the logs zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[kha]

Where can i find the import/export log?

[lbauer]

It should be in the same directory as the Export/Import tool, which is in the Vault client directory. It's called VaultFolderExportImport.txt.

[kha]

I just sent the attachment with subject line: Attn: Linda

[lbauer]

I think we've determined the problem:

----3/11/2009 11:10:13 AM admin--<snip>(204.255.139.211)--SSL Disabled (1143d493-683d-4002-8d5d-1fdbb060db4b) CheckIn: $/IMP-0903111109/Brtrc.Web2005/Brtrc.Web2005.csproj returned: FailCheckInCommentRequired

You have checkin comments required for the repository that you're importing into. You'll need to turn this off during the import. This setting is in the Admin Web Client under Source Control Repositories->(Repository name)->Require Checkin Comments.

[kha]

I am now having this problem again with different repository. I unchecked the "required check in comment" option of that repository, but I still get the same error. It seems like regardless whether that option is checked or unchecked, it still requires me "checkin comment".

If I don't have it check, i checked in a file to that repository without entering comment, it said "the Check In/Commit transaction failed. See the message pane for details". And the Message Pane says "a checkin comment is required".

If I have the option checked, i checked in a file to that repository without entering comment, pop up window with a shorter red X message "Check In Comments are required for this Repository".

I know it's not a problem with the repository I exported, because I could import it to a brand new repository (created for testing purposes) w/o problem.

I restarted my Vault Client every time the option changed.

[lbauer]

Are you doing another import? Is that when you're getting the error?

Have you tried restarting the Vault server and trying the import again? Use the "iisreset" command from the command line.

It's possible the setting is being cached in memory, and restarting will flush that out.

Let me know if this does not resolve the problem.

[kha]

Yes, that is what I tried to do: export and import.

Is there anyway to prevent this happen again? It's so inconvenient for our developers that everytime we need to change the settings and it doesn't take the change, then we need to restart IIS.

[lbauer]

Most changes in the Vault Admin Web Client should take affect without an IIS reset, though generally clients need to be restarted after a change. Sometimes, though, it takes a Vault server restart to flush the cache and get the new configuration info.

Did the import work after you restarted IIS? Were checkin comments no longer required?

[kha]

Did the import work after you restarted IIS? Were checkin comments no longer required?

Yes, the import work.
Checkin comments were no longer required.
This is little frustration because i had to move stuff around and this problem hold me off. I thought unchecking the "check in comment required" option which takes only 1-2 seconds, but actually it turned out to be more involved than that (restart IIS on Vault Server).

Honestly, I posted the question with a hope that I don't have to restart IIS

Thanks for helping

[lbauer]

Sorry!

It *might* be possible to just restart the Vault App pool for the settings to change. You could try that next time. Checkin comment configuration changes worked on my system without a restart, so we've not sure why a restart is sometimes needed.