Post reply

sqlservr.exe - There is no disk on drive A:

  • March 8, 2004 at 2:36 pm

    #83884

    Hello:

    I get the following error message when I try to backup or restore a database from EM:

    sqlservr.exe - There is no disk on drive A:

    There is an MS KB article for this.

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q281345

    They provide three workarounds:

    1) edit the registry to hide all hard errors

    2) leave floppy in there permanently

    3) live with the error message

    I am not satisfied with these workarounds.  I am wondering if anyone has an alternative solution to this problem.

    thanks in advance,

    Billy

  • March 8, 2004 at 3:33 pm

    #497910

    Haven't found any other ways. It's a bug.

  • March 8, 2004 at 5:12 pm

    #497914

    I looked for a little bit, also, and there don't seem to be any other workarounds available. Since you don't want to be bothered by the error message, and you probably don't want to disable that class of errors altogether, the best option is probably to move the floppy drive down in the boot order (so it doesn't cause problems in a server reboot) and leave a floppy in the drive permanently.

    I wonder why it addresses the floppy drive - that's an odd behavior.

    Ryan

  • March 9, 2004 at 2:25 am

    #497933

    I had a problem with this on a couple of Compaq servers ( at a previous employment), the problem was casued by a config change the ops guys made to the server, nothing to do with SQL Server, I can't remember what the reason or fix was - but it might be worth checking out. Whatever it was the ops guys changed it back, but they wouldn't tell me exactly what it was. Probably something to do with accessing the server from the floppy - although the drive still worked.  Sometimes a similar issue is caused by saving an email to a floppy.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

  • March 9, 2004 at 2:53 am

    #497940

    We have experienced this problem too, and I agree with Colin that it seems to be a configuration change and not directly connected with SQL Server - it just suffers this strange manifestation - and we never quite managed to determine what exactly.  We got around the issue eventually by disabling the floppy device on the servers affected.  The curious thing was, that sometime later, a drive was re-enabled accidentally on one of the servers and the problem seemed to have cured itself - one of life's mysteries.

  • March 9, 2004 at 7:10 am

    #497960

    It may be worth checking th efollowing registry entry to see if it is pointing to your A: drive.  (This is unlikely to happen, but could give the same results)

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\<InstanceNameHere>\MSSQLServer\BackupDirectory

    This should normally point to your ...\MSSQL\BACKUP directory.

     

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • March 10, 2004 at 6:47 am

    #498113

    Had this issue as well. There is a hotfix available for this. At least for SQL 2000 SP2. You can request if from Microsoft, se below. With SQL 7.0 it's solved in SP4. You can also solve it by installing MDAC 2.7 SP1 since it updates sqloledb.dll to a new version compared to MDAC 2.6 that comes with SQL 2000 default installation (MDAC 2.7 SP1 is also installed with SQL 2000 SP3a).

    FIX: Error Dialog Box During SQL Server Database Backup

    http://support.microsoft.com/default.aspx?scid=kb;en-us;Q319246

  • April 27, 2004 at 11:21 pm

    #504423

    SQL 2000 SP3a fixes this error

Viewing 8 posts - 1 through 7 (of 7 total)

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