I am creating a small test setup (dma config) to play with srm+process automation.
The system does not have Elastic to save resources.
When I try to open the Profiles manager (or even Services), cube closes.
The root cause is most likely linked to the below alarm in the console.
Is it not possible to run this without elastic?
If it can: how can I resolve the problem?
Setup:
Server version : 10.0.10.0-9454
Client version : 10.0.2034.2144
PA-1.0.0_CU1-20200907160000
SRM-1.2.5_CU1-20200903180000
The exception:
Unexpected exception while initializing BaseProfileManager: System.IO.FileLoadException: Could not load file or assembly 'System.IO.FileSystem, Version=4.0.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'System.IO.FileSystem, Version=4.0.3.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ---> System.IO.FileLoadException: Could not load file or assembly 'System.IO.FileSystem, Version=4.0.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'System.IO.FileSystem, Version=4.0.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].at Roslyn.Utilities.FileUtilities.OpenFileStream(String path)
at Microsoft.CodeAnalysis.MetadataReference.CreateFromFile(String path, MetadataReferenceProperties properties, DocumentationProvider documentation)
at Skyline.DataMiner.Net.MediationSnippets.MediationCompiler.CreateReferences(DotNetVersion version)
at Skyline.DataMiner.Net.MediationSnippets.MediationCompiler..ctor()
at Skyline.DataMiner.Net.MediationSnippets.MediationLoader..ctor(MediationSnippetRetriever mediationSnippetRetriever, ILoggerWrapper log)
at Skyline.DataMiner.Net.Profiles.BaseProfileManager.OnInitializeMediationSnippetsCrud()
at Skyline.DataMiner.Net.Profiles.BaseProfileManager.OnInitialize()
at Skyline.DataMiner.Net.ManagerStore.BaseManager.Initialize()
at Skyline.DataMiner.Net.ManagerStore.ManagerStore.InnerInitializeSync(BaseManager manager)
Hi Mieke,
That exception is caused due to an assembly redirect in the file "C:\Skyline DataMiner Configs\Skyline DataMiner\Files\SLNet.exe.config". There, the System.IO.FileSystem 'newVersion' should be set to 4.0.2.0. (It seems this was changed to 4.0.3.0 for some reason, we will have a look at this internally)
Changing this back to 4.0.2.0 should resolve that exception.
In regards to the SRM setup you are creating, you will need Elastic for that.
Mieke,
Your upgrade failed when deploying the latest DataMiner version. (check the update log).
Please run the DataMiner upgrade again, to solve your problem.