New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Highlighted
Captain
Captain
3475 views

"specified cast is not valid" after upgrading from ALM QC 11 patch 4 to ALM QC 11patch 18

Jump to solution

Due to the license revocation problem we have upgraded 2 weeks ago from ALM QC 11 patch 4 to ALM QC 11patch 18.

 

We did have some OTA client problems (see other forum entries here) in the first days but could solve all problems.

 

But we have another problem:

 

We have a self-written subroutine in the workflow scripts which copies defects from one project to another project.

 

The subroutine works stable for years now.

 

The subroutine is used in the following context:

(1) copy defect from project A on server X to project B on server X

(2) copy defect from project C on server Y to project D on server Y

(3) copy defect from project A on server X to project D on server Y

 

(1) still works fine with patch 18 no error message, (2) still works fine with patch 18 no error message, (3) with patch 18 the defect is copied successfully, but after the copy process the error message "specified cast is not valid" is shown !! The error message is not shown in English but in German "Die angegebene Umwandlung ist ungueltig". Our ALM language is English, the OS client language is German. The OS on our clients is Win 7 32, IE version is 9 or 10.

 

Any idea why the error message is raised only if we transfer the defect from one server to another server?

 

The fle exception.txt has the following content:

 

System.InvalidCastException: Die angegebene Umwandlung ist ungültig.
   bei Mercury.TD.Client.UI.Adapters.Services.TDWorkflowService.ExecuteBooleanEvent(IBaseEntity entity, String eventName, Object[] parameters)
   bei Mercury.TD.Client.UI.Adapters.Services.TDWorkflowService.OnActionExecuting(Object sender, CancelableCommandEventArgs args)
   bei System.EventHandler`1.Invoke(Object sender, TEventArgs e)
   bei Mercury.TD.Client.UI.Core.Services.CommandListsRegistryService.OnCommandExecutingHandler(Object sender, CancelableCommandEventArgs e)
   bei Mercury.TD.Client.UI.Components.CommandList.OnCommandExecuting(Object sender, CancelableCommandEventArgs e)
   bei Mercury.TD.Client.Library.WeakEvent.EventWrapper`1.OnExecute(Object sender, T args)
   bei Mercury.TD.Client.Library.WeakEvent.WeakEventHandler`1.Raise(IEventWrapper eventWrapper, Object sender, EventArgs args)
   bei Mercury.TD.Client.Library.WeakEvent.WeakEventHandler.DoRaiseEvent(Object sender, EventArgs args)
   bei Mercury.TD.Client.Library.WeakEvent.WeakEventHandler.RaiseEvent(Object sender, EventArgs args)
   bei Mercury.TD.Client.UI.Components.Command.OnExecuting(Object sender, CommandEventArgs args)
   bei Mercury.TD.Client.UI.Components.Command.OnExecute(Object sender, CommandEventArgs args)
   bei Mercury.TD.Client.UI.Components.Command.ExecuteEventHandler(Object sender, EventArgs eventArgs)
   bei Mercury.TD.Client.UI.Components.ThirdParty.Toolbars.CommandButtonTool.ToolClickHandler(Object sender, ToolClickEventArgs e)

 

Tags (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Captain
Captain

the problem could only be fixed by the upgrade to ALM QC 11.5

View solution in original post

0 Likes
4 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

When you say "servers" do you mean ALM application servers? Do you have two separate instances of ALM? If so, are they running the same version and patch level?

[If this post solves or helps solve your issue, mark the thread as solved and give KUDOS to the author for their assistance.]

(Opinions expressed in my postings are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any solution/suggestion posted.)
0 Likes
Highlighted
Captain
Captain

Yes, application servers, two separate instances, both are running the same ALM version and patch level. Both are running the same OS version and the same JBoss version.

 

... but there is a difference: one application server is behind our firewall, the second application server is before our firewall. The second server is accessed by some of our customers (as beta tester).

0 Likes
Highlighted
Captain
Captain

the problem could only be fixed by the upgrade to ALM QC 11.5

View solution in original post

0 Likes
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner
@ribalm/ Microfocus experts,

I recently applied patch 6 on top of alm 12.21 patch 5, I am getting same error message "specified cast is not valid" while executing custom workflow code.

Can this issue be fixed by making changes in custom workflow code or applying some other patch is only fix for this issue?

Please advise.

Regards,
Srihari

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.