DotNetNuke scheduler doesn't run import job
Last Post 10-07-2009 09:49 AM by Robb Bryn. 4 Replies.
AddThis - Bookmarking and Sharing Button
Author Messages
Robb BrynUser is Offline
going with the flow
going with the flow
Posts:74
Avatar

--
10-07-2009 05:28 AM

    I created an import definition and scheduled it manually by adding a scheduled item with fullclassname=DataSprings.DNN.Modules.UserImport.UserImportProcess,DataSprings.DNN.Modules.UserImport and object dependency=DataSprings_UserImport.

    I set the time lapse to 5 minutes, the retry frequency to 1 minute, retain schedule history to 25, no event to run on, catch up enabled, and selected my web server to run on.  The schedule is enabled. 

    I see the Next Start time in the schedule window updating as time goes by, but I get no history for the job, and it doesn't show in the View Schedule Status window (other jobs scheduled do show up, and have history for them).  Is there something else I am missing?

    Thanks

    Robb

     

    David ToUser is Offline
    river guide
    river guide
    Posts:2719
    Avatar

    --
    10-07-2009 07:36 AM
    HI, so under the Host / Schedule you see the userimport schedule but if you click on "History", it doesn't show anything? If you go to Admin / Event Viewer, do you see any errors? -- David
    Robb BrynUser is Offline
    going with the flow
    going with the flow
    Posts:74
    Avatar

    --
    10-07-2009 08:22 AM
    we figured it out. When we went to create the job it asked us which server we wanted it added to... we put it on the wrong server (the website was moved from serverA to serverB and apaprently still had references to ServerA somewhere)
    David ToUser is Offline
    river guide
    river guide
    Posts:2719
    Avatar

    --
    10-07-2009 08:47 AM
    Cool, thanks for figuring it out for me. -- David
    Robb BrynUser is Offline
    going with the flow
    going with the flow
    Posts:74
    Avatar

    --
    10-07-2009 09:49 AM
    Thanks for the quick response. As it turns out, the wrong web server was selected for the scheduled job to run on (there were several listed). Simple problem, simple fix, symptoms didn't point in that direction initially.


    ---
  • film izle
  • 720 izle
  • film
  • sinema izle
  • film makinesi
  • T�rk�e dublaj film
  • film izle
  • film izle
  • baglan film izle
  • sinema izle
  • 1080 film izle
  • film mercegi