Quantcast
Channel: Ivanti User Community: Message List
Viewing all articles
Browse latest Browse all 12704

Upgrading Service Desk (Running MDM) doesn't finish and throws the error "Thread was being aborted"

$
0
0

Issue:   (I ran into this issue and found the solution so I thought I would share)

Upgrading Service Desk (Running MDM) doesn't finish and throws an error in the MetadataManager.xml file.

MDMError.jpg

 

Running MDM returns the following "Thread was being aborted" error in the MetadataManagerResult.xml

 

-<MetadataLogEntry xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<Sql>ALTER TABLE tps_appointment ADD CONSTRAINT fkey$tps_user_group$crbyusr FOREIGN KEY (tps_creation_user_guid) REFERENCES tps_user (tps_guid)</Sql>

<Result>Success</Result>

</MetadataLogEntry>

-<FatalError>

<Description>Thread was being aborted.</Description>

<CallStack> at Touchpaper.Framework.Data.Metadata.ChildQueryAttributeList.get_Values() at Touchpaper.Framework.Data.Metadata.Internal.Module.ResolveQueryImportReferences(ClassType classType, QueryTemplate query) at Touchpaper.Framework.Data.Metadata.Internal.Module.ResolveImportReferences(MetadataObject parent) at Touchpaper.Framework.Data.Metadata.MetadataObject.ResolveImportReferences[T](MetadataObject parent, IMetadataCollection`1 collection) at Touchpaper.Framework.Data.Metadata.MetadataCatalog.ResolveImportReferences(MetadataObject parent) at Touchpaper.Framework.Data.Metadata.Tools.ClassBuilder.GetExistingModuleGuids(MetadataCatalog catalog) at Touchpaper.Framework.Data.Metadata.Manager.MetadataManager.DoConversion(MetadataCatalog metadata, Boolean isMdmOperation) at Touchpaper.Framework.Data.Metadata.Manager.MetadataManager.SetupDatabase(MetadataCatalog metadata)</CallStack>

</FatalError>

</MetadataLog>

 

Solution:  (The steps taken here are for updating the culture for US Installations)

1) Update the Framework and WebAccess tps.config files to use "en-US" located under C:\ProgramData\LANDesk\ServiceDesk\Framework or WebAccess

<add key="SystemCulture" value="en-US" />

 

2) Run the following script to update the system culture from en-GB to en-US

Use [DatabaseName]

update md_catalog set md_culture = 'en-US'

 

3) Run the following script to update the user's culture from en-GB or Null to en-US.

--Note: This should only be run if the culture is the same for all users in the system.

update tps_user set tps_culture = 'en-US'

 

4) Run and IISReset on the Web and Application Servers.

 

5) Run MDM to upgrade.  Should run without any problems based on the system culture being set properly.


Viewing all articles
Browse latest Browse all 12704

Trending Articles