Tips and Tricks in a world of Mix

Archive for June, 2011

SSRS ExecutionLogStorage – Report Server Execution Log – Stop the Logging !

So , we’ve got a problem we couldn’t solve with Reporting Services .

It got pumped with logging few GB each day , and threatened to stop working because of that. When we caught it , it was 10 GB already.

If the space defined for the DB would end , it would stop working , and if there is no limits of logging on SQL Server it can crash the OS of the server itself.


The  Microsoft post explained in a few rows how to limit the log entries , but we just didn’t got it until they sent us snapshots .


So , what you really need to do is :


  • Go to Sql Server Management Studio
  • Connect but not to the usual Database Engine , but to the Reporting Services


  • Once you are connected: Right Click on the server – Properties to get Server Properties window as shown below:


  • Click on the Logging tab on the left pane:


  • Here you can see the default entries: Enable Report Execution logging and Remove log entries older than 60.

If you uncheck the enable report execution logging: There will not be any logging in the execution log table when the report executes.

If you alter the number of days the log entries has to be stored from 60 to any number required the execution log will be deleted after the specified days.

You can choose from either options as per the business requirement.


So that’s the Logging we couldn’t find at the beginning , from the Microsoft post.

Now you can !


Pay Attention!

If you have a vividly SSRS , still each insert and delete will be written down in SQL Server , that means that still your DB can continue to swallow through the Transaction Log .


You should check the need for the table ExecutionLogStorage (logging)  in your case at all .


Database (mdf ) cannot be opened due to inaccessible files/insufficient memory/disk space.


If the database is inaccessible and received the error mentioned below through MSSQL Server Management studio:

Please follow the steps mentioned below:
1. Make sure that the Windows server has got enough disk space.
2. If the disk space is ok, then login to the MSSQL Server Management studio.
3. Select the particular database and right click on it. Click on "Detach" option to detach the database from the MSSQL management studio.
(Before that make sure that you have the backup of the database or a MDF file)
4. The database will be removed.
5. Click on Databases, right click on it and select the option of "Attach".
6. Click on Add to attach the MDF file of the database.
7. Click Ok.

HTTP Error 403.14–Forbidden – Default Document missing





Solution 1 – Final – best practice

Insert in Web.Config of the Website inside system.webServer those lines –



<add value="index.aspx" />



The value is obviously your default document.

Solution 2

The problem is probably your site doesn’t know what is the default web page it must enter .

So you must define it at



Add your start page inside , for instance :



Add –> insert the page name –> you can see it added (in my case index.aspx)

It will work now..


Why is this solution bad?

Each time you’ll upload your WebSite you’ll need to define the Default Document .

If you’ll forget the application won’t work.


Solution 3


Other solution I’ve found at .


If you are using IIS 7 then you probably might face this error.It’s a little frustrating when such errors occur and simple IIS 6 or IIS 5.1 users when it was really simple to configure and run a website, those users feel really hooked up.

I myself faced a lot of issues but as you progress with IIS 7 you will find it simple to configure and very easy to manage.

As far as this issue is concerned in the earlier versions of IIS we used to just set the directory browsing checkbox to be checked in order to enable directory browsing on the virtual directory or the website, its really simple in IIS 7 also just click the directory browsing option in the configuration section and on the right side of the directory browsing view you will find enable by default directory browsing is disabled.It will be more clear from the below image.



This will solve your Directory Browsing issue for IIS 7.Stay tuned for more on IIS 7 tips and tricks series.



Why is this solution bad?

The second solution I’ve found I am not sure about what are the security outcomes of permitting browsing the whole website directory ..

I think that people can just enter the System Folder on your Server – it’s a severe security problem.

Redirect WebSite IIS 7–Host Name


Create a new WebSite at IIS 7 (no , virtual directory is not good enough)


  1. Define site name
  2. Connect to physical path
  3. Define redirect site name – Host Name


The Host Name is the new url address for your site . It”ll work through port 80 , as defined at the picture.

You can enter another port , if you wish.

Port 80 is a default port for http protocol unsecured traffic . (Second default port is 8080)

Port 443 is a default port for https ssl enabled , secured with certificates traffic . 



New Website called WebDDD

Edit Site(right pane) –> Bindings… –> YourNewRedirectName “DDD” on port 80

Add –> You can add more redirects with different names and ports.



Now we should see the IP of our server

Start –> run –> cmd  –> ping YourServerName –> get the YourServerNameIP

Goto –> Your local terminal –>  C:\Windows\System32\drivers\etc –> open hosts with Notepad –>

add a line

YourServerNameIP    YourNewRedirectName

Now you’ve connected the Local Terminal with the Server Binding .

That’s it . On your local PC you can access the web site through http://DDD

and you’ll go to http://WebDDD  .


If you get some security message from IIS – > check in the File System –> Your WebSite folder –> properties –> security –> Domain Users


If you are working with Server you should define the DNS in your Active Directory also..

There is a duplicate ‘system.web.extensions/scripting/scriptResourceHandler’ section defined


Filename: \\?\c:\dev\PreCompAdmin\web.config

Line number: 6

Error: There is a duplicate ‘system.web.extensions/scripting/scriptResourceHandler’ section defined



This is a known issue with ASP.NET 4.0 / vs 2010


"The workaround for the second scenario is to delete or comment out all the system.web.extensions configuration section definitions and configuration section group definitions from the application-level

file. These definitions are usually at the top of the application-level
file and can be identified by the configSections element and its children."


Symptoms :


Browsing any application on the server you are getting :

System.Runtime.InteropServices.COMException: An operations error occurred


Probabal Reason :

The reason is some installation performed on the server causing problematic connection to your Active Directory .


Solution :

Just restart your Application Server. It should solve it!

Workaround crush browsers – Work Offline – Client-side Storage


I’ve found a few technologies that can give you the option of handling the browser crush or actually working for some time offline , without some fancy monstress framework implemented synchronizing every thing you do. You’ll probably need to implement sync by yourself..

List of the Technologies :

1)jStorage – store data locally with JavaScript


2)Alternative Client-Side Storage using Sessvars.js

IE7 gave up at 32 Mb with a “out of memory” error. Firefox gave up at 32-64 Mb -sometimes crashed there about – otherwise threw an “out of memory” error.Safari gave up at 64 Mb and crashed. Opera has a limit built in (wise) and gave up after 2 Mb, throwing the error “Object to large (implementation limit.)”


3) My Sample – implementing the example published by parts in Apples site.

tutorial of Apple for Safari explaining how to work with Isolated Storage.





Now , when you have my research , go crush your browsers freely !

Tag Cloud

%d bloggers like this: