I am getting: unable to create file share "//server/share". I however and sure I am putting it in as \\server\share.
I had this problem because my LDAP Bind Account was something other than simply the username. I had domain\username and that caused the file share to not work. I changed it to just username and then the file share worked.
Some more detail: I tried connecting to a share off a Windows 10 device but got the same error. I tried pinging the machine from the console of the appliance and can without a problem. Thinking maybe it was a permissions issue and to just get it working I gave Everyone full rights at the share and NTFS level but same error. Thinking maybe its a Windows 10 issue I created a share off a Server 2012 R2 server. Following the same steps as before I still got the same error.
We had the same issue over here when we had ldap set to use ssl. Either turning ssl off or enabling ssl in the old management interface on port 3443 solved the problem for us.
I set it up with \\server\share and that was fine, redid the machine and now that didn't work, what worked was \\server.domain.com\share, weird.
Sam
i am having the same issue...
created the share on file server, trying to add the share and get the same error. i have everyone as read/write to the share.
my LDAP is not using secure...
did anyone find a solution yet?
I tried \\server.domain.com\share but still same error. I am using and set to ldap. Still same error.
Same problem here. Tried switch LDAP on and off and nothing. Tried using hostname.domain.com and nothing. Tried using IP address and still same problem.
You did create the share on the server before adding it into Appvolumes?
And did you check share permissions on the share? (so not NTFS permissions)
Adding me to the list of people with this problem. Neither Customizations nor Applications works for me, tried all possible configurations.
If you go an look at the AV 3.0 log file right after you attempt to create the file share, post that here. Path: https://IPAddressAV30Svr:3443/log
I am working on this issue with a few people.
Same problem here. Not able to add a share.
the log file as from my environment:
[2016-04-02 11:05:36 UTC] P2148R4229 INFO Started POST "/xms/file_shares" for 127.0.0.1 at 2016-04-02 13:05:36 +0200
[2016-04-02 11:05:36 UTC] P2148R4229 INFO Processing by Xms::FileSharesController#create as JSON
[2016-04-02 11:05:36 UTC] P2148R4229 INFO Parameters: {"data"=>{"id"=>"1459595136682", "name"=>"appshare1", "virtual"=>"true", "physical"=>"false", "policies"=>"false", "auto_import"=>"true", "type"=>"FileShare", "status"=>"pending", "status_message"=>"", "path"=>"\\\\ng-file01.intern.domainname.nl\\Appvolumes", "local_path"=>"", "hypervisor_ids"=>{"0"=>"1", "1"=>"2"}, "last_sync"=>"2016-04-02T11:05:36.683Z"}}
[2016-04-02 11:05:36 UTC] P2148R4229 INFO Creating directory: "/mnt/wem/__ng_file01_intern_domainname_nl_Appvolumes"
[2016-04-02 11:05:37 UTC] P2148R4229 ERROR Unable to mount file share because of permission: error 32, File share must be in the given domains.
[2016-04-02 11:05:37 UTC] P2148R4229 ERROR Unable to create file share "//ng-file01.intern.domainname.nl/Appvolumes"
[2016-04-02 11:05:37 UTC] P2148R4229 INFO Completed 400 Bad Request in 348.7ms (Views: 0.5ms | ActiveRecord: 2.4ms)
[2016-04-02 11:05:37 UTC] P2148R4229 INFO
apparently permission error (32). Using AD with secure connection. appvolume manager is ng-appvolumes03.domainname.nl and the fileshare is \\ng-file01.intern.domainname.nl\Appvolumes
I had this problem because my LDAP Bind Account was something other than simply the username. I had domain\username and that caused the file share to not work. I changed it to just username and then the file share worked.
That was it. I had the user id as user@domain.com. I took @domain.com off and it just worked. Thanks for the help.
cstalhood3's solution worked for me. I removed @domain.com from my LDAP bind and then the share creation worked. Thanks!
yup same here. removing the domain name from the LDAP bind user account and it worked just fine.....
I'm having the same issue however my BIND is using Administrator (no domain before or after)
There are a few others here with the same issue - Re: Getting "Unable to create file share" error
Awesome post, this fixed it for me!
I had to add in my FQDN of my share and that fixed it
\\share-01\AppCapture - Not working
\\share-01.internal.domain.com\AppCapture - WORKED!
Thanks !
Once i updated my LDAP Bind without the domain\username just username it i was able create my AV manager and File Share locations! Thanks