MSSQLSERVER service fails with event id 5731 after installation of SP1,

Question

Post reply

MSSQLSERVER service fails with event id 5731 after installation of SP1,

Ian Shiel

SSC Rookie

Points: 37
More actions
November 1, 2006 at 12:40 pm

#121200

Hello all
We had a working SQL Server 2005 standard edition database. We had moved the master, model, msdb, temp and resouce databases to different disks (RAID 0+1 arrays) as described in Books online.
We installed SP1 and since then the MSSQLSERVER service fails to start with event id 5731.
The application log shows:-
One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
0000: 35 14 00 00 10 00 00 00   5.......
0008: 09 00 00 00 4e 00 56 00   ....N.V.
0010: 53 00 45 00 52 00 56 00   S.E.R.V.
0018: 45 00 52 00 00 00 07 00   E.R.....
0020: 00 00 6d 00 61 00 73 00   ..m.a.s.
0028: 74 00 65 00 72 00 00 00   t.e.r...
Has anyone else had this issue or similar? Cant find anything on Microsoft's support site in relation to this. One thing that may have had an impact was that one of the disks in the RAID 0+1 array was faulty but the array was still online (this being the reason for RAID in the first place!) so this *shouldn't* (?) be the cause.

I would appreciate any help/advice with this.This database is not a production system and we had just finished moving the system databases as described above so it can all be re-installed and moved again relatively easily (i.e. no lost data!). However, would like to know if anyone else has had this experience or can suggest a fix so that we dont have to re-install.
Regards & Thanks
Ian

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Johan Bijnens SSC Guru Points: 135266 More actions · Answer 1

- So you moved the systemdb's and the RTM still worked ?

- what are your startup parameters for sqlserver ?

- check the original locations to see if sp1 put new db-files overthere (especialy resouce-files)

Johan

Learn to play, play to learn !

Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:

- How to post Performance Problems
- How to post data/code to get the best help[/url]

- How to prevent a sore throat after hours of presenting ppt

press F1 for solution, press shift+F1 for urgent solution 😀

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me

Ian Shiel SSC Rookie Points: 37 More actions · Answer 2

Q: So you moved the systemdb's and the RTM still worked ?

A: Yes

Q : what are your startup parameters for sqlserver ?

A:

-dF:\MSSQL\DATA\master.mdf;

-eF:\MSSQL\ELOG\errorlog;

-lG:\MSSQL\LOGS\mastlog.ldf

Q: check the original locations to see if sp1 put new db-files overthere (especialy resouce-files)

A: I don't believe it did - I did check and didn't see any files relating to the system dbs in the MSSQL.1 folder in C.....

We ran out of time on this so we uninstalled SQL Server 2005 and deleted the .mdf and .ldf files. We then re-installed SQL Server 2005, moved the system dbs and installed SP1 on top of this and it is now working..... Fingers crossed.

Thanks

Ian

Johan Bijnens SSC Guru Points: 135266 More actions · Answer 3

topic "Moving System Databases" in BOL describes it clearly.

When I find some time I'll have to test this procedure myself. (this will be after 3 weeks because I'll have some vacation and will be joining sqlpass )