HI,
We acknowledge that hard deletion of records is not something that is currently
designed for with the DDM tool. The general consideration on this was due to
the fact that "soft" deletion is the prolific model officially designed for in
the applications. While hard deletes are possible, th
Can you better describe your upgrade scenario and the failure itself.
What versions/products are you upgrading from? Is it just ITSM, or ITSM + SRM?
+ SLM?, etc?
What was the failure?
Ramon Kagan, MBA, PMP
Manager, Product Development
BMC Software
From: Action
HI Peter,
I would not recommend disabling the workflow, it is there specifically to guard
you. Merging of companies is more complicated than just the company name. All
dependant data will be updated as well and may result in collisions (e.g.
approval, auto-assignment, etc). This is not a su
Frank,
Not knowing your complete environment 5 minutes for the stack you show here
looks to be fairly normal as the caches are being built during startup time.
However, as Dave Easter stated in his reply, please ensure the preload thread
options are in fact configured and enabled. The ITSM in
ch we did and still no
success. May be "HPD:Help Desk_SLA" (which is out of the Box) is another form
that needs to be deleted.
This is definitely good information for other customers.
Thanks
Mahesh
On Tue, Oct 19, 2010 at 9:53 PM, Kagan, Ramon
mailto:ramon_ka...@bmc.com>> wrote:
While I don't have full details into the problem. With SLM installed, the
likely solution is to drop the join form created by SLM/SLA, run the ITSM
upgrade and then re-establish the Service target as described in the SLM
install guide in the post install section.
__
Defect 343855 is specific to when ITSM and older versions of SLM are installed
on the same environment. In that case, the older versions of SLM/SLA created
join forms across ITSM main forms which causes upgrade problems for ITSM due to
field references existing when trying to upgrade the HPD fo
7 matches
Mail list logo
