Jarl,
Thanks for the trick. It came back with the BusinessTimeWorkdays being
the problem on the 2 servers. It looks like the time field changed in
that form between versions.
Now we can make the appropriate changes!
Now I am going to read that Configuration Guide 7.5 right away cover to
I am reposting this since I did not get any replies and we are running out
of options.
I am still hoping that someone has an idea or a suggestion on what we can
try. We have this issue escalated with BMC and been looking for a
reason/solution/fix for 2 weeks now.
What does the api/sql logging say?
--
J
2010/9/22 pascale.bo...@daimler.com:
**
I am reposting this since I did not get any replies and we are running out
of options.
I am still hoping that someone has an idea or a suggestion on what we can
try. We have this issue escalated with BMC and
If you turn on the SQL logs and restart the server do you see any errors?
Fred
-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of pascale.bo...@daimler.com
Sent: Wednesday, September 22, 2010 2:40 PM
To: arslist@ARSLIST.ORG
There was a few filters that were firing. We verified all of them,
couldn't find anything wrong with them, so we did a backup and deleted
them. Still have the error showing up at startup.
Thank you,
Pascale Boyer
Remedy Technical Lead Developer
Daimler Trucks North America LLC
Montgomery
Just a thought. Have you tried removing lines from the ARMonitor.cfg
file to see if you can start it without error when a particular line is
removed lines. That may help to narrow down what is causing the
problem. If the error stops.
Todd Arner
Great Lakes
Since you got this error when the server starts, the api/sql turned on when
starting the server may give you some help.
Another trick can be to add the -checkdb option when starting the arserver
from command line.
(Page 372 in Configuration Guide)
--
Jarl
2010/9/22 pascale.bo...@daimler.com
390600 is the Admin thread. That makes me think it is something happening
during the loading of objects into the server's memory cache. With the SQL
logging on and restarting the server you should be able to cross-reference the
time of the error in the arerror.log file with what is being
Don't forget to turn on startup logging (there's a KB on it), by setting the
-t flag in the armonitor.cfg file. That will let you get more information
as well.
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Jarl Grøneng
Sent: Wednesday,
Hi all,
We have upgraded 3 different environments from 7.0.01 patch 008 to 7.5
patch 6. On 2 out of 3, we see the same error, but only at start-up. The
third one has no error. Those are 3 totally independent and different
servers.
But the 2 that are showing the error message at start-up do
10 matches
Mail list logo
