Re: ITSM Upgrade Issues
I actually have another 7.0 system which is an virtual image that was a blank install and that field ID is the same as mine here as well. This is just bascially an instance of one field that is not importing right. There are many others like this. Another example is on the HPD:HelpDesk form, the customers incidents table. All of the fields on that table in all of my systems start with 301 but the install is trying to import them as 303. On Sun, Jul 4, 2010 at 11:20 AM, Robert Molenda robert.mole...@gmail.comwrote: ** Interesting - I checked my Clean build ITSM 7.5.01 - patch 0 system - and the field ID is the 303778300 as you are mentioning as the to be imported version. Was this system a clean-build, or an upgrade or .. ?? Could someone have run change-id on the field for some reason? Is this the only field or are there more? HTH Robert On Fri, Jul 2, 2010 at 1:38 PM, Kevin Begosh kbeg...@gmail.com wrote: ** okay so I have been having ITSM upgrade issues and I have finally narrowed it down. Basically what is happening is I am running the ITSM install and it is trying to import .def .arx files etc and it is failing some definition files because it is trying to import a form with a field that already exists and failing saying that it already exists but the DB ID's are different. Example: One of the installs is importing the form FIN:LoadCosts and is failing because in the current system the field Related Cost is there, which it should be but it is Field ID 270002018. The field ID trying to be imported is 303778300. I have looked at other system the same version as mine and the current field ID is the same as mine 270002018. So why is this form failing to import, shouldn't it be over writing that field? Has anyone else seen this or run into this issue? Current system: ARS 7.5 Patch 4 CMDB 7.6 Patch 1 ITSM 7.03 Patch 9, plus the compatibility Patch Windows 2003 Server SQL 2005 DB VMWare Virtual Server I am trying to upgrade to ITSM 7.6 Patch 1 I have tried ITSM 7.6 Patch 1, ITSM 7.6, and now I am trying ITSM 7.5 and the same issue is happening on all three upgrades. -- Kevin Begosh _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- If it were not for the gutter, my mind would be homeless! _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- Kevin Begosh ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: ITSM Upgrade Issues
Whoops - my bad - I looked at my 7.5 system and not my 7.0 :( On my 7.0.2 system on FIN:Costs the Related Costs field is 270002018 as you have mentioned - however there is not a FIN:LoadCosts (probably a difference between ITSM 7.0.2 and 7.0.3 which I never built/saved...) Interesting that in the installation guide for 7.5 the specific versions for Asset / Change were mentioned to be able to be upgraded from 7.0.3 but not for Incident and Problem... Might be interesting to check the field id on a 7.1 system... On Tue, Jul 6, 2010 at 7:31 AM, Kevin Begosh kbeg...@gmail.com wrote: ** I actually have another 7.0 system which is an virtual image that was a blank install and that field ID is the same as mine here as well. This is just bascially an instance of one field that is not importing right. There are many others like this. Another example is on the HPD:HelpDesk form, the customers incidents table. All of the fields on that table in all of my systems start with 301 but the install is trying to import them as 303. On Sun, Jul 4, 2010 at 11:20 AM, Robert Molenda robert.mole...@gmail.comwrote: ** Interesting - I checked my Clean build ITSM 7.5.01 - patch 0 system - and the field ID is the 303778300 as you are mentioning as the to be imported version. Was this system a clean-build, or an upgrade or .. ?? Could someone have run change-id on the field for some reason? Is this the only field or are there more? HTH Robert On Fri, Jul 2, 2010 at 1:38 PM, Kevin Begosh kbeg...@gmail.com wrote: ** okay so I have been having ITSM upgrade issues and I have finally narrowed it down. Basically what is happening is I am running the ITSM install and it is trying to import .def .arx files etc and it is failing some definition files because it is trying to import a form with a field that already exists and failing saying that it already exists but the DB ID's are different. Example: One of the installs is importing the form FIN:LoadCosts and is failing because in the current system the field Related Cost is there, which it should be but it is Field ID 270002018. The field ID trying to be imported is 303778300. I have looked at other system the same version as mine and the current field ID is the same as mine 270002018. So why is this form failing to import, shouldn't it be over writing that field? Has anyone else seen this or run into this issue? Current system: ARS 7.5 Patch 4 CMDB 7.6 Patch 1 ITSM 7.03 Patch 9, plus the compatibility Patch Windows 2003 Server SQL 2005 DB VMWare Virtual Server I am trying to upgrade to ITSM 7.6 Patch 1 I have tried ITSM 7.6 Patch 1, ITSM 7.6, and now I am trying ITSM 7.5 and the same issue is happening on all three upgrades. -- Kevin Begosh _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- If it were not for the gutter, my mind would be homeless! _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- Kevin Begosh _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- If it were not for the gutter, my mind would be homeless! ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: ITSM Upgrade Issues
yeah, I guess the question or problem I have that I am waiting support to come back with is if you are able to upgrade from 7.03 Patch 9 to 7.5 or 7.6 then how is the new field ID's suppose to change. It is trying to add Field ID 303. with the same name as one that exists and it's failing because you cannot have the two fields with the same DB name. So I am consufsed to what should happen with the install and/or why so many other people are not having issues. The only thing I can think of is that it is suppose to replace that field and if it's not doing it then why not? On Tue, Jul 6, 2010 at 11:59 AM, Robert Molenda robert.mole...@gmail.comwrote: ** Whoops - my bad - I looked at my 7.5 system and not my 7.0 :( On my 7.0.2 system on FIN:Costs the Related Costs field is 270002018 as you have mentioned - however there is not a FIN:LoadCosts (probably a difference between ITSM 7.0.2 and 7.0.3 which I never built/saved...) Interesting that in the installation guide for 7.5 the specific versions for Asset / Change were mentioned to be able to be upgraded from 7.0.3 but not for Incident and Problem... Might be interesting to check the field id on a 7.1 system... On Tue, Jul 6, 2010 at 7:31 AM, Kevin Begosh kbeg...@gmail.com wrote: ** I actually have another 7.0 system which is an virtual image that was a blank install and that field ID is the same as mine here as well. This is just bascially an instance of one field that is not importing right. There are many others like this. Another example is on the HPD:HelpDesk form, the customers incidents table. All of the fields on that table in all of my systems start with 301 but the install is trying to import them as 303. On Sun, Jul 4, 2010 at 11:20 AM, Robert Molenda robert.mole...@gmail.com wrote: ** Interesting - I checked my Clean build ITSM 7.5.01 - patch 0 system - and the field ID is the 303778300 as you are mentioning as the to be imported version. Was this system a clean-build, or an upgrade or .. ?? Could someone have run change-id on the field for some reason? Is this the only field or are there more? HTH Robert On Fri, Jul 2, 2010 at 1:38 PM, Kevin Begosh kbeg...@gmail.com wrote: ** okay so I have been having ITSM upgrade issues and I have finally narrowed it down. Basically what is happening is I am running the ITSM install and it is trying to import .def .arx files etc and it is failing some definition files because it is trying to import a form with a field that already exists and failing saying that it already exists but the DB ID's are different. Example: One of the installs is importing the form FIN:LoadCosts and is failing because in the current system the field Related Cost is there, which it should be but it is Field ID 270002018. The field ID trying to be imported is 303778300. I have looked at other system the same version as mine and the current field ID is the same as mine 270002018. So why is this form failing to import, shouldn't it be over writing that field? Has anyone else seen this or run into this issue? Current system: ARS 7.5 Patch 4 CMDB 7.6 Patch 1 ITSM 7.03 Patch 9, plus the compatibility Patch Windows 2003 Server SQL 2005 DB VMWare Virtual Server I am trying to upgrade to ITSM 7.6 Patch 1 I have tried ITSM 7.6 Patch 1, ITSM 7.6, and now I am trying ITSM 7.5 and the same issue is happening on all three upgrades. -- Kevin Begosh _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- If it were not for the gutter, my mind would be homeless! _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- Kevin Begosh _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- If it were not for the gutter, my mind would be homeless! _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- Kevin Begosh ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: ITSM Upgrade Issues
Interesting - I checked my Clean build ITSM 7.5.01 - patch 0 system - and the field ID is the 303778300 as you are mentioning as the to be imported version. Was this system a clean-build, or an upgrade or .. ?? Could someone have run change-id on the field for some reason? Is this the only field or are there more? HTH Robert On Fri, Jul 2, 2010 at 1:38 PM, Kevin Begosh kbeg...@gmail.com wrote: ** okay so I have been having ITSM upgrade issues and I have finally narrowed it down. Basically what is happening is I am running the ITSM install and it is trying to import .def .arx files etc and it is failing some definition files because it is trying to import a form with a field that already exists and failing saying that it already exists but the DB ID's are different. Example: One of the installs is importing the form FIN:LoadCosts and is failing because in the current system the field Related Cost is there, which it should be but it is Field ID 270002018. The field ID trying to be imported is 303778300. I have looked at other system the same version as mine and the current field ID is the same as mine 270002018. So why is this form failing to import, shouldn't it be over writing that field? Has anyone else seen this or run into this issue? Current system: ARS 7.5 Patch 4 CMDB 7.6 Patch 1 ITSM 7.03 Patch 9, plus the compatibility Patch Windows 2003 Server SQL 2005 DB VMWare Virtual Server I am trying to upgrade to ITSM 7.6 Patch 1 I have tried ITSM 7.6 Patch 1, ITSM 7.6, and now I am trying ITSM 7.5 and the same issue is happening on all three upgrades. -- Kevin Begosh _attend WWRUG10 www.wwrug.com ARSlist: Where the Answers Are_ -- If it were not for the gutter, my mind would be homeless! ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
ITSM Upgrade Issues
okay so I have been having ITSM upgrade issues and I have finally narrowed it down. Basically what is happening is I am running the ITSM install and it is trying to import .def .arx files etc and it is failing some definition files because it is trying to import a form with a field that already exists and failing saying that it already exists but the DB ID's are different. Example: One of the installs is importing the form FIN:LoadCosts and is failing because in the current system the field Related Cost is there, which it should be but it is Field ID 270002018. The field ID trying to be imported is 303778300. I have looked at other system the same version as mine and the current field ID is the same as mine 270002018. So why is this form failing to import, shouldn't it be over writing that field? Has anyone else seen this or run into this issue? Current system: ARS 7.5 Patch 4 CMDB 7.6 Patch 1 ITSM 7.03 Patch 9, plus the compatibility Patch Windows 2003 Server SQL 2005 DB VMWare Virtual Server I am trying to upgrade to ITSM 7.6 Patch 1 I have tried ITSM 7.6 Patch 1, ITSM 7.6, and now I am trying ITSM 7.5 and the same issue is happening on all three upgrades. -- Kevin Begosh ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
