Specificy for Windows 7.
Please try Disable the generation of thumbs.db files by the Local Group Policy Editor and your problems will be resolved. They are only generated for compatibility with outdated applications, and are most certainly NOT needed for Windows operation.
Run "Group Policy" - select Edit Group Policy when it comes up.
> User Configuration
> Administrative Templates
> Windows Components
> Windows Explorer
CREATE TABLE #counts
EXEC sp_MSForEachTable @command1='INSERT #counts (table_name, row_count) SELECT ''?'', COUNT(*) FROM ?'
SELECT table_name, row_count FROM #counts ORDER BY table_name, row_count DESC
DROP TABLE #counts
The output will be a list of tables and their row counts.
If you just want the total row count across the whole database, appending:
SELECT SUM(row_count) AS total_row_count FROM #counts
will get you a single value for the total number of rows in the whole database.
From here: http://serverfault.com/questions/360438/iis-complains-about-a-locked-section-how-can-i-find-out-where-its-locked
I have this section in my web.config:
<modules runAllManagedModulesForAllRequests="true" />
<anonymousAuthentication enabled="true" />
<windowsAuthentication enabled="true" />
IIS7 crashes and complains about the autientication section:
Error Code 0x80070021
Config Error This configuration section cannot be used at this path.
This happens when the section is locked at a parent level.
Locking is either by default (overrideModeDefault="Deny"),
or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
How to Fix.
1.Open IIS Manager
2.Click the server name in the tree on the left
3.Right hand pane, Management section, double click Configuration Editor
4.At the top, choose the section system.webServer/security/authentication/anonymousAuthentication
5.Right hand pane, click Unlock Section
6.At the top, choose the section system.webServer/security/authentication/windowsAuthentication
7.Right hand pane, click Unlock Section
On the report form, add a script manager from the toolbox before the report control: open the toolbox and select Ajax Extensions - Script Manager, then drag it onto the form. Using Visual Studio 2012, what I ended up with was the following new control on the form:
<asp:ScriptManager ID="ScriptManager1" runat="server"></asp:ScriptManager>
Full details for Visual Studio 2012 at http://msdn.microsoft.com/en-us/library/ms252104.aspx
This issue is because you have more than one 'Microsoft.Reporting.WebForms' referenced in your Web.Config file.
From here: https://social.msdn.microsoft.com/Forums/ie/en-US/2530fbe4-b594-4aca-a086-23fb74c2b1cc/response-contenttype-applicationpdf-not-working-in-ie-11?forum=iewebdevelopment&prof=required
Tools>Internet Options>Advanced tab, uncheck "Do not save encrypted files to disk"
PDF is not natively supported in MSIE browsers... You need an installed and enabled PDF file reader ActiveX control to render the PDF file stream.
From here: http://devonenote.com/2013/09/how-to-find-startup-folder-in-windows-server-2012/
In Windows Server 2008 R2, to define an application to be startup automatically for current user, one common way is to create an application shortcut and add it to startup folder. In Windows Server 2012, you might find you can’t find this startup folder any more.
Here is the steps to find startup folder in Windows Server 2012.
- WinKey + C to open the charms bar
- Click “Search”
- Enter shell:startup and click on the first result returned.
From here: http://www.isolutionspartners.com/sql-reporting-services-error-maximum-request-length-exceeded/
You could, quite honestly, run into this error in a lot of situations involving a web app, but we’re talking specifically about SSRS in this post. The basic problem here, is that your posting an amount of data to a web app larger than it is configured to accept. Hence, it is throwing an error.
It’s an easy fix though. You’ve got to adjust the web.config for the web app, which in the case of reporting server, is usually somewhere like this:
For SQL Server 2012: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER2012\Reporting Services\ReportServer
Find the web.config file for your reporting services instance, open it up, and track down the line that looks something like this
executionTimeout = "9000" />
Now just add a max request length attribute in there to fix the problem, adjust your size as needed. This is 5meg.
executionTimeout = "9000" maxRequestLength="500000" />
And now you’ll need to restart IIS. start->run->”iisreset”
From here: https://blogs.technet.microsoft.com/enterprisemobility/2009/07/01/using-multiple-monitors-in-remote-desktop-session/
If your RDP's "Use all my monitors for the remote session" is disabled you can get around it as follows.
1. Create an RDP file with your specific connection.
2. Right click on the .rdp file and select Open with Notepad.
3. Add the following 2 lines to the bottom.
4. Save and then use!
Have a great day!
The options in VS for exceptions to determine if the debugger should break on an exception. Though VS will always break on an unhandled exception and a language break (debugger). The options do not stop the script debugger from being attached when you launch IE from VS.
The options in VS to enable or disable JIT debugging change just the just-in-time debug feature. Enabling JIT debug simply means that if a running application not launched by VS hits a break condition the user should be prompted if they want to attach VS to debug the application. This also don't change if script debugging is enabled when you launch IE from VS.
The options in Internet Explorer to disable script debugging only changes if IE should run with debugging enabled always. In IE11 with VS2013 this feature is never needed but is there to support older versions of VS.
The easiest way to get the behavior you want is to do:
1. Right click on a aspx/html file there is a ‘Browse with…’ item. This will bring up a dialog to configure your browser.
2. Click the Add button. Add something like:
Path: c:\Program Files (x86)\Internet Explorer\iexplore.exe
Friendly name: Internet Explorer (no debug)
3. Set that as your default