Karthick's Blog!

For people who were troubled with the 4 GB DB limit in SQL Express, here is the good news, the DB limit has been increased to 10 GB, enjoy!

For people who work in ISA or trying to explore, stop googling or binging for ISA, it is now ForeFront Threat Management Gateway 2010 or more popularly MS wanting us to call it as TMG! This works only on Win 2008. http://www.microsoft.com/forefront/threat-management-gateway/en/us/default.aspx - Explore more here

Create Backups Directory Create a backup directory for storing the scheduled SharePoint backups (e.g.d:\backupsharepoint) Create Bat File Directory Create a directory for storing the backup script file (e.g. d:\scriptssharepoint) Create Bat File Create a bat file using the code below, modified for your environment. Use UNC paths when using in a server farm environment. @echo off echo ==================================================== echo Backup Script For Office SharePoint Server 2007 echo ==================================================== cd \program files\common files\microsoft shared\web server extensions\12\bin @echo off stsadm.exe -o backup -url http://servername -filename d:\backupssharepoint\backupsharepoint.dat -overwrite @echo off echo completed Schedule bat file Schedule the backup to run frequently, during off peak hours. Open Start > Programs > Accessories > System Tools > Scheduled Tasks Add a Scheduled Task Schedule

By default, MOSS 2007 has a setting of allowing file sizes of upto 50 MB. If you need to change it, do the following: 1. Change the Max Upload Size in Central Admin -> Application Management -> Web Application General Settings 2. Also in IIS 7, change the Connection Timeout to how many ever seconds you want - reason is, the more the file size, the longer it is going to take to upload, so to be safe, default is 120 seconds

Scenario : you are trying to use this ACE OLEDB provider to programmatically import from an excel file in your ASP.Net 2.0 application running on Windows Server 2003 64 bit What google / forums say: they tell you to change your target platform to x86 in VS 2008 and compile it, now unfortunately for a web app - you cannot do that. So we need to see some other means. Some facts to know: IIS 6.0 does not have the capability to have different application pools running on different bits, whereas IIS 7.0 on Win 2008 Server brings in that capability. But here we are with IIS 6.0 ASP.Net 2.0 however supports both 32 bit and 64 bit and IIS 6.0 supports runing them in parallel. This is what you need to do: 1. Enable 32bit on 64 bit App using the Adminutil script 2. Run Aspnet_regiis -i from the c:\windows\microsoft.net\framework folder - this represents 32 bit. 3. Changed ASP.Net v2 32 bit to Allowed in IIS 6 Web Service Extensions After that, your 32 bit ASP.Net code will run like

Whenever you are having your code trying to manipulate files in document libraries and they have to work in different identities, you most properly will have your "Allowunsafeupdates=true" line added in your code. This works most times, but at certain scenarios, it might throw up the below error (at the time when the code is trying to move a document from one library in one site to another library in another site). The same code however would have worked for the Admin login. Resolution The resolution for this is not in the code unfortunately! All you need to do is go to your Central Administration -> Application Management -> Web Application general Settings and turn off the "Security Validation" Bingo, your code for all users starts working fine!

This is my scenario. I have one server running AD, SQL 2008, MOSS 2007 SP2 and wanted to separate the AD into one server and MOSS into a new server. This is what I did (and definitely not as simple as I thought it would be!) Leave the AD server as it is Install Windows, SQL, MOSS on the new machine Format and install AD on the first server Re-join the MOSS server to the Domain Create all required SharePoint accounts in the AD Now, you will have your SharePoint site giving an HTTP 404 error mostly If you check the EventVwr, you will have "Cannot open database...Login Failed" error for the SharePoint content access account You need to delete this user from the AdminContent database and re-add by giving that respective login After that, you need to re-create the Schema as well (Ensure the particular admin account for example domain\spadmin is scripted in a notepad and kept Once you do the above, you will have both the Central Admin and Sites opening properly but not

When doing stsadm restore, sometimes you might end up getting access denied error. If you get this, first, check whether your command prompt is running as Administrator even if that does not solve the issue, go and add your Administrator account (assuming that is your main services account), as your primary site collection administrator (this is in Central Admin). Make sure Secondary Admin is not the same as the primary admin. Secondary admin ideally can be the machine's administrator (assuming your server is a member server of the doman and you alreay have added the domain administrator as the primary admin)

On your desktop, create a folder and rename the folder with this: GodMode.{ED7BA470-8E54-465E-825C-99712043E01C} Once done, just open the folder and you will see magic :) - You can access almost ALL administrative functions from this single Window!

After installing SharePoint Server 2007 on Windows Server 2008 R2, you may start to see the following error message in the event logs : Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,…). hr = 0×80070005, Access is denied. Inspection of the detailed tab of the event log entry will show information about the process that generated the error. Take note of the user mentioned after the “- User: Name:” portion of the bytes. To resolve this error, simply give that user full permission to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS registry key.