TF30225: Error uploading report 'Sprint Burndown': - tfs

We are trying to create a new TFS Team Project, but we're encountering the following error.
Exception Message: The current action cannot be completed. The user data source credentials do not meet the requirements to run this report or shared dataset. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified.
I've tried changing every aspect of the TFS Report Source, but nothing appears to work.
I've also tried setting the Execution account (even to admin) and setting no user required.
However, nothing works.
Thoughts?

Related

Unable to add attachments to a Jira issue using Power automate

For the internal communication without our organization we're trying to setup a power automate flow to get the data from a microsoft forms form and create a issue in jira.
Using a Jira connector for Power-Automate we're able to create a issue but we're unable to add attachments to that issue.
We've created a Power-Automate flow that follows the following steps:
When a response is submitted, This is the trigger. When a response is submitted to the form the power automate flow will trigger.
Initialize a variable.
In order to add multiple attachments to a issue we're creating a array called aAttachments.
Apply to each loop.
Get response details from form
Create jira issue
Get attachments from form
Insert attachments in a json object.
loop trough all the entries in the json
Get file contents
Add file to array
HTTP Post request. Communicatie with the jira rest API and trying to send the file information.
All steps work apart from step 11. We keep getting a 404 return with the following output.
Issue doesnt exist or you dont have the right permissions to view the issue.
We know the issue exists because the issue is created, and the persmissions needed are open to the public.
This is the Post request:
What should change in order to add the attachments to the issue created.
This may help:
Issue attachments not getting through for non-admin users via email
1 - Navigate to the project where the issues are being created > Project Settings > Permissions and check if the user that is creating the issue (Or the default reporter set for your e-mail handler) is configured with the Create Attachments permission.
2 - Check if the attachment you are trying to add has the size allowed in your site, under Jira Settings > System > Attachments
Unable to attach files to issues in Jira

Team Foundation Server 2017 - Database Restore failing

I am running through my disaster recovery process for TFS 2017/18 and am trying to restore the databases to the SQL server 2016 instance on the same machine as the TFS Admin tool.
I am using the TFS Administration Tool to take the full backups and also to restore them.
The issue is that after the ReportServer and ReportServerTmp DBs get restored, the TFS_Warehouse and other TFS_ databases hang while doing the restore.
The log file shows the error message: Login Failed for user 'domain\machinename$' Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: ]
The SQL Server has the NT Authority/Network Service account and I have also tried giving it 'domain\machinename$' as well.
I have compared it to another Virtual Machine that has a standard installation of SQL Server and TFS Server on it and I cannot see any obvious difference.
Does anyone know of a solution for this?
Regards
Based on the error message "Login Failed for user 'domain\machinename$' Reason: Failed to open the explicitly specified database 'ReportServer'. [CLIENT: ]".
Seems the related database had been dropped (database missed) or there is any service is trying to access the database which does not exist.
That means you did not restore the databases correctly or you did not really full back up the databases correctly. And when you use SSMS and manually restore each database, the related database online again, so it works.
Yes we recommend use the Scheduled Backups feature wizard to backup or restore the DBs. However you need to note below things:
You can use the backups you made of the original deployment to restore
the data from that deployment to the new server. When restoring the
data, be sure to restore all databases and the SharePoint Farm to the
same point in time. If you followed the guidance in Create a backup
schedule and plan, you used the Scheduled Backups feature to
create your backups. You will use these backups to restore your data.
If you manually configured your backups, you cannot use the Restore
wizard in Scheduled Backups to restore those databases. You must
manually restore them using the software you used to back them up.
Source : Restore the databases
Generally, we can use the SQL Server Profiler to trace the error, then debug accordingly. Within SQL Server Management Studio , choose Tools menu and then SQL Profiler with Audit Login/Logout, User Error Message events selected and check the relative entries of login fails. See below threads for details:
SQL Server Error 18456: Finding the Missing Databases
Login failed for user 'domain\username'. Reason: Failed to open the
explicitly specified database. [CLIENT: ]
UPDATE:
For the account issue, please refer to the Required permissions part in this article :Restore the databases. Just add the TFS service account as the sysadmin role, then try it again.
Required permissions
To perform these procedures, you must be a member of the following
groups or have the following permissions:
A member of the Administrators security group on the server.
Either a member of the SQL Server System Administrator security group, or your SQL Server Perform Back Up and Create Maintenance
Plan permission must be set to Allow.
A member of the sysadmin security group for the databases for Team Foundation.
A member of the Farm Administrators group.

TFS 2018 Scheduled backups error TF401002

I am trying to create scheduled backups on my TFS server.
This phase passed (no problems here):
But in next phase (When i clicked on Configure button) i got this error:
Here is the log file:
https://file.io/ZvJKLB
** I am already changed LogOn services 'Sql server', 'Job agent' to my user.
Thank you for helping!
Please try to give db_backupoperator.
if you dont have security issues the cleanest way is to give "sysamin" permission to Matan user.
Please keep in mind this error could be masking the underlying error.
During migration to Azure DevOps Server 2020.1, I received the same error and had to review the scheduling tool's log file to find that the log file for one of the databases was full.
In both the TFS 2018 configuration tool and the Azure DevOps Server 2020.1 configuration tool, there is a link to the detailed log output. Make sure you review the detailed log output before adjusting permissions on your SQL server.
*
[Info #15:34:39.634] Granting account DOMAIN\YourServiceAccount
permissions to initiate database backups of
Tfs_YourCollectionsName [Error #15:34:39.649] Exception Message:
TF30042: The log file for the database is full. Contact your Azure
DevOps Server administrator to back up the transaction log for the
database to free up some log space.
*
The fix was to perform a LOG backup to SQL Server's 'NUL' output and then configure scheduled backups:
BACKUP LOG [Tfs_YourCollectionName]
TO DISK = N'NUL' WITH NOFORMAT, NOINIT, NAME = N'Tfs_YourCollectionName-Full Database Backup',
SKIP, NOREWIND, NOUNLOAD, COMPRESSION, STATS = 10
GO

TFS Reporting pointing to old server

I had a problem with TFS that forced me to restore TFS to a new server. Everything is working fine except for the Warehouse, Analysis Services and the Reports.
Mainly the report keeps pointing to the old server, and when I try to edit it by pointing to new server TFS Administration Console returns the following message:
I do not wish to restore my old reports; I would like to create all the TFS reporting from scratch. Would someone please point me to the correct place to start?
Thanks!
To target the report to the new server, please follow the steps below:
1). Go the TFS Administration Console, go to Application Tier -> Reporting, then click the Edit link.
2). On the Reporting dialog, check the Use Reporting checkbox.
3). On the Warehouse tab, type the new server name on the Server field.
4). On the Analysis Service tab, specify the new server name in the Server field, Database name, and user account information.
5). On the Reports tab, type your new server name and click the Populate URLs button to have these reporting server URLs populated. Then type the user account information.
This was finally solved by clicking the "Specify non-default instance" checkbox, without entering any value in the following combobox. TFS has created the Warehouse and Analysis database by itself.

TFS 2012 - Scheduled Backups Failing

I'm trying to setup Nightly Backups for my TFS 2012.4 development box going off to another server, but it's failing.
The server is has SQL Express and TFS Express on it, trying to send the backups over to a network path on another share.
When going through the Wizard it will successfully pass all of the Readiness Checks, including permissions. It will fail when it tries to run the backup job for the first time under Confirming Permissions.
Error is:
TF401002: The SQL Server Database Engine failed to save the database
backup to path \[share]\c$\TFSBackup. Please grant SQL service
account read/write access to that folder.
I've tried adding "Everyone" with full control to the folder on the backup server, but it still fails with the same error.
Added the full log to http://pastebin.com/80PrYXqx
This may be a problem with using the administrative share path of c$. I suggest you go to your [share] server and make the TFSBackup folder a shared folder, and give your share the appropriate permissions.
Then you can change this:
\\[share]\c$\TFSBackup
To something like this(depending on what you name your share):
\\[share]\TFSBackup$
I know it's an old post, but just incase anyone else has issues. I had the same issue configuring backups. The following resolved it for me:
1) Open up "Services" and note the "Log On As" user for "Sql Server" and "Sql Server Agent"
2) On the folder that your backups are being saved to, go to Properties -> Security -> Edit
3) Add the users from #1, and check "Full Control", Save

Resources