Custom developed solution called Timer2013.wsp. This solution has been globally deployed and activated as site feature. This Timer Job is supposed to copy data (items) between 2 lists. Expected behavior is farm solution
Timer2013.wsp with its Timer Job as a feature will be successfully deployed on production farm and copy list items between lists. This solution worked fine on version 2010 after SharePoint ungraded to 2013 this solution fails.
Hello Ajeet
I got some logs today from the splog created yesterday as per your recommendation , thanks.
SPLogevent:
Area : SharePoint Foundation
Category : Logging Correlation Data
Level : Medium
EventID : xmnv
Message : Name=Timer Job ITimer Jobv2013
Area : Unknown
Category : ITimer Jobv2013
Level : Monitorable
EventID : 00000
Message : Writing to the ULS log: Workflow Error2 : {0}
Area : SharePoint Foundation
Category : Monitoring
Level : Medium
EventID : b4ly
Message : Leaving Monitored Scope (Timer Job ITimer Jobv2013). Execution Time=1.5792509941906
i created them but they are empty 0 k even after running the custom timer jobs , am i missing smth?
can you create a log file with Correlation IDÂ
get-splogevent | ?{$_.Correlation -eq “<Correlation ID>“} | select Area, Category, Level, EventID, Message | Format-List > C:\Awesome.log
In your case I suppose their are two Correlation IDÂ
0990ab9c-5068-a0bd-0c20-3ca606231efa
 0990ab9c-7069-a0bd-0c20-3e7eaf46cb98
Thanks you Maciej i have sent your recommendations to our devs.
From logs we can see that Timer Jobs is triggered twice  but no idea what might be the cause:
08/05/2014 17:40:00.51      OWSTIMER.EXE (0x6C50)       0x71C4  SharePoint Foundation  Logging Correlation Data   xmnv   Medium       Name=Timer Job ITimer Jobv2013      0990ab9c-5068-a0bd-0c20-3ca606231efa
08/05/2014 17:40:00.53      OWSTIMER.EXE (0x6C50)       0x5804  SharePoint Foundation  Logging Correlation Data   xmnv   Medium       Name=Timer Job ITimer Jobv2013      0990ab9c-7069-a0bd-0c20-3e7eaf46cb98
