TFS 2012 Install fails on SQL configuration. TF400711 - sql

Im installing TFS 2012 on a windows Server 2012 VM. Im using a single server configuration and have SQL server standard installed. When I go through the TFS setup wizard it hangs on creating the database and after an hour or so I get the error below.
TF255356: The following error occurred when configuring the Team Foundation databases: TF400711: Error occurred while executing servicing step Update Servicing Resources for component UpdateTfsServicingResources during Install: TF246018: The database operation exceeded the timeout limit and has been cancelled. Verify that the parameters of the operation are correct.. For more information, see the configuration log.
You can view my log here:
https://docs.google.com/file/d/0B8ioN5Ats0NlY1AzYjRJR19wck0/edit?usp=sharing&pli=1

Related

SSIS Deployment Error while deploying packages into SQL Server

I was Trying to deploy SSIS package from Visual studio 2019 into MS SQL Server 2016, I have been facing deployment error as shown below:
"“A .NET Framework error occurred during execution of user-defined routine or aggregate "deploy_project_internal": System.ComponentModel.Win32Exception: A required privilege is not held by the client.”
After few hours of debugging found that the error is actually from SQL Server. SQL Server is unable to run the stored procedure from SSISDB "[catalog].[check_schema_version] ".
Hence we realized that there are certain privileges for the current service account on which SQL Server is running. Hence we have created a new local admin account and provided all privileges.
• As per Microsoft suggestion, we have added the SQl server service account & SQL server integration service account in the below Configs :
o Edited DCOM config properties and provided granted the Local Launch and Local Activation permissions for the below component services
 Microsoft SQL Server Integration Services 11.0, Microsoft SQL Server Integration Services 12.0 and Microsoft SQL Server Integration Services 13.0
o Further we extended permissions for both the service accounts as below :
 Log on as a service .
 Permission to write to application event log.
 Impersonate a client after authentication.
 Adjust memory quotas for a process
Below are the two group policies yet to be added :
 Bypass traverse checking
 Replace a process-level token
I would like to know if this resolves the issue and please suggest anything that we are missing here to resolve the issue.
After adding the New service account to the listed group policies, the deployment got succeeded.
I ran into this problem after a new Security Policy was put in place that broke WinRM (disabled "Allow remote server management through WinRM"). Even after rolling back the change I could not deploy SSIS packages. I finally fixed the problem by running the "Repair" SQL option from the installation disk and then restarting the server. After that deployments worked as normal.

Team Foundation Server 2015 Database Error TF:246017

my tfs console stop working giving error. When i open the tfs administrator console.it works fine a week ago but suddenly start giving this error and my all developers are facing this error.
TF246017: Team Foundation Server could not connect to the database. Verify that the instance is specified correctly, that the server that is hosting the database is operational, and that network problems are not blocking communication with the server.
I have check the databases for the tfs they are working fine means they accept queries and showing result.
also i have checked through command DBCC CHECKDB command and giving zero errors.
kindly help me for this error I'm new to TFS
TFS 2015 installed on Windows server 2012 R2

Error while installing database engine service with SQL Server 2017

I get the error:
Object reference not set to an instance of an object
while I am installing the SQL Server 2017 database engine service.
In previous tabs, only the windows firewall gives warning, but I already have made rule for port 1433. In SSMS, when I try to connect with database engine, it causes a login failed error (Error 18456, state:1).
I have already tried reinstalling and also tried to use .net framework repair tool, but that didn't help.
Also I found that interesting thing that I do not have problem with connecting to analyses services in SSMS.

Configuring TFS SQL Server Instance connecting Error

I am new to Team Foundation server and when I am configuring TFS for SQL Server, I am getting below error where TFS is not able to connect to the SQL Server instance where as when I connect to SQL Server it is connecting successfully. Both SQL Server and TFS are on the same server machine. Please advise
Error while clicking on Test Link
According to the error info, you need to make sure the TFS service accounts(which you started the TFS Installer) have permissions on the DB server.
Add the account in the list of logins in SQL Server side and retry
the previous operation.
Moreover, if Windows Firewall is on the TFS box, switch it off during the installation and try again. After finish the installation reopen the firewall.
For more details you could take a look at below similar issue:
Errors during TFS 2013 install–and how I worked past them
Workaround Error TF255049: Punching a hole through Windows
Firewall

What are the connection managers to connect to an external SSAS cube in SSDT 2012

We are experiencing issues when executing an SSIS package from a SQL Server job. However, when we execute the package locally, it is successful. The package connects to an external SSAS cube using MDX. I have attached the error message below. The connection manager is OLE DB Provider for Analysis Services 11.0. We can successfully ping the external site where the cube is located from the server
with the job.
Unfortunately, at this point, it appears that the issue is related to the windows server core install. I found this link which outlines the issues related to core - http://technet.microsoft.com/en-us/library/ee441257(v=ws.10).aspx. We can get the job to execute from a Windows Server with a full version install, but not on the core install.