export from 3.1.3 and import to 5.1, possible?

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
kha
Posts: 221
Joined: Fri Sep 12, 2008 8:25 am

export from 3.1.3 and import to 5.1, possible?

Post by kha » Fri Mar 25, 2011 2:42 pm

I have old source gear vault 3.1.3 and we need to consolidate it to the latest vault version we are having which is 5.1. I don't see we have export/import tool with v3.1. So, is there any recommendation for how to consolidate these 2?

Thanks! :!:

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: export from 3.1.3 and import to 5.1, possible?

Post by lbauer » Fri Mar 25, 2011 3:34 pm

Folder Export/Import was implemented in Vault 3.5, so you should upgrade your old Vault Server to at least version 3.5.3. You won't need a license, as only the Vault Admin will need to login.

If I recall, the Vault Folder Export/Import Tool can be found in the Vault Admin Tool directory in version 3.5.3. The Export/Import Tool was also in the Vault client directory, so you could install the Vault 3.5.3 client to get the Export/Import Tool for that version.

Previous versions are available here:
http://www.sourcegear.com/vault/downloads2.html

Please note that if any files or folders have been obliterated from the database, Vault folder export/import may not be able to re-create the history, as it has been deleted..
Linda Bauer
SourceGear
Technical Support Manager

kha
Posts: 221
Joined: Fri Sep 12, 2008 8:25 am

Re: export from 3.1.3 and import to 5.1, possible?

Post by kha » Mon Mar 28, 2011 11:50 am

Hi Linda,

I upgraded to 3.5 and when I tried to connect to the vault server, i got this error:
Unable to connect to http://208.201.131.29/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The request failed with HTTP status 403: Forbidden.

Everyone is on the same server, db on server A, vault server is server A, and client on server A as well.
When I did the upgrade, I entered in the sa password for the sql and it created sgvaultuser in that sgvault db.

When I looked at the sgvault.log, i found this:

----3/28/2011 11:46:23 AM admin--servername(IP)--SSL Disabled System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at VaultServiceSQL.VaultSqlConn.OpenConn()
at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(HttpApplicationState has, VaultLoginInfo vli, VaultSqlConn& conn) at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at VaultServiceSQL.VaultSqlConn.OpenConn()
at VaultServiceAPILib.VaultServiceAPISystem.GetOpenSqlConn(HttpApplicationState has, VaultLoginInfo vli, VaultSqlConn& conn)


I can browse the http://<vault server IP>/vaultservice fine.
Last edited by kha on Mon Apr 09, 2012 10:25 am, edited 1 time in total.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: export from 3.1.3 and import to 5.1, possible?

Post by lbauer » Mon Mar 28, 2011 4:31 pm

What operating system is this on, and what version of SQL Server are you using?

It's strange that it's trying to use Network Services.

Send me a copy of the Vault Server installation log. It's called Vault_install.log and is in your user's temp directory on the server machine. Type %temp% in an address bar to find your temp directory. Send the log zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

See if this is relevant to the HTTP 403 error:

http://support.sourcegear.com/viewtopic ... den#p23700
Linda Bauer
SourceGear
Technical Support Manager

kha
Posts: 221
Joined: Fri Sep 12, 2008 8:25 am

Re: export from 3.1.3 and import to 5.1, possible?

Post by kha » Tue Mar 29, 2011 2:03 pm

Linda,

I did a search on c: and D: on the server and found no vault_install.log (nor vault*.log)
%temp% has no log in there, just one picture file :? %temp% takes me to C:\DOCUME~1\......

the vault server is windows 2003 SP2

kha
Posts: 221
Joined: Fri Sep 12, 2008 8:25 am

Re: export from 3.1.3 and import to 5.1, possible?

Post by kha » Tue Mar 29, 2011 3:24 pm

I found the problem. When i did the installation, i choose Machine option that uses Network Service.
I just uninstalled and reinstall with web.config option, and everything works fine for me.

Thanks, Linda. :!: :)
Last edited by kha on Wed Mar 30, 2011 1:55 pm, edited 1 time in total.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: export from 3.1.3 and import to 5.1, possible?

Post by lbauer » Wed Mar 30, 2011 8:44 am

Thanks for the update. That's good news. : )
Linda Bauer
SourceGear
Technical Support Manager

kha
Posts: 221
Joined: Fri Sep 12, 2008 8:25 am

Re: export from 3.1.3 and import to 5.1, possible?

Post by kha » Wed Mar 30, 2011 1:58 pm

Linda,

I exported a repository from 3.5 version and tried to import it to 5.1 version, it asks me to
"Please select a User from the drop down list, and click "map" to associate the two.
Mapping an existing Vault user to a new one will replace any existing association"

I don't want to map user, i clicked cancel and it quit the import wizard. I guess I have to do User Mapping, but don't know why i have to map and who should I map to. I have to map users to all listing "export users" which is like 10 of them, otherwise the OK button won't be enabled for me to click. :cry:

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: export from 3.1.3 and import to 5.1, possible?

Post by lbauer » Wed Mar 30, 2011 3:33 pm

You do have to map users. Folder export/import recreates all transactional history and transactions are associated with users. Often, the users associated with the exported data are the same as in the Vault database where the data will be imported. So you want "Bill" that you're importing to be the same as "Bill" in the destination repository.

If the user doesn't exist in the destination, you can create a new user to map to and then later deactivate that user on the destination server so the user won't take up a license. If the data being imported is primarily archival, and who did what isn't important, you can map all the users to a single user in the new location.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply