0
Answered

Method not found when trying to get Schema

Carol Wapshere 1 week ago • updated by Curtis Lusmore 6 days ago 14

Trying to request schema for an HPE Content Manager connector and I get the following error:

An error has occurred: Method not found: 'Unify.Product.IdentityBroker.IEntitySchemaConfigurationUtility Unify.Product.IdentityBroker.IMultiKeyedConnectorFactoryInformation.get_SchemaConfigurationUtility()'.

Is this because the connector doesn't support schema retrieval, or have I done something wrong?

The Agent test connection succeeds, and that's as far as I've got.

Affected Versions:
Fixed by Version:

Answer

Answer

The original issue

An error has  occurred: Method not found: 'Unify.Product.IdentityBroker.IEntitySchemaConfigurationUtility
Unify.Product.IdentityBroker.IMultiKeyedConnectorFactoryInformation.get_SchemaConfigurationUtility()'

is not environmental, will only depend on the version of Broker and all patches installed, and will require a patch to fix. If you didn't experience this issue in lower environments, there must be a difference in what is installed. If schema retrieval works in Dev, make sure that what is installed in Dev is also installed in higher environments. If it doesn't, please try upgrading Dev to confirm that the upgrade will resolve the issue.

Also - would this also mean I'd have to update Aurion and MIM components?

No, upgrading UNIFYBroker from v5.3.1.0 to v5.3.1.1 will not require updating other components.

Under review

Hi Carol,

Can you please provide the versions for UNIFYBroker and the UNIFYBroker/HPE Content Manager connector?

IDB v5.3.1 Revision #0

HPE CM connector v5.3.0.0


Further on this - I've manually set up the schema the same as the CASA solution, but when I try to run an Import All I get the error below.

I can successfully open the page http://HPECMServiceAPI/Location and run ad-hoc queries on Location objects, so I think that means the Service API is functional. I have also done a Wireshark trace and I can see the json data being sent back.

The CM version is 9 build 1.2.1107.

I'll send the Agent and Connector files separately by email. Here's the error reported in Broker:


Change detection engine import all items failed.
Change detection engine import all items for connector CM Persons failed with reason Value cannot be null.
Parameter name: source. Duration: 00:00:00.4062545
Error details:
System.ArgumentNullException: Value cannot be null.
Parameter name: source
at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source)
at Unify.Product.IdentityBroker.HPTrimV9WebCommunicator.<>c.b__43_0(RestLocationResult result)
at System.Linq.Enumerable.WhereArrayIterator`1.MoveNext()
at Unify.Product.IdentityBroker.HPTrimV9WebCommunicator.RestWorkaround(IWebServiceCommunicatorInformation information, IEnumerable`1 fields, Boolean includeAccessControls, String searchQuery, Int32 pageSize)
at Unify.Product.IdentityBroker.HPTrimV9WebCommunicator.d__30.MoveNext()
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at Unify.Framework.Collections.EnumerableExtensions.d__10`1.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source)
at Unify.Product.IdentityBroker.AuditReadingConnectorDecorator.GetAllEntities(IStoredValueCollection storedValues, CancellationToken cancellationToken)
at Unify.Product.IdentityBroker.EventNotifierReadingConnectorDecoratorBase`1.GetAllEntities(IStoredValueCollection storedValues, CancellationToken cancellationToken)
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.ImportAllChangeProcess()
at Unify.Product.IdentityBroker.ChangeDetectionImportAllJob.RunBase()
at Unify.Framework.DefinedScopeJobAuditTrailJobDecorator.Run()
at Unify.Product.IdentityBroker.ConnectorJobExecutor.<>c__DisplayClass30_0.b__0()
at Unify.Framework.AsynchronousJobExecutor.PerformJobCallback(Object state)

Hi Carol,

I wasn't able to reproduce this using the latest version of UNIFYBroker (v5.3.1 Revision #1). Are you able to try updating to the latest version?

Not easily - Broker is installed across four environments. Are you sure it is this? Once I upgrade Dev I'll be in change control hell to get the rest upgraded.

Also - would this also mean I'd have to update Aurion and MIM components?

Answer

The original issue

An error has  occurred: Method not found: 'Unify.Product.IdentityBroker.IEntitySchemaConfigurationUtility
Unify.Product.IdentityBroker.IMultiKeyedConnectorFactoryInformation.get_SchemaConfigurationUtility()'

is not environmental, will only depend on the version of Broker and all patches installed, and will require a patch to fix. If you didn't experience this issue in lower environments, there must be a difference in what is installed. If schema retrieval works in Dev, make sure that what is installed in Dev is also installed in higher environments. If it doesn't, please try upgrading Dev to confirm that the upgrade will resolve the issue.

Also - would this also mean I'd have to update Aurion and MIM components?

No, upgrading UNIFYBroker from v5.3.1.0 to v5.3.1.1 will not require updating other components.

I'm in DEV - the CM connector is only installed in DEV, and it's not working there.

My comment was about Broker itself, which is also in Test, UAT and Prod with the Aurion connector installed.

Do you expect this to also fix the issue with not being able to import any data - source value Null? That's the real blocker.

Oh okay, thanks for clarifying. I'll look at the "source value Null" error now, but could you please provide the logs with the full stack trace for the original error?

That has fixed the schema issue.

Sorry for combining two things on one thread - do you want me to start a new one for the import issue (which is still there)?

Thanks for the update.

We can split it out later. Can you please send me the network trace you mentioned earlier with the JSON reponse?

Can you please try placing this patch into the Services directory and re-trying the import?

Unify.IdentityBroker.Communicator.HPTrim.We....dll

You did it! Just imported some locations :-)

Answered
Excellent news. The patch should be available in the next release of the UNIFYBroker for HPE Content Manager connector.