Thursday - last edited Thursday by Michael_S
######################################################
Installing application AuthServer...
MSI Version: 5.1.1.34.
Installation of AuthServer exited with code 1603. Please see https://learn.microsoft.com/en-us/windows/win32/msi/error-codes for more information.
Thursday
I don't know how to help at the moment, however, I'm going to install an API on my personal PC so I can help with something, as soon as we talk 🤝
Thursday - last edited Thursday
This '1603' Microsoft error indicates that you do not have the necessary privileges to perform a particular action and need elevated permissions (i.e. local administrator). For this script it is necessary to run PowerShell as an administrator, as noted in the script itself:
yesterday
Yes, I have open PowerSheel by Run As Administrator ONLY
yesterday
I get following error in Event Viewer:
Application: dotnet.exe
CoreCLR Version: 8.0.824.36612
.NET Version: 8.0.8
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.EntityFrameworkCore.Abstractions, Version=8.0.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.
File name: 'Microsoft.EntityFrameworkCore.Abstractions, Version=8.0.7.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'
at Microsoft.EntityFrameworkCore.Infrastructure.EntityFrameworkServicesBuilder.TryAddCoreServices()
at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.ApplyServices(IDbContextOptions options, ServiceCollection services)
at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.<GetOrAdd>g__BuildServiceProvider|4_1(IDbContextOptions _, ValueTuple`2 arguments)
at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.<>c.<GetOrAdd>b__4_0(IDbContextOptions contextOptions, ValueTuple`2 tuples)
at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd[TArg](TKey key, Func`3 valueFactory, TArg factoryArgument)
at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.GetOrAdd(IDbContextOptions options, Boolean providerRequired)
at Microsoft.EntityFrameworkCore.DbContext..ctor(DbContextOptions options)
at Microsoft.EntityFrameworkCore.DbContext..ctor()
at Microsoft.AspNetCore.Identity.EntityFrameworkCore.IdentityUserContext`5..ctor()
at Microsoft.AspNetCore.Identity.EntityFrameworkCore.IdentityDbContext`8..ctor()
at ImsServer.DataAccess.ImsContext..ctor()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitCache(ServiceCallSite callSite, RuntimeResolverContext context, ServiceProviderEngineScope serviceProviderEngine, RuntimeResolverLock lockType)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScopeCache(ServiceCallSite callSite, RuntimeResolverContext context)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor`2.VisitCallSite(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass2_0.<RealizeService>b__0(ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(ServiceIdentifier serviceIdentifier, ServiceProviderEngineScope serviceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetService[T](IServiceProvider provider)
at ImsServer.BusinessLogic.Services.MemoryAppCache.PopulatePredefinedRolesAsync()
at ImsServer.Web.AppStart.AppInitializationService.Initialize(IServiceScope scope, IWebHostEnvironment environment)
at ImsServer.Web.Program.Main(String[] args)
at ImsServer.Web.Program.<Main>(String[] args)
yesterday
This error can occur when the installer script is unable to find the correct version of the dll identified in the error.
In this example, the dll is 'Microsoft.EntityFrameworkCore.Abstractions'
The error stack indicates the script/installer requires a .NET 8 version of this dll, although it is likely finding a different version of the dll elsewhere on the Operating System, likely due to it being higher in the PATH variable search order (further details available in this Microsoft documentation).
If you can confirm that no other software on the server requires the older version of this component, uninstalling it should in most cases resolve your issue. Otherwise, setting the PATH for the required version higher should help.
If this doesn't help and you still require assistance with this, we'd recommend opening up a Support ticket with us and providing the steps to reproduce and the logs so we could investigate further.