we got TFS 2013 install, it was successful install and working fine, until we need change the data tier database, so how could config TFS app server pointing to new named database,
the database instance is same one, just changed it name
You can use the tfsconfig registerdb and remapdbs command to achieve this rename/move scenario
tfsconfig.exe remapdbs /DatabaseName:data.tfs.contoso.local;Tfs_Configuration /SQLInstances:data.tfs.contoso.local
Ed has a blog on this too.
Related
I'm trying to compare the Azure SQL Managed instance to my local database project. But when I make a selection of the database "Ok" button is not getting enabled.
This used to work a month ago but all of a sudden it stopped working.
It's an issue with only one Azure SQL Managed Instance. We have one more Azure SQL Managed instance which is working alright(We can compare successfully).
And also it's just with Visual Studio, I have tried Visual Studio 2019 as well. We can compare alright in 'Azure Data Studio'.
Same issue with MI. Fixed by manually editing SchemaCompare.scmp file. Just add your source module section:
<SourceModelProvider>
<ConnectionBasedModelProvider>
<ConnectionString>Data Source=db.database.windows.net;Initial Catalog=aaa;Persist Security Info=False;User ID=xxx;Pooling=False;MultipleActiveResultSets=False;Connect Timeout=60;Encrypt=True;TrustServerCertificate=False;Authentication="Active Directory Interactive"</ConnectionString>
</ConnectionBasedModelProvider>
</SourceModelProvider>
Its been quite sometime that I am trying to publish the data base for my website using webdeploy in VS 2013 but I keep getting the following error:
Web deployment task failed. (Could not generate deployment script.
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.
I have tried installing the new updates. I am making sure that the local server is running during deployment. I have made sure that I enter the full server name rather than a dot. I have literally done everything that I could think of but to no avail.
Can anyone help me, please?
The issue might be related to VisualStudioVersion environment variable, which needs to be set to VisualStudioVersion=11.0 or VisualStudioVersion=12.0 to support SQL Server 2014. Check this answer, also here is the info how to target the VisualStudioVersion.
I'm getting nothing but this error TF246017 I'm not able to access TFS as admin or domain user
While accessing administration console, showing the error TF246017
Domain users getting TF31001 where the server returns TF246017
TFS was working fine with SQL Server 2008. And now we have also installed SQL server 2012 in the same machine.( I believe it doesn't connected anyway to tfs server)
But, even after uninstalling SQL 2012, it displays the same error
In application tier/ database tier, getting error as Error retrieving value.
Unable to access http://xxxxxxx:8080/tfs displays same error TF246017
And also, im unable to locate the sql express database to take the backup.
How to resolve this issue?
Note : I'm using TFS 2012 and VS2010
Login to windows server using the same windows credential user you used during SQL Server installation.
Verify or add the new windows user credential (assuming you are using different user credential to connect to TFS) to be part of sysadmin user group in SQL Server or ask your SQL Server DBA to add the user to sysadmin group.
Note: This is required because for every new TFS Team project created, TFS presents 2 option empty database or new database. To create new database the TFS admin user have to be part of SQL server sysadmin group
If TFS 2012 was installed using the same windows credential, open the TFS Admin console and add or verify the user is listed in "administration Console Users" list.
If TFS Admin console reads "You do not have permission or not administrator" or something along this line, then you need to log out and log back using the correct windows credential used for installation or use one of the TFS admin user and then add the new user credential.
Recommendation: To avoid confusion I would recommend use the same user credential for SQL Server and TFS server. Ex: "domainname/tfs" is local admin to the server, sysadmin in SQL Server DB and also admin user to TFS server.
To make like simple start of by, adding the windows user (intended to use as TFS admin) as windows administration group. Then logout and log back using the TFS admin user to install SQL Server and TFS server.
I had a similar issue branch code in my version of TFS (Azure DevOps Premise). I tracked my issue down by looking at the event viewer on the local TFS server and found that I was that I was getting the following SQL error:
DESCRIPTION: SQL Server Assertion: File: , line=951 Failed Assertion =
'IS_OFF (BUF_MINLOGGED, m_buf->bstat) || pageModifyType !=
PageModifyType_Contents || GetPagePtr ()->IsTextPage ()'. This error
may be timing-related. If the error persists after rerunning the
statement, use DBCC CHECKDB to check the database for structural
integrity, or restart the server to ensure in-memory data structures
are not corrupted.
I found the first item in the following answer solved my issue.
I simply switched my main TFS database containing my collection to FULL recovery mode and I was immediately able to proceed with my previously erroring task.
Connect to your SQL instance via SQL Server Management Studio and check if any of the TFS databases are in a "Recovery Pending" state. If so, restart your SQL instance and the state should return to normal. Worked for me!
Just find out the Team foundation application under application pool. right click and go to advance setting set the identity using the credentials used for SQL Sever or TFS Admin and done ..you can now access the TFS as earlier.
I was tasked to research migrating a 2007 MOSS to ShrePoint 2010. Got two servers, one is runing a SQL 2008, and the other has SharePoint 2010 already installed. I need to migrate several publishing and team sites and their corresponding databases. I started reading this article on Upgrade and Migration for SharePoint Server 2010
, then another at Migrate an existing server farm to a 64-bit environment but have a little confusion about wheather I'm migrating, upgrading, or moving the system, as each article defines steps to do this.
Current 2007 MOSS and SQL 2005 are on Windows 2003 32-bit OSs. The new system which at this point in not part of the farm but is in the same domain, are a 64-bit blades running Win 2008 OS with SQL 2008 and SharePoint 2010 - all already instaled / Central Admin site already running. The whole farm consists of 2 severs I just described.
Thanks for reading my post and appreciate any pointers!
Risho.
I just went through this exact scenario. The documentation on the various methods can get confusing. Note, for simple farms (no BDC, etc.), all you really need is the content databases. Here's a simple way to accomplish your goal:
On existing, 2007 farm, make sure it's Service Pack 2
On existing 2007 farm, run stsadm -o preupgradecheck
Fix any errors identified by the upgrade checker
Backup the Content database(s) you want to migrate (old 2007 farm)
Restore Content database(s) to new SQL server
Create a new Web Application on the new 2010 farm. A new WebApp will need to create a Content DB, so name it something like WSS_Content_Temp. This will be the WebApp that you will restore your Content to, so name the WebApp appropriately. You'll remove the content DB, so name it whatever you want.
From PowerShell, run: Test-SPContentDatabase -name <NameOfMovedContentDB> -webapplication http://yourNewWebApp
Fix any errors identified
From PowerShell, mount the newly restored/moved database. Run Mount-SPContentDatabases -name <NameOfRestoredContentDB> -webapplication http://yourNewWebApp. You should see a progress % number that is incrementing. Depending on how big your content databases are, this could take a while (30+ minutes)
From Central Admin -> Application Management, select/highlight your new Web Application.
The go back to Central Admin -> Manage Content Databases, and remove the original, temp Content DB (WSS_Content_Temp)
At this point, if all went well, you should be able to browse to http://yourNewWebApp and see all your content.
Rinse and repeat as needed.
This might be wrong place to ask this question.
I spent effort in setting up thr sharepoint 2010 2 tier farm. I have settled up the sql server databases required for sharepoint, installed on different machine. and sharepoint on another machine. it took around 6 days, but at the end i noticed that i have computer name with something "win43453-676" like this. where as my manager wants to to keep relavant name like "CentralAdminMachine" of central admin pc. if i changed the name of machine , i am unable to open even central administration site. is there any remedy to change this name in configuration database and all....?
There is both a PowerShell cmdlet and an STSADM command that allow you to change the server name. Both require that you first change the name through the standard Windows System control panel. After that (and a restart) you can use:
Rename-SPServer [-Identity] <OriginalServerName> -Name <NewServerName>
http://technet.microsoft.com/en-us/library/cc263117(office.12).aspx
or
Rename-SPServer [-Identity] <SPServerPipeBind> -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]]
http://technet.microsoft.com/en-us/library/ff607556.aspx
There are some people who seem to recommend the STSADM (even though PowerShell is the Microsoft recommend way on SharePoint 2010) because it seems to work and not the give error that the PowerShell command does about feature dependency, but it looks like you can try either one.
And you may need to update your alternate access mappings to enable any custom URLs to work as well.