Monday, December 25, 2006

the type of page you have requested is not served because it has been explicitly forbidden. The extension .mdb may be incorrect.Please review the URL

Situation:
After uploading a '.mdb' file on to sharepoint server, when you click on the '.mdb' file you get the error:
the type of page you have requested is not served because it has been explicitly forbidden. The extension .mdb may be incorrect.Please review the URL below and make sure that it spelled correctly.

Reason:
ISAPI extension for the '.mdb' is available in the IIS available ISAPI modules and trying to execute this extension. But the '.mdb' file is forbidden to execute on the server.

Fixes:

If you are not technical savy or do not have any permissions to do the below changes, Mouse hover on the file name in the doc lib and select "down load a copy" from the context menu.


Temp fix:
Take out the 'ISAPI extension' for the .MDB file from the IIS.
This will be fixed in 5 minutes, but needs the IIS to be halted.
Stop the IIS and do the following steps.

  1. Go to the sharepoint server
  2. IIS -> Websites
  3. Right click on the web application -> properties
  4. Home Directory -> Configuration
  5. Scroll down the 'ISAPI' extensions -> select '.mdb' -> Remove.
    iisreset

Permanent fix:
Take out the 'mdb' ISAPI module from the ASP.NET configuration.

  1. Go to the CONFIG folder on the machine where, ASP.NET is installed.
    dir:\Windows\Microsoft.NET\Framework\Version\CONFIG and open the web.config file
  2. Search for the following snippet
    in the <httpHandlers> section:
    <add path="*.mdb" verb="*" type="System.Web.HttpForbiddenHandler" validate="True" />
    AND
    add the following lines

    a) <add path="*.mdb" verb="*" type="System.Web.UI.PageHandlerFactory" validate="True" /> in the <httpHandlers> section


    b) <add extension=".aspx" type="System.Web.Compilation.PageBuildProvider" /> in the <buildProviders> section


Thursday, October 26, 2006

Content Editor Webpart Current Date time in sharepoint

copy paste the code in the 'source editor' of a content editor webpart:


<SPAN id=tP> </SPAN> <SCRIPT type=text/javascript>function tS(){ x=new Date(tN().getUTCFullYear(),tN().getUTCMonth(),tN().getUTCDate(),tN().getUTCHours(),tN().getUTCMinutes(),tN().getUTCSeconds()); x.setTime(x.getTime()+dS()+34200000); return x; } function tN(){ return new Date(); } function dS(){ return ((tN().getTime()>fD(0,3,1,1).getTime())&&(tN().getTime()<fD(0,9,1,-1).getTime()))?3600000:0; } function fD(d,m,h,p){ var week=(p<0)?7*(p+1):7*(p-1),nm=(p<0)?m+1:m,x=new Date(tN().getUTCFullYear(),nm,1,h,0,0),dOff=0; if(p<0){ x.setTime(x.getTime()-86400000); } if(x.getDay()!=d){ dOff=(x.getDay()<d)?(d-x.getDay()):0-(x.getDay()-d); if(p<0&&dOff>0){ week-=7; } if(p>0&&dOff<0){ week+=7; } x.setTime(x.getTime()+((dOff+week)*86400000)); } return x; } function lZ(x){ return (x>9)?x:'0'+x; } function tH(x){ if(x==0){ x=12; } return (x>12)?x-=12:x; } function y2(x){ x=(x<500)?x+1900:x; return String(x).substring(2,4) } function dT(){ window.status=''+eval(oT)+'';  document.getElementById('tP').innerHTML=eval(oT); setTimeout('dT()',1000); } function aP(x){ return (x>11)?'pm':'am'; } var dN=new Array('Sun','Mon','Tue','Wed','Thu','Fri','Sat'),mN=new Array('Jan','Feb','Mar','Apr','May','Jun','Jul','Aug','Sep','Oct','Nov','Dec'),oT="dN[tS().getDay()]+' '+tS().getDate()+' '+mN[tS().getMonth()]+' '+y2(tS().getYear())+' '+':'+':'+' '+tH(tS().getHours())+':'+lZ(tS().getMinutes())+':'+lZ(tS().getSeconds())+aP(tS().getHours())";if(!document.all){ window.onload=dT; }else{ dT(); }</SCRIPT>

Monday, May 29, 2006

All About MSO Cache folder

Some times you are tempted to delete the 'MSO Cache' folder as it contains huge data/content.
MSO Cache, aka 'Local install source' folder is empty until you try to install office applications from a CD. When you insert the office CD in to the device, system will check for the free space drive. If it finds any drive containing at leaset 1.5 GB free space, install source files are copied to this folder. These files are used when you click on the 'repair' option on the 'Add/Remove' control panel module and service pack updates.

