none
SharePoint Timer Job + External DLL

    Question

  • Hi Everyone,

    I am currently stuck with the following problem, can anyone please assist:

    I have created a new SharePoint Timer Job, it deploys fine. But when i run the job via Central Admin the job failes with the error:

    Could not load file or assembly 'COPDataAccess, Version=1.0.0.0, Culture=neutral, PublicKeyToken=95726c1e97db343b' or one of its dependencies. The system cannot find the file specified.

    COPDataAccess is a dll output from one of the other projects in the solution.

    How can I fix this issue?

    Kind regards,
    JP

    Monday, July 02, 2012 9:35 AM

Answers

All replies

  • Hi

    You should add all referenced asseblies (exluding std ones) to GAC manually or in visual studio package designer


    LinkedIn Profile
    SharePoint Advanced Visibility Options project

    • Proposed as answer by HeToC Monday, July 02, 2012 10:00 AM
    • Marked as answer by JPRoelofse Monday, July 02, 2012 10:12 AM
    Monday, July 02, 2012 9:50 AM
  • Hi

    In your Visual Studio project: Click the Package Designer, then the Advanced button at the bottom, click Add and Add Existing Assembly. Specify the location of the COPDataAccess.dll file and click OK.


    Kind Regards Bjoern
    Blog

    Monday, July 02, 2012 9:59 AM
    Moderator
  • Hi,

    I added the DLL to the package now in the advanced settings.

    After I deploy, I can see that the dll is in the GAC

    I am still receiving the same error.

    Do you have any other ideas.

    Thank you

    Monday, July 02, 2012 10:01 AM
  • Have you restarted SharePoint Timer Service ?

    it is a windows service can be found on your SP web front ends via:

    Start -> Administrative Tools -> Services -> SharePoinr 2010 Timer


    LinkedIn Profile
    SharePoint Advanced Visibility Options project

    • Edited by HeToC Monday, July 02, 2012 10:05 AM
    • Marked as answer by JPRoelofse Monday, July 02, 2012 10:12 AM
    Monday, July 02, 2012 10:03 AM
  • Thank you, it worked.

    I didnt think i need to restart the SP timer service in windows to run this timer job, I thought it would be enough to just run it out of central admin. 

    Thank you

    Monday, July 02, 2012 10:12 AM
  • OMG, restarting the service really work.

    TKS.

    Wednesday, October 02, 2013 6:00 AM