I ran into an error today that for the life of me, have no idea how it appeared or how to fix it. If someone has ran into this problem and has fixed it, PLEASE enlighten me.
ERROR: "Column 'SecondsAfterLastPing' does not belong to table Table"
[ArgumentException: Column 'SecondsAfterLastPing' does not belong to table Table.]
System.Data.DataRow.get_Item(String columnName) +3108760
EPiServer.DataAbstraction.ScheduledJob.Create(DataRow row) +1649
EPiServer.DataAbstraction.ScheduledJob.Load(String method, String typeName, String assemblyName) +76
EPiServer.UI.Admin.DatabaseJob.OnLoad(EventArgs e) +459
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3064
This happens on every single scheduled job. As soon as I click on the link to view a scheduled job, this error displays.
I've seened to stumble across the problem. The stored procedure for netschedulerlist was wrong.
SELECT CONVERT(NVARCHAR(40),pkID) AS pkID,Name,CONVERT(INT,Enabled) AS Enabled,LastExec,LastStatus,LastText,NextExec,[DatePart],Interval,MethodName,CONVERT(INT,fStatic) AS fStatic,TypeName,AssemblyName,InstanceData, IsRunning, CurrentStatusMessage
ORDER BY Name ASC
I had to change it to this.
Select CONVERT(NVARCHAR(40), pkID) AS pkID, Name, CONVERT(INT,Enabled) AS Enabled, LastExec, LastStatus, LastText, NextExec,[DatePart], Interval, MethodName, CONVERT(INT,fStatic) AS fStatic, TypeName, AssemblyName, InstanceData, IsRunning, CurrentStatusMessage, DateDiff(second,LastPing,GetDate()) as SecondsAfterLastPing
ORDER BY Name ASC
In case anyone else runs across the problem
I think this has to do with having the hotfix pack of EPiServer 6 R2 installed on the machine, but the database isn't upgraded. Could that be the case here as well?
Hi I got this error, running the SchemaUpdate.sql solved the problem.
We are already aware of this issue and are looking into it. Seems like upgrade scripts for R2 doesnt have the latest changes for schema update as mentioned in my blog post. Temporary workaround is to run the Schema Update script manually for now.
I got this problem too. I can confirm the script fixed it. Thanks Shahid Nawaz :)
Thanks for this post Joshua, this saved me a lot of troubleshooting on my current project. Guess that's another blemish on the CMS 6 R2 hotfix then.
Any fixes for this on the way? It is pretty fast to fix but would be nice with a hotfix :)
I think this was in the latest hotfix Simen. I could be wrong but I am pretty sure it was put in there.
Ok, thats good news :)
yes, it has been fixed in latest drop. http://world.episerver.com/Articles/Items/About-the-Latest-Updates-for-EPiServer-CMS-and-Relate/
© Episerver 2017 |
About Episerver World