thanks for the reply, i was able to solve the issue and puttting it over here for the future if some 1 else gets in to the same problem.

the issue is related to the re-booting after the reboot the principal was not able to connect the server.. based on my research there are 2 steps to solve it.

- re-start ur service which will bring the mirror server to (principal and synchronized state)

if that doesnt work than we have to do the long process.

remove mirroring and config the mirroring again

for this these are the steps to follow.

on the mirror server since the database is set as a mirror database and showing in a restore state; change that to the regular state

for this you have to run the ALTER DATABASE <database name> SET PATNER OFF

this will bring the database in the regular state

now you have to do apply the full backup and all the trans log backups up till the last trans log backup.

i know in the books online it says just full backup and one trans log backup will do but it didnt work in my case. i had to apply full backup and all the avialable trans long backups from the principal database to the mirror database.

make sure to use the NON_ RECOVERY option and replace or overwrite the existing database option.

once that is set than use the mirror wizard and configure the database mirroring.

long process but worked like a charm for me.

thanks for every onces help.