I've been testing a VSS to TFS migration for my job. The test server that we have tfs installed on has the drives partitioned. The system stays on C drive and we don't touch that drive. We have the E drive for our applications.
I wrote the configuration file so the migration would run and it runs fine. But for some reason it's migrating the data to the C drive. The C drive only has enough space so the system will run fine. Here is what my config file looks like:
<?xml version="1.0" encoding="utf-8"?>
<SourceControlConverter>
<ConverterSpecificSetting>
<Source name="VSS">
<VSSDatabase name="E:\TFS\projectfolder\project"></VSSDatabase>
</Source>
<ProjectMap>
<Project source="$/" Destination="$/Test-Location"></Project>
</ProjectMap>
</ConverterSpecificSetting>
<Settings>
<TeamFoundationServer name="servername" port="port" protocol="http" collection="tfs/DefaultCollection" />
<Output file="Migration.xml" />
</Settings>
</SourceControlConverter>
Why is VSSconverter migrating my files to the C drive? I've researched this for a week or more and cannot find anything that is helping me out. Do I need to specify the E:\ in the destination? Could this be caused by how the TFS server was configured? Any help would be appreciated.
I'm not sure which data you are talking about. TFS stores all data in the SQL database unlike VSS that stores the source on the file system. Do you store your TFS database file on C: drive on that box by any chance?
Related
I'm trying to set proxy server in client.conf globally. But it does not working.
I created plastic-global-config repo on cloud, created "allrepo" folder, added client.conf file in it, committed. But after restarting GUIclient, globalconfig folder doesn't appeared in /local/plastic4 folder.
My client.conf file contains:
<?xml version="1.0"?>
<ClientConfigData xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Language>en</Language>
<WorkingMode>LDAPWorkingMode</WorkingMode>
<CacheServer>192.168.1.231:9999</CacheServer>
</ClientConfigData>
What am I doing wrong here?
I'm afraid the "client.conf" is a local client file that cannot be globally configured. Please check the following link where we explain all the available files to be globally configured:
https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide
I'm trying to build a TDS project the TFS hosted server. The project uses the HedgehogDevelopment.TDS package, but when build time comes, a license exception occurs.
I am passing the owner and key information to visual studio in this way:
/p:TDS_Owner="$(TDSOwner)" /p:TDS_Key="$(TDSKey)"
Where the variables are the owner and key. I have verified that the values are correct, yet I still get a license exception, indicating that TDS cannot find these values.
Is there a flaw in how I am giving visual studio these parameters? How can I get a TDS project to build using the HedgehogDevelopment.TDS package?
First, please make sure you have installed TDS on the build server.
You can actually include the License info with a config file by following below steps.
Add this file manually here: xxx(TDSFilesFolder)\HedgehogDevelopment\xxxProject\vx.0
Call the file TDSLicense.config
Save the following (with your license information in) in the file: <?xml version="1.0" encoding="utf-8" ?> <license Owner="CompanyName" Key="aaaa-bbb-ccc-dddd" />
If it's a permissions issue with reading the license from the registry - this should sort it out. More detail info you can take a look a this blog.
I keep getting the TF60024 error "Unable to create the intermediate database required by VSS Converter on Microsoft SQL Server .\SQLEXPRESS. CREATE DATABASE permission denied in database 'master'." When I run the VSSConverter with "Migrate" and my xml file.
Here is my XML file:
<?xml version="1.0" encoding="utf-8"?>
<SourceControlConverter>
<ConverterSpecificSetting>
<Source name="VSS">
<VSSDatabase name="z:\CHS_SourceSafe"></VSSDatabase>
</Source>
<ProjectMap>
<Project Source="$/Account Automation SQL" Destination="$/Account Automation SQL"></Project>
<!--Other projects excluded-->
</ProjectMap>
</ConverterSpecificSetting>
<Settings>
<TeamFoundationServer name="CHS-TFS" port="8080" protocol="http" collection="tfs/DefaultCollection"></TeamFoundationServer></Settings>
</SourceControlConverter>
My network guy told me to mention:
I am a local admin on the Server (CHS-TFS)
I am a sys adm on both TFS 2010 64 bit and SQL Server (2008 R2 64 bit).
I'm running this from the (win 7): "c:\program files (x86)\Microsoft Visual Studio 10.0\Common7\IDE" folder.
The ANALYZE function returned 0 errors.
I've tried adding the ".root" to the end of the Source, that didn't help.
We also tried NT AUTHORITY\NETWORK SERVICE full access (thinking that maybe it was using that as a default login)
Any suggestions?
EDIT:
I found this one blog post:
http://blogs.msdn.com/b/dparys/archive/2009/09/17/create-database-permission-denied-in-database-master-my-fix.aspx
that seemed to deal with the issue, I worked though it, and still I'm getting the same error.
I finally figured out how to do this a different way. I watched this video:
You Tube video that explains other way of doing this
And downloaded this tool:
File to download
And it was much easier to do.
ERROR:
Cannot attach the file 'C:\Users\dboyle\Desktop\New folder
(2)\OilNGasWeb\OilNGasWeb\App_Data\aspnet-MvcApplication4-20130726115749.mdf' as database 'aspnet-MvcApplication4-20130726115749'.
*This error occured after deleting my Web.config file *( replacing it with a new one from a new project and replacing the default conection string with what i needed)
EDIT:
Sofar I have tried deleting the .mdf physical file and from VS, also from SQL. Then re-running the update from the package manager within VS. The database gets made, yet same error persists.
I have found
<ObjectGroup Name="DefaultConnection" Order="1" Enabled="False">
<Destination Path="Data Source=ANE-SQL\ANESQLSERVER;Initial Catalog=OilGas;User ID=software;Password=GLvp$102" />
<Object Type="DbCodeFirst">
<Source Path="DBMigration" DbContext="OilNGasWeb.Models.OilNGasDB, OilNGasWeb" MigrationConfiguration="OilNGasWeb.Migrations.Configuration, OilNGasWeb" Origin="Configuration" />
</Object>
</ObjectGroup>
in my website.pubxml file ( it still shows my old database name ) will this interfier?
While doing database update using code-first migrations in ASP.Net MVC, came across the strange exception and details are as follows,
Issue back ground details,
Manually deleted auto created ".mdf" file from App_Data folder using Visual Studio.
Executed update-database in package manager console. Then got the below exception,
System.Data.SqlClient.SqlException (0x80131904): Cannot attach the file 'E:\Backup\Practice\MVC4\DotNetExamples\DotNetExamples\App_Data\DotnetExamples.mdf' as database 'DotnetExamples'.
Solution:
If you delete the DB file, it still stays registered with SqlLocalDB. Sometimes it fixes it by deleting DB. We can do this from the command line.
Open the "Developer Command Propmpt for VisualStudio" under your "Start/Programs menu->All Programs->Visual Studio 2012->Visual Studio Tools"
Run the following commands:
sqllocaldb.exe stop v11.0
sqllocaldb.exe delete v11.0
Please have the .mdf file and SSMS instance of the Database Deleted.
Now execute "update-database" command from package manager console and it will create database for you without any obstacles.
You probably have an attached db with the same name in your SQL Server, just open up SQL remove it and run your MVC4 again.
I had the same problem.
I used Visual Studio 2015 and SQL Server LocalDB v12 so the answer from the accepted answer didn't work for me. I used these commands instead (without version) and it worked:
sqllocaldb.exe stop
sqllocaldb.exe delete
I am trying to deploy a console application to a folder on a DMZ server using autodeploy with MSBuild and Team Foundation Server.
I am already deploying multiple sites to that same server and it works great. I have tried multiple ways but the files are not deployed.
First, I tried to deploy the console app in the same way as i do for my web site, ie:
<MSBuild
Projects="$(SolutionRoot)\MySolution.sln"
Properties="AllowUntrustedCertificate=True;AuthType=Basic;
Configuration=DEBUG;CreatePackageOnPublish=True;
DeployIisAppPath=Default Website/dummy.dev.myapp;
DeployOnBuild=True;DeployTarget=MsDeployPublish;
MSDeployPublishMethod=WMSvc;
MsDeployServiceUrl=https://xxx.xxx.xxx.xxx:8172/MsDeploy.axd;
UserName=userid;Password=password;UseMsdeployExe=True"
/>
Without success.
EDIT: No error message is returned. It all seems to go well.
Then, I also tried to deploy the console app as follows:
<Exec Command=""C:\Program Files\IIS\Microsoft Web Deploy V2\MSDeploy.exe"
-verb:sync
-source:contentpath="$(OutDir)\MyApp.Precompiled"
-dest:contentpath="D:\dev.myapp",computername=xxx.xxx.xxx.xxx,username=userid,password=password"
ContinueOnError="false" />
I actually also tried with computername as https://xxx.xxx.xxx.xxx:8172/MsDeploy.axd.
EDIT: The following is what I got.
EXEC: FileOrFolderNotFound
EXEC: Object of type 'contentPath' and path 'E:\Builds\1...\dev.myapp' cannot be created.
EXEC: The path '\?\E:\Builds\1...\dev.myapp' is not valid.
EXEC: 1.
E:\Builds\1...\BuildType\Targets\Deploy.targets (142): The command ""C:\Program Files\IIS\Microsoft Web Deploy V2\MSDeploy.exe" -verb:sync -source:contentpath="E:\Builds\1...\dev.myapp" -dest:contentpath="D:\dev.myapp",computername=https://xxx.xxx.xxx.xxx:8172/MsDeploy.axd,username=userid,password=password" exited with code -1.
I realize I haven't read all of the error, Do I really need an UNC path?
Does anyone know how to do this?
I finally found out how to make it work.
<Exec Command=""C:\Program Files\IIS\Microsoft Web Deploy V2\MSDeploy.exe"
-verb:sync
-source:contentpath="$(OutDir)\MyApp.Precompiled"
-dest:contentpath="D:\dev.myapp",computername=https://xxx.xxx.xxx.xxx:8172/MsDeploy.axd,username=userid,password=password,authtype=Basic
-allowUntrusted=True"
ContinueOnError="false" />
I changed computername to computername=https://xxx.xxx.xxx.xxx:8172/MsDeploy.axd, added authtype=Basic and allowUntrusted=True and voila it worked.
It was quite frustrating not having any kind of feedback of what went wrong with the first option. But when I was using the second alternative I got feedback to work with.
If anyone know how to make this work using the MSBuild task, please feel free to enlighten me.
Try dirPath provider instead of contentPath, it'll behave more like a folder sync rather than IIS web site deployment.
Considering the sync worked using the EXEC task, did you make sure you have the Microsoft.WebApplication.targets in your csproj (or vbproj) file? I could see it just ignoring that msbuild task without the correct targets file included.
For example in my web service project files, I have this towards the bottom of my csproj file
<Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" />