HI David,

Can you give us some more detail on what it means "when access rights to a
newly-created field are not properly defined?"  It is a bit bothersome to
think 1) a lack of permissions can cause memory issues 2) that it is easy
to not properly define a field which would cause memory issues.

Jason

On Wed, Oct 24, 2012 at 1:42 PM, David M. Clark <[email protected]>wrote:

> "We are getting this error intermittently over the past couple of weeks"
>
> Have you recently customized anything in that area?  I've seen this happen
> when access rights to a newly-created field are not properly defined.
>
> -D
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList) [mailto:
> [email protected]] On Behalf Of Longwing, LJ CTR MDA/IC
> Sent: Wednesday, October 24, 2012 3:31 PM
> To: [email protected]
> Subject: Re: ARERR 300 Malloc failed on server
>
> Ken,
> It sounds like your arserver was bouncing up against a upper memory limit.
>  This can happen sometimes with memory leaks that don't properly release
> memory once used.  A restart of the service brings the system back down to
> initial minimums of startup.  You may want to make sure that you are on the
> most recent patch of 7.5 to ensure that any known issues are taken care of
> properly.
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList) [mailto:
> [email protected]] On Behalf Of Cecil, Ken
> Sent: Wednesday, October 24, 2012 1:42 PM
> To: [email protected]
> Subject: ARERR 300 Malloc failed on server
>
> **
>
> We are getting this error intermittently over the past couple of weeks.
> The most consistent time it is occurring is when trying to attach a largish
> attachment (around 4MB). Some have also received it when trying to open an
> attachment. Yesterday for awhile we were getting the error anytime the
> SDA's were trying to attach any attachment to an Incident. I ended up
> restarting the ar server service.
>
>
>
> Has anybody run across something similar? (Arerr 300 when working with
> attachments)
>
>
>
> I have a support request in with BMC and waiting for a reply. The KB
> articles I found did not seem to apply.
>
>
>
>
>
> Thanks
>
>
>
>
>
> Ken Cecil
>
> 574-283-4248
>
> [email protected]
>
>
>
>
>
> AR 7.5
>
> ITSM 7.6
>
> Windows 2003 Enterprise 64bit
>
> SQL 2008
>
>
>
>
> ________________________________
>
> This email and any files transmitted with it are confidential and intended
> solely for the addressee. If you have received this email in error please
> notify the system manager. Subject to local law, communications (including
> traffic data) with Hubbell may be monitored by our systems [or a third
> party's systems on our behalf] for the purposes of security and the
> assessment of internal compliance with Hubbell policies. This footnote also
> confirms that this email message has been swept for the presence of
> computer viruses.
> www.hubbell.com <http://www.hubbell.com/>  - Hubbell Incorporated
>
>
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12
> www.wwrug12.com ARSList: "Where the Answers Are"
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to