Does anyone have an answer for this? I'm experiencing something very similar to this. My Solaris environment is not having the problem that I have on Windows. When a non-admin user is trying to run INT:HPDTMS:INC:ActivateTaskandTGBuildFlow (during a save task), they get the malloc error. After I gave her admin permissions, she was able to save a task.
Thanks! Melissa On Sep 18, 3:07 pm, Hall Chad - chahal <[EMAIL PROTECTED]> wrote: > I've tried using both Remedy User 6.3 patch 20 and Remedy User 7.0.1 > patch 4 against a 7.0.1 patch 4 AR Server. I can't reproduce this > problem. Again, I appear to be running the first drop of AR Server 7.0.1 > patch 4 so this may be something that was broken in the second drop. > > Emad - can you confirm the timestamp on the arserver executable that you > are currently running? > > Chad Hall > (501) 342-2650 > > ________________________________ > > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza > Sent: Tuesday, September 18, 2007 10:01 AM > To: [EMAIL PROTECTED] > Subject: Re: Updated : Malloc Erros after Applying 7.0.1 Patch 4 anyone? > > Emad, > > To add to what Chad has to say, it could also be a issue with your > client. Is your client version/patch the same as the server > version/patch? If not update it and check to see if this condition > prevails.. > > Cheers > > Joe > > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > > [mailto:[EMAIL PROTECTED] Behalf Of Hall Chad - chahal > Sent: Tuesday, September 18, 2007 9:14 AM > To: [EMAIL PROTECTED] > Subject: Re: Updated : Malloc Erros after Applying 7.0.1 Patch 4 > anyone? > > ** > > I tried it on active links as a non-admin user and still > couldn't reproduce the problem. Either I have a different drop of 7.0.1 > patch 4 (possible) or there is some unknown variable at play. My > arserver.exe timestamp property is 200708141640. > > Chad Hall > (501) 342-2650 > > ________________________________ > > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Emad Zaky > Sent: Monday, September 17, 2007 8:45 PM > To: [EMAIL PROTECTED] > Subject: Re: Updated : Malloc Erros after Applying 7.0.1 Patch 4 > anyone? > > ** > > Try it on an Active Link with a user having non-admin > permissions but having permissions on the Active Link.... > > That is the condition I found which causes issues. > > For out-of-the-box workflow that uses this type of AL try: > Changing Task sequence using the up-down arrows beside the table-field > on a change request (not sure whether the same is on incidents or > not).... > > On 9/17/07, Hall Chad - chahal <[EMAIL PROTECTED]> wrote: > > ** > > I've been testing 7.0.1 patch 4 so I just tried this out myself. > It worked fine and didn't cause any errors anywhere. I tried executing > it in both filters and active links, and both worked fine. Is there some > other configuration setting that contributes to this that I may not > have? > > Chad Hall > (501) 342-2650 > > ________________________________ > > From: Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] On Behalf Of Emad Zaky > Sent: Saturday, September 15, 2007 1:06 PM > To: [EMAIL PROTECTED] > Subject: Updated : Malloc Erros after Applying 7.0.1 Patch 4 > anyone? > > ** > > Hi All, > > It seems that the culprit in this error is the execution of the > $PROCESS$ > > Application-Query-Delete-Entry > > On active Links. > > True enough we are now able to replicate the crash.... > > Hopefull this will be fixed in Patch 5 :(::::: > > Regards, > > Emad > > __20060125_______________________This posting was submitted with HTML in > it___ > ************************************************************************* > The information contained in this communication is confidential, is > intended only for the use of the recipient named above, and may be > legally privileged. > > If the reader of this message is not the intended recipient, you are > hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited. > > If you have received this communication in error, please resend this > communication to the sender and delete the original message or any copy > of it from your computer system. > > Thank you. > ************************************************************************* > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives atwww.arslist.orgARSlist:"Where the > Answers Are"- Hide quoted text - > > - Show quoted text - _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
