Monday, February 27, 2012

SQL Repair to Fix Error 7105 in Microsoft SQL Server

Microsoft SQL Server allows you to include various LOB (Large Object) data types on your database. Such data types help you use multimedia files, such as images. Although these data types are very useful for SQL Server database, however they may prove harmful for the database in some situations. The database page may become inaccessible and lead to data loss. In such cases, you have to go for SQL recovery solutions to get your data back.

As a practical example of the issue with your SQL Server database, you may run across the following message while LOB data referenced by the database page row can’t be retrieved:

“Msg 7105, Level 22, State 6, Line 1
The Database ID 11, Page (255:177), slot 1 for LOB data type node does not exist. This is usually caused by transactions that can read uncommitted data on a data page. Run DBCC CHECKTABLE”

The severity of the error is every high and thus the server terminates the connection. In order to get your data back in such cases, SQL database recovery solutions become need of hour.

Grounds of the issue:

You may face this behavior of SQL Server because of any of the below reasons:

· Some sort of corruption issue is there either within LOB page structures that are referenced to database page or within database page.

· The database query, which is failing to process, is either using NOLOCK query hint or READ UNCOMMITTED ISOLATION LEVEL.

· SQL Server database engine has some issues and thus causing the failure of queries with above mentioned error.


Use any of the following solutions to work around this issue:

· Run DBCC CHECKDB on database or the DBCC CHECKTABLE on affected table.

· Avoid using NOLOCK query hint or READ UNCOMMITTED if DBCC command does not return any error.

· Restore the database from most recent backup. In order to make sure that you do not lose further data, you must have valid and current backup.

If backup is not available and other options are unable to fix the issue, then SQL recovery software come for your rescue. The commercial recovery applications work efficiently in virtually every corruption scenario and extract all corrupted data. They are extremely safe and easy to use.

SharePoint Database Recovery When Stsadm.exe Does Not Restore Database

The stsdm.exe is a very powerful and useful command-line utility of Microsoft SharePoint Server. It lets you perform a wide range of operations on your SharePoint Server database, which includes backup and restore database. You can use stsadm.exe -o backup to backup and stsadm.exe –o restore to restore the database, in case of database corruption and can avoid needs of SharePoint Recovery solutions.

Stsadm.exe backup utility helps you handle corruption in a number of situations, but it does not backup user profile information. This issue usually occurs on Microsoft SharePoint Server 2003 and 2007. You may run across this issue if the following conditions are true:

  • You create backup of personal site using Stsadm.exe utility and then try to restore it.
  • You create a new SSP (Shared Services Provider), which has a number of new SSP databases.

This issue can prove very harmful in case of database corruption. When database gets damaged, you can not restore the user profiles using the backup. At this point of time, you have to opt for SharePoint repair solutions.


This is a design issue in Microsoft SharePoint Server. SharePoint 2007 stores user profile information in SSP database. Whereas, SharePoint 2003 stores the information in _PROF database that is used by portal application.


In order to create a complete backup of profile information, you must following the below actions:

  • You must do complete backup of the SSP database and then restore it, in case of SharePoint 2007. In case you have concern of database damage in SSP database, and there is a backup that was taken before the point of corruption, you can restore complete SSP backup to get absolute information.
  • You must create complete backup of the _PROF database, which is used by portal applications, in SharePoint 2003. The process may need that you also restore all the portal applications.
The above solutions are helpful if you take these things in consideration before creating the backup. If you have created backup earlier and facing database corruption now, then you have to fix it using SharePoint database repair solutions. It is best possible using advanced and effective commercial recovery applications.

Thursday, February 23, 2012

Word Document Recovery Mac When Application Does Not Work Properly

Microsoft Word is undoubtedly the most widely used word processing application. Almost every computer user uses this application for different tasks, ranging from writing a simple document to complex guide. MS Word is also available for Mac OS X, as a part of Office for Mac Application Suite. However, under some situations, the application may start behaving strangely and make your data unavailable due to corruption. At this point, you need to opt for Mac Word document recovery options.

As an example of some strange issues with Microsoft Word document, the numbering may become incorrect when you add or remove a figure and caption in a document that has captions attached to figures. At the same time, you may also face the following problems:

  • The ‘Update Fields’ option is grayed out when you right click the caption.
  • The ‘Update Fields’ option is not enabled even if you select entire document, using Command + A, and right click anywhere in the document.
  • If you press F9 key, to update whole document, after selecting entire document, it does not make any effect.
  • You have inserted a Table of Figures in the document and updated entire document using F9 key, the Table of Figures is updated but with wrong captions. The problem of wrong captions continuous throughout the document.
  • The document gives errors while opening and sometimes crashes.

This problem sometimes makes your documents unusable and may put you in need of Mac Office repair solutions.


