Post reply

Management Studio Not Recognizing Drive

  • October 8, 2008 at 2:08 pm

    #126955

    I was helping out our Sharepoint admin on his space issues. We detached a couple of the large files from Sharepoint C: drive and moved them over to the E: drive. When I went to attach the files, I was only given the option of files on the C: drive. We could not get the E: drive to show up on Management Studio. We are working on the local server. Is there a SQL setting I need to be looking at?

    Thanks

  • October 8, 2008 at 2:25 pm

    #882568

    Direct attached storage, SAN, NAS, network drive?

    Is is a clustered server? If so, is the E drive a dependency of SQL in the cluster admin?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 8, 2008 at 2:32 pm

    #882579

    both drives are on the same machine.

  • October 8, 2008 at 2:39 pm

    #882583

    Is it a clustered server?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • October 8, 2008 at 2:45 pm

    #882589

    no, it is not a clustered server.

  • October 8, 2008 at 2:53 pm

    #882596

    Does the SQL runtime account have access to E drive?

    try creating a test DB on E drive and see if the query gives you an error.

    cheers,

    Carlton..

  • October 9, 2008 at 8:19 am

    #882918

    no i cannot create a drive on the E: drive.

    Here is my error.

    TITLE: Microsoft SQL Server Management Studio Express

    ------------------------------

    Create failed for Database 'test'. (Microsoft.SqlServer.Express.Smo)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Database&LinkId=20476

    ------------------------------

    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)

    ------------------------------

    Directory lookup for the file "E:\data\test.mdf" failed with the operating system error 2(The system cannot find the file specified.).

    CREATE DATABASE failed. Some file names listed could not be created. Check related errors. (Microsoft SQL Server, Error: 5133)

  • October 9, 2008 at 8:28 am

    #882923

    It's fixed. I had him go through his permissions on C: drive and compare it to E: drive. Once he finished his adjustments, SQL Server recognized the E: drive.

  • October 9, 2008 at 8:45 am

    #882942

    Hi Adam

    U mean u detached the database from drive c and then tried to attach on drive E, are you trying to attach the database via management studio, or via SQL, if via SQL can u post the SQL, and what version of SQL are you using

    🙂

  • October 9, 2008 at 3:03 pm

    #883139

    I figured, SQL will throw msgs like this if the runtime account doesn't have permission to the location/share that its looking for.

    Cheers,

    Carlton..

Viewing 10 posts - 1 through 9 (of 9 total)

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