This is a development system, but we are prepping for an Asset install into production, which has the identical configuration (and same missing AST:BaseElement).
I wonder if it is the "authentication" between the CMDB processes and ARServer. Any thoughts? Pending feedback from BMC, I will be trying to poke things with cmdbdriver to see if I get a different response. I will also try re-applying CMDB 2.1 patch 4 again to. I have good backups so getting to a known state is not a problem. Chuck On Mon, Jul 20, 2009 at 4:38 PM, Joe DeSouza <[email protected]> wrote: > ** > The SHR:Schema Names is not a meta data table so the AR System server > should not really care about that entry if you are using the cmdbdriver to > create that form. > > Is this a test system? If not you may just be better off trying to > reinstall. > > Joe > > ------------------------------ > *From:* Charles Baldi <[email protected]> > *To:* [email protected] > *Sent:* Monday, July 20, 2009 4:29:43 PM > *Subject:* Re: Install Asset onto a working Incident/Problem/Change > system? > > ** The SHR:Schema Names form already had an entry, but the arschema table > does not. > > On Mon, Jul 20, 2009 at 4:14 PM, Joe DeSouza <[email protected]>wrote: > >> ** >> Does the arschema table have an entry for it already? >> >> Joe >> >> ------------------------------ >> *From:* Charles Baldi <[email protected]> >> *To:* [email protected] >> *Sent:* Monday, July 20, 2009 4:07:55 PM >> >> *Subject:* Re: Install Asset onto a working Incident/Problem/Change >> system? >> >> ** Yes, same errors when importing manually. Fundamentally these are all >> because the AST:BaseElement form does not exist. I cannot find a def file >> that imports this and I believe that is because it is expected to be built >> from the CMDB through the Sync Asset UI process (cmdbdriver) which is >> failing to create the form. >> >> Chuck >> >> On Mon, Jul 20, 2009 at 2:52 PM, Joe DeSouza <[email protected]>wrote: >> >>> ** >>> And manually importing these fails too? >>> >>> Joe >>> >>> ------------------------------ >>> *From:* Charles Baldi <[email protected]> >>> *To:* [email protected] >>> *Sent:* Monday, July 20, 2009 1:43:15 PM >>> >>> *Subject:* Re: Install Asset onto a working Incident/Problem/Change >>> system? >>> >>> ** Joe, >>> Good suggestion, but the installer is not "failing". It completes >>> happily, but the summary table at the end (and the log files) show many, >>> many def file load errors along the way. >>> >>> Chuck >>> >>> On Mon, Jul 20, 2009 at 1:33 PM, Joe DeSouza <[email protected]>wrote: >>> >>>> ** >>>> The contents of your Share Application Properties form may be prompting >>>> your installer that Asset is already installed? Did you try clearing the >>>> Asset related entries in the Share Application Properties (entries with the >>>> current version you are trying to install) form and then trying to install >>>> it? >>>> >>>> If you choose the route to clear those entries, I would suggest that you >>>> take a backup of these entries and then delete them just in case you need >>>> to >>>> revert. >>>> >>>> Joe >>>> >>>> ------------------------------ >>>> *From:* Charles Baldi <[email protected]> >>>> *To:* [email protected] >>>> *Sent:* Monday, July 20, 2009 1:17:54 PM >>>> >>>> *Subject:* Re: Install Asset onto a working Incident/Problem/Change >>>> system? >>>> >>>> ** >>>> So when I try to install Asset, I get 60 failed objects under the ast >>>> component and the culprit appears to be that the system is unable to create >>>> AST:BaseElement. If I try to force the creation using Sync Asset UI, I get >>>> the cryptic logs: >>>> >>>> Start processing of form AST:BaseElement >>>> Creating new form >>>> Will fetch display infor for form AST:BaseElement >>>> Will make the new Form AST:BaseElement that is an inner join on >>>> BMC.CORE:BMC_BaseElement >>>> Failed to create Form for: AST:BaseElement >>>> Form does not exist on server >>>> AST:BaseElement >>>> >>>> Of course the AST:BaseElement does not exist, that is why I am creating >>>> it! Has anyone seen this before or have suggestions on how to fix this? >>>> >>>> - I am logged-in as Demo with proper (administrator) privs >>>> - I confirm that Demo can create forms >>>> - I tried "forcing" things by creating a fake AST:BaseElement form >>>> >>>> I still get the can't create message. Have a call in with BMC but no >>>> response in over 24 hours :-( >>>> >>>> Chuck >>>> >>>> >>>> On Thu, Jul 16, 2009 at 2:19 PM, strauss <[email protected]> wrote: >>>> >>>>> ** >>>>> >>>>> No. >>>>> >>>>> Install Asset 7.0.03 which is current to patch 003. >>>>> >>>>> Install Patch 007 which will bring Asset up to 007, but unfortunately >>>>> will overwrite any changes 008 made to the other apps. >>>>> >>>>> Install Patch 008 or 009 which will bring ALL of the apps to the same >>>>> level. >>>>> >>>>> >>>>> >>>>> We went live on 007 in Spring 08 but were looking at patching ITSM to >>>>> 008 or 009 this spring, while also trying to get the ITSM Suite licensing >>>>> that would have given us Asset (the only one we lack). It was not funded, >>>>> but we delayed our patching until after that decision so as to avoid the >>>>> situation that you are in. Applying 007 at our site requires that I >>>>> reconstruct a _*lot*_ of customizations in Incident – learned and >>>>> documented when we went from 006 to 007 just before go live in May 08, >>>>> whereas 008 and 009 had very little effect on Incident (better designed >>>>> patches) and mostly applied to Change and Task which we have not >>>>> customized. >>>>> >>>>> >>>>> >>>>> Christopher Strauss, Ph.D. >>>>> >>>>> Call Tracking Administration Manager >>>>> >>>>> University of North Texas Computing & IT Center >>>>> >>>>> http://itsm.unt.edu/ >>>>> >>>>> >>>>> >>>> *From:* Action Request System discussion list(ARSList) [mailto: >>>> [email protected]] *On Behalf Of *Charles Baldi >>>> *Sent:* Thursday, July 16, 2009 1:12 PM >>>> *To:* [email protected] >>>> *Subject:* Re: Install Asset onto a working Incident/Problem/Change >>>> system? >>>> >>>> >>>> >>>> ** >>>> >>>> To clarify, we do have CMDB 2.1.0 at patch 4. >>>> >>>> >>>> >>>> Our first attempt to install Asset resulted in a pile of errors against >>>> missing forms (e.g., AST:PurchaseLineItemAssetJoin). I was puzzled because >>>> I expected the Asset install to handle all the AST forms. Perhaps this is >>>> because we are at ITSM patch 008? >>>> >>>> >>>> >>>> So Chris, you are saying that we should >>>> >>>> 1. Install ITSM patch 007 (downgrade) >>>> >>>> 2. Install Asset >>>> >>>> 3. Re-apply patch008 >>>> >>>> >>>> >>>> Chuck >>>> >>>> On Thu, Jul 16, 2009 at 2:07 PM, strauss <[email protected]> wrote: >>>> >>>> ** >>>> >>>> Asset installs at patch 003, and cannot be brought up to patch 008 >>>> without first running patch 007, the last patch to include patches 004-006. >>>> Because patch 007 will apply to ALL ITSM apps, it will knock ALL of your >>>> other apps back to 007. Then you can run 008 against everything. The >>>> release notes for 009 were very specific about all of this… not sure about >>>> 008. If you had to do any post 008 cleanup on Incident, etc., you will >>>> have >>>> to do it again. >>>> >>>> >>>> >>>> Christopher Strauss, Ph.D. >>>> >>>> Call Tracking Administration Manager >>>> >>>> University of North Texas Computing & IT Center >>>> >>>> http://itsm.unt.edu/ >>>> >>>> >>>> >>>> *From:* Action Request System discussion list(ARSList) [mailto: >>>> [email protected]] *On Behalf Of *Charles Baldi >>>> *Sent:* Thursday, July 16, 2009 12:43 PM >>>> *To:* [email protected] >>>> >>>> >>>> *Subject:* Install Asset onto a working Incident/Problem/Change system? >>>> >>>> >>>> >>>> ** >>>> >>>> Hello list, >>>> >>>> We have been asked to install Asset Management into an existing >>>> configuration that already has Incident, Problem, and Change. Our current >>>> configs are: >>>> >>>> ARS 1.7 p005 >>>> >>>> Incident/Problem/Change 7.0.03, p008 >>>> >>>> Windows 2003 server >>>> >>>> SQL Server 2005 >>>> >>>> >>>> >>>> We are opening an issue with BMC to get some direction, but I wondered >>>> if anyone else has experience in "retro fitting" Asset into an existing >>>> ITSM >>>> install. I'm hoping to be able to do this without doing a ground-up >>>> install >>>> with Asset first, then Incident/Problem/Change, then patch, then re-apply >>>> customizations. Am I dreaming? >>>> >>>> >>>> >>>> Thanks in advance, >>>> >>>> Chuck Baldi >>>> >>>> > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