Deleting the MSO Cache files:
Do not delete the 'MSo Cache' folder directly.
  1. While installing office:
    check the 'delete installation files' check box before clicking the 'finish'.
  2. Any time After installing office"
    Open the 'Disk Cleanup' tool located at :
    start -> All programs -> Accessories -> System Tools
    Check the 'Office setup files' check box and click to delete.

Saturday, May 20, 2006

URL Redirection basics for IIS

Source: http://blogs.msdn.com/david.wang/archive/2005/08/01/HOWTO_Common_URL_Redirection_Techniques_for_IIS_Summary.aspx

The web server can perform three types of redirection to handle any given request from the client:

  1. Client-Side Redirection - The server sends a "302 Redirect" response with a Location: header containing the new URL, and the client makes another request to the new URL.
  2. Server-Side Redirection - The server transparently rewrites the request URL to another URL which remains on the same website as the original.
    (This Redirection is also known as CourtesyURL/Pretty URL/URL shadowing/URL masking Publishing or Exporting internal website to be accessible externally/Redirecting URL on one web server to be handled by another web server/One web server reverse-proxying another server/Force HTTP requests to HTTPS/SSL )
  3. Server-Side Forwarding - The server transparently rewrites the request URL to another URL which does NOT remain on the same website as the original. Note the new website can be on another machine, but not necessarily.

    Some people classify these types depending on the URL refresh. But its not correct.

Apache never has built in URL redirections. You need to install and configure add-on modules like mod_redirect to get Client-Side Redirection, mod_rewrite to get Server-Side Redirection, and mod_proxy to get Server-Side Forwarding. These are embedded into the httpd.config and .htaccess includes.

IIS Core has built-in Client-Side redirection and configurable via the HttpRedirect property. You need to install add-on modules to get Server-Side Redirection and Server-Side Forwarding behavior.

Redirection possibilities and technology to perform:

  1. Client-Side Redirection using:
    IIS "Core" (no code) - HttpRedirect
    IIS "Core" (script code) - HttpErrors and ASP
    ASP (script code) - Response.Redirect
    ISAPI Filter (compiled code) - SF_REQ_SEND_RESPONSE_HEADER
    ISAPI Extension (compiled code) - HSE_REQ_SEND_RESPONSE_HEADER, HSE_REQ_SEND_URL, HSE_REQ_SEND_URL_REDIRECT_RESP
  2. Server-Side Redirection using:
    IIS "Core" (no code involved) - IIsWebFile and ScriptMaps
    ASP (some code involved) - Server.Transfer and Server.Execute (ASP only)
    ISAPI Filter (compiled code) - SetHeader( "url" ) in SF_NOTIFY_PREPROC_HEADERS or SF_NOTIFY_AUTH_COMPLETE
    ISAPI Extension (compiled code) - HSE_REQ_EXEC_URL and HSE_REQ_EXEC_UNICODE_URL and Wildcard Application Mapping
  3. Server-Side Forwarding using:
    ISAPI Filter (compilied code) - Using WinHttp
    ISAPI Extension (compiled code) - Using WinHttp and Wildcard Application Mapping

Tuesday, February 7, 2006

dell note book no audio device showed in the contreol panel sounds utility

After you re-install the windows on Dell Notebook (especially Inspiron e 1505), while trying to install the audio drivers, you will never get to install the drivers.

Reason:
This is due to the poor documentation from the dell support.
Every one trying to re-install the drivers will land into the Dell's support page:
http://support.dell.com/support/downloads/driverslist.aspx?c=us&cs=19&l=en&s=dhs&SystemID=INSPIRONI6400/E1505&os=WW1&osl=en&servicetag=&catid=-1&impid=-1&deviceid=10430&libid=1&typeid=-1&dateid=-1&formatid=-1&releaseid=R152924&formatcnt=1&vercnt=9

You need to follow the order of installation. Dell never documented this order. Neither they specified the level of importance correctly. Usually all the users look at the 'Urgent' category and try to install them first. This will cause the mess.
Fix:
Follow the below order:

  1. Install Dell Notebook System Software (on your downloads page expand the System Utilities category). Restart.
  2. Next install the Intel Mobile Chipset driver (expand the Chipset category). Restart.
  3. Install the Sigmatel audio driver (expand the Audio category). Restart not needed.

If you have already installed sigmatel before the steps2. Un install it first and re -install in the order. If you still can not get the sound, that means that there is a problem with the windows registry. Do the below steps to create the Registry key for the Sigmatel:

  1. Open the device manager ( My Computer -> Right click -> Properties -> Hardware -> Device Manager)
  2. Right click on the 'Media Controller' -> update driver.