You may run across this behavior of Microsoft Word for Mac application due to any of the following reasons:

  • The preferences of Microsoft Word are corrupted. It can be due to improper system shutdown, application malfunction, or other similar reasons.
  • The Word document itself is corrupted and application is unable to read it.


Try out any of the following solutions to sort out this issue:

  • Start MS Word by holding down the Shift key press. It bypasses your preferences and Normal template.
  • Save document in different format, such as .Doc or RTF.
  • Copy entire content of the document, except paragraph symbol, and paste in new blank document.
  • If you are using Mac OS X 10.7 Lion, then try to find a different version of the file on your Mac hard drive.
If all the above methods fail, you have to use commercial recovery applications. Such tools are particularly designed to restore damaged Word document in all cases of corruption. They offer safe recovery for all the Microsoft Word for Mac objects.

Entourage Repair If Creating New MUD Folder Does Not Fix the Problem

Microsoft Entourage is a flagship E-mail client from Microsoft for Mac OS X users. This advanced application helps you effectively manage all your emails, contacts, notes, and other data. However, under some situations, the application may not open or crash while working. This behavior is pretty frequent and occurs due to database corruption. It leads to data loss and you have to opt for Entourage database recovery solutions to get your valuable data back.

In a practical scenario of the above problem with the application, you may run across any of the following error messages while using it:

  • The Office database is damaged.
  • Entourage cannot access your data. To try to fix the problem, rebuild database.
  • The action could not be completed. An unknown error (4362) occurred.

When it happens, it makes all your valuable data inaccessible, and you need to recover Entourage database, by fixing this problem, to get your data back.


This problem occurs due to database corruption, as mentioned in the above error messages. After corruption, Entourage can not read the database and it becomes unusable.


There are several possible solutions of this problem, such as rebuilding the Entourage database, as stated in the Error message. However, you can also fix this problem by creating a new Microsoft User Data (MUD) folder. Following are the steps to create MUD folder on your Mac machine:

  • Quit all Mac Office applications, including Office Reminders.
  • Location ‘HD/Users/USER_NAME/Documents’ folder and move to desktop.
  • Launch Microsoft Entourage. It automatically creates a new MUD folder and an Identity.
  • Quit Entourage and locate “HD/Users/USER_NAME/Documents/Microsoft User Data/Office 2008 Identities/IDENTITY_NAME” folder. Rename the database file with new name.
  • Replace database file in newly created MUD folder with database file in previously moved MUD folder.
Start Microsoft Entourage to check if the problem is fixed. This solution works in a number of situations. However, if you are not lucky enough to fix your problem using this solution, then Entourage recovery software are there for you. They help you fix every database corruption problem, nevertheless of the cause and extent of damage.

Tuesday, February 21, 2012

FileMaker Recovery When You Fail to Take Common Precautions

File corruption or database corruption is an unavoidable situation, even with one of the safest relational database management systems- FileMaker Pro. When it happens, it renders your precious data inaccessible, causing severe situations of data loss. In order to avoid database corruption and needs of FileMaker recovery solutions, you must take proper measures.

How FileMaker Database Corruption Occurs?

FileMaker is a storage media based application, thus it does not require loading whole database into main memory while opening the file. It transfers data as required. Any kind of application failure or malfunction in such situations leads to database corruption. Due to improper system shutdown or unexpected application termination, the file may not be written completely on the drive.

Ways to Prevent FileMaker Database Corruption:

You can prevent database corruption by taking some common precautions with your application. Following are some common strategies that can help you avoid FileMaker database corruption and requirements of FileMaker repair solutions:

  • Create regular backup of your database using advanced backup tool. Effective backup software must provide multiple database copies for restoration.
  • Save clone of the database. Since it is possible to recover only data from corrupted file, clone makes sure that you have a database to house the data.
  • Always avoid unexpected system shutdown or application termination. You can do this by having a good Uninterrupted Power Supply (UPS). You should never force quit the application.
  • Earlier versions of FileMaker have a size limitation with the database. If the database size grows over the set limit, it may get damaged. You should keep it in mind.
  • A corrupted or bad sector affected media is one of the most frequent reasons of database corruption. If you notice that multiple files are getting damaged, then you should check hard drive using Disk Utility.
  • You must regularly perform database maintenance. Routine compression rewrites whole database and makes database healthy.

If you do not take the above precautions and face database corruption, then inbuilt recovery option of FileMaker Pro comes into picture. However, this process deletes structures and harbor corruption. Thus it is not safe and is not even advised to be used.

Under such situations, FileMaker Pro recovery utilities come into picture. Such third-party tools are capable of effectively handling all corruption scenarios. They do not make any changes to the database and offer absolute recovery with high-end scanning techniques.