1. UNIFYBroker Forum
  2. UNIFYBroker/Micro Focus Content Manager
  3. Questions
0
Answered

HPRM provisioning error

Paul Zelenewicz 6 years ago in UNIFYBroker/Micro Focus Content Manager • updated by Beau Harrison (Senior Product Software Engineer) 6 years ago • 3

UNIFYBroker 5.3.1

HP Trim Connector 5.3.0.0

Currently getting the following error on user provision to HPRM:


System.ArgumentException: Could not parse uri string
"genericuser" to long value for setting uri of reference field
LocationUseProfileOf.
   at
Unify.Product.IdentityBroker.RequestFactory`2.SetLocationPropertyRefValue[TRef](PropertyIds
propertyId, IConnectorEntity data, Func`1 createRef, Action`1 assign)
   at
Unify.Product.IdentityBroker.LocationRequestFactory.CreateComponent(ILocationRequestFactoryInformation
info)
   at
Unify.Product.IdentityBroker.HPTrimV8WebRequests.AddLocationRequest(IConnectorEntity
data)
   at
Unify.Product.IdentityBroker.HPTrimV8WebCommunicator.AddLocations(IEnumerable`1
data, Guid connectorId, IWebServiceCommunicatorInformation information,
CancellationToken cancellationToken)
   at
Unify.Product.IdentityBroker.HPTrimWebCommunicatorDecorator.AddLocations(IEnumerable`1
data, Guid connectorId, IWebServiceCommunicatorInformation information,
CancellationToken cancellationToken)
--- End of stack trace from previous location where
exception was thrown ---
   at
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at
Unify.Product.IdentityBroker.HPTrimWebCommunicatorDecorator.AddLocations(IEnumerable`1
data, Guid connectorId, IWebServiceCommunicatorInformation information,
CancellationToken cancellationToken)

I suspect that this is due to a user with the URI of 'genericuser' not existing within HPRM. 

Can you please confirm.

GOOD, I'M SATISFIED
Satisfaction mark
Satisfaction mark by Paul Zelenewicz 6 years ago
Under review
Beau Harrison (Senior Product Software Engineer) 6 years ago

Hi Paul

Uris in HPRM are numeric, so 'genericuser' being used as a uri is not correct. Check that in IdB all uri fields are set as 'long' type, and that any MA/PowerShell/etc mapping to uri fields is being done correctly.

If that is all ok, attach configuration files and I will look into this issue further.

Paul Zelenewicz 6 years ago

Thanks for the explanation Beau,

I found that there is a config helper file which contains the URI value for the 'generic user' template to use for provisioning.

This currently contains the value 'genericuser' but it makes sense that it actually should contain the numeric URI value of the generic user.

Answered
Beau Harrison (Senior Product Software Engineer) 6 years ago

Customer support service by UserEcho