Night Utilities in TAM 11.1

[Pastie]

Hi,

Has anyone else experienced intermittent issues with Night Utilities in TAM 11.1? We have been using 11.1 for about 2 months and since the upgrade we have had issues with the utility not finishing overnight, resulting in a Global Lock being left in place. This means our early risers cant get into TAM until I arrive.

Once I get into the office and clear the lock, we are often left with Attachments or Invoices being un-viewable until we manually run DBMAINT which takes around 45 minutes for a site our size. With this happening once a week its resulting in a large amount of down time for us.

There are no server side errors, and the NIGHTLOG just shows Night Utilities starting and then nothing else.

We are using the same server, same procedure etc that we have for years - the only different factor is TAM 11.1 so I am starting to think it may be related.

Anyone had similar issues?

[Andrew Carrick]

Man I hate that, I occasionally get calls at 7am if there's a global lock. We're not on v 11 so it's not frequent thankfully. Is there nothing showing on the PC that runs the Utilities, like an unfinished process? What does Task Manager show if anything? And when you say unviewable, do users get an error or do documents just not open?

[Jim Jensen]

We're on 11.1 and use night utilities every night and I've not had any problems. Doesn't really help you figure out what's wrong, but at its possible to run it without the problems.

[Mark]

I'm also having no problems with NU.  Only been on 11.15 for a few weeks though, and my NU is automated and has been for a very long time (5+ years?)

[Jan Regnier]

Ditto here - no issues with Night Util - with 11.1

[Alice Mooney]

Take a look at the Event Viewer on the NU computer.  Look at both the Application and System logs to see if something is failing or just hiccuping enough to cause this. If there is anything with a red "X" and you're not sure what it means, post it here in case someone can decipher it for you.

[Mark]

Also, it's possible this is just an open files issue...