Post reply

DB Log File Location Error

  • October 23, 2019 at 9:10 am

    #3691250

    na_ma_cool wrote:

    Yes @mvdba, I tried both accounts that is logged with sql sa account and logged with windows authentication mode but that didn't worked.

    I think you misunderstood me

    if you go to services.msc and look at the log on account for these 3 items - what accounts are they running as (feel free to mask bit of it , and please don't paste passwords)

    sqlserver

    sqlserver agent

    sqlserver integration services

    MVDBA

  • October 24, 2019 at 5:25 am

    #3691514

    Thanks @steve-2 T. Yup i tried with UNC path but the error changed to "The user name or password is incorrect". Keeping in mind that the .bak file is generating fine in this scenario too. I am attaching 3 screenshots as follows.

    1. First Screenshot shows where and how set the unc path for .TXT file
    2. Second Screenshot shows where and how i set the unc path for backup job i.e the .BAK files
    3. Thirst Screenshot shows the job history viewer.

    By the way my UNC path is \\10.3.6.162\i\BK

    While i am fully accessing the above path and in that above server direcoty I, i added user "Everyone" for full sharing rights.

    • This reply was modified 5 years, 1 month ago by  na_ma_cool.

    Attachments:
    You must be logged in to view attached files.

  • October 24, 2019 at 6:24 pm

    #3691728

    @na_ma_cool, make sure you check the folder/file security also and that the sqlagent service account has access to read/write to that share and folder.  Share security and folder/file security is two different things.

    Have you tried the CMD shell option to verify the security? Open the cmd prompt as the SQLAgent account, and try this:

    copy con \\10.3.6.162\i\BK\test.txt

    (type some text)

    Press Ctrl+Z.

    This will create a text file in the network location and help you verify read/write access.

    Now, your screenshot showed "user name or password is incorrect".  In the above scenario, you generally would get an "access denied" if you don't have access.  Are you using a proxy and you may have type in an incorrect password? I tested this by creating a credential account with an incorrect password.  The system does not verify that the password works or not. I then added that credential to the sqlagent proxy.

    I then created a simple agent job where the the step use the sqlagent proxy.  When I run it, it gives my the erorr that you got: The user name or password is incorrect.

    So maybe check your credential account assuming you're using a proxy on that step?

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply