Hi Product Team,

On some import change imports from MA to Adapter, the import on the adapter keeps status is marked as running regardless if it has been completed

Screenshot attached

Schedules not running as shown to Tony.
May be related to TATTS-25, however the configurations were changed as advised.

Logs to be uploaded shortly.

I’m troubleshooting an issue at TAFE where the Unify web service for managing user profiles is throwing HTTP400 errors currently and was hoping you might be able to provide some guidance on where to look next.

On Richard’s advice I’ve done a WCF trace capture from the Identity Broker side and have found the following error occurring:
System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

I’ve looked through the Sharepoint logging and not found anything indicating what could be happening – therefore was hoping that you might be able to advise if there is a way to capture logs/debug the Unify solution that has been deployed within Sharepoint.

This is a continuation of the CIT / SSICT implementation.

Updates pushed into Identity Broker from FIM aren't presented to NIM as updates.

Here is an extract of the NIM DirXML logs that shows the error message:

5/06/2012 15:04:36.12v: 0 CIT Driver L3 PT:UnifyPublicationShim: polling
5/06/2012 15:04:36.12v: 0 CIT Driver L3 PT:UnifyPublicationShim: createWebServiceInterface: URL: http://192.168.16.230:59990/IdentityBroker/NIMDriver.svc?wsdl
5/06/2012 15:04:36.12v: 0 CIT Driver L3 PT:UnifyPublicationShim: createWebServiceInterface: Creating service
5/06/2012 15:04:36.13v: 0 CIT Driver L3 PT:UnifyPublicationShim: createWebServiceInterface: Creating interface
5/06/2012 15:04:36.14v: 0 CIT Driver L3 PT:UnifyPublicationShim: createWebServiceInterface: Returning port
5/06/2012 15:04:36.69v: 0 CIT Driver L3 PT:UnifyPublicationShim: javax.xml.ws.soap.SOAPFaultException: Specified method is not supported.

Placeholder connectors with no key set will fail during export due to a ArrayOutOfBoundsException.

Instead, the service should not start if there is no key.

I know we've had issues with this one in the past, but as FIM/TeamCity are two prominent examples of it seeming possible and we generally only target 2008 R2 + these days we should take another look.

Custom actions may also have been a problem before because of 2008 certification, but 2012 only suggests the following is not allowed:

Nested install custom actions (type 7, 23, and 39)

EDIT: This would be in the form of a checkbox where people can opt out.

IdB provides meaningless GUIDs instead of name when reporting errors in UI. Need to provide name of connector or adapter.

Example:
Adapter import all entities for adapter e14dde8a-73ff-4723-acbd-b34f5cb38ac0 failed with reason EMAIL_ADDR is not a valid LDAP attribute name Parameter name: attributeName. Duration: 00:00:01.1860000

New c21 users do not have their position populated in ILM until VERY late in their lifecycle (sporadic population of position data). As a result users do not have any associated position information / manager details etc at provision time.

I have not seen this at any other client site.

Example User
Employee ID: 1200210

RAW GTR:

cbr="detlst",gw_transactionid="17",detnumber="1200210",dettitle="MR",detsurname="Mazereeuw",detdatejnd="2012-12-03",
detg1name1="Martin",detg1name2,detprefnm,detpresurn,dettele,detbirdate="1967-04-17",detmarcd,detemailad,detterdate,
detntid,dettempdt2,dettempdte,detsubpos="OTA012",detalttele,updatetag="MORROWE ;21127140110",accesslevel="add",status="ok" 

C21 Org Unit Connector imports all position information correctly

C21 Placement Connector provides the correct reference between posnumber and employeeID/detNumber

C21 Employee ADAPTER does NOT show associated position information for the new user - This occurs WEEKS later

I originally thought there was an error with the relationship processing in the adapter configuration within idB. All connector information seems to be available for the relationship to occur, although the adapter does not present the information with the relationships intact...

This is very strange as the transformations seem to be correct for all existing users RE position information - It just seems to be processed at a later date regardless of if the information is available in identity broker..

I will post the adapter config tonight

HALP!

Test file connector imports data which contains start and an end date. An adapter is configured with this as it base connector and applies Is Operative Transformation as follow:

A full import brings in the changes to the Is Operative Column (Active) on changes are shown using a delta.

General UI:

I think the aim should be to have as much above 'the fold' as possible. I dont like having to scroll down to see essential info. The Logo takes up waaay to much space. Approx 1/3 of the screen is wasted on the logo & white space.