Thanks but if I rolled back our db to an ealier version where IO_GEN table was fine, I would lose all our user's updates of the last week.
I could create a tmp DB from our backup. But could I then copy/paste the rows from IO_GEN out of my temp DB into my production DB without causing further harm? Talked to my DBA and his recommendation was 'no'. In RedDot before 10, I could just restart dllhost.exe and the pub queue would pop right back up, if stalled out or killed off. In 10, this is now called the Process Server. I've restarted that service several times with no luck. Hmmm.... This seems like it should be simple...there must be some way to restart the pub queue from within RedDot or from within the DB, right? Thanks for any ideas guys!! Kelly On Mar 24, 5:54 pm, Tony Gayter <[email protected]> wrote: > My first port of call would be to roll the databases back (assuming you > backed them up before playing with the data) and reboot all three rd > servers and see if the jobs are still stuck. If they are then cancel them > in the job queue from the server manager. I am assuming youtried this > before messing with the DB but thought I would throw in what I would do. I > expect one of the clustered servers still thinks there are jobs in the > queue. > On Mar 24, 2012 10:43 PM, "Kelly" <[email protected]> wrote: > > > > > Hi all - Can anyone help us out with this? > > > Last week, we had trouble with jobs contantly being 'stuck' in the > > Publishing Queue so we deleted all rows from IO_GEN. > > > This cleared our stuck jobs just fine - but now any workflow that uses > > "Start Publication" refuses to publish. Unfortunately, we have about > > 200 individual workflows that use 'Start Publication' :^( > > > Can publish pages manually and can run server jobs to publish whole > > site - but anything that used Publishing Queue ( i.e. - worfkflow ) > > will not run. > > > RD Support says they are not sure there is a way to restart the > > publishing queue and I am on the hook to get this working this weeend > > before users get back to their desks on Monday morning. Rebooting > > hasn't worked nor has creating a new workflow. > > > We run RedDot 10.1 SP2 with SQL database in a clustered environment (1 > > RedDot publishing server, 3 RedDot editing servers). > > > Any ideas gratefully appreciated!! > > > Thanks! > > Kelly > > > -- > > You received this message because you are subscribed to the Google Groups > > "RedDot CMS Users" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/reddot-cms-users?hl=en.- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
