Hmm - not good. Thanks for the info. I ended up deleting everything related to this app in our stage environment and remigrating it all fresh from dev. I'll try the migration to prod, and if I get the same results, I'll do the same there.
Thanks again, Lyle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ Longwing Sent: Friday, February 27, 2009 2:24 PM To: arslist@ARSLIST.ORG Subject: Re: Errors migrating form using Migrator or by importing def file Lyle, It looks like you have some data dictionary corruption related to that form, the reason it works when you delete and re-create is that it's assigned a new form index and everything goes in as new instead of an update. You may see if you can restore the DB from prod into your stage server, and then re-try the migration....if the corruption never made it to your production environment you would be able to avoid having to backup the data and re-import. But if you do, please remember to also grab any workflow associated with the form, because that will also get deleted. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Lyle Taylor Sent: Friday, February 27, 2009 1:42 PM To: arslist@ARSLIST.ORG Subject: Re: Errors migrating form using Migrator or by importing def file Hi David, Sorry, was trying to be quick and forgot to include the extra info. We're on 7.1 patch 005. Patch 006 only resolves issues with the Thai language, which we are not using. However, I also get the error when simply importing a def file, so I'm not sure the issue is actually related to Migrator. In the end, I got around the error by dropping the existing form on the stage server and then remigrating. That succeeded, but is not generally how I'd like to do things as this means that I'm going to have to backup and reimport all the data on that form in production... If anyone has any ideas what's actually going on, I'd like to hear them. Otherwise, I've found a workaround and can keep going for now. Thanks, Lyle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of David.M Clark Sent: Friday, February 27, 2009 1:30 PM To: arslist@ARSLIST.ORG Subject: Re: Errors migrating form using Migrator or by importing def file Lyle, Migrator has issues. Always has. You didn't specify what version of the AR System you are running, but if you're on anything less than 7.5 start by downloading and installing the latest patch of BMC Remedy Migrator. (7.1.00 Patch 006 as of 02/11 when I had to do it.) If the problem(s) persist you can try calling tech support, or buy one of the alternative products that our two notes are now going to generate advertisements for on this forum. -D David M Clark Remedy Programmer/Analyst >>> Lyle Taylor <tayl...@ldschurch.org> 2/27/2009 2:09 PM >>> Hi List, I'm trying to migrate some forms from our development to our stage environment and am getting odd errors that don't make sense to me. I get several errors like this: Migration Error: 3700: Unable to create field 536880919 AR System Error: 382: The value(s) for this entry violate a unique index that has been defined for this form What's odd is that there are no indexes defined by me on the form - if I go look at the form properties, no indexes are listed. In addition, the majority of the fields it's giving me errors about already existing on the form. I also get this error if I export the form to a def file and try to import it on the stage server. For one of the fields I get this: Migration Error: 3700: Unable to create field 536880923 AR System Error: 129: Field limit definition is invalid qualification - LDS:EMI:Messages, 536880923 That field is a regular character field that is pretty much unchanged from what gets added to a form by default except that the name was changed. I haven't defined any limits for the field or changed any of the other options such as QBE Match, etc. Has anyone else come across issues like this? Any idea how to resolve them? Thanks, Lyle Taylor NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
