Results 1 to 6 of 6
  1. #1
    Join Date
    Sep 2004

    Unanswered: Restore database stuck on (Loading)

    I recently installed MSDE on a laptop. I then restored several databases from backup files without problem. However, one database is constantly stuck at the grey colour displaying the (Loading) message.

    Why won't this database restore ? It is of course the most important database and I only have the one backup file.

    This only appears to fail on his server. Do I need to uninstall MSDE and start over ?

  2. #2
    Join Date
    Feb 2004
    In front of the computer
    Provided Answers: 54
    It's probably the machine's "critical need detector", it might be a wee bit too sensitive or mis-adjusted.

    On a slightly more serious note, what tools are you using to do the restore? The only tool that could do a restore that ships with MSDE is OSQL.EXE, and I'm pretty comfortable that you aren't using that! Enterprise Mangler would be my first guess, but that is still only a guess.

    Could the dump (backup) have been made with a later service pack than you are using to restore it? That can make things get really crabby sometimes.

    Is the database file one that this instance of MSDE can handle? Depending on the MSDE version, you can handle up to 2 Gb of data (although I've seen data and log dumps over 10 Gb).

    If none of those ideas pan out, then my first suggestion would be to:

    1 Disable everything you can that uses MSDE (keep notes!)
    2 Stop the MSDE service
    3 Restart the MSDE service
    4 Try to load the offending database
    5 If you can't load the database, stop the MSDE service
    6 Examine the Errorlog file carefully
    7 If you can't find anything in the Errorlog, consider posting it here.
    8 if the database can be posted, consider posting the backup too for us to play with!


  3. #3
    Join Date
    Jul 2003
    San Antonio, TX
    If it's in Loading state, could it be that you are restoring from a backup device that contained incomplete set of full db backup and some trx logs?
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  4. #4
    Join Date
    Sep 2004
    But it restores without fail on any number of other servers. So I think the backup file is ok.

    I have gone through the steps above and can't see anything wrong. I have pasted the errorlog below for perusal.

    Yes I am using Enterprise manager. I also tried the restore database command from isqlw utility and that also produced the error :

    Processed 8432 pages for database 'IPSHOW_NEW', file 'IPSHOW_Data' on file 1.
    [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
    Server: Msg 11, Level 16, State 1, Line 0
    General network error. Check your network documentation.
    Processed 1 pages for database 'IPSHOW_NEW', file 'IPSHOW_Log' on file 1.

    Connection Broken

    2004-12-23 15:56:36.01 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
    Dec 17 2002 14:22:05
    Copyright (c) 1988-2003 Microsoft Corporation
    Personal Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

    2004-12-23 15:56:36.01 server Copyright (C) 1988-2002 Microsoft Corporation.
    2004-12-23 15:56:36.01 server All rights reserved.
    2004-12-23 15:56:36.01 server Server Process ID is 1392.
    2004-12-23 15:56:36.01 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
    2004-12-23 15:56:36.09 server SQL Server is starting at priority class 'normal'(1 CPU detected).
    2004-12-23 15:56:36.13 server SQL Server configured for thread mode processing.
    2004-12-23 15:56:36.13 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
    2004-12-23 15:56:36.15 spid3 Starting up database 'master'.
    2004-12-23 15:56:36.53 server Using 'SSNETLIB.DLL' version '8.0.766'.
    2004-12-23 15:56:36.53 spid5 Starting up database 'model'.
    2004-12-23 15:56:36.68 spid3 Server name is 'SBUTLER'.
    2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 4
    2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 5
    2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 6
    2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 9
    2004-12-23 15:56:36.68 spid3 Skipping startup of clean database id 10
    2004-12-23 15:56:36.68 spid3 Starting up database 'IPSHOW_NEW'.
    2004-12-23 15:56:36.68 server SQL server listening on 1433.
    2004-12-23 15:56:36.69 server SQL server listening on 1433.
    2004-12-23 15:56:36.98 spid3 Bypassing recovery for database 'IPSHOW_NEW' because it is marked IN LOAD.
    2004-12-23 15:56:37.09 server SQL server listening on TCP, Shared Memory, Named Pipes.
    2004-12-23 15:56:37.09 server SQL Server is ready for client connections
    2004-12-23 15:56:37.22 spid5 Clearing tempdb database.
    2004-12-23 15:56:38.58 spid5 Starting up database 'tempdb'.
    2004-12-23 15:56:38.78 spid3 Recovery complete.
    2004-12-23 15:56:38.78 spid3 SQL global counter collection task is created.
    2004-12-23 15:57:35.63 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
    2004-12-23 15:57:35.78 spid51 Starting up database 'msdb'.

  5. #5
    Join Date
    Aug 2002
    Post the statement used in ISQL to restore the database.
    And ensure the backup file is stored on the MSDE server and if you are trying to restore from a network location due to th network issues it may be failing with the above error.

    Refer to this KBA;en-us;827452 for relevancy.
    --Satya SKJ
    Microsoft SQL Server MVP

  6. #6
    Join Date
    Sep 2004
    I gave up and uninstalled MSDE. As it turns out he required Reporting Services and a Developer Edition of SQL Server so all for the best in the end. Thanks for the assistance.

Posting Permissions

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