Identity Broker Forum

Welcome to the community forum for Identity Broker.

Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.

0
Answered

UNIFY Management Studio always installs to ~\Program Files (x86)\UNIFY Solutions\Management Studio

Bob Bradley 14 years ago updated by anonymous 9 years ago 5

When deploying the management console I tried overriding the default C:\Program Files (x86)\UNIFY Solutions\Management Studio but the software was installed to C:\Program Files\UNIFY Solutions\Management Studio regardless. Not unhappy that it splits it out this way, but it's not the option I selected.

0
Fixed

Can you change the installation directory for the IdB Service?

Daniel Walters 14 years ago updated by anonymous 9 years ago 9

The Identity Broker Service has been written up to be installed on a D: drive here at DET but the installer : "UNIFY Identity Broker Service v3.0.6 x64" does not give an option to select the installation directory. Is there any way to get it installed on the D: drive? Moving the files doesn't work because then the service isn't pointing to the executable.

0
Fixed

Identity Broker Service fails to start (timeout) when removing connectors/adapters

Ross Currie 14 years ago updated by anonymous 9 years ago 10

Thought I'd added this one already, but can't see it....

Essentially what happens here is that when you start the Identity Broker service, it has a database timeout. I don't have the exact log message, but I can reproduce and will do so once I finish working in the environment I'm in (next week). Removing all connectors/adapters from the config has no impact. Clearing the database allows the service to restart.

My understanding is that this error is caused by Identity Broker's clean-up process that occurs during startup... for example, if a connector has been removed, Identity Broker deletes all entities in that connector... etc.

The issue comes in where you have large volumes of data. The time taken to run the entity deletion command exceeds Identity Broker's database timeout.

This can cause problems in development environments where you are chopping and changing connectors/adapters quite regularly. In production it's not as big an issue, though it can have some impact.

Two work-arounds:
1) Leave all connectors/adapters in when testing new ones.. just extend timings
2) Manually delete entities for those connectors/adapters you're removing from the Entity table before

The description for Event ID 0 from source The following error in Identity Broker occurred during start of the server: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Error occurred in module: Identity Broker

