Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

This forum is for IT Professionals who have questions/issues or other feedback about Forefront Identity Manager (FIM) 2010 suite

older | 1 | .... | 161 | 162 | (Page 163) | 164 | 165 | .... | 204 | newer

    0 0

    Hello There,

    Is it possible to integrate FIM\MIM with any ESB (Enterprise Service Bus e.g. IBM, ORACLE) platform and what will be the benefits or advantages to doing this.

    I am not an ESB expert but will just like to know why this will be likely scenario for Identity Management System Like MIM\FIM


    Akinzo


    0 0

    Hi,

    Whenever I am trying to create new user its giving me below postprocessing error on portal log.But user is getting created synced to active directory. Suddenly some access issue happened which we recovered but this issue started, Can somebody help.

    System.InvalidOperationException: There was an error generating the XML document. ---> System.InvalidOperationException: The type Microsoft.MetadirectoryServices.FunctionLibrary.NoFlowSingleton was not expected. Use the XmlInclude or SoapInclude attribute to specify types that are not known statically.
       at System.Xml.Serialization.XmlSerializationWriter.WriteTypedPrimitive(String name, String ns, Object o, Boolean xsiType)
       at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterRequestParameter.Write1_Object(String n, String ns, Object o, Boolean isNullable, Boolean needType)
       at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterRequestParameter.Write9_UpdateRequestParameter(String n, String ns, UpdateRequestParameter o, Boolean isNullable, Boolean needType)
       at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriterRequestParameter.Write11_RequestParameter(Object o)
       --- End of inner exception stack trace ---
       at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle, String id)
       at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o)
       at Microsoft.ResourceManagement.WebServices.WSResourceManagement.RequestType.AddParameter(RequestParameter parameter)
       at Microsoft.ResourceManagement.WebServices.WSResourceManagement.RequestType.SetRequestParameters(OperationType operation, UniqueIdentifier targetObject, List`1 requestParameters)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(CreateRequestDispatchParameter dispatchParameter)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause, Boolean doEvaluation, Nullable`1 serviceId, Nullable`1 servicePartitionId, Boolean maintenanceMode, String synchronizationSequenceIdentifier)
       at Microsoft.ResourceManagement.WebServices.RequestDispatcher.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier targetIdentifier, OperationType operation, String businessJustification, List`1 requestParameters, CultureInfo locale, Boolean isChildRequest, Guid cause)
       at Microsoft.ResourceManagement.Workflow.Hosting.RequestWorkItemProcessor.CreateRequest(UniqueIdentifier requestor, UniqueIdentifier objectId, OperationType operation, List`1 requestParameters, Guid parentRequest)
       at Microsoft.ResourceManagement.Workflow.Hosting.RequestWorkItemProcessor.ProcessPutWorkItem(UpdateRequestWorkItem updateWorkItem)
       at Microsoft.ResourceManagement.Workflow.Hosting.RequestWorkItemProcessor.ProcessWorkItem(WorkItem workItem)</RequestStatusDetail>

    Thanks,

    Venkatesh Mahajan


    0 0

    Hello,

    I change the scenario of Microsoft Identity Manager 2016, and so i must be reinstall it.

    I take a backup from FIM Synchronization db and FIMService DB. fim synchronization installed successfully but when i try to install service and portal the following error terminate the installation

    EXEC [setup].[ResetAttributeKey]
        @attributeObjectKey = @ob
        DateTime=2016-06-08T04:03:14.6982829Z
    Microsoft.ResourceManagement Verbose: 0 : Execute SQL : The transaction failed with the following errors System.Data.SqlClient.SqlException: The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (283).
    The DELETE statement conflicted with the REFERENCE c
        DateTime=2016-06-08T04:03:14.6982829Z
    Microsoft.ResourceManagement Error: 3 : The database upgrade fails to run the post-process sql script for configuration updates. 
    The error message: Execute SQL : The upgrade tool has rolled back. 
    The sql transaction running the script ConfigurationChange2004Attribute.sql failed. 
     Exception: System.Data.SqlClient.SqlException: The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (283).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (284).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (285).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (286).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (287).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (288).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (289).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (290).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (291).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (292).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (293).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (294).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (295).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (296).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (297).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (298).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (299).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (300).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (301).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (302).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (303).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (304).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (305).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (306).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (307).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (308).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (309).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (310).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (311).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (312).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (313).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (314).
    The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. Cannot insert duplicate key in object 'fim.AttributeInternal'. The duplicate key value is (315).
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
    The statement has been terminated.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
       at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.IdentityManagement.DatabaseUpgrade.Program.ExecuteSqlScript(SqlConnection connection, String sqlFile, Boolean embeddedAsResource, Boolean hasPlaceholders, Boolean continueOnError) 

        DateTime=2016-06-08T04:03:14.6982829Z
    Microsoft.ResourceManagement Verbose: 0 : Database upgrade : Out-of-box object upgrade completed.
        DateTime=2016-06-08T04:03:14.6982829Z
    Microsoft.ResourceManagement Verbose: 0 : Database upgrade : Out-of-box object upgrade complete with errors. Execute SQL : The upgrade tool has rolled back. 
    The sql transaction running the script ConfigurationChange2004Attribute.sql failed. 
     Exception: System.Data.SqlClient.SqlException: The DELETE statement conflicted with the REFERENCE constraint "FK_BindingInternal_AttributeInternal". The conflict occurred in database "MIMService", table "fim.BindingInternal", column 'AttributeKey'.
    Violation of PRIMARY KEY constraint 'PK_AttributeInternal'. 
        DateTime=2016-06-08T04:03:14.6982829Z
    Microsoft.ResourceManagement Error: 3 : Database upgrade : Encountered errors when upgrading the out-of-box objects.
        DateTime=2016-06-08T04:03:14.6982829Z
    Microsoft.ResourceManagement Verbose: 0 : The AppDomain's parent process is exiting.
        DateTime=2016-06-08T04:03:14.6982829Z


    0 0

    Hi,

    For the custom authorization workflows, what happens when we upgrade the assembly version and deploy into the system?

    Does all the authorization requests present in the FIM Portal associated with the earlier assembly version get cancelled? Or they will remain as it is and only the new requests that are created after the deployment will start making use of the new assembly version and the old ones will remain as it in "Authorizing" state, still providing the approver to approve/reject the request?

    Thanks,


    Veena


    0 0

    Hello guys,

    I've created a management agent to call 2 webservices(one for get data, another to delete data), I've already created all the functionality but when I did Full Import then in Event Viewer I get this error:

     

    The extensible extension returned an unsupported error.
     The stack trace is:
     "System.InvalidOperationException: Could not find endpoint element with name 'HTTP_Port' and contract 'SAPObtencion.SI_OS_ObtenerUsuarios' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found in the client element.
       at System.ServiceModel.Description.ConfigLoader.LoadChannelBehaviors(ServiceEndpoint serviceEndpoint, String configurationName)
       at System.ServiceModel.ChannelFactory.InitializeEndpoint(String configurationName, EndpointAddress address)
       at System.ServiceModel.ChannelFactory`1..ctor(String endpointConfigurationName, EndpointAddress remoteAddress)
       at System.ServiceModel.ConfigurationEndpointTrait`1.CreateSimplexFactory()
       at System.ServiceModel.ClientBase`1.CreateChannelFactoryRef(EndpointTrait`1 endpointTrait)
       at System.ServiceModel.ClientBase`1.InitializeChannelFactoryRef()
       at FimSync_Ezma.SAPObtencion.SI_OS_ObtenerUsuariosClient..ctor(String endpointConfigurationName)
       at FimSync_Ezma.EzmaExtension.GetImportEntries(GetImportEntriesRunStep importRunStep)
    Forefront Identity Manager 4.1.3419.0"

    I've added the reference webservice in the .sln on visual studio and did a build of the solution, obtaining 2 files -->main.dll and main.dll.config (both are on the Extensions folder), so why is not getting the info of the config file?

    Could you please help me to find out what I'm missing?

    Thank you so much for your response.


    0 0

    Hi,

    Hoping someone out there may have experienced this same issue.  I'm attempting to remove the value of a reference attribute attached to the "User" object in the FIM portal using an MPR / standard workflow.

    Based on the following link I have set up a workflow step to set the reference attribute to a space character

    https://social.technet.microsoft.com/Forums/en-US/bc2f6c99-5702-48ba-87b3-41eeb12dc40f/delelting-a-reference-value-in-fim-2010?forum=ilm2

    This kind of works in the sense that the attribute value is successfully removed, but a side effect is that the MPR looks like it is being called multiple times (when I look in "search requests" it is just filled with MPR calls to remove the attribute value on the same identity, the only option I have to stop them is to disable the MPR).

    I've tried using out of the box Function Evaluator and also using the Tools4FIM Function Evaluator to remove the reference attribute value, both display the same behaviour (the value is removed but multiple MPR calls are spawned).

    If I change the MPR to remove the value from a non-reference attribute (eg, a simple indexed string attribute) then the MPR is only called once as expected, so it seems to be specifically when trying to remove the value of a reference attribute.

    Details of how the MPR / Set / Workflow is configured is as follows :

    Requestors and Operations:

    set "Specific Set of Requestors" to "All Objects"

    Tick "modify a single-valued attribute" only

    Target Resources:

    Target Resource Definition Before Request is my configured Set of users

    Target Resource Definition After Request is the same Set as above

    Select specific attributes is selected and only the reference attribute is in the list of attributes

    Policy Workflows

    Has just the single workflow configured to run (Function evaluator step to set the reference attribute value to a single space character)

    Just wondering if anyone has seen the same thing ?

    We're using FIM 2010 R2 SP1 (4.1.3508.0)


    0 0

    We have a basic security group member sync from a portal to AD.

    The problem is that when we remove all the members from the security group in the portal and try to sync this to AD, the modification will not flow to AD. If I check the group from the metaverse, it says that member-attribute has been populated from the AD (Contributing MA has changed to ADMA) even the attribute flow presedence says that FIMMA is first one and ADMA the second one.

    Also if we use preview before before we run FIMMA Delta Sync, Import attribute flow section is saying Repopulation.

    What could be the problem?


    0 0

    Hello.

    Ive been trying to setup a test environment using MIM2016.

    I have everything setup, users coming in from AD, DG and SG populate within MIM, and using the admin account, I can see all the groups.   Logging in with a normal user however, I do not see any SGs.  I can see DGs, but no SGs.  I've rebuilt this server, and also built another test server from scratch, just to see if I missed something, but it still has the same results.  Originally I was using the MIM2016 deploy guide, but it doesn't have anything about self group management, which is the main reason I want to use this in production.

    https://docs.microsoft.com/en-us/microsoft-identity-manager/deploy-use/microsoft-identity-manager-deploy

    Since there isn't much info for MIM2016, I used FIM2010R2 TechNet guide:

    https://technet.microsoft.com/en-us/library/jj150428(v=ws.10).aspx

    Any ideas on what I am missing?  If I add the user to the "Group Administrators" set, they can see SGs fine.  But according to the PFE that I'm working with, this should not be necessary (nor is it listed anywhere in any of the FIM build guides I've seen.)

    Thanks for any help, this has been giving me migraines....   x.X

    Ken 


    0 0

    Hi all,

    I've built a custom workflow for a customer that takes a template that's assigned to a user on creation and enumerates all groups which has this template as a member, adding the user to the same groups.

    It works fine, but it's horrendously slow.  In their environment of 6688 groups and 39543 users, it's taking around 30 minutes to complete the workflow.

    Running the same XPath in Powershell is just as slow, unless I specify -OnlyBaseResources on Export-FIMConfig, in which case it completes the enumeration in around 20 seconds.  There's no way of doing the same in the workflow activity, is there? Any suggestions as to how to make it quicker?  I'm leaning towards using Craig Martin's (excellent) Powershell activity to do the same, just so I can specify the -OnlyBaseResouces option.

    Thanks in advance.

    Paul.


    0 0

    Hi,

    We have a FIM 2010 R2 environment that has been up and running and happy for over a year now.

    A few days ago we started receiving errors when exporting to AD with Exchange 2010. We get an extension-dll-timeout error, sometimes followed by an unexpected-error on the next object. The export run takes three minutes and then stops, leading me to believe this may be related to WsManConnectionInfo timing out perhaps. The event log shows the following error message:

    "There is an error in Exch2010Extension AfterExportEntryToCD() when exporting an object with DN [valid DN here]"

    Type: Microsoft.MetadirectoryServices.TerminateRunException

    Message: PowerShell runspace is not initialized. This can happen when the host process was restarted in the midle of the export run."

    [Note that the misspelling of "midle" is in the error message.]

    There were recently changes to the Exchange servers, so I'm assuming the problem is a setting there, but the Exchange team is convinced their stuff is fine.

    Does WsManConnectionInfo seem like a reasonable culprit? Is there a way to increase the default timeout from three minutes (maybe a registry setting)? Or maybe something else? If anyone has a solution I would appreciate it. Been working on this off and on for a few days and am a bit stumped.

    Thank you!




    0 0

    Hello

    I've developed a custom agent (ECMA 2.3?, MIM 4.3.2195.0), for some time it's worked as expected, but after adding some new features it's broken.

    MACapabilites.ExportType is set to AttributeUpdate, that's mean for multivalued attribute to take care of deletes old and adds new values and bring them to export phase.

    Case: Object Obj with multivalued attribute Attr changed value from M to N

    On export csentry have such settings:

    Correct behavior (Was)

    1. Obj.ObjectModificationType set to ObjectModificationType.Update
    2. Attr.ModificationType set to AttributeModificationType.Update
    3. M.ValueChanges.ModificationType set to ValueModificationType.Delete
    4. N.ValueChanges.ModificationType set to ValueModificationType.Add

    Incorrect behavior (Now)

    1. Obj ObjectModificationType set to ObjectModificationType.Update
    2. Attr.ModificationType set to AttributeModificationType.Replace
    3. N.ValueChanges.ModificationType set to ValueModificationType.Add

    Current behavior is same as in ECMA 2.0 or ExportType = AttributeReplace.

    I've checked ExportType in run-time and MIM DB table [dbo].[mms_management_agent], ExportType is 1 (AttributeUpdate).

    I don't want to recreate agent as it has accumulated data saved in CS, and it's painful to lost it. Need your help:)




    0 0
  • 06/13/16--00:30: how to stop start up sign in
  • how do I take my password sign in off at start up

    0 0

    Does anyone know if there is an installation walk-through for just installing MIM 2016 for Galsync?


    Orange County District Attorney


    0 0
  • 06/14/16--00:36: Password Reset Fails
  • I installed MIM 2016 on test lab before deploy in production.

    user is able to register in Registration portal. The problem when user try to reset password on portal, error appear : Error while attempt to reset password.

    I tried to troubleshoot and searched for solutions but couldn't find a solution.

    Noting that I didn't make any changes in DC group policy. do I have to make any changes in group policy????

    Please help.

    Thanks.


    0 0

    I'm getting this error in Synchronization Service Manager every time after I run full import with one of my management agents (uses extension). Can you tell me a way to fix this? I read somewhere that the cause of error might be that dll was changed in FIM extension folder when running management agent, so is the problem with management agents dll that I'm getting error on?

    0 0

    Greeting Dear Community, Thanks for reading & the help!

    I am new to FIM 2010 and my organization.

    Our organization uses FIM 2010. We have a project that we need to migrate the current domainname/username to a new domainname/username. Our final goal is let us to do single sign-on.

    The backoffice uses a legacy HR app that's runs Oracle, we have plans to migrate to SAP in 2019

    And we have issues that the active directory of our network is consistently NOT in sync with our HR apps.

    FIM2010 manages our AD.

    The current process is our sys-admin will export the content of AD & Oracle will import the file and conciliate  the two sets of data. One from AD & one from our HR apps.

    From business process perspective, it would make sense that FIM2010 can communicate with the HR apps and generate the AD info.

    Can FIM2010 pull data from Oracle ???

    How would you all see the solutions of this project ??

    Where I can read up on for how FIM2010 can integrate with other apps ??

     




    0 0

     

    شركة صيانة هيتاشى الاولى فى مصر

    نحن نعمل جاهدين على راحه عملائنا فى صيانة هيتاشى بالضمان الشامل على الجهاز بالكامل

    توكيل هيتاشى

    صيانة تكييفات هيتاشى

    صيانة تكييفات هيتاشى

    خدمة اصلاح تكييفات هيتاشى

    ارقام صيانة هيتاشى

    0235682820 // 01154008110 // 0235710008 // 01092279973

    اسطول صيانة متنقل ل اصلاح وصيانة اجهزة هيتاشى بالمنزل والضمان الشامل

    احنا رائدون في صيانة جميع اجهزة هيتاشى

    الصيانةالفورية بالمنزل

    صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى

    صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى

    صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى

    صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى

    صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى

    صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى

    صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى

    صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى صيانة هيتاشى

     

    متميزون فى صيانة هيتاشى (( قطع غيار اصلية )) ((ضمان شامل ))

    قسم خاص للتجديد الجهاز بالكامل (( صيانة هيتاشى الاول فى مصر )) اصلاح فورى بالمنزل

    كول سنتر 24 ساعة

    سيارات مجهزة للاصلاح بالمنزل

    خدمةسريعه للاصلاح اجهزة هيتاشى

    0235682820 // 01154008110 // 0235710008 // 01092279973

    الحماية الكاملة full protection الحماية الكاملة full protection الحماية الكاملة full protection الحماية الكاملة full protection الحماية الكاملة full protection الحماية الكاملة full protection الحماية الكاملة full protection الحماية الكاملة full protection الحماية الكاملة full protection الحماية الكاملة full protection

     

    hitachi hitachi hitachi hitachi   hitachi hitachi hitachi  hitachi   hitachi hitachi

     hitachi hitachi

    hitachi hitachi hitachi hitachi   hitachi hitachi hitachi hitachi   hitachi hitachi hitachi hitachi

    hitachi hitachi   hitachi hitachi  hitachi hitachi hitachi hitachi  hitachi hitachi hitachi hitachi

    hitachi hitachi hitachi hitachi   hitachi hitachi hitachi hitachi  hitachi hitachi hitachi hitachi

    hitachi hitachi hitachi hitachi   hitachi hitachi hitachi hitachi  hitachi hitachi hitachi hitachi

    hitachi hitachi hitachi hitachi   hitachi hitachi hitachi hitachi  hitachi hitachi hitachi hitachi

    hitachi hitachi hitachi hitachi   hitachi hitachi hitachi hitachi  hitachi hitachi hitachi hitachi

     

    خدمة عملاء هيتاشى : 02.35699066 || 02.35710008

    مركز صيانة هيتاشى : 01154008110 // 01092279973

    الوكيل هيتاشى ؛02.35699066

    توكيل هيتاشى ؛02.35710008

    وكيل هيتاشى توكيل  هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة تكييف هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى وكيل  هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة تكييف هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى

    وكيل هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة تكييف هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى وكيل  هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة تكييف هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى

     

     

     

    وكيل هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة تكييف هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى وكيل  هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة ديب

    وكيل هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة تكييف هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى وكيل  هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة تكييف هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى

    تكييفاتهيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء

    شركة صيانة هيتاشى تعطى ضمان عام كامل على الصيانة

    ومتابعه كل ثلاثة اشهر لضمان جوده الخدمة

    الاصلاح الفورى بالمنزل

    قطع غيار اصلية

     

    خدمة عملاء هيتاشى : 02.35699066 || 02.35710008

    مركز صيانة هيتاشى : 01154008110 // 01092279973

    الوكيل هيتاشى ؛ 02.35699066

    توكيل هيتاشى ؛ 02.35710008

    وكيل هيتاشى توكيل  هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة تكييف هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى وكيل  هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة هيتاشى هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى

    وكيل هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة هيتاشى هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى خدمة عملاء هيتاشى وكيل  هيتاشى توكيل هيتاشى صيانة تكييفات هيتاشى اصلاح تكييفات هيتاشى صيانة هيتاشى هيتاشى صيانة تكيف هيتاشى مركز صيانة هيتاشى توكيل صيانة تكييفات هيتاشى

     

    صيانة هيتاشى الدقي - صيانة هيتاشى الزيتون - صيانةهيتاشى المعادي - صيانة هيتاشى الزمالك - صيانة هيتاشى مصر الجديدة - صيانة هيتاشى مدينة نصر - صيانة هيتاشى الهرم - صيانة هيتاشى المهندسين - صيانة هيتاشى حلمية الزيتون - صيانة هيتاشى حدائق الهرم - صيانة هيتاشى عين شمس - صيانة هيتاشى القاهرةالجديدة - صيانة هيتاشى فيصل - صيانة هيتاشى العباسية - صيانة هيتاشى حدائق القبة - صيانة هيتاشى حدائق حلوان - صيانة هيتاشى حلوان

     


    0 0

    I enter the date on a User edit RCDC form in the Portal. Using the default OOB user edit form.

    The hint tells me to enter the date as d.MM.yyyy so I have entered 1.7.2016 0:00:00

    When I send an Email notiification the value in [//Target/EmployeeStartDate] is shown as 2016-06-30 21:00

    What is happening here?


    0 0

    Hi, 

    I am using Domino Connector 8.x on FIM 2010 R2 . 

    The Global Parameter options are:

    Perform Import by :Search

    Enable creation of _contact objects :Non-Reference values

    Exclude Conflict Objects is checked

    I am able to perform Export and Full Import. But Delta import is not fetching records . When i am running Delta Import , status shows as :completed-transient-objects and No records are fetched.

    Any help will be appreciated. Thanks!!


    0 0

    I've upgraded my development FIM 2010 R2 environment to MIM 2016 (4.3.2195) on new virtual servers (same underlying hardware).  The OS is Server 2012 R2 and SQL is 2014 Standard (12.0.4213.0). I'm getting hundreds of failed-modification-via-web-services errors when exporting to the FIM connector which look to be due to deadlocks:

    Stack Trace: Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---&amp;gt; System.Data.SqlClient.SqlException: Reraised Error 50000, Level 13, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 50000, Level 13, State 1, Procedure ReRaiseException, Line 37, Message: Reraised Error 1205, Level 13, State 51, Procedure GenerateRequestOutput, Line 1148, Message: Transaction (Process ID 110) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
       at System.Data.SqlClient.SqlConnection.OnError

    I've worked with my DBA and we've tweaked a few things on the SQL side (including adding RAM and moving disk to new SAN storage), but it doesn't seem to have helped much at all.  My FIM 2010 setup seemed to handle largish volumes of updates like this (3000+) relatively error-free.  I'm hesitant to upgrade my production environment without resolving this, since that volume of change does occur there periodically as well.  Is there tuning I can do to reduce or eliminate this problem?  What additional information about my setup would be helpful?  Most of the person updates that are failing look to be minor and not really different from those that appear to be succeeding.

    -Robert
    UW-River Falls


older | 1 | .... | 161 | 162 | (Page 163) | 164 | 165 | .... | 204 | newer