AM,PM,IM,CM have been observed has having the same issue. We did the hack that is described in the article here to enable us to complete the installation of the full suite.
Note also that you will get an issue With CMDB V2 patch 1, same fix will help there. i.e. if you have the 7.0.1 components AND CMDB V2 patch 1, the first thing that breaks is the app. installers complaining about an invalid object store version (so set the version number back to 2.0.0 in Application Properties) and then when you restart the installer you get complaints about the 7.0.1 components (approval and maybe assignment too), so same fix again and you are then good to go.
HTH,
Gareth
On 27/10/06, strauss <
[EMAIL PROTECTED]> wrote:
__20060125_______________________This posting was submitted with HTML in it___
Support says that this is a known issue (that has not made the
knowledgebase yet, I guess) with the following resolution:
"This is caused by the SHARE:Application_Properties records for
Assignment Engine. When it used to say 7.0 as the version, the ITSM 7.0
installers would accept it and move on. However, now that there is
Assignment Engine 7.00.01, the installer checks the
SHARE:Application_Properties records for Assignment Engine and doesn't
recognize the version. This is a known issue, and there is a simple
workaround for this: You can locate the SHARE:Application_Properties
records for Assignment Engine in your User tool, and modify the version
from 7.00.01 to 7.0, save the record, and then run the ITSM 7.0
installs. Once they're completed, you can always go back to the
SHARE:Application_Properties records for Assignment Engine in your User
tool and modify the version back to 7.00.01."
Beats the heck out of uninstalling the 7.00.01 Assignment Engine and
installing 7.0 in its place before ITSM. The Incident Management 7.0
installation runs once this change has been made. It is too early to
tell if it completes, or if any of the other installers I need to run
(PM, CM, RKM, SLM) will hit similar traps.
Chris