The following error occurred:
System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
at System.Data.Linq.ChangeDirector.StandardChangeDirector.DynamicDelete(TrackedObject item)
at System.Data.Linq.ChangeDirector.StandardChangeDirector.Delete(TrackedObject item)
at System.Data.Linq.ChangeProcessor.SubmitChanges(ConflictMode failureMode)
at System.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode)
at System.Data.Linq.DataContext.SubmitChanges()
at Unify.Data.LinqContextConversionBase`4.DeleteItems(HashSet`1 deletedItems, TContext sourceContext, SqlConnection connection)
at Unify.Data.LinqContextConversionBase`4.SubmitChanges()
at Unify.Framework.IdentityBrokerEngine.SetUpEntityRepositoryPartitions(IEnumerable`1 connectorConfigurationCollection, IEnumerable`1 adapters)
at Unify.Framework.IdentityBrokerEngine.Start()
at Unify.Framework.UnifyEngine.Start()


withAllMinusIncludesOnIndex.sqlplan
withAllSelect.sqlplan
withoutEntityValueIncludesIndex.sqlplan
0
Fixed

Placeholder Connector Changes

Peter Wass 14 years ago updated by anonymous 9 years ago 6

Summary Watchers
The placeholder connector does not appear to trigger the changes plugin in Unify Now. This is an issue where the placeholder is used to generate transformation data for a different object. when the placeholder changes the other object should have a change registered so that it can trigger the UN import.

0
Completed

'Refresh' Entity Viewer

Peter Wass 14 years ago updated by anonymous 9 years ago 1

A 'Refresh' Button on the Entity Viewer which does a requery of the entities. Currently it seems to use a cache (which is faster) but it doesn't refresh when I want it requiring me to restart the server.

Shane Day It no longer uses a cache on the server. Would still be useful to provide a refresh button.

0
Fixed

Fix schema validation error message

Shane Day (Chief Technology Officer) 14 years ago updated by anonymous 9 years ago 2

The schema validation error messages should be updated to include connector names as well as IDs. For example:

20100203,10:43:00,An entity failed validation.,Adapter,Warning,The entity d8569f97-658b-4f4f-8764-9bb9dce3cf0f on connector cb5776a7-948e-456e-bf90-79881424e2eb failed validation 2 times for the following reasons: The field mailType with value WSS is not specified in the schema.; MAIL_TYPE is a required field and is not present.,Normal

Does not include the name of the connector.

0
Fixed

Error msg for missing dataConnection node

Adam van Vliet 14 years ago updated by anonymous 9 years ago 5

As some of the demo extensibility files do not contain the dataConnection node, it could be easy to miss this item out when creating the full extensibility file.
Currently only a generic exception is thrown, a better exception may be helpful.

0
Completed

Better reporting of error when attempt to save item to adapter with a null key value.

Shane Day (Chief Technology Officer) 14 years ago updated by anonymous 9 years ago 4

As originally reported in FINANCE-30, and resolved with that issue, when a item is to be saved, and one of the key values is null, the following error is displayed:

Errors:
Timestamp	Severity	Source	Module	Message
3/02/2011 1:30:02 PM	Error	Logging	Logging	"Unable to raise start notification:

System.NullReferenceException: Object reference not set to an instance of an object.
at Unify.Framework.MultiKeyValue.<ToString>b__0(IValue value)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArrayTSource(IEnumerable`1 source)
at Unify.Framework.MultiKeyValue.ToString()
at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args)
at System.String.Format(IFormatProvider provider, String format, Object[] args)
at System.String.Format(String format, Object arg0, Object arg1, Object arg2)
at Unify.Notification.ConnectorModifyAnchorEntityNotificationFactory.GetConnectorServiceProcessDetail()
at Unify.Notification.ConnectorNotificationFactory.GetServiceProcessDetail()
at Unify.Notification.TaskNotifier`1..ctor(INotificationMessageService messageService, T factory)"

Timestamp	Severity	Source	Module	Message
3/02/2011 1:30:02 PM	Warning	Adapter request to save entity to adapter space failed.	Adapter	"Adapter request to save entity 531f8d06-81b1-488f-b5e8-6dc932a0093d
to adapter space 278900c3-9b42-4c36-9400-6f1e5eb3354a failed with reason Object reference not set to an instance of an object.. 
Duration: 00:00:00.1718750
Error details:
System.NullReferenceException: Object reference not set to an instance of an object.
at Unify.Notification.TaskNotifier`1.Dispose()
at Unify.Framework.EventNotifierModifyAnchorConnectorDecorator.ModifyAnchor(MultiKeyValue oldKey, MultiKeyValue newKey)
at Unify.Framework.Adapter.<>c_DisplayClass34.<CheckAnchorChangeOnSave>b_2f(KeyValuePair`2 keyValue)
at Unify.Framework.Visitor.<>c_DisplayClass1`1.<Visit>b_0(T item, Int32 index)
at Unify.Framework.Visitor.VisitT(IEnumerable`1 visitCollection, Action`2 visitor)
at Unify.Framework.Visitor.VisitT(IEnumerable`1 visitCollection, Action`1 visitor)
at Unify.Framework.Adapter.CheckAnchorChangeOnSave(IEntitySchema connectorSchema, IEnumerable`1 entitiesToSave, IEntityPartitionUpdatableContext connectorContext, IEnumerable`1 entityIds)
at Unify.Framework.Adapter.SaveEntities(IEnumerable`1 entities, Boolean reflect)
at Unify.Framework.Adapter.SaveEntity(IAdapterEntity entity, Boolean reflect)
at Unify.Framework.Adapter.SaveEntity(IAdapterEntity entity)
at Unify.Framework.AdapterNotifierDecorator.SaveEntity(IAdapterEntity entityToSave)
at Unify.Framework.LDIFAdapter.ExportAdapterEntity(IAdapterEntity adapterEntity, Guid adapterId)
at Unify.Framework.LDIFAdapterServiceHostDecorator.ExportAdapterEntity(IAdapterEntity adapterEntity, Guid adapterId)
at SyncInvokeExportAdapterEntity(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)"

It would be better if an explanation is given instead of a NullReferenceException.

0
Fixed

Incorrect display of Identity Broker icon in taskbar - while on 'Combine when taskbar is full'

Tony Sheehy 14 years ago updated by anonymous 9 years ago 2

When the taskbar buttons property is set to 'Combine when taskbar is full' the default shortcut icon appears, instead of the UNIFY Management Studio icon showing.


incorrect-icon.png
0
Fixed

Unable to create Event Source in Windows Server 2008

Shane Day (Chief Technology Officer) 14 years ago updated by anonymous 9 years ago 17

Win Event Loggers are unable to create log entries in Windows Server 2008.

This should be resolved as this means start up errors are not able to be logged on services, or Password Reset.


e.zip