SQL Server 2008 DB, report server, and IIS all on same Win XP machine inside firewall.
(Dev machine--production will be on a Win Server 2003 or 2008)
Test data is February, 21.5K records. Presumable other months will be similar.
Client and tester are Win XP SP3 with IE6. Long story, but can't change from IE6.
Report Server log shows that fetching, filtering, and rendering are all done within a little over one second.
If the parameter settings are such that the result set is 3,117 records, Visual Studio renders in ten seconds, IE6 in about a minute.
For a larger result set (not sure exactly, probably around eight thou), Viual Studio renders in fifteen seconds OR crashes. IE6 hangs forever.
Same parameters, Chrome thinks it's done in fifteen seconds. Doesn't display grid, but export to Excel works.
Safari, Opera, Firefox all fail to do authentication pass-through.
Not yet able to try IE7/8/9/... due to requirement to have IE6 on development machine. (Not that it matters, since client can't use it but I wanted to compare).
Unless a resolution can be found, I am going to have to give the client a pre-formatted URI for an Excel dump and have her do the filtering in Excel.
Looks like there is no answer. We're starting to free ourselves from IE6, but IE7 and IE8 have the same problem. And we're kind of stuck with them because we use Sharepoint.
The report works on FireFox, but FireFox fails to pass authentication through to Sharepoint.
Opera and Safari retrieve all the data, but don't display it. (When the busy curson goes away, the window is blank except the toolbar, but the "dump to Excel" icon works!)
So, the sort-of answer is
"The way to display huge amounts of data with SSRS is sometimes to not use SSRS"
I was starting to put it in another tool when the client decided other things were more important.
Related
i have an asp.net web site made to simply allow people to update some sqlserver tables.
The website works perfectly on the host server in Edge and IE11.
On other machines when accessing the server like so :
http://server.net/8081/homepage.aspx
It works in Chrome and Edge.
however in IE11 it displays wrong. Some colours come across, all gridviews appear correctly but layout is literally bonkers.
Is there something simple i am missing? This is my first time publishing a site in asp.net. all help appreciated.
It seems every resource regarding things like CSS3 and HTML5 nag me about particular things not being implemented in older browsers, and hacky workarounds. Really who uses IE 9 or 10 anymore anyway? IE11 is out, Edge is default on W10, and I assume most / all people use it. To me it seems to make the most sense to simply make the page render properly on the latest Chrome (what I use), Firefox, Edge, and Safari..
Ughhh apple. My understanding is that the Windows version of Safari is very outdated and trying to get a (questionably obtained) image of macOS working in a VM has been unsuccessful. I'm not spending a dime for any Apple products just to test my site on their browser. So what can I do in order to test how my site will work in it?
Regarding your question...
Who uses IE 9 or 10 anymore anyway?
Typically, people with older Windows systems. This is important for your website based on whether or not IE 9/10 users will be accessing the website that is being supported. (A review of your website's web logs can shed light on this.) If your website is an internal intranet site, then an organization's IT department may dictate the browsers that users can use. However, large eCommerce websites will often support older browsers out of fear of losing customers to rivals.
Regarding your second question...
How do I go about ensuring the site is functional and looks reasonably
good on apple products conveniently, without any apple products while
on a minimal budget?
Without actual Apple products, something that emulates these displays is needed. One option is the "Inspect" option with the Chrome browser. (Display your website on Chrome, right-click, select "Inspect".) Inspect allows you to choose between a Desktop or Mobile display. With a Mobile display, you also have the option of selecting several Apple displays (e.g. iPhone, iPad, etc.). This is probably the next best thing to having the actual Apple device and its display for website testing.
We recently migrated from a SQL Server 2008 SSRS server to a new SQL Server 2016. The entire report catalog was restored and upgraded to this new server. Everything is working, except the horrible performance of the web portal.
The performance while connecting to the web portal from a domain joined computer seems decent, but connecting to the web portal over the internet is seriously frustrating. Even simply trying to browse a directory of reports is a wait of several seconds, and running any given report is similarly slow. It's slow in IE11, Edge, Chrome, Safari, you name it. Like 25+ seconds to go from login to viewing the Home directory.
We are using NETWORK SERVICE as the service account, and NTLM authentication. We aren't getting any permission errors in the UI or the logs. HOWEVER in Edge browser, using the developer tools, I notice several 401 unauthorized HTTPS GET requests for things like reports/assets/css/app-x-x-x-bundle.min.css. So perhaps there is a permissions issue somewhere? Other interesting items in the developer tools is that things like reports/api/v1.0/CatalogItemByPath(path=#path)?#path= are taking like 10 seconds. These are JSON types.
Certain reports that do things like have a parameter depend on another parameter selection will sometimes not work. The waiting icon spins and when the report returns the selection will not be kept, nor the second parameter filled. Sometimes it works, however, which is part of what makes this so maddening.
There are no explicit error messages, but something is getting bogged down in a major way. There are no resource issues on this server that we can see- it's got plenty of headroom in terms of RAM and CPU.
This is not a report optimization problem; the entire UI is slow for everything.
I think this should be releated to IIS settings but don't know exactly what it is.
As you can see below, this login message pops up for each images, 8 images 8 times in Opera.
And the major browsers react to this page different.
IE9 works good(this is the reason why I found this problem now. It's internal site and almost every users use IE...)
Chrome(17.0.963.56 m) works good.
Safari(5.1.2) is also good.
Opera 11.61 has a problem like I said...
And FF SHOWS NO IMAGES and don't even ask for login. And Firebug says it's "NetworkError: 404 Not Found!".
I don't know what's going on.
This site requires to login and it's internal, so I can't give you the link. Sorry for the inconvenient.
And this site is running on Windows Server 2003. And the image containing folder is shared for web(I don't know why it's shared. But don't want to change the setting). I don't know this may cause this situation.
If Opera opens a user name/password dialog, the site is probably sending a WWW-Authenticate header in response to those image requests. You can open Opera's developer tools ("Tools > Advanced > Opera Dragonfly" or right-click in page and select "Inspect element") and use the network feature to inspect the full headers.
I don't know how you can disable this header if it is sent, it depends on the server settings and what type of server you're running, and I'm not at all familiar with Windows Server 2003.
Sometimes the style sheet disappears when naviguating on our WSS 3.0 sites (white background on the site, no colors, no formatting, etc.). This has mainly happened with IE6 (corporate browser for the majority of our computers). The fixes were :
clean up temporary internet files
if it still doesn't work, upgrade to IE 7
However, this time, the upgrade to IE 7 hasn't worked, the style sheet isn't applied. When we clean up temporary internet files, things go back to normal, but after a while the css disappears again.
Here are a few ideas on what you could try:
Fiddler should be able to tell you if there is a network problem.
Check the HTML for anything unusual. Is it malformed in any way? Can you save a copy and run it through an online validator (although this is limited in use as SharePoint's default markup isn't compliant).
If some users are having the issues but others aren't, check their permissions on the server.
You could also try using the SharePoint "Log in as another user" feature to see if the problem can be reproduced on your machine when logged in as them. You may also want to try running Internet Explorer as that user.
Check the Event Viewer on both client and server for anything unusual.
Check the IIS logs on the server for any errors.
Check the SharePoint ULS logs on the server in the "12 Hive" for errors that might be related to this problem.
Try running Process Monitor on the client and reproduce the problem. Search for keywords such as FAIL or ERROR to see if anything appears. Make a note of the time the problem occurs and see if the Process Monitor logs give any additional information.
Is there some javascript that's involved as well? Could it be a virus scanner that is set way to strict? As you pointed out in one of the comments, the CSS isn't even being requested (at IIS log level, which is as basic as you get, not even in SHarePoint yet), so it HAS to be something on the client PC.