Results 1 to 6 of 6
  1. #1
    Join Date
    Dec 2007
    Posts
    3

    Question Unanswered: master database rebuild takes long time

    Hi All,

    I'm trying to rebuild my master database for sql server 2000. The process of rebuilding stared fine. But it is almost 4 hours since it got started. Performing it on a test system. Got doubtful and started the same on another test system. Issue is same and it is almost 2 hours. The Db size is less than 100 MB in both cases. IS IT NORMAL? I've tried the same for SQL SERVER 2005 and it got finished in couple of minutes. Please advise.

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    I have not seen a rebuild of master run for 4 hours. Do you have anything attempting to connect as administrator? Perhaps some monitoring software? Or some software that likes to restart stopped services, in case they have crashed?

  3. #3
    Join Date
    Dec 2007
    Posts
    3

    Master rebuild takes long time

    Hi,

    I've checked the services. They are fine. There was no monitoring software installed. The issue is same with another test system too.Copied the log below:

    2007-12-18 08:04:56.70 server Attempting to initialize Distributed Transaction Coordinator.
    2007-12-18 08:04:57.59 server Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
    2007-12-18 08:04:57.65 spid3 Starting up database 'master'.
    2007-12-18 08:04:57.65 spid3 udopen: Operating system error 5(Access is denied.) during the creation/opening of physical device C:\Program Files\Microsoft SQL Server\MSSQL\data\master.mdf.
    2007-12-18 08:04:57.70 spid3 FCB::Open failed: Could not open device C:\Program Files\Microsoft SQL Server\MSSQL\data\master.mdf for virtual device number (VDN) 1.
    2007-12-18 08:04:57.70 spid3 Error: 5105, Severity: 16, State: 4.
    2007-12-18 08:04:57.73 spid3 udopen: Operating system error 5(Access is denied.) during the creation/opening of physical device C:\Program Files\Microsoft SQL Server\MSSQL\data\mastlog.ldf.
    2007-12-18 08:04:57.73 spid3 FCB::Open failed: Could not open device C:\Program Files\Microsoft SQL Server\MSSQL\data\mastlog.ldf for virtual device number (VDN) 2.
    2007-12-18 08:04:57.75 spid3 Error: 5105, Severity: 16, State: 4.
    2007-12-18 08:04:57.75 spid3 Error: 5180, Severity: 22, State: 1.

    Any help in this regard is highly apperciated

  4. #4
    Join Date
    Jan 2004
    Location
    In a large office with bad lighting
    Posts
    1,040
    Looks like you don't have permisions to write to the C drive on the server.

    -- This is all just a Figment of my Imagination --

  5. #5
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,800
    Provided Answers: 11
    More likely this is the problem where the master.mdf and mastlog.ldf files are marked readonly. There is a KB article about this somewhere. The short of it is, you copy the data files from CD to the local machine, mark them as writeable, then use that location to rebuild master from.

  6. #6
    Join Date
    Dec 2007
    Posts
    3

    Success!!!!'master database rebuild takes long time'

    Hi,

    This step worked well. Cleared the read only attributes for master .mdb and .ldf files and rebuild completed successfully.

    THANKS A LOT

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •