It's been a while since I attempted to change or modify that field, but if
memory serves, the last time I modified it, everything worked (I had to make a
modification to make those stored procedures run again).
I checked a couple more things in enterprise manager and I can't figure out how
to get rid of that Z. If I open the field table, the field ID doesn't have the
z appended to the end. If I open the table and return all rows, it also
doesn't have the Z. The only place I can see it, is when I generate the SQL
script for that particular table.
Michael A. McManus, SSgt, USAF
Remedy Developer
HQ 754 ELSG/DOMH
DSN: 596-6472 / Comm: 334-416-6472
-Original Message-
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED]
On Behalf Of Joe D'Souza
Sent: Thursday, April 03, 2008 3:54 PM
To: arslist@ARSLIST.ORG
Subject: Re: Weird field ID issue
**
I had that issue once many years ago.. I do not know why it was caused but I am
guessing it happened at the time I tried to delete that field and it wasn't
successfully deleted.. it was not seen from the Admin tool but I could still
see it in the T table and there was a row in the fields table referring to it.
Luckily I didn't have any workflow attached to that field so my cleanup process
was simple at db level..
If you didn't attempt deleting that field, maybe you did attempt modifying it,
and the operation was not complete due to a timeout?
Joe
-Original Message-
From: Action Request System discussion list(ARSList) [mailto:[EMAIL
PROTECTED] Behalf Of McManus Michael A SSgt HQ 754 ELSG/DOMH
Sent: Thursday, April 03, 2008 1:47 PM
To: arslist@ARSLIST.ORG
Subject: Weird field ID issue
**
Listers,
I'm not entirely sure if this is an ARS issue or a SQL
issue but we're having problems with one of our stored procedures. Back before
any of us had any idea what we were doing in Remedy, one of our guys created a
stored procedure to handle archiving. Basically just a select insert then
drop. He also created an unarchive stored procedure in case anyone wanted to
get an incident out of the archive form. One of my analysts tried to unarchive
a ticket today and encountered the following error: ARERR [552] Failure during
SQL operation to the database : Insert Error: Column name or number of supplied
values does not match table definition. (SQL Server 213)
I opened enterprise manager and generated a SQL script for the
archive_incident and incident forms to make sure they matched up (my normal
course of action when one of these operations fails) and everything appeared to
match up, but at the bottom of the scripts, this is what I saw. On the
incident script: [C536870918] [varchar] (30) COLLATE
SQL_Latin1_General_CP1_CI_AS NULLOn the
Archive_Incident script: [C536870918Z] [varchar] (30) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL
I'm at a total loss where that Z came from. This stored procedure has
worked on several occasions with the only issue being a need for reordering of
the columns if someone made a change to one form but not the other. I've never
seen the name of a column change however. When I log into the administrator
tool, and click on the field in question, the Database ID matches on both forms.
I tried googling for help, but apparently my googlefu is weak. Anyone
encountered something like this before or have an idea of how to fix it?
Thanks much,
Michael A. McManus, SSgt, USAF
__Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are html___
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: Where the Answers Are
