Upgrade issue from OnBase 16 to OnBase 19 (EP1 Foundation)

[Ramy_Mohareb]

After OnBase 16 upgraded to OnBase EP1 Foundation, we have an issue that once user open OnBase they face a bad error in the login page, and also on the upload page. Workflows are not showing in Unity client also, although available in studio.

All users face the same issue.

Error 1:

The value -100 for itemTypeID can not be less than zero
Parameter name: itemTypeID
Actual value was -100.

Error 2:

System.ArgumentOutOfRangeException: The value -100 for itemTypeID can not be less than zero
Parameter name: itemTypeID
Actual value was -100.
   at Hyland.Workflow.Shared.Guard.VerifyArgumentGreaterThanEqualZero(Int64 val, String argumentName)
   at Hyland.Workflow.LifeCycleAssociatedItemType..ctor(Int64 lifeCycleID, Int64 itemTypeID, Int64 flags)
   at Hyland.Workflow.Core.Data.LifeCycleDataAccess.GetUnityLifeCycleIdToAssociatedItemTypes(String dataSourceName)
   at Hyland.Workflow.Core.DataSourceCache.<>c__DisplayClass38_0.<GetUnityLifeCycleIdToAssociatedItemTypes>b__0()
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at System.Lazy`1.get_Value()
   at Hyland.Workflow.Core.DataSourceCache.AddOrGetExisting(String dataSourceName, String cacheKey, Func`1 fnValueFactory)
   at Hyland.Workflow.Core.DataSourceCache.AddOrGetExisting(String dataSourceName, DataSourceCacheKey cacheKey, Func`1 fnValueFactory)
   at Hyland.Workflow.Core.DataSourceCache.GetUnityLifeCycleIdToAssociatedItemTypes(String dataSourceName)
   at Hyland.Workflow.Core.UnityLifeCycle.get_AssociatedItemTypeIDs()
   at Hyland.Core.Workflow.Services.Canvas.ServiceImpl.ClientServiceImpl.<>c.<.cctor>b__72_5(ILifeCycle lc, Object obj)
   at Hyland_Workflow_ILifeCycleElementSerializer-1197463521.CreateElement(Element , Object , Object )
   at Hyland.Types.Serialization.ElementSerializer`1.CreateElement(Element element, T item, Object state)
   at Hyland.Types.Serialization.ElementSerializer`1.CreateElement(T item, Object state)
   at Hyland.Types.Serialization.ElementSerializer`1.CreateElementList(IEnumerable`1 list, Object state, Predicate`1 predicate)
   at Hyland.Types.Serialization.ElementSerializer`1.CreateElementList(IEnumerable`1 list, Object state)
   at Hyland.Core.Workflow.Services.Canvas.ServiceImpl.ClientServiceImpl.GetWorkflowInitData(Session session, Boolean includeGenericWorkflow)
   at Hyland.Core.Workflow.Services.Canvas.Workflow.Initialize()

[Ryan_Wakefield]

I would highly recommend contacting FLOS. This error would be better addressed by them due to EP1 being so new.

[Ramy_Mohareb]

First line of support still investigating 

[Ramy_Mohareb · Accepted solution]

This issue impacted production badly, we couldn’t wait long time for support to come back after weekend, as they responded that they can’t work on this issue during weekend, as its very complicated and has to wait for high skilled people during the week working hours and it’s not severity 1 !! while customer was furious and it compromised the customer confidence in us and in the product.

After deep investigation we are able to rectify the issue.

Our Analysis: Before the upgrade, Doc type “SYS Defaults - Not To Be Assigned” of itemtypenum “-100” was unintentionally assigned to a lifecycle in studio that was created for reason to do a particular global functionality for all importer documents. This particular unintentional configuration of that doc type caused the problem after the upgrade. It worked fine for OnBase 16 and assumingly for all OnBase versions pre-OB19EP1 Foundation, but due to new logic of pre-checking in new software of OnBase19 when opening OnBase, workflow tab, import , etc.. , it was breaking. Those prechecks Were not there in previous versions of OnBase. That was the issue.

Our Rectification:: When we removed the assignment of that doc type from the lifecycle, all issues Were resolved for all the users, workflows are showing, import and login errors disappeared.

Please Note the above bug in order not to face other customers as well while upgrading to OnBase 19 EP1

[Ryan_Wakefield]

I am definitely glad you guys found this out and were able to resolve it. Hopefully nothing more like this happens going forward for you guys.