SS2012 Export Wizard Access is denied












3















When a user exports to a flat file she gets an access denied error. The wizard allows her to preview the data so she has access on the db side. From Windows she can create a new file in the target destination so she seems to have network permissions. She is logged into her computer with a network username and into SS2012 with a SS login. Everyone else can run the export wizard to this location successfully. I am stumped!










share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Why is she using a local SQL Server login? A SQL Server login cannot authenticate to a network resource without a proxy as far as I know and can remember if you have the folder security ACL settings correctly configured at least. Perhaps there is an elaborate workaround but try having the user use their domain username and grant it the DB permissions and then that may solve the problem. The issue is likely the SQL Server login ID does not MODIFY permission to the folder it's exporting to but if the domain username does, then using that to authenticate to SQL and exporting with it should too.

    – Pimp Juice IT
    Feb 16 '17 at 21:34













  • Walmart, All our users logon to their computers with Domain logins and into SS with SS logins. This is a legacy issue. Remember, all the other users can export successfully.

    – Andy
    Feb 16 '17 at 21:59











  • It's hard to say without being there and looking over your setup. I've never had any luck getting local SQL Server logins to authenticate to network resources without using a proxy and using the RUN AS from a SQL Agent job or EXECUTE AS LOGIN or whatever it is using straight T-SQL. I could probably figure this out without a lot of time if I were there since I've spent hours and hours on such issues in the past and know all the gotchas.... I'd see for yourself how it works from a different account from the beginning until the end and then compare with the one it doesn't work for to start.

    – Pimp Juice IT
    Feb 16 '17 at 22:15











  • Walmart, I have run the wizard start to finish successfully on several other computers and accounts. The wizard actually lets you choose a combination of local and network credentials for both the data source and destination. Kind of cool how you can use 2 different sets of logins in a single application.

    – Andy
    Feb 16 '17 at 22:28











  • Does everyone use the same SS login? If not, or does the export work if someone else uses her SS login on their system, and if she uses someone else's SS login on hers?

    – T.H.
    Feb 17 '17 at 10:17


















3















When a user exports to a flat file she gets an access denied error. The wizard allows her to preview the data so she has access on the db side. From Windows she can create a new file in the target destination so she seems to have network permissions. She is logged into her computer with a network username and into SS2012 with a SS login. Everyone else can run the export wizard to this location successfully. I am stumped!










share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Why is she using a local SQL Server login? A SQL Server login cannot authenticate to a network resource without a proxy as far as I know and can remember if you have the folder security ACL settings correctly configured at least. Perhaps there is an elaborate workaround but try having the user use their domain username and grant it the DB permissions and then that may solve the problem. The issue is likely the SQL Server login ID does not MODIFY permission to the folder it's exporting to but if the domain username does, then using that to authenticate to SQL and exporting with it should too.

    – Pimp Juice IT
    Feb 16 '17 at 21:34













  • Walmart, All our users logon to their computers with Domain logins and into SS with SS logins. This is a legacy issue. Remember, all the other users can export successfully.

    – Andy
    Feb 16 '17 at 21:59











  • It's hard to say without being there and looking over your setup. I've never had any luck getting local SQL Server logins to authenticate to network resources without using a proxy and using the RUN AS from a SQL Agent job or EXECUTE AS LOGIN or whatever it is using straight T-SQL. I could probably figure this out without a lot of time if I were there since I've spent hours and hours on such issues in the past and know all the gotchas.... I'd see for yourself how it works from a different account from the beginning until the end and then compare with the one it doesn't work for to start.

    – Pimp Juice IT
    Feb 16 '17 at 22:15











  • Walmart, I have run the wizard start to finish successfully on several other computers and accounts. The wizard actually lets you choose a combination of local and network credentials for both the data source and destination. Kind of cool how you can use 2 different sets of logins in a single application.

    – Andy
    Feb 16 '17 at 22:28











  • Does everyone use the same SS login? If not, or does the export work if someone else uses her SS login on their system, and if she uses someone else's SS login on hers?

    – T.H.
    Feb 17 '17 at 10:17
















3












3








3








When a user exports to a flat file she gets an access denied error. The wizard allows her to preview the data so she has access on the db side. From Windows she can create a new file in the target destination so she seems to have network permissions. She is logged into her computer with a network username and into SS2012 with a SS login. Everyone else can run the export wizard to this location successfully. I am stumped!










share|improve this question
















When a user exports to a flat file she gets an access denied error. The wizard allows her to preview the data so she has access on the db side. From Windows she can create a new file in the target destination so she seems to have network permissions. She is logged into her computer with a network username and into SS2012 with a SS login. Everyone else can run the export wizard to this location successfully. I am stumped!







sql-server sql-server-2012 import






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 17 '17 at 4:42









Max Vernon

50.7k13112223




50.7k13112223










asked Feb 16 '17 at 20:36









AndyAndy

567




567





bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Why is she using a local SQL Server login? A SQL Server login cannot authenticate to a network resource without a proxy as far as I know and can remember if you have the folder security ACL settings correctly configured at least. Perhaps there is an elaborate workaround but try having the user use their domain username and grant it the DB permissions and then that may solve the problem. The issue is likely the SQL Server login ID does not MODIFY permission to the folder it's exporting to but if the domain username does, then using that to authenticate to SQL and exporting with it should too.

    – Pimp Juice IT
    Feb 16 '17 at 21:34













  • Walmart, All our users logon to their computers with Domain logins and into SS with SS logins. This is a legacy issue. Remember, all the other users can export successfully.

    – Andy
    Feb 16 '17 at 21:59











  • It's hard to say without being there and looking over your setup. I've never had any luck getting local SQL Server logins to authenticate to network resources without using a proxy and using the RUN AS from a SQL Agent job or EXECUTE AS LOGIN or whatever it is using straight T-SQL. I could probably figure this out without a lot of time if I were there since I've spent hours and hours on such issues in the past and know all the gotchas.... I'd see for yourself how it works from a different account from the beginning until the end and then compare with the one it doesn't work for to start.

    – Pimp Juice IT
    Feb 16 '17 at 22:15











  • Walmart, I have run the wizard start to finish successfully on several other computers and accounts. The wizard actually lets you choose a combination of local and network credentials for both the data source and destination. Kind of cool how you can use 2 different sets of logins in a single application.

    – Andy
    Feb 16 '17 at 22:28











  • Does everyone use the same SS login? If not, or does the export work if someone else uses her SS login on their system, and if she uses someone else's SS login on hers?

    – T.H.
    Feb 17 '17 at 10:17





















  • Why is she using a local SQL Server login? A SQL Server login cannot authenticate to a network resource without a proxy as far as I know and can remember if you have the folder security ACL settings correctly configured at least. Perhaps there is an elaborate workaround but try having the user use their domain username and grant it the DB permissions and then that may solve the problem. The issue is likely the SQL Server login ID does not MODIFY permission to the folder it's exporting to but if the domain username does, then using that to authenticate to SQL and exporting with it should too.

    – Pimp Juice IT
    Feb 16 '17 at 21:34













  • Walmart, All our users logon to their computers with Domain logins and into SS with SS logins. This is a legacy issue. Remember, all the other users can export successfully.

    – Andy
    Feb 16 '17 at 21:59











  • It's hard to say without being there and looking over your setup. I've never had any luck getting local SQL Server logins to authenticate to network resources without using a proxy and using the RUN AS from a SQL Agent job or EXECUTE AS LOGIN or whatever it is using straight T-SQL. I could probably figure this out without a lot of time if I were there since I've spent hours and hours on such issues in the past and know all the gotchas.... I'd see for yourself how it works from a different account from the beginning until the end and then compare with the one it doesn't work for to start.

    – Pimp Juice IT
    Feb 16 '17 at 22:15











  • Walmart, I have run the wizard start to finish successfully on several other computers and accounts. The wizard actually lets you choose a combination of local and network credentials for both the data source and destination. Kind of cool how you can use 2 different sets of logins in a single application.

    – Andy
    Feb 16 '17 at 22:28











  • Does everyone use the same SS login? If not, or does the export work if someone else uses her SS login on their system, and if she uses someone else's SS login on hers?

    – T.H.
    Feb 17 '17 at 10:17



















Why is she using a local SQL Server login? A SQL Server login cannot authenticate to a network resource without a proxy as far as I know and can remember if you have the folder security ACL settings correctly configured at least. Perhaps there is an elaborate workaround but try having the user use their domain username and grant it the DB permissions and then that may solve the problem. The issue is likely the SQL Server login ID does not MODIFY permission to the folder it's exporting to but if the domain username does, then using that to authenticate to SQL and exporting with it should too.

– Pimp Juice IT
Feb 16 '17 at 21:34







Why is she using a local SQL Server login? A SQL Server login cannot authenticate to a network resource without a proxy as far as I know and can remember if you have the folder security ACL settings correctly configured at least. Perhaps there is an elaborate workaround but try having the user use their domain username and grant it the DB permissions and then that may solve the problem. The issue is likely the SQL Server login ID does not MODIFY permission to the folder it's exporting to but if the domain username does, then using that to authenticate to SQL and exporting with it should too.

– Pimp Juice IT
Feb 16 '17 at 21:34















Walmart, All our users logon to their computers with Domain logins and into SS with SS logins. This is a legacy issue. Remember, all the other users can export successfully.

– Andy
Feb 16 '17 at 21:59





Walmart, All our users logon to their computers with Domain logins and into SS with SS logins. This is a legacy issue. Remember, all the other users can export successfully.

– Andy
Feb 16 '17 at 21:59













It's hard to say without being there and looking over your setup. I've never had any luck getting local SQL Server logins to authenticate to network resources without using a proxy and using the RUN AS from a SQL Agent job or EXECUTE AS LOGIN or whatever it is using straight T-SQL. I could probably figure this out without a lot of time if I were there since I've spent hours and hours on such issues in the past and know all the gotchas.... I'd see for yourself how it works from a different account from the beginning until the end and then compare with the one it doesn't work for to start.

– Pimp Juice IT
Feb 16 '17 at 22:15





It's hard to say without being there and looking over your setup. I've never had any luck getting local SQL Server logins to authenticate to network resources without using a proxy and using the RUN AS from a SQL Agent job or EXECUTE AS LOGIN or whatever it is using straight T-SQL. I could probably figure this out without a lot of time if I were there since I've spent hours and hours on such issues in the past and know all the gotchas.... I'd see for yourself how it works from a different account from the beginning until the end and then compare with the one it doesn't work for to start.

– Pimp Juice IT
Feb 16 '17 at 22:15













Walmart, I have run the wizard start to finish successfully on several other computers and accounts. The wizard actually lets you choose a combination of local and network credentials for both the data source and destination. Kind of cool how you can use 2 different sets of logins in a single application.

– Andy
Feb 16 '17 at 22:28





Walmart, I have run the wizard start to finish successfully on several other computers and accounts. The wizard actually lets you choose a combination of local and network credentials for both the data source and destination. Kind of cool how you can use 2 different sets of logins in a single application.

– Andy
Feb 16 '17 at 22:28













Does everyone use the same SS login? If not, or does the export work if someone else uses her SS login on their system, and if she uses someone else's SS login on hers?

– T.H.
Feb 17 '17 at 10:17







Does everyone use the same SS login? If not, or does the export work if someone else uses her SS login on their system, and if she uses someone else's SS login on hers?

– T.H.
Feb 17 '17 at 10:17












1 Answer
1






active

oldest

votes


















0














T.H. Everyone has a their own logins. I love your idea to try someone elses SS login from her machine. Unfortunately the export was successful from her machine with my SS login and also a success from my machine with her SS login. I say unfortunately because it now works from her machine with her own SS login. The issue has resolved itself but I don't know why! :-(






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "182"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2fdba.stackexchange.com%2fquestions%2f164592%2fss2012-export-wizard-access-is-denied%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









    0














    T.H. Everyone has a their own logins. I love your idea to try someone elses SS login from her machine. Unfortunately the export was successful from her machine with my SS login and also a success from my machine with her SS login. I say unfortunately because it now works from her machine with her own SS login. The issue has resolved itself but I don't know why! :-(






    share|improve this answer




























      0














      T.H. Everyone has a their own logins. I love your idea to try someone elses SS login from her machine. Unfortunately the export was successful from her machine with my SS login and also a success from my machine with her SS login. I say unfortunately because it now works from her machine with her own SS login. The issue has resolved itself but I don't know why! :-(






      share|improve this answer


























        0












        0








        0







        T.H. Everyone has a their own logins. I love your idea to try someone elses SS login from her machine. Unfortunately the export was successful from her machine with my SS login and also a success from my machine with her SS login. I say unfortunately because it now works from her machine with her own SS login. The issue has resolved itself but I don't know why! :-(






        share|improve this answer













        T.H. Everyone has a their own logins. I love your idea to try someone elses SS login from her machine. Unfortunately the export was successful from her machine with my SS login and also a success from my machine with her SS login. I say unfortunately because it now works from her machine with her own SS login. The issue has resolved itself but I don't know why! :-(







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 21 '17 at 20:04









        AndyAndy

        567




        567






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Database Administrators Stack Exchange!


            • 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%2fdba.stackexchange.com%2fquestions%2f164592%2fss2012-export-wizard-access-is-denied%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







            Popular posts from this blog

            SQL Server 17 - Attemping to backup to remote NAS but Access is denied

            Always On Availability groups resolving state after failover - Remote harden of transaction...

            Restoring from pg_dump with foreign key constraints