• 0

Creating a directory on a shared drive


Question

I have a shared drive mapped to my local as drive Z. Using Windows Explorer, I can create directories in that folder all day long. The moment I try to add a directory from anywhere else, I get an error (a device attached to the system is not functioning). I'd ideally like to create the new directory from C# - which throws that same exception. I've tried xcopy and robocopy and both of those also fail with the same error.

 

So, does anyone know why creating a folder would work 100% of the time in explorer and 0% from anywhere else (including the most needed C# code)?

 

I've tried both of these to no avail

var di = new DirectoryInfo("z:\");
di.CreateSubDirectory("Test");


var di = new DirectoryInfo("\\servername\sharename\attachments\");
di.CreateSubDirectory("Test");

 

I've also tried (where test is the folder I'd like created)

xcopy file.txt z:\test\file.txt /T 
robocopy c:\ z:\test\ file.txt /COPY:DT

 

I've also done this with no happiness... Same error

c:\> z:
z:\> md test

 

 

If I navigate to either the Z drive or the share directly in Windows Explorer, I can right click and add a folder (and rename it).  I'm stumped.   I keep thinking its a permissions issue of some kind but then rationalize that Explorer and a command prompt are both running as my user (non-elevated) so how can permissions come into play.. 

 

Any one have any ideas?

 

 

    

0 answers to this question

Recommended Posts

There have been no answers to this question yet

This topic is now closed to further replies.
  • Posts

    • It does when you're a software developer and you have to provide supports for these people.
    • Epic endless battle between Windows and Linux, as if it matters what OS the fella next door is running!
    • Microsoft 365 getting "major change" to how app updates will be released by Sayan Sen Microsoft tends to publish messages regarding upcoming Microsoft 365 app updates and changes on its Microsoft 365 admin center dashboard. Some of these posts are labelled as a "major change" as they require admin attention and monitoring to ensure smooth deployment of such changes, which can be new feature additions or removal of some. Communicating these early is crucial given that they can introduce bugs and issues, and sometimes they can be numerous as it happened with Outlook following a big Calendar upgrade. Microsoft recently announced changes to Teams-certified third-party app approvals. However, it may not be available to all licenses as initially announced. You can find the details in its dedicated article here. Another "major change" Microsoft has announced is about how the Microsoft 365 (M365) app update channels will function. For those who may not be familiar, the tech giant currently releases M365 app updates in four ways: Current channel, Monthly Enterprise channel, Semi-Annual Enterprise channel (preview), and Semi-Annual Enterprise Channel. Administrators, depending on how often and soon their organizations want the updates, can choose the servicing channel. However, Microsoft has announced today that it is deprecating the semi-annual preview channel and at the same time, reducing the support for the semi-annual channel from 14 months down to eight months. On the positive side, the company is extending the monthly channel servicing from one month to two. In an updated support document regarding this, Microsoft has outlined the changes. It writes: "Update Channel Changes Coming July 2025: Microsoft is making significant changes to update channels beginning July 2025: Monthly Enterprise Channel: Rollback support extended to 2 months (from 1 month) Semi-Annual Enterprise Channel (Preview): Being deprecated - migrate devices immediately Semi-Annual Enterprise Channel: Support duration reduced to 8 months (from 14 months), shifting to focus on unattended devices" Some additional details regarding this have also been released. Below, Microsoft has explained why the Semi-Annual Channel is seeing the alteration. The company writes: You can find the updated support document here on Microsoft's official website. Details about the change have also been communicated to the M365 Admin Center via message ID MC1087098.
    • Polaroid went bankrupt due to poor sales after the rise in digital cameras and cheaper analogue alternatives. Now nearly everyone has a digital camera in their pocket , it's pointless. Nostalgia wont sell big numbers.
  • Recent Achievements

    • Dedicated
      jbatch earned a badge
      Dedicated
    • Week One Done
      Leonard grant earned a badge
      Week One Done
    • One Month Later
      portacnb1 earned a badge
      One Month Later
    • Week One Done
      portacnb1 earned a badge
      Week One Done
    • First Post
      m10d earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      264
    2. 2
      snowy owl
      158
    3. 3
      +FloatingFatMan
      145
    4. 4
      ATLien_0
      140
    5. 5
      Xenon
      131
  • Tell a friend

    Love Neowin? Tell a friend!