It turns out that BMC Support was able to replicate the issue by turning
on Encryption. Thanks to Larry for bringing up his issue, as I would
not have thought to try changing encryption settings for this error.
BMC created defect SW00385907 for this, and it sounds like a fix will be
included in an upcoming patch.
David Durling
On 12/17/2010 11:31 AM, David Durling wrote:
It seems like the timeout problem does not occur when the Security
Policy is set to "Disabled" on the Encryption page. So, until I find out
more, my current options are to disable encryption or use a binary file
from patch 006 on our patch 007 server.
I've sent the information about the encryption setting to Support to see
what they say -
David
On 12/16/2010 2:28 PM, David Durling wrote:
Thanks Larry,
Your api logs look similar to mine.
Since this server is not production, I disabled encryption and don't see
the timeout yet - but I need to wait a while more to confirm.
I'll post again on the results.
David
On 12/16/2010 11:04 AM, L G Robinson wrote:
Hi David,
It may be coincidental, but the last entries in my API logs before
the timeout seem to indicate a call to "ARGetEncryptInfo".
Also, when I disable standard encryption (not required), the problem
disappears.
--
David Durling 706-542-0223
Enterprise IT Services [email protected]
University of Georgia
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
