Isolated Storage issues prevent service from starting

Matthew Clark 7 years ago • updated by anonymous 3 years ago 2

The Identity Broker service is currently failing to start, Rev 389, running the 32-bit service:

Application: Unify.Service.Connect32.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.IsolatedStorage.IsolatedStorageException
at System.IO.IsolatedStorage.IsolatedStorage.InitStore(System.IO.IsolatedStorage.IsolatedStorageScope, System.Type)
at System.IO.IsolatedStorage.IsolatedStorageFile.GetStore(System.IO.IsolatedStorage.IsolatedStorageScope, System.Type)
at Unify.Service.IdentityBrokerService32..ctor(System.IO.DirectoryInfo)
at Unify.Service32.ConnectServiceBootStrap.Main()

The error is occurring on an attempt to retrieve the isolated storage file. Of note is that the 64-bit installer attempts this in the OnStart() method of the service, whereas the 32-bit attempts this in the service constructor.

Affected Versions:
Fixed by Version:

Running the 64-bit installer instead revealed that the assembly is missing from the service. There may be a number of assemblies like this, so I will go through and have a look

This issue has been an ongoing process of fixing issues with the service that prevent it from starting. This is covered by IDB-146. Issue closed.