- #INKLET CANNOT GRANT PERMISSION SOFTWARE#
- #INKLET CANNOT GRANT PERMISSION PASSWORD#
- #INKLET CANNOT GRANT PERMISSION WINDOWS#
XP CMDSHELL procedure to enable SQL to see external drives Just as others have done after researching the web, I have managed to do the following:
#INKLET CANNOT GRANT PERMISSION SOFTWARE#
A custom software tool on each terminal points to the local database and upload target database. The overall objective that I am trying to accommplish is to have data from three local terminals each with custom SQL database to populate a SQL database (same structure) located on a mapped network drive. NB: Kindly, look at and advice me futher. I ran the SQL you gave to map a network dirve. Please make sure that the path you are trying to use is a shared path and that the SQL accoun that is running the backup has read and write access on that folder. The correct format there would be:ĮXEC XP_CMDSHELL 'net use H: \\servername\sharename /user:domain\username password' GREAT tip, this is a huge help if you only have SQL Mgmt Studio access to your server, and can't reach it via RDP or SMB.Īs Len mentioned upthread, with a default SQL server setup you will probably also have to pass domain credentials through with that net use command, for authenticating to your desired share. After trying different things I found, that the command is case sensitive on this server so it works with EXEC xp_cmdshell instead of EXEC XP_CMDSHELL. I was able to do the enable procedure without errors but can´t use the exec xp_cmdshell command. And I would note that good to have the same user on SQL and on you network storage machine Now define that share drive for SQL with the xp_cmdshell command as follows:ĮXEC XP_CMDSHELL 'net use H: \\RemoteServerName\ShareName'. mainly have to give credentials(User name and PWD) in XP_cmdshell.
#INKLET CANNOT GRANT PERMISSION PASSWORD#
When i run the last command where you set the network path it asks me to put the password in for the user for my share Error message is: The directory name is invalid.ĮXEC XP_CMDSHELL 'net use Z: \\.net\azureshareddata\shareddata\STATUSPOINT\DEV\DailyDBSync/USER.\metroshareddata password'Ībove is my command and i dont know where i make mistake
If all is OK with that please make sure that the SQL Server service account has access on that shared folder.Īn error occurred while executing batch.
#INKLET CANNOT GRANT PERMISSION WINDOWS#
Please make sure that don't face any issue while mapping the drive from the windows side. This is great! Thank you - I wanted to add something though, if you're share has a space in it, you will need to encapsulate the path in double-quotes like so:ĮXEC XP_CMDSHELL 'net use Z: "\\RemoteServer\Shared Drive" MyPassword /User:Domain\LoginName' This is really helpful and resolve my needs. Its really useful !!! Keep posting and sharing good things !!! Wednesday, Febru5:20:13 AM - Vilhelm Yngvi Kristinsson This process has changed slightly, this method worked great then I updated my SQL Server and then the mapped drives dissapeared and I couldn't get them back no matter what I did to execute this again, you now need to include the username and password when setting it up!ĮXEC XP_CMDSHELL 'net use E: \\ipaddress\share'ĮXEC XP_CMDSHELL 'net use E: "\\ipaddress\share name\share name" /user:domain\username password /persistent:yes'Īlso note the use of double quotes around the share path, regardless if I had spaces in the name or not, I was getting path not found errors without them! Worked like a charm for my servers across AD OUs! Thank you for sharing! :)Įxcellent post. What's the lifecycle for these drives to stay alive? Thanks, it worked, but somehow, after 2 weeks it stopped working and I had to recreate the map drives.
How can i prevent the mapping from disapearing after a server or service restart? I tried this on several servers all have this problem. Its interesting but even with the /persistent:yes, it keeps losing the connection after the SQL service restarted. So whenever SQL Server restarts the drive gets remapped. One way you can do this is to create a startup stored procedure to map the drive. One thing you could do is create a SQL Agent Job to run each day to do the mapping, this should help with the issue. Not sure how long the mapped drives stay connected or what casues them to disconnect. Very useful command and very helpful in terms of using the network drive Thanks this is a very useful article and very well explained.Ĭreate and use Network Drive for your shared folder instead. xp_cmdshell is mapping a drive for a service account. Surely that first mapping (of a Z: drive) is totally unnecessary.
Tuesday, Septem11:13:22 AM - Derek Broughton
0 kommentar(er)
