Dellagnese,

In the majority of cases you can follow the steps in the knowledgebase Article ID: 21219 or search for  "Background Tasks window does not open or no background task is displayed."

Casey Knapp

Senior Customer Support Analyst, Sage Construction and Real Estate

Sage North America

What should be done to correct the error when deleting the registry key per article #21219 does not work?

What should be done to correct the error when deleting the registry key per article #21219 does not work?

Hi Amanda,

In most cases, the above article does resolve the issue, however we've seen some situations where we have to take it a step further to trigger a response. I urge you to rename it one more time to see if that does the trick.

You can rename the entire Timberline key (one level above Background Tasks) as a further way to test. Sage 300 will re-create this renamed key the next time you launch into Sage Desktop or TS - Main. Be aware that these keys control things unique to your workstation - things such as column widths, and custom buttons to name a few which is why we always suggest renaming instead of deleting keys.

I cannot find the article #21219 as mentioned in this thread and I am having the same problem.

Teresa-

You would have to log into the customer portal and search in the knowledgebase for article 21219:

• Go to support.na.sage.com then click on [Login] on the right hand side.

• Log in with your registered customer portal (this login will be linked to your customer account information to verify your active support plan)

• Once logged in, select your "Sage 300 CRE" product on the left hand pane.

I am also having this problem. I have tried to suggested answer to rename the folders and it has not fixed the problem. I exited completely out of Timberline before renaming the folder. On the article it said there are some instances where this does not fix the background tasks. What is done in that case? Am I to now call Timberline and have them access my computer remotely?

Hi -

If following article 21219 does not resolve the issue, please call into support to have one of our analysts help you with the issue.