Share function failed. (400099)

My Cloud OS 3 Personal & Network Attached Storage My Cloud
1

I am trying to get familiar with the device by creating/deleting shares at the moment and have run into an issue.

I am unable to create or delete shares, as well as change their media serving/public settings.

Any time I attempt any of the previous actions i receive the error: 

  “Share function failed. (400099)”

I’ve done some searching and it seems I am one of the only ones to receive this error. 

Any ideas?

2

Hello johngaden, this issue is currently under investigation. Have you tried some of the basic troubleshooting steps, like doing a powercycle or doing a factory restore? 

3

Had the same issue.

I did everything, and nothing helped. 

At the end I jus did a system restore (System Only), and after that I was able create all users again and after setting permission to access all shares. 

But that was really scary.

4

I had the same problem using share name paul for username paul.  I rebooted ant tried again - no luck so, I changed his username to paulb and the share paulb worked.

5

I had the same problem (Share finction failed (400099)) when I tried to create a share called Movies. I then tried to create a share called Movie. Both attempts failed. However, when I look at My Computer (Windows 7) under Network and MDMYCLOUD to see what shares are on the device, both Movies and Movie appear as shares. However, when I use MY Cloud Dashboard to inspect the shares, they do not appear. Thus I have now created two shares that I cannot delete. I am able to create directories on the shares, and they survived a reboot of the WDMYCLOUD storage device. This is particularly troubling as I now do not trust the device at all. Any ideas?

6

if someone does a system only restore, the data stored on mycloud should remain untouched? What is exactly is happening and do someone needs to do all set up from sratch?

thx // greetz

7

The System only restore leaves the data stored on the mycloud intact. From the WD video regarding this what is done is:

  • Change all system settings to default ones
  • Make all private shares public
  • Remove any administrator password
  • Data remains intact

You can watch the video here:  https://www.youtube.com/watch?v=2c9bUz5KqTA

I had to do this on my system today because I was having issues with share permissions amongst other things and it appears to have solved the issues.

However, you might want to wait for someone with more expereince to reply since I’ve only had my device just over a week. 

8

thx inversechi for ur good explaination.

I’m now about to think if I run system only restore without having a backup …

cheers

9

Hi jubei04,

Is there soon an ‘official’ solution for this issue?

Thanks,

10

All I can say is the first post seemed to be in February… Now August and WDC do not seem to have solved this one.  Seems to be no rhyme nor reason.  Some names for shares work, some bring up this error… Shame as I would like my users to have their private area called with their name

11

Further to my earlier post.  I had the error 400999 when trying to set up a share called Lynne.  If I look now through Explorer i see a shared folder “Lynne” created on the Mycloud Network Drive, but if I use the Mycloud Dashboard it cannot see it.  Basically Explorer tells me I have 13 shared folders, mycloud tells me 11.  the two shares I had error 400099 do not show.  I cannot seem to be able to remove them either in Windows 

12

I had this issue when I was having performance issues I tried to create a couple of shares with no errors, but it never finished. turns out they where partialy created and visable from windows but not the UI.

I fianlly removed the partially created shares in Unix, then re-created them in the UI without issue. from my experiance if you are having any issues don’t try to create anything

try this at your own risk and backup files before editing them

I removed the problem share sections in /etc/samba/overall_share - I have also had this file get out of sync and had to manually set permissions.

in /shares I removed the problem directories

in /etc/trustees.conf I removed the problem sections

unmounted the problen nfs shares

13

Larry

Many thanks, but regret your reply went over my head, plus I have zilch knowledge of Unix, and doing all this with Windows 7.  As I am just setting up at the moment looks like I may be best starting from a factory reset and start from scratch

14

yes not really for the faint of heart. also why I didn’t go into great details only enough for someone already familier with Linuxs can follow it as it is easy to make things worse if you are not sure what you are doing.

you could use another share name and just forget the old one or if you don’t have much data on it a factory restore is probably best. this will delete data so have another copy available.

from my experiance be patient and don’t create any users or shares if it is not performing well at the time

15

Okay, once again i’m stuck manually editing the samba config, because updating to the most recent firmware has buggered up changing permissions and renaming shares… AGAIN.

The first time around, the developers buggered it up by changing the indenting characters from 2 (two) spaces in the overall_share file to a tab indent (or vice versa, i forget which way round it was), subsequently buggering up whatever function that re-wrote changes made in the UI to the samba config for existing shares.

Now it seems that the following occurs:

  1. Renaming an existing share fails, where it updates the samba config, but doesn’t update the UI, leaving it in an unsyncronized state.

  2. Queuing up multiple permission changes at once does not seem to guarantee that all changes will be written to the samba config, whilst simultaniously always changing in the UI, leaving it in an unsyncronized state.

For crying out loud WD developers, this really is embarrasing to watch **bleep** like this happen to a mass-market product. Configuring shares and permissions on a NAS device is about as basic a function as you can hope to perform, and yet you manage to balls it up on multiple occasions. Get your **bleep** together.

I suggest writing the ENTIRE overall_share file out again every time ANY change is made from whatever data source the UI draws on directly, instead of having some elaborate -and apparently broken- ego stroking function that tweaks small portions of it, for no apparent functional/performance reason.

As an aside, the time it takes to perform an extremely simple action in the UI in gerenal is bloody awful.

-Moccy (angry).

-Edit: and apparently the firmware update also wiped out my safepoint setup. Fantastic.

16

This is crazy that WD treats us as beta testers! I had the same problem with unfinished share creation , the funny thing is that I was able create almost the same share (with first capital letter… in box we have linux) and it was visible in samba and in the UI, after deleting it the old one was visible (i wonder which physical dir was used). Finally I removed wrong share using ssh (I was warned that I can loose my warranty). The conclusion is that WD cannot create firmware with really basic NAS functionality working fine (creating shares, changing rights etc.) and repairing their mistakes violate warranty! It **bleep**  (edit: Really?  It wasn’t really abusive)! Moreover uploading lots of pictures causes slow downs and finally NAS stops responding, great. Cheers from new Beta Tester!

17

Has anyone got an answer to this? I am an IT professional and have spent the last two weeks on and off trying to get this box to work correctly (rebooting, restoring, etc.) all hoping that the data I initially copied too it wont get lost (I’m now using my desktop to back it up just in case, crazy stuff). I am now at the point where I am creating shares and copying content from shares that no longer work (because of this error and the inability to make changes  or make the share visible to DLNA clients etc.) I am starting to lose the plot as the dashboard is so slow, functionality stops working. I have multiple shares that are not visible on the dashboard, shares that have a different name in windows explorer to that in the dashboard and shares that are not visible in the dashboard but visible to windows (but I cant share out to DLNA). This product is a midge’s **bleep** away from being thrown through Curry’s door (literally). I am not one for being beaten, but this product is almost there.

I’ve never in 35 yearss in the IT industry dealt with a product as flaky as this.

18

Exact same problem here. For the zillionth time. I would be ashamed to work for WD, delivering X like this. But hey, ask them if they care. All they care about is taking our money.

19

Impossible, the problem still goes on. I got with my new MyCloud the same problem in german language.

Don’t no WD Member read this board?

regards, WolfgangE

20

Moderators read the forums but not support. The best method is to contact WD Support:

By Phone or By Email . You can also Creat a New Support Case using the same Email and Password that you registered your My Cloud with. https://westerndigital.secure.force.com/ind/ID_Login

2 Likes