Using SQL backup and restore for MOSS


  • Back Up and Restore the content database to a new Sql server
  • In Central Administration page
  • Go to Application Management and Click on Create or extend web application.
  • Therein Create a new web application. Once application is created don’t create Site Collection.
  • Now again go back to Application Management.
  • Therein click Content Databases
  • Change the web application to point to web application you just created.
  • Remove the default content database created while creating the web application.
  • Then click on Add a content database
  • Specify the Database Server where the content database was restored and in database name specify the name of the content database.
  • The site should get restored properly.

Check out this good information


(Service Unavailable) Could not load all ISAPI filters for site/service. Therefore startup aborted.


After running the Sharepoint products and technologies configuration wizard successfully, the central administration site page opens up.

( We were installing MOSS 2007 on 64 bit machine)

But in my case it was giving the following error

“Service Unavailable”

Checking into event log gave the following information

Could not load all ISAPI filters for site/service. Therefore startup aborted.


ISAPI Filter ‘C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_filter.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture. The data field contains the error number. To learn more about this issue, including how to troubleshooting this kind of processor architecture mismatch error, see

Searching for it the solution that I found was the following

// Disabling the 32bit mode for your web site.

cscript C:\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

and then the following

// Registering ASP.NET 2.0 as the default framework for that web site

aspnet_regiis.exe -i

This resolved the issue for us!!


“Setup is unable to proceed due to the following error: Internet Information Services is running in 32-bit emulation mode. Correct the issue listed above and re-run setup.”


Got this issues while running the set up for MOSS 2007 on 64-bit edition of Windows server 2003.

The resolution i found for this was following

1) Open the command prompt

2) Navigate to the following directory

“….: \Inetpub\Adminscripts”

3) Type the following command

adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 0

4) And finally IISRESET.


Error: Backup failed for Object Shared Search Index failed in event OnBackupComplete

Hi I got this error when i was taking the backup of the farm

stsadm.exe -o backup -directory \\d-4526\MossFarmBackup -backupmethod full

The solution for this is to

Go to Central Administration Page.

Click on your Shared Service

Then on Search Settings there Reset all crawled content

This should solve the problem


“A SharePoint database named ‘….. ‘already exists. You must supply another name for the new database.” – Using Sql Server BackUp and Restore of Content Database.

To create a new web application which will use an existing content database we need to do the following.

Open Sql Server Management Studio

To take back up of the database in my case it was ‘WSS_Content_fa5cc7a0686e424bbe4fc128b4a48cf4’

Right click the database select tasks select Offlinethen select Detach.

Get the mdf and ldf file for the database.

Attach the files and create a new database.

Now to Central Administration Site Application Management Create a new web application

Let the name of the database as default.

Now go to Content Database within Application Management Select the web application just created.

Click on the Database Name Select Database Status as Offline and Check Remove Content database check box.

Now click on Add Content Database In the Database Name specify the name of the new restored database.

This is the point we can get this error “A SharePoint database named ‘….. ‘already exists. You must supply another name for the new database”

The solution for this is to go to

SharePoint_Config database There run this query

delete from Objects where name=’name of restored db’;


Unhandled Exception: Microsoft.SharePoint.SPException: The form submission cannot be processed because it exceeded the maximum length allowed by the Web administrator. Please resubmit the form with less data.


When one of our users tried uploading a picture of size somewhere around 3 mb in the picture library, he received the above mentioned error. Initial solution that we found in the kb article was to increase the httpRuntime within our web site.

<httpRuntime maxRequestLength=”51200” />

maxRequestLength –

Optional Int32 attribute. Specifies the limit for the input stream buffering threshold, in KB. This limit can be used to prevent denial of service attacks that are caused, for example, by users posting large files to the server. The default is 4096 KB. If the threshold is exceeded, a ConfigurationErrorsException is thrown.

But as we can see it is already set to somewhere around 50mb so that shouldn’t be the problem.

Thankfully the solution for this was to open central administration site

Central Administration > Application Management > Web Application General Settings

There change the

Maximum Upload Size which was set to 2 mb to
desired value.


%d bloggers like this: