Leonard, I traced the error in the SQL log and I found the offending INSERT operation, then I got to compare two INSERTs, one with a failing result and one with a successful result, and I found that the error was in the "Mail Station" field (id 1000000036) in HPD:IncidentInterface_Create form, this field had a char lenght of 50, and the same field in CTM:People had 90, which I assume is a bug in the app or maybe somebody made unauthorized changes, because when SRM:Request tried to do a push fields action to generate an incident and get values from a person´s record, that mismatch was stopping the workflow.
The reason why a user would be able to create the incident only after his record was deleted and manually submitted again, and this event ocurred to some users and others don´t, is that MS Active Directory probably is populating a non expected value in that particular field everytime it syncs the record´s data between Remedy and MS AD. Thank you very much for your help. -Mauricio M. 2008/6/26 Leonard Neely - FOJ <[EMAIL PROTECTED]>: > You may need to turn on SQL logging, and reproduce the error. The SQL log > should show exactly what statement is being executed upon failure. From > that you should be able to identify what the offending field is. > > If this is always failing for the same user(s), then most likely, there is a > bad piece of data on the People or Location record (i.e. Department, Postal > Code, Etc. > > HTH > > Leonard Neely > Column Technologies > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Mauricio M. > Sent: Thursday, June 26, 2008 6:11 PM > To: arslist@ARSLIST.ORG > Subject: Re: Request ID "In Process" .. again, SQL Error > > Hi Scott, > > We´ve done several tests and unfortunately, a free text field is not > the problem, we have tested with the very same summary values and free > text input, but it doesn´t make the trick. It works for some users but > others don´t get it. > We have seen that if you delete the faulting user record and create it > again from scratch, then this user is able to generate the incident > and incident ID. Since all users were imported from and are in sync > with MS Active Directory, maybe it is related to some strange > character being inserted somewhere. > If you have any idea, please let me know, your comment was helpful and > sure any extra help will be very valuable. > > Thanks, > Mauricio M. > > > > 2008/6/21 Scott Parrish <[EMAIL PROTECTED]>: >> What the error in the CAI Event form is telling you is that data that is >> being pushed to a certain field is too large for the field (for instance, >> pushing 101 characters to a 100 character length field). Most probably > this >> is coming from a free text field on the Requester Console, that's why when >> the same categorization and summary are selected by two different people > the >> error occurs for one and not the other. >> >> Scott Parrish >> IT Prophets, LLC >> (770) 653-5203 >> www.itprophets.com >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:[EMAIL PROTECTED] On Behalf Of Mauricio M. >> Sent: Friday, June 20, 2008 9:15 PM >> To: arslist@ARSLIST.ORG >> Subject: Request ID "In Process" .. again, SQL Error >> >> Dear All, >> >> I´d appreciate your help with this odd issue regarding incident >> generation from the Requester Console, thanks in advance for your help >> as always... >> >> When I push the New Request button, the Incident ID will not be >> created and the Incident will not be pushed to Helpdesk form. The ID >> gets stuck in status "In Process". >> It happens only to some users, some users don´t have any problem at >> all, even though both lucky and failing users use the same >> categorization, summary, etc., and I haven´t been able to find a >> pattern. >> >> A record is actually created in SRM:Request, but If I check the latest >> entry in CAI:Event, I will get the following information: >> >> SRM_OUT_CREATE_APP_REQUEST >> Form: HPD:IncidentInterface_Create >> Return Code:Error >> Error: ARCreateEntry - Failure during DB operation. The statement has >> been terminated.String or binary data would be truncated. (SQL Server >> 8152) >> >> I have checked the filter log, and I can detect one error, stopping >> filter processing, somewhere between filter >> SHR:SHR:UpdateGroupListAdd_100 and the filter that updates the >> HPD:Worklog, but there is no detail where the error is exactly >> ocurring. >> >> Please, shed some light, >> Thanks and best regards, >> -Mauricio >> >> > ____________________________________________________________________________ >> ___ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> >> > ____________________________________________________________________________ > ___ >> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org >> Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" >> > > ____________________________________________________________________________ > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
