Post reply

Event log error

  • December 22, 2014 at 6:59 am

    #293248

    I have scripts that send error log reports to me every day for all of our production VMs. I keep seeing this message in several of our sql 2012 installations, should I be concerned? Is there something I can do to remedy this? I can't imagine that the CopyDatabaseWizard is being invoked, either. Error message follows:

    Activation context generation failed for "c:\program files (x86)\microsoft sql server\120\Tools\Binn\managementstudio\CopyDatabaseWizard.exe".Error in manifest or policy file "c:\program files (x86)\microsoft sql server\120\Tools\Binn\managementstudio\CopyDatabaseWizard.exe" on line 8. The value "1.0" of attribute "version" in element "assemblyIdentity" is invalid.

  • January 5, 2015 at 9:47 am

    #1767815

    I have the same error. I suspect it has something to do with my nightly full database backups.

  • January 5, 2015 at 4:38 pm

    #1767908

    Have you checked that you don't have any maint plans or SSIS pkgs that may be calling it?

    Watch my free SQL Server Tutorials at:
    http://MidnightDBA.com
    Blog Author of:
    DBA Rant – http://www.MidnightDBA.com/DBARant

    Minion Maintenance is FREE:

  • January 5, 2015 at 4:45 pm

    #1767912

    Correct, that has been ruled out.

  • January 5, 2015 at 4:48 pm

    #1767914

    Well then, if there are no other problems with SQL and you can't find anything online about it then I'd say you can ignore it until it becomes an issue.

    How many times a day does it happen?

    Watch my free SQL Server Tutorials at:
    http://MidnightDBA.com
    Blog Author of:
    DBA Rant – http://www.MidnightDBA.com/DBARant

    Minion Maintenance is FREE:

  • January 5, 2015 at 5:12 pm

    #1767924

    I've only seen it once a day, but on multiple VMs.

    This was happening with sql 2012 SP1 and then after I upgraded to SP2 + CU3.

    Nothing is breaking, but then again I don't ever use the copy database wizard 🙂

  • January 6, 2015 at 8:04 am

    #1768102

    Pretty much the same story with me except we use SQL Server 2014

  • January 6, 2015 at 8:06 am

    #1768104

    Y unsolved mysteries like that can be annoying, but pick your battles. If it's not causing any problems then let it go.

    Watch my free SQL Server Tutorials at:
    http://MidnightDBA.com
    Blog Author of:
    DBA Rant – http://www.MidnightDBA.com/DBARant

    Minion Maintenance is FREE:

  • January 6, 2015 at 7:58 pm

    #1768316

    I suspect that only Microsoft can answer this mystery.

  • July 29, 2015 at 4:54 am

    #1815658

    I found the short way:

    1. make a backup copy of "copydatabasewizard.exe";

    2. edit "copydatabasewizard.exe" with an Hex editor;

    3. search for "assemblyIdentity";

    4. change "version" value (right of "=" char) from "1.0" to "1.0.0.0"

    5. save change

    And voila ! "copydatabasewizard.exe" works again !

    Don't know why MS has an incorrect manifest embedded in that file, FYI version number must have 4 digits, not 2.

    Ciao.

    Paolo.

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

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