Varieties of SQL Server Error 5172

Continuing the previous article, the error 5172 is the results of some errors found in the file header page (page 0) in MDF or LDF file.

Besides the PageAudit error that I already elaborate on previous article, there are also other variations of this error types as follows :

Error 5172: The header for file ‘%ls’ is not a valid database file header. The TornPage property is incorrect.

This is caused by the boot page do not passed the torn page checking. Please refer to my article about torn page to fix the torn bits in order to eliminate this error.

The other variations including :

Error 5172: The header for file ‘%ls’ is not a valid database file header. The FGID property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The FILEID property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The SIZE property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The MAXSIZE property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The GROWTH property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The PERF property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The BACKUP LSN property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The UPDATE LSN property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The MIN SIZE property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The STATUS property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The UserShrinkSize property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The SectorSize property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The FirstLsn property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The MaxLsn property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The RecoveryForkName property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The CreateLsn property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The DifferentialBaseLsn property is incorrect.

Error 5172: The header for file ‘%ls’ is not a valid database file header. The DifferentialBaseGuid property is incorrect.

Generally, this error is caused by, for still unknown reason, routine to retrieve these property from file header page returns the null result or the length of the result do not match with the expected length.

The prevalence of these kind of error is very rare. For example, by searching the Google for “FGID Property” yields only about 5 cases.

Also in my experiences, I do not yet encounter this kind of error to be analyzed for the precise cause, and so, I can not provide the sample case study for the remedy ๐Ÿ™‚

Although it is very rare, this is the show stopper kind of error, or in other word, fatal error. It is effectively prevented you to attach and use the database. So, you should pray and hope that you will never encounter this calamity ๐Ÿ™‚

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


%d bloggers like this: