Hi,
I've upgraded to DataMiner version 10.1.0 CU1 and I'm receiving below warnings in the alarm console. The exception mentions to check for missing .dll files and check slnet.exe.config file. It doesn't mention what dll files should be present (and where) nor does it give an indication on what could be wrong in the slnet config file. Could somebody help me on fixing these warnings or indicate what is causing this? What is Microsoft.PowerShell.ScheduledJob used for, is this for Windows Task Scheduler?
Unexpected Exception [SLNet tried to load Microsoft.PowerShell.ScheduledJob;
Please check for missing .dll files and check the slnet.exe.config file.
stack= at Skyline.DataMiner.Net.SLNetService.CurrentDomain_AssemblyResolve(Object sender, ResolveEventArgs args)
at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.LoadWithPartialNameInternal(AssemblyName an, Evidence securityEvidence, StackCrawlMark& stackMark)
at System.Reflection.Assembly.LoadWithPartialName(String partialName)
at System.Management.Automation.ExecutionContext.LoadAssembly(String name, String filename, Exception& error)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.FixupFileName(String moduleBase, String name, String extension)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(String moduleManifestPath, ExternalScriptInfo scriptInfo, Hashtable data, Hashtable localizedData, ManifestProcessingFlags manifestProcessingFlags, Version version, Version requiredVersion, ImportModuleOptions& options, Boolean& containedErrors)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(ExternalScriptInfo scriptInfo, ManifestProcessingFlags manifestProcessingFlags, Version version, Version requiredVersion, ImportModuleOptions& options)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModule(PSModuleInfo parentModule, String fileName, String moduleBase, String prefix, SessionState ss, Object privateData, ImportModuleOptions& options, ManifestProcessingFlags manifestProcessingFlags, Boolean& found, Boolean& moduleFileFound)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadUsingExtensions(PSModuleInfo parentModule, String moduleName, String fileBaseName, String extension, String moduleBase, String prefix, SessionState ss, ImportModuleOptions options, ManifestProcessingFlags manifestProcessingFlags, Boolean& found, Boolean& moduleFileFound)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadUsingModulePath(PSModuleInfo parentModule, Boolean found, IEnumerable`1 modulePath, String name, SessionState ss, ImportModuleOptions options, ManifestProcessingFlags manifestProcessingFlags, PSModuleInfo& module)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleNamedInManifest(PSModuleInfo parentModule, ModuleSpecification moduleSpecification, String moduleBase, Boolean searchModulePath, String prefix, SessionState ss, ImportModuleOptions options, ManifestProcessingFlags manifestProcessingFlags, Boolean loadTypesFiles, Boolean loadFormatFiles, Object privateData, Boolean& found, String shortModuleName)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(String moduleManifestPath, ExternalScriptInfo scriptInfo, Hashtable data, Hashtable localizedData, ManifestProcessingFlags manifestProcessingFlags, Version version, Version requiredVersion, ImportModuleOptions& options, Boolean& containedErrors)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.LoadModuleManifest(ExternalScriptInfo scriptInfo, ManifestProcessingFlags manifestProcessingFlags, Version version, Version requiredVersion, ImportModuleOptions& options)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.CreateModuleInfoForGetModule(String file, Boolean refresh)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.GetDefaultAvailableModules(String[] name, String directory, List`1 availableModules, List`1 modulePaths, Boolean refresh)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.GetAvailableLocallyModulesCore(String[] name, Boolean all, Boolean refresh)
at Microsoft.PowerShell.Commands.ModuleCmdletBase.GetModule(String[] name, Boolean all, Boolean refresh)
at Microsoft.PowerShell.Commands.GetModuleCommand.GetAvailableLocallyModules(String[] names, IDictionary`2 moduleSpecTable, Boolean all)
at Microsoft.PowerShell.Commands.GetModuleCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
at System.Management.Automation.CommandProcessorBase.DoExecute()
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
at System.Management.Automation.Runspaces.LocalPipeline.StartPipelineExecution()
at System.Management.Automation.Runspaces.PipelineBase.CoreInvoke(IEnumerable input, Boolean syncCall)
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
at System.Management.Automation.PowerShell.Invoke[T]()
at System.Management.Automation.AnalysisCache.GetExportedCommands(String modulePath, Boolean testOnly, ExecutionContext context)
at System.Management.Automation.CommandDiscovery.TryModuleAutoDiscovery(String commandName, ExecutionContext context, String originalCommandName, CommandOrigin commandOrigin, SearchResolutionOptions searchResolutionOptions, CommandTypes commandTypes, Exception& lastError)
at System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)
at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)
at System.Management.Automation.PSScriptCmdlet.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess)
at System.Management.Automation.PSScriptCmdlet.DoEndProcessing()
at System.Management.Automation.CommandProcessorBase.Complete()
at System.Management.Automation.CommandProcessorBase.DoComplete()
at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(CommandProcessorBase commandRequestingUpstreamCommandsToStop)
at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
]: Unresolved Assembly ()
These kinds of errors are created when SLNet tries to load a specific dll dependency (Microsoft.PowerShell.ScheduledJob) but is unable to find it in the regular folders (C:/Skyline DataMiner/Files(/x64)).
This is usually caused by an issue in C:\Skyline DataMiner\Files\SLNet.exe.config
In this file you will find several <dependentAssembly> tags under <configuration><runtime><assemblyBinding>
This configuration instructs SLNet on which dll versions it needs to load for certain dlls. If for example you have a Newtonsoft.Json version 9.0 in the Files folder but the configuration defines version 11.0 you will get a similar error.
If however you are running on a Windows Server 2008 R2 as Michiel suggests, then this system is indeed no longer supported and you may experience other issues in the future.
More information on redirecting assembly versions (https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions)
Hi, the DMS is running on Windows Server 2012 R2. I checked the updates section and installed the ‘optional’ update “Microsoft .NET Framework 4.8 for Windows Server 2012 R2 for x64 (KB4486105)” and then rebooted the DMAs. The warnings no longer appeared in the alarm console after executing this.
Perhaps there can be a more clear indication by software if a certain .NET installation is missing (or automatic install)? I was originally running 9.5 main release without problems, then updated to 9.6 -> 10.0 -> 10.1 main release where the problems occurred so if there are new dependencies required then an update package could perform a check for these new dependencies to indicate if something is missing