September 12, 2012 at 12:22 pm
If I try to run Server Actity or Query Statistics reports for any of the servers in my enviornment, I see a "retrieving Data' page for several seconds, and then "Error: A data source instance has not been supplied for the data source 'Snapshot Time'"
I dont see any specific hits on this message out there on the net, nor here.
Im running this as an administrative user. Disk Usage reports work just fine across the board. And the 'last snapshot upload times' values are all staying up to date for all instances.
I used these a day or three ago, and no changes have been made (that I am aware of) to configuration, servers that are uploading MDW data, etc...
Any thoughts or suggestions?
September 12, 2012 at 12:38 pm
my Sysadmin colleague in the next desk over said "just reboot it" in (sorta) jest.
I insisted this couldnt possibly be something a reboot would fix, and fought/googled/profiled, and screwed with this for an hour.
then rebooted.
and then it worked.:w00t:
February 22, 2015 at 5:18 pm
Hey I realise this is an old post, but I am having a similar issue except my error line ends with 'DS_TraceEvents'. I did come a across a MS connects tread which said this issue still exits in 2014, and they cant get round to fixing it (Really Microsoft? You just let known bugs form previous SQL versions into your new version?)
I was wondering, did you reboot the MDW server, or the remote server you were collecting data from?
Thank you,
D.
February 25, 2015 at 6:23 am
Duran: Have you managed to get any further?
It looks like you read the same article as me before coming here. Typical Microsoft response "It's broken, we're not going to fix it because we're too busy fixing the other broken stuff, deal with it!"
This is so frustrating, I have just set up my MDW and got most of my servers reporting to it nicely over the last few days. Disk usage reports were one of the main things I wanted. Of course when I was showing the storage guy here, saying what a brilliant tool this was, I was demonstrating on the MDW database itself, which is the only one that works.
"Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information upon it. When we enquire into any subject, the first thing we have to do is to know what books have treated of it. This leads us to look at catalogues, and at the backs of books in libraries."
— Samuel Johnson
I wonder, would the great Samuel Johnson have replaced that with "GIYF" now?
February 25, 2015 at 6:36 am
Duran (2/22/2015)
Hey I realise this is an old post, but I am having a similar issue except my error line ends with 'DS_TraceEvents'. I did come a across a MS connects tread which said this issue still exits in 2014, and they cant get round to fixing it (Really Microsoft? You just let known bugs form previous SQL versions into your new version?)I was wondering, did you reboot the MDW server, or the remote server you were collecting data from?
Thank you,
D.
sorry, I just got the notification from the most recent reply and realized Id forgotten to answer this question when I got the notification from your reply 😛
I restarted SQL on the MDW server, not the remote server it was collecting from.
February 25, 2015 at 3:51 pm
Hello,
Basically the only way around it is to set up the MDW's locally and then it works fine, M$ is not going to fix this (so stupid to let a bug go into 2014, I just don't understand that).
The upside of it though is that you will cut down on a lot of network traffic, assuming you are uploading during the working day. Be sure to stagger the upload time thought to relieve disk work.
I want to look at custom data sets next, I understand you can create them from scripted out profiler traces, but I am not sure if I need to create the tables to accommodate the new incoming data, I surely must. I'm also interested in whether extended events can be incorporated as well, seeing as that is the direction it is all going in.
Regards,
D.
March 8, 2015 at 7:56 pm
In response to the original post..(Thank you Bill Ramos)
In digging into this problem, the MDW reports access several collection set views in msdb. The mdw_reader and mdw_admin roles apply only to the actuall MDW. The workaround is to create a new role in msdb that you can add the login/user to so that mdw_reader and mdw_admin user can run all reports. Here is the workaround script.
-- Allow the mdw_reader/admin role to see the MDW overview report in OE.
use [sysutility_mdw] -- replace this with your MDW DB name
GO
GRANT VIEW DEFINITION TO [mdw_reader]
GO
-- Add a new msdb role for the dc_report_reader
USE [msdb]
GO
CREATE ROLE [dc_report_reader] AUTHORIZATION [dbo]
GO
GRANT SELECT ON [dbo].[syscollector_collection_sets] TO [dc_report_reader]
GO
GRANT SELECT ON [dbo].[syscollector_execution_log] TO [dc_report_reader]
GO
GRANT SELECT ON [dbo].[syscollector_config_store] TO [dc_report_reader]
GO
-- For each mdw_reader like user, you need to add them to the dc_report_reader role in MSDB
USE [msdb]
GO
CREATE USER [mdw_user] FOR LOGIN [mdw_user]
GO
EXEC sp_addrolemember N'dc_report_reader', N'mdw_user'
GO
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply