On 01/02/2014 03:58 PM, Dan Stover wrote:
Thank you, Moritz, for your response. Sorry for the delayed response on my part.
More information:
This problem cropped up (perhaps coincidentally) when I was trying to move a work flow process from beta to live. Some of this had to be manual and some export/import. There was also some customized code that is used in certain situations. When this problem occurred, I tried to solve it and was unsuccessful. I then went back to a previous backup of OTRS and the problem was still there. I then restored from a week before I did anything (when it was working fine) and the problem was still there.
Did you delete all caches during the restore? OTRS is very eager to use the caches for performance reasons, and invalidates the caches whenever you change anything in the database through the OTRS code. When you change the database directly, you have to also invalidate the caches yourself. Also as Renee said, please look into your web server's error log (plus into the OTRS logs, if it logs into another location. Cheers, Moritz