Post reply

log shipping

  • September 22, 2017 at 4:26 am

    #328684

    Hi

    We are moving our databases to a new server. The old server, which is still live has sql 2012 STANDARD edition. We are setting up log shipping to our new SQL2102 ENTERPRISE edition so we can minimise downtime by having to t only restore  the last transaction log when we decide to switch over.
    Anyways, I am getting an error when i try and do the initial log shipping setup : "A file activation error occurred. The physical file name D:DATA\databanseName_dat.mdf" may be incorrect. Diagnose and correct additional errors and retry operation"

    The SQL SERVICE has full permissions on the data folder, as does the SQL Agent (not sure that is actually needed but i added it anyway)

    Is this because we are log shipping from standard to Enterprise ? Both editions are 2012

  • September 22, 2017 at 5:09 am

    #1960456

    What other errors, do you have or what else is logged in the error log at the same time?

    Do you have filestream enabled on the database?

  • September 22, 2017 at 5:16 am

    #1960459

    PearlJammer1 - Friday, September 22, 2017 4:26 AM

    Hi

    We are moving our databases to a new server. The old server, which is still live has sql 2012 STANDARD edition. We are setting up log shipping to our new SQL2102 ENTERPRISE edition so we can minimise downtime by having to t only restore  the last transaction log when we decide to switch over.
    Anyways, I am getting an error when i try and do the initial log shipping setup : "A file activation error occurred. The physical file name D:DATA\databanseName_dat.mdf" may be incorrect. Diagnose and correct additional errors and retry operation"

    The SQL SERVICE has full permissions on the data folder, as does the SQL Agent (not sure that is actually needed but i added it anyway)

    Is this because we are log shipping from standard to Enterprise ? Both editions are 2012

    Yes; Successful log shipment process is possible when both the versions are same (i.e. Standard to Standard)

  • September 22, 2017 at 5:41 am

    #1960463

    anthony.green - Friday, September 22, 2017 5:09 AM

    What other errors, do you have or what else is logged in the error log at the same time?

    Do you have filestream enabled on the database?

    Hi, Thanks for your reply.
    There are no other errors in the error log except the one I quoted. There is one error referencing the.mdf file and another error of the same nature referencing the .ldf file.
    FileStream is not enabled.

  • September 22, 2017 at 5:43 am

    #1960464

    adilahmed1989 - Friday, September 22, 2017 5:16 AM

    PearlJammer1 - Friday, September 22, 2017 4:26 AM

    Hi

    We are moving our databases to a new server. The old server, which is still live has sql 2012 STANDARD edition. We are setting up log shipping to our new SQL2102 ENTERPRISE edition so we can minimise downtime by having to t only restore  the last transaction log when we decide to switch over.
    Anyways, I am getting an error when i try and do the initial log shipping setup : "A file activation error occurred. The physical file name D:DATA\databanseName_dat.mdf" may be incorrect. Diagnose and correct additional errors and retry operation"

    The SQL SERVICE has full permissions on the data folder, as does the SQL Agent (not sure that is actually needed but i added it anyway)

    Is this because we are log shipping from standard to Enterprise ? Both editions are 2012

    Yes; Successful log shipment process is possible when both the versions are same (i.e. Standard to Standard)

    Hi 
    I know log shipping works from the same version/edition i.e. sql2012 standard to sql2012 standard. My question is will it work from sql2012 standard to sql2012 Enterprise ?

  • September 22, 2017 at 5:45 am

    #1960465

    PearlJammer1 - Friday, September 22, 2017 5:43 AM

     My question is will it work from sql2012 standard to sql2012 Enterprise ?

    Yes

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • September 22, 2017 at 6:00 am

    #1960467

    Your error message got mangled with a smilie. Can you either paste the whole thing again, or post a screenshot? Preferably both.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • September 22, 2017 at 6:45 am

    #1960477

    GilaMonster - Friday, September 22, 2017 6:00 AM

    Your error message got mangled with a smilie. Can you either paste the whole thing again, or post a screenshot? Preferably both.

    Hi Gail
    Here is the error again - pretty much the same as i posted minus the smiley..

  • September 22, 2017 at 6:56 am

    #1960480

    D:Logs is not a valid path. It should be D:\Logs. Check your setup and paths.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • September 22, 2017 at 7:06 am

    #1960484

    GilaMonster - Friday, September 22, 2017 6:56 AM

    D:Logs is not a valid path. It should be D:\Logs. Check your setup and paths.

    OMG!!!
    School boy error. This has fixed it Gail. Thank you. I'm afraid I got so wrapped up in permissions to the SQLSVC and SQL AGENT and versions I have totally failed to check that!!

    It is now working like a charm - thank you!!

Viewing 10 posts - 1 through 9 (of 9 total)

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