Local Computer drives are not visible when creating backup through wizardSQL Server 2000: Database copy wizard - Claims files already exist (they don't) or there is not enough disk space (there is)When successfully configured SQL Server for database mirroring, got an error saying it's not configured for database mirroringRestoring SQL Server backup to SQL Azure on SQL Management StudioMS SQL Start Mirroring Error

Multi tool use
Multi tool use

Extending prime numbers digit by digit while retaining primality

When Bnei Yisroel travelled in the midbar, what happened on Shabbos?

What mathematical theory is required for high frequency trading?

What does this Swiss black on yellow rectangular traffic sign with a symbol looking like a dart mean?

What constitutes a syllable?

Find the common ancestor between two nodes of a tree

Greeting with "Ho"

Second 100 amp breaker inside existing 200 amp residential panel for new detached garage

Are there examples of rowers who also fought?

How to work with PETG? Settings, caveats, etc

What is the "ls" directory in my home directory?

Find All Possible Unique Combinations of Letters in a Word

Prisoner on alien planet escapes by making up a story about ghost companions and wins the war

What is the meaning of "понаехать"?

Methodology: Writing unit tests for another developer

In the US, can a former president run again?

What does it cost to buy a tavern?

How do I remove this inheritance-related code smell?

Cut the gold chain

How could empty set be unique if it could be vacuously false

Explicit song lyrics checker

Rejecting an offer after accepting it just 10 days from date of joining

What was the first third-party commercial application for MS-DOS?

Text alignment in tikzpicture



Local Computer drives are not visible when creating backup through wizard


SQL Server 2000: Database copy wizard - Claims files already exist (they don't) or there is not enough disk space (there is)When successfully configured SQL Server for database mirroring, got an error saying it's not configured for database mirroringRestoring SQL Server backup to SQL Azure on SQL Management StudioMS SQL Start Mirroring Error






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















When I connect to a database on a remote server through SSMS running on my own computer and I follow the backup wizard for a database, none of my local computer drives are listed. All I can see are drives on the remote server and I can't get access to them since I do not have enough permissions.



It seems weird, why I can't see my own computer drive volumes when creating a backup file?



Here's what I do:



On Object Explorer, right click on database then click on Tasks > Backup, Add > ...



Part of error message: Can not access the specified path on server.










share|improve this question






























    1















    When I connect to a database on a remote server through SSMS running on my own computer and I follow the backup wizard for a database, none of my local computer drives are listed. All I can see are drives on the remote server and I can't get access to them since I do not have enough permissions.



    It seems weird, why I can't see my own computer drive volumes when creating a backup file?



    Here's what I do:



    On Object Explorer, right click on database then click on Tasks > Backup, Add > ...



    Part of error message: Can not access the specified path on server.










    share|improve this question


























      1












      1








      1








      When I connect to a database on a remote server through SSMS running on my own computer and I follow the backup wizard for a database, none of my local computer drives are listed. All I can see are drives on the remote server and I can't get access to them since I do not have enough permissions.



      It seems weird, why I can't see my own computer drive volumes when creating a backup file?



      Here's what I do:



      On Object Explorer, right click on database then click on Tasks > Backup, Add > ...



      Part of error message: Can not access the specified path on server.










      share|improve this question
















      When I connect to a database on a remote server through SSMS running on my own computer and I follow the backup wizard for a database, none of my local computer drives are listed. All I can see are drives on the remote server and I can't get access to them since I do not have enough permissions.



      It seems weird, why I can't see my own computer drive volumes when creating a backup file?



      Here's what I do:



      On Object Explorer, right click on database then click on Tasks > Backup, Add > ...



      Part of error message: Can not access the specified path on server.







      sql-server ssms






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 3 at 10:13









      Daniel K

      330111




      330111










      asked Jun 3 at 5:58









      Mohammad lm71Mohammad lm71

      1064




      1064




















          1 Answer
          1






          active

          oldest

          votes


















          2














          This behaviour is expected.



          SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.



          You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.






          share|improve this answer

























          • SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's OBVIOUS that what you said is not that obvious !!!

            – Mohammad lm71
            Jun 3 at 7:21






          • 1





            No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.

            – TomTom
            Jun 3 at 7:30












          • You obviously didn't pay attention to the word through in I connect ... through SSMS running on my own computer. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.

            – Mohammad lm71
            Jun 3 at 9:38












          • SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).

            – TomTom
            Jun 3 at 9:39











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "2"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969888%2flocal-computer-drives-are-not-visible-when-creating-backup-through-wizard%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          This behaviour is expected.



          SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.



          You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.






          share|improve this answer

























          • SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's OBVIOUS that what you said is not that obvious !!!

            – Mohammad lm71
            Jun 3 at 7:21






          • 1





            No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.

            – TomTom
            Jun 3 at 7:30












          • You obviously didn't pay attention to the word through in I connect ... through SSMS running on my own computer. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.

            – Mohammad lm71
            Jun 3 at 9:38












          • SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).

            – TomTom
            Jun 3 at 9:39















          2














          This behaviour is expected.



          SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.



          You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.






          share|improve this answer

























          • SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's OBVIOUS that what you said is not that obvious !!!

            – Mohammad lm71
            Jun 3 at 7:21






          • 1





            No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.

            – TomTom
            Jun 3 at 7:30












          • You obviously didn't pay attention to the word through in I connect ... through SSMS running on my own computer. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.

            – Mohammad lm71
            Jun 3 at 9:38












          • SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).

            – TomTom
            Jun 3 at 9:39













          2












          2








          2







          This behaviour is expected.



          SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.



          You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.






          share|improve this answer















          This behaviour is expected.



          SQL Server runs on the remote server, in a service account so it cannot not see your own volumes. Why would SQL Server have any special rights to see your local computer?.



          You have to create a file share on your local computer, assign appropriate permissions and then you CAN use UNC format (computernamesharename) to use that local file share.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jun 3 at 10:34









          Daniel K

          330111




          330111










          answered Jun 3 at 7:00









          TomTomTomTom

          46.2k642120




          46.2k642120












          • SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's OBVIOUS that what you said is not that obvious !!!

            – Mohammad lm71
            Jun 3 at 7:21






          • 1





            No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.

            – TomTom
            Jun 3 at 7:30












          • You obviously didn't pay attention to the word through in I connect ... through SSMS running on my own computer. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.

            – Mohammad lm71
            Jun 3 at 9:38












          • SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).

            – TomTom
            Jun 3 at 9:39

















          • SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's OBVIOUS that what you said is not that obvious !!!

            – Mohammad lm71
            Jun 3 at 7:21






          • 1





            No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.

            – TomTom
            Jun 3 at 7:30












          • You obviously didn't pay attention to the word through in I connect ... through SSMS running on my own computer. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.

            – Mohammad lm71
            Jun 3 at 9:38












          • SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).

            – TomTom
            Jun 3 at 9:39
















          SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's OBVIOUS that what you said is not that obvious !!!

          – Mohammad lm71
          Jun 3 at 7:21





          SQL Server is running on my computer, it's accessing to remote SQL server, so SSMS knows my computer drives, it's OBVIOUS that what you said is not that obvious !!!

          – Mohammad lm71
          Jun 3 at 7:21




          1




          1





          No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.

          – TomTom
          Jun 3 at 7:30






          No, it is not. Let me quote your first sentence that you obviously did not read yourself: "I connect to a database on a remote server". Remote server != local computer. SSMS != SQL Server. SSMS locally can see them, but it sends STRINGS to the server, and the server has diffrerent ideas what C: means than your SSMS on your computer.

          – TomTom
          Jun 3 at 7:30














          You obviously didn't pay attention to the word through in I connect ... through SSMS running on my own computer. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.

          – Mohammad lm71
          Jun 3 at 9:38






          You obviously didn't pay attention to the word through in I connect ... through SSMS running on my own computer. Never mind, It sucks when there are tons of obvious phrases with no feasible solution.

          – Mohammad lm71
          Jun 3 at 9:38














          SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).

          – TomTom
          Jun 3 at 9:39





          SSMS running local is irrelevant. Backups are - as documentation states - run WITHOUT ssms - all SSMS does is send the command string to the server. As such, you can run SSMS where you want, what matters is that the server can reach the location through the path you enter into SSMS (because that path gets sent to the server).

          – TomTom
          Jun 3 at 9:39

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Server Fault!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969888%2flocal-computer-drives-are-not-visible-when-creating-backup-through-wizard%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          R5r,cnY,1s r,HWt5Vw 7jnSO MA,j,zv,n8G3QWsli,wBYSTBkMvu,PNjn11zn,HXfe8dYqXyF,mFA7m0X0JcF
          JPRmXOntMvVFQdXxkEQJ9yOK HN tnmb7A,XM Fe,w26mYy,pOup g3y31cSO,ZiQe0IhSWVqRlJtpJGCPsMF

          Popular posts from this blog

          RemoteApp sporadic failureWindows 2008 RemoteAPP client disconnects within a matter of minutesWhat is the minimum version of RDP supported by Server 2012 RDS?How to configure a Remoteapp server to increase stabilityMicrosoft RemoteApp Active SessionRDWeb TS connection broken for some users post RemoteApp certificate changeRemote Desktop Licensing, RemoteAPPRDS 2012 R2 some users are not able to logon after changed date and time on Connection BrokersWhat happens during Remote Desktop logon, and is there any logging?After installing RDS on WinServer 2016 I still can only connect with two users?RD Connection via RDGW to Session host is not connecting

          Vilaño, A Laracha Índice Patrimonio | Lugares e parroquias | Véxase tamén | Menú de navegación43°14′52″N 8°36′03″O / 43.24775, -8.60070

          Cegueira Índice Epidemioloxía | Deficiencia visual | Tipos de cegueira | Principais causas de cegueira | Tratamento | Técnicas de adaptación e axudas | Vida dos cegos | Primeiros auxilios | Crenzas respecto das persoas cegas | Crenzas das persoas cegas | O neno deficiente visual | Aspectos psicolóxicos da cegueira | Notas | Véxase tamén | Menú de navegación54.054.154.436928256blindnessDicionario da Real Academia GalegaPortal das Palabras"International Standards: Visual Standards — Aspects and Ranges of Vision Loss with Emphasis on Population Surveys.""Visual impairment and blindness""Presentan un plan para previr a cegueira"o orixinalACCDV Associació Catalana de Cecs i Disminuïts Visuals - PMFTrachoma"Effect of gene therapy on visual function in Leber's congenital amaurosis"1844137110.1056/NEJMoa0802268Cans guía - os mellores amigos dos cegosArquivadoEscola de cans guía para cegos en Mortágua, PortugalArquivado"Tecnología para ciegos y deficientes visuales. Recopilación de recursos gratuitos en la Red""Colorino""‘COL.diesis’, escuchar los sonidos del color""COL.diesis: Transforming Colour into Melody and Implementing the Result in a Colour Sensor Device"o orixinal"Sistema de desarrollo de sinestesia color-sonido para invidentes utilizando un protocolo de audio""Enseñanza táctil - geometría y color. Juegos didácticos para niños ciegos y videntes""Sistema Constanz"L'ocupació laboral dels cecs a l'Estat espanyol està pràcticament equiparada a la de les persones amb visió, entrevista amb Pedro ZuritaONCE (Organización Nacional de Cegos de España)Prevención da cegueiraDescrición de deficiencias visuais (Disc@pnet)Braillín, un boneco atractivo para calquera neno, con ou sen discapacidade, que permite familiarizarse co sistema de escritura e lectura brailleAxudas Técnicas36838ID00897494007150-90057129528256DOID:1432HP:0000618D001766C10.597.751.941.162C97109C0155020