0
Fixed

Service fails to start (FileNotFoundException, FilterCustomAttributeRecord)

Matthew Woolnough 5 years ago updated by Dilip Ramakrishnan 2 years ago 11 1 duplicate

Application: Unify.Service.Connect.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
Stack:
at System.ModuleHandle.ResolveType(System.Reflection.RuntimeModule, Int32, IntPtr*, Int32, IntPtr*, Int32, System.Runtime.CompilerServices.ObjectHandleOnStack)
at System.ModuleHandle.ResolveType(System.Reflection.RuntimeModule, Int32, IntPtr*, Int32, IntPtr*, Int32, System.Runtime.CompilerServices.ObjectHandleOnStack)
at System.ModuleHandle.ResolveTypeHandleInternal(System.Reflection.RuntimeModule, Int32, System.RuntimeTypeHandle[], System.RuntimeTypeHandle[])
at System.Reflection.RuntimeModule.ResolveType(Int32, System.Type[], System.Type[])
at System.Reflection.CustomAttribute.FilterCustomAttributeRecord(System.Reflection.CustomAttributeRecord, System.Reflection.MetadataImport, System.Reflection.Assembly ByRef, System.Reflection.RuntimeModule, System.Reflection.MetadataToken, System.RuntimeType, Boolean, System.Object[], System.Collections.IList, System.RuntimeType ByRef, System.IRuntimeMethodInfo ByRef, Boolean ByRef, Boolean ByRef)
at System.Reflection.CustomAttribute.GetCustomAttributes(System.Reflection.RuntimeModule, Int32, Int32, System.RuntimeType, Boolean, System.Collections.IList, Boolean)
at System.Reflection.CustomAttribute.GetCustomAttributes(System.Reflection.RuntimeAssembly, System.RuntimeType)
at System.Attribute.GetCustomAttributes(System.Reflection.Assembly, System.Type, Boolean)
at System.AppDomain.GetTargetFrameworkName()

Affected Versions:
v4.0.1 RC3
Fixed by Version:
v4.1.5 RC2

Answers

Answer

This has been fixed in the latest RC. The cause is Microsoft .NET v4.6 changing the way it resolves assembly level attributes.

Answer

Thanks for that extra information. This issue is actually a duplicate of https://voice.unifysolutions.net/communities/6/topics/66-service-fails-to-start, so I will merge them shortly.

Thanks.

Duplicates 1

Answer

This has been fixed in the latest RC. The cause is Microsoft .NET v4.6 changing the way it resolves assembly level attributes.

ASP.NET MVC3 installed as well (pre-requisite to install the IDB Service)

Under review

Hi Dilip,

What analysis have you performed? Have you searched for existing tickets? If so, what did you search for?

Thanks.

Checked the below

1. UNIFY Service account permissions (Local administrator, Logon as service)

2. SQL Server permissions, connectivity - OK

3. Same box MIM 2016 SP1 is installed and running OK

4. same box MIM Event Broker is installed and running OK


There is a Windows report file which I have attached here.

While searching the forum for existing tickets - I could find one - https://voice.unifysolutions.net/communities/6/topics/118-idb-4003-service-cannot-start  but the error condition appears to be different

Answer

Thanks for that extra information. This issue is actually a duplicate of https://voice.unifysolutions.net/communities/6/topics/66-service-fails-to-start, so I will merge them shortly.

Thanks.

Does this mean I have to install 4.1.5 RTM x64 IDB Broker Service instead? Please let me know.

Yes. Was there a reason you were installing an older version?

We are doing an as-is migration (no changes to UNIFY Identity Broker Service and SAP HCM Broker, only FIM 2010 R2-> MIM 2016 SP1 and MIM Event Broker) for this customer. 

That's why installed the same version per current FIM solution.

I'll give it a go with 4.1.5 RTM version and update the ticket. 

Thanks.

No issues starting IDB v4.1.5 . All good.