Im using TFS 2012, SQL2012, and Sharepoint 2010. I went through the advanced installation of TFS and believe I missed some permission or something with an application pool. Everything related to TFS works well but any time I go to the project dashboard under Task Burndown I see this error:
Reporting Services Error
An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Query execution failed for dataset 'dsProjectGuid'. (rsErrorExecutingCommand) Get Online Help
For more information about this error navigate to the report server on the local server machine, or enable remote errors
SQL Server Reporting Services
Then under Burn Rate I see this error:
An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Query execution failed for dataset 'dsProjectGuid'. (rsErrorExecutingCommand) Get Online Help
For more information about this error navigate to the report server on the local server machine, or enable remote errors
SQL Server Reporting Services
I came across this post which seems similar but then I try to actually
process the database I get an error.
Also, if I go to the TFS Administration Console >> Application Tier >> Reporting, I see the Warehouse database and Analysis database are "Configured and Jobs Enabled".
What am I missing? Thanks in advance.
First you don't mention:
The OS (Windows Server 2012 or 2008 or 2008 R2 and which SP???)
SharePoint Foundation or SharePoint Server 2010, is it SharePoint with SP1 or not??
The error you faced when you manually try to process the warehouse???
Anyway, the reporting errors could be happened because many reasons, so my advice to you, just take a look on my 2 Guides about installing TFS 2012 and 2010, see the reporting section, you will know exactly what you should do and how to verify every step before moving to the next one, they have videos and documents with every detail steps needed.
I recommended to have a look on the whole sections because sometimes the error will be in the service account used for configuring the Report Service which will exiting on the first section.
TFS 2012 Guide
TFS 2010 Guide
http://www.experts-exchange.com/Programming/Languages/.NET/Q_26427476.html
I referred the above link which worked for me.
I set initial catalog for data source TfsReportDS as "Tfs_Warehouse" and the initial catalog for data source TfsOlapReportDS as Tfs_Analysis. Other setting I left it to default which is 'windows Integerated security' for TfsReportDS and 'credentials are not required for Tfs2010OlapReportDS
Jacob
Related
I have an AWS instance, on which SQL Server 2014 has been running for more than 3 years.
But a few days ago, suddenly the SQL Server stopped running.
I checked the server and tried to start SQL Server service from services, from SQL Server Configuration Manager etc. but I'm not able to start the server and got following error:
So I checked event viewer entries and I found these two errors:
I started some research work over web to overcome on this issue and I found that I can start SQL service using below command using T902:
net start MSSQL$REVCORD /T902
And SQL Server service started successfully.
But I want to make SQL Server / services back to normal as before so I can start / stop services normally.
I found on web that this cause is due to corruption in master SQL Server database, I don't have backup of master SQL Server database so I cannot restore it back.
I checked multiple threads over web and tried multiple things to overcome this issue but no luck.
So finally I decided to reinstall/recover SQL Server 2014, but I am getting another error while reinstalling:
Based on finding over web, all threads showing that I have to uninstall and reinstall SQL Server to make it normal again.
Please help! It's a live server with multiple calls continously so I cannot uninstall/reinstall SQL Server there due to possible data loss.
The first thing:
select * from sys.sysmessages where error = 5833
The message:
The affinity mask specified is greater than the number of CPUs supported or licensed on this edition of SQL Server.
Check your edition, and fix the affinity mask so that the number of CPUs satisfy the number which is supported by your edition.
You can fix it in SSMS on the Processors tab in your server properties, or using sp_configure
We have a Windows Server 2008 R2, Service Pack 1 with an SQL Server 2008 R2 (Microsoft SQL Server Standard Edition (64-bit), version 10.50.4042.0) for creating scheduled reports in SSRS. The Report Server services didn't start up after a server restart a while ago and when I noticed that after several days, I started the service. Then it began to loop thru all reports constantly, as if the server not was aware of that it had already done that report.
When I look in the table [ReportServer].[dbo].[ExecutionLogStorage] I can see that new reports are created constantly as fast as the previous report is ready. It looks to loop thru all reports.
I found two errors in Windows application log which maybe are connected to the problem, or not.
Failed to unload app domain DefaultDomain. The following exception occurred: Error while unloading appdomain. (Exception from HRESULT: 0x80131015).
ProcessName: ReportingServicesService
ProcessId: 4308
Failed to trace event: System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain.
I really don't understand what to do. The server has been running for several years, doing the scheduled jobs without any problem. I have restarted SQL Server Agent, Reporting Services as well as the whole server and it doesn't make any difference.
I am thankful for any help.
Lage
I got help from MS Developer Network, so want to share it here if someone get similar problems.
https://social.msdn.microsoft.com/Forums/en-US/1cd9f753-02b2-4dea-a77a-0fa33fe80c7a/sql-server-reporting-services-scheduler-in-infinite-loop-spamming-reports?forum=sqlreportingservices
Best regards
Lage
I am trying to run SQL Server Data Quality Services on SQL Server 2014 with 32GB of RAM, plenty of disk space, and the latest updates (Microsoft SQL Server 2014 (SP2-CU2) (KB3188778) - 12.0.5522.0 (X64) Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: ) (Hypervisor))
The data resides on the same server, separate database.
Knowledge base is created and published with three domains over about a million records table. And that where it stops working: creating data quality project fails after displaying cheerful message "Analysis of data source has been completed successfully" - clicking "Next" button leads to message #1, and, after restarting the application (and the server - just in case), the message #2
SQL Server Data Quality Services server has stopped working
Refresh of client view table for user [domain\user] failed.
These are fairly consistent.
Examining both the server and the client logs reveals nothing (besides a full stack dump for the error), and the only suggestion from Microsoft forums is “to apply latest service pack”; the latest service pack has been applied but still no cigar.
Any insights/suggestions would be highly appreciated!
thank you,
-al
P.S. Excerpt from the client log:
2/13/2017 9:19:26 AM|[]|1|ERROR|CLIENT|Microsoft.Ssdqs.Studio.ViewModels.Utilities.UIHelper|An error has occurred.
Microsoft.Ssdqs.Infra.Exceptions.EntryPointException: Refresh of client view table for user [domain\user] failed.;
at Microsoft.Ssdqs.Proxy.Database.DBAccessClient.Exec();
After poking around I have found a question similar to my on MSDN blog: a user complained that his DQS installation has STOPPED working after applying CU2 to his SQL Server 2014 instance... So, I downgraded mine from [(SP2-CU2) (KB3188778)] to [(SP2) (KB3171021)], and - drums rolling - everything started working!
This is not a solution but an acceptable workaround, and I can continue analyzing my data until I upgrade to SQL Server 2016, and the fun begins anew!
I have installed WSS 3.0 on Windows Server 2008 R2. Over the weekend the system admin installed Double Take to backup the server. During the installation process SQL Server 2008 was installed. Now when I load WSS the page is blank and on the server I get the classic "Internal 500" error. I uninstalled all the 2008 SQL Server items and tried to get the WSS site back up and running. I have verified the database is still located on the server and has my existing data. I have successfully backed this up for safety. I ran the Sharepoint Products and Technologies Configuration Wizard but no luck getting the site back up and running. I looked around the forums and didn't see this exact problem. Help....
Have you checked that the database is still accessible by WSS and that WSS has permissions to read/write to the database.
Also have you checked your event log on the server. This can sometimes give information about errors/issues that WSS is having when trying to access its database and failing.
Hope this helps..
Details are as follows:
Environment:
SSRS 2008 Server, SQL Server 2008 for database, Report Developed in SQL Server Business Intelligence Devlopment Studio - Reporting Project
Error Messages:
"An error occurred during client rendering."
"An error has occurred during report processing."
"Query execution failed for dataset 'DataSource1'."
"For more information about this error navigate to the report server on the local server machine, or enable remote errors "
I have done that (navigation & all that) and the result was that a parameter of a scalar variable needs to be declared. The funny thing is that those variables are properly declared in the datasource and in the report sources everywhere. Also this report/datasource worked no problem on SSRS 2005. In the Development Environment the report runs perfectly. On the server the report only fails when executing and after the parameters have been accepted. We use no stored procedures.
Any help / ideas will be greatly appreciated.
Thanks in advance.
I experienced problems in SSRS 2005 where deploying changes to a report didn't properly update changes to parameters, in particular newly added parameters. The fix was to delete the existing report using Report Manager and then upload the modified version.
Hope this helps,
Bill
When you run in the Dev environment, you're using your windows credentials. Do you also use your windows credentials when you run through SSRS? or are you using different credentials?