Open Closed

Error code:-42, when trying to run the application on different computers #10107

User avatar
0
jtorres created

Configuration

  • Template: app
  • Created ABP Studio Version: 1.4.1
  • Current ABP Studio Version: 1.4.2
  • Tiered: No
  • Multi-Tenancy: Yes
  • UI Framework: blazor
  • Theme: leptonx
  • Theme Style: system
  • Theme Menu Placement: side
  • Run Install Libs: Yes
  • Run Bundling: No
  • Progressive Web App: No
  • Run Progressive Web App Support: No
  • Database Provider: ef
  • Database Management System: postgresql
  • Separate Tenant Schema: Yes
  • Create Initial Migration: Yes
  • Run Db Migrator: Yes
  • Mobile Framework: none
  • Public Website: Yes
  • Social Login: Yes
  • Include Tests: Yes
  • Kubernetes Configuration: Yes
  • Distributed Event Bus: rabbitmq
  • Use Local References: No
  • Optional Modules:
    • GDPR
    • FileManagement
    • TextTemplateManagement
    • LanguageManagement
    • AuditLogging
    • Chat
    • OpenIddictAdmin
  • Selected Languages: Spanish, English
  • Default Language: Spanish
  • Create Command: abp new OPUSNova -t app --ui-framework blazor --database-provider ef --database-management-system postgresql --theme leptonx --separate-tenant-schema --public-website --without-cms-kit --dont-run-bundling -chat -file-management

  • Exception message and full stack trace:

  • 11:01:17.428 Information CLI command executed. Command: "pwsh -Command "netsh interface ipv4 show excludedportrange protocol=Tcp"" Working directory: "C:\Users\jtorr\AppData\Local\abp-studio\current" CommandResult { ExitCode: 0, IsSuccess: True, StartTime: 11/14/2025 11:01:16 -06:00, ExitTime: 11/14/2025 11:01:17 -06:00, RunTime: 00:00:01.2504615 } 11:01:17.430 Information Starting the application: OPUSNova.HttpApi.Host 11:01:17.430 Information Running the project: C:\Codigo\OPUSNova\src\OPUSNova.HttpApi.Host\OPUSNova.HttpApi.Host.csproj 11:01:17.433 Information Project has been started: C:\Codigo\OPUSNova\src\OPUSNova.HttpApi.Host\OPUSNova.HttpApi.Host.csproj 11:01:17.433 Information Application has been started: OPUSNova.HttpApi.Host 11:01:17.448 Information Starting the application: OPUSNova.Blazor 11:01:17.449 Information Running the project: C:\Codigo\OPUSNova\src\OPUSNova.Blazor\OPUSNova.Blazor.csproj 11:01:17.451 Information Project has been started: C:\Codigo\OPUSNova\src\OPUSNova.Blazor\OPUSNova.Blazor.csproj 11:01:17.451 Information Application has been started: OPUSNova.Blazor 11:01:17.466 Information Starting the application: OPUSNova.Web.Public 11:01:17.466 Information Running the project: C:\Codigo\OPUSNova\src\OPUSNova.Web.Public\OPUSNova.Web.Public.csproj 11:01:17.468 Information Project has been started: C:\Codigo\OPUSNova\src\OPUSNova.Web.Public\OPUSNova.Web.Public.csproj 11:01:17.469 Information Application has been started: OPUSNova.Web.Public 11:01:18.069 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:18.069 Information Start processing HTTP request "GET" "https://localhost:44302/health-status" 11:01:18.069 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:18.069 Information Sending HTTP request "GET" "https://localhost:44302/health-status" 11:01:18.100 Information Start processing HTTP request "GET" "https://localhost:44383/health-status" 11:01:18.100 Information Sending HTTP request "GET" "https://localhost:44383/health-status" 11:01:22.785 Information Start processing HTTP request "GET" "https://localhost:44302/health-status" 11:01:22.785 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:22.785 Information Sending HTTP request "GET" "https://localhost:44302/health-status" 11:01:22.785 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:22.816 Information Start processing HTTP request "GET" "https://localhost:44383/health-status" 11:01:22.816 Information Sending HTTP request "GET" "https://localhost:44383/health-status" 11:01:26.975 Information OPUSNova.HttpApi.Host exited with code: -42 11:01:27.226 Information OPUSNova.Web.Public exited with code: -42 11:01:27.486 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:27.486 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:29.002 Information Automatically restarting the application: OPUSNova.HttpApi.Host 11:01:29.002 Information Running the project: C:\Codigo\OPUSNova\src\OPUSNova.HttpApi.Host\OPUSNova.HttpApi.Host.csproj 11:01:29.007 Information Project has been started: C:\Codigo\OPUSNova\src\OPUSNova.HttpApi.Host\OPUSNova.HttpApi.Host.csproj 11:01:29.007 Information Application has been restarted: OPUSNova.HttpApi.Host 11:01:29.236 Information Automatically restarting the application: OPUSNova.Web.Public 11:01:29.236 Information Running the project: C:\Codigo\OPUSNova\src\OPUSNova.Web.Public\OPUSNova.Web.Public.csproj 11:01:29.241 Information Project has been started: C:\Codigo\OPUSNova\src\OPUSNova.Web.Public\OPUSNova.Web.Public.csproj 11:01:29.241 Information Application has been restarted: OPUSNova.Web.Public 11:01:29.624 Information Start processing HTTP request "GET" "https://localhost:44302/health-status" 11:01:29.624 Information Sending HTTP request "GET" "https://localhost:44302/health-status" 11:01:29.856 Information Start processing HTTP request "GET" "https://localhost:44383/health-status" 11:01:29.856 Information Sending HTTP request "GET" "https://localhost:44383/health-status" 11:01:32.205 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:32.205 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:34.352 Information Start processing HTTP request "GET" "https://localhost:44302/health-status" 11:01:34.352 Information Sending HTTP request "GET" "https://localhost:44302/health-status" 11:01:34.600 Information Start processing HTTP request "GET" "https://localhost:44383/health-status" 11:01:34.601 Information Sending HTTP request "GET" "https://localhost:44383/health-status" 11:01:36.915 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:36.915 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:38.988 Information OPUSNova.HttpApi.Host exited with code: -42 11:01:39.292 Information Start processing HTTP request "GET" "https://localhost:44383/health-status" 11:01:39.292 Information Sending HTTP request "GET" "https://localhost:44383/health-status" 11:01:39.957 Information OPUSNova.Web.Public exited with code: -42 11:01:41.144 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:41.144 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:41.767 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:41.767 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:42.391 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:42.391 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:43.014 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:43.014 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:43.014 Information Automatically restarting the application: OPUSNova.HttpApi.Host 11:01:43.014 Information Running the project: C:\Codigo\OPUSNova\src\OPUSNova.HttpApi.Host\OPUSNova.HttpApi.Host.csproj 11:01:43.017 Information Project has been started: C:\Codigo\OPUSNova\src\OPUSNova.HttpApi.Host\OPUSNova.HttpApi.Host.csproj 11:01:43.017 Information Application has been restarted: OPUSNova.HttpApi.Host 11:01:43.637 Information Start processing HTTP request "GET" "https://localhost:44302/health-status" 11:01:43.637 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:43.637 Information Sending HTTP request "GET" "https://localhost:44302/health-status" 11:01:43.637 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:43.965 Information Automatically restarting the application: OPUSNova.Web.Public 11:01:43.965 Information Running the project: C:\Codigo\OPUSNova\src\OPUSNova.Web.Public\OPUSNova.Web.Public.csproj 11:01:43.968 Information Project has been started: C:\Codigo\OPUSNova\src\OPUSNova.Web.Public\OPUSNova.Web.Public.csproj 11:01:43.968 Information Application has been restarted: OPUSNova.Web.Public 11:01:44.277 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:44.277 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:44.587 Information Start processing HTTP request "GET" "https://localhost:44383/health-status" 11:01:44.588 Information Sending HTTP request "GET" "https://localhost:44383/health-status" 11:01:44.915 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:44.915 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:45.553 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:45.553 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:46.193 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:46.193 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:46.845 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:46.845 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:47.487 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:47.487 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:48.127 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:48.127 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:48.376 Information Start processing HTTP request "GET" "https://localhost:44302/health-status" 11:01:48.376 Information Sending HTTP request "GET" "https://localhost:44302/health-status" 11:01:48.764 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:48.764 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:49.287 Information Start processing HTTP request "GET" "https://localhost:44383/health-status" 11:01:49.287 Information Sending HTTP request "GET" "https://localhost:44383/health-status" 11:01:49.395 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:49.395 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:50.033 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:50.034 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:50.677 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:50.677 Information Sending HTTP request "GET" "https://localhost:44382/" 11:01:51.300 Information Start processing HTTP request "GET" "https://localhost:44382/" 11:01:51.300 Information Sending HTTP request "GET" "https://localhost:44382/"

  • Steps to reproduce the issue:

  • When trying to run an existing application on my licensed computer

  • When trying to run an existing application on any of my licensed colleagues' computers

  • When creating a new solution and attempting to run the new solution, on my computer and on my colleagues' licensed computers

Go to accepted answer
2 Answer(s)
  • User Avatar
    0
    AI-Bot created
    Support Team ABP Agent
    1. Solution

    • What exit code -42 means in ABP Studio

      • In ABP Studio, “exited with code: -42” indicates the target app (e.g., HttpApi.Host, Web.Public) terminated unexpectedly soon after start. It’s typically caused by an unhandled startup failure (ports, configuration, missing env/deps), not by ABP Framework itself. The Solution Runner then keeps attempting restarts.

    • Likely causes from your log and setup

      • HTTPS port conflict or reservation: Studio probes health endpoints at 44302/44383 and the UI at 44382. If these ports are blocked, reserved by HTTP.SYS, or fall into Windows excluded port ranges, the app can start then crash.
      • Certificate/HTTPS binding issues: Kestrel can fail when the dev cert is missing/untrusted on new machines.
      • PostgreSQL connectivity: With Separate Tenant Schema + initial migration run, any wrong connection string or unreachable DB can kill the host at startup.
      • NuGet feeds/tooling: If global NuGet.config forces an unreachable private source for tools or packages, builds can succeed partially but runtime may fail later during dynamic restore.
      • Environment differences between machines: Missing .NET SDKs required by the solution, or prereqs not present.

    • Fix checklist (perform on every affected machine)

      1. Verify .NET SDKs
        • Install the SDKs targeted by your solution (check global.json and csproj TargetFramework). Ensure dotnet --info shows them.
      2. Clean/restore/build once outside Studio
        • From the solution folder:
          • dotnet clean
          • dotnet restore
          • dotnet build -c Debug
        • If build fails, fix errors first.
      3. Ensure HTTPS dev certificate is installed and trusted
        • dotnet dev-certs https --clean
        • dotnet dev-certs https --trust
      4. Free or remap ports
        • Check excluded/occupied ports:
          • netsh interface ipv4 show excludedportrange protocol=TCP
          • netsh http show urlacl
          • netstat -ano | findstr :44382
        • If 44302/44382/44383 are in excluded ranges or used, change ports:
          • In each app’s appsettings.json (or launchSettings.json), change Kestrel:Endpoints:Https:Url (and Health endpoints) to free ports, or in ABP Studio Runner profile set different ports, then run again.
      5. Trust local hostnames
        • Make sure you browse the exact HTTPS URLs Studio opens. If the browser prompts for cert trust, accept it.
      6. Verify PostgreSQL connectivity
        • Confirm the default connection string in your HttpApi.Host appsettings.* points to a reachable PostgreSQL instance with correct credentials.
        • Test with psql or a client using the same host, port, db, user, password.
        • If you use separate schemas per tenant, ensure the database exists and the migrator was executed successfully.
      7. Re-run the DbMigrator
        • From src/OPUSNova.DbMigrator:
          • dotnet run
        • Fix any migration/connection errors it shows.
      8. Check global NuGet config for unreachable private feeds
        • If you have a company NuGet feed configured globally that is not reachable on some machines, it can break tool/package restore. Remove or disable it temporarily in %AppData%\NuGet\NuGet.Config or related config files and keep nuget.org active.
        • This exact issue was reported and fixed by removing a stale private feed from NuGet.Config.
      9. Start projects manually to see first exception
        • Run OPUSNova.HttpApi.Host from command line:
          • dotnet run
        • Observe the first thrown exception/stack trace in the console; it often reveals the exact root cause that Studio abstracts as exit code -42.
      10. ABP Studio prerequisites
      • Ensure ABP Studio CLI is installed and can run:
        • abp cli version
      • If it fails due to NuGet source issues, fix NuGet.Config as in step 8.

    • Notes for Blazor WASM + Public Website profile

      • The Blazor (WASM) and Public site rely on the HTTP API host being up. If the host crashes (-42), both health checks will fail and Studio restarts them. Fixing the host’s startup error usually resolves the rest.
    1. Sources
    • https://abp.io/community/articles/kcfec59b
    • https://abp.io/community/articles/0x6kmwry
    • https://abp.io/support/questions/8950

    This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  • User Avatar
    0
    jtorres created

    De acuerdo a las recomendaciones ejecute el comando: dotnet run --project src/OPUSNova.HttpApi.Host/OPUSNova.HttpApi.Host.csproj

    Como resultado manda esto: aparece ABP-LIC-0018: “Your trial period has ended!”. Eso hace que el proceso termine inmediatamente y ABP Studio muestre “exited with code: -42

    Detalle 14:24:34 INF] TRIAL-INFO - You are using the trial version of ABP and your expiry date is 2025-11-10 [14:24:34 ERR] ABP-LIC-0018 - iA5wWKYJaP1jwR0HjSE: Your trial period has ended! - Please contact to license@abp.io to purchase a license. [14:24:34 ERR] ABP-LIC-0018 - w2Qqo7AHOYV3iD25y0Y: Your trial period has ended! - Please contact to license@abp.io to purchase a license. [14:24:34 ERR] ABP-LIC-0018 - y7V81uKZMLDDl5PtxHv: Your trial period has ended! - Please contact to license@abp.io to purchase a license. [14:24:34 ERRb48fce22034d4ceb8ea2d686d2f8ae83=False

    Contexto: Asunto: Urgente: Problema de ejecución de aplicación para usuarios migrados de licencia Trial a Business

    Estimado equipo de soporte,

    Solicitamos su asistencia urgente con un problema de licenciamiento que afecta a tres de nuestros desarrolladores.

    A continuación, detallamos la situación:

    Licencia Trial: Inicialmente, operamos con una licencia Trial para 3 desarrolladores. Dicha licencia expiró el 10 de noviembre de 2025.

    Nueva Licencia Business: Antes del vencimiento, el 29 de octubre de 2025, adquirimos una nueva licencia Business.

    Migración de Usuarios: A la licencia Business se incorporaron los 3 desarrolladores que usaban la licencia Trial (utilizando sus mismos correos electrónicos) y se añadieron 2 miembros nuevos al equipo.

    El Problema: Los 3 desarrolladores originales que fueron migrados de Trial a Business no pueden ejecutar la aplicación. Sin embargo, los 2 desarrolladores nuevos, que no tuvieron licencia Trial, sí pueden ejecutar los proyectos sin inconvenientes.

    Acciones Tomadas: Los 3 desarrolladores afectados ya realizaron un cierre de sesión (Logout) y un nuevo inicio de sesión (Login) para intentar forzar el reconocimiento de la licencia Business, pero el problema persiste.

    Esta situación está afectando nuestra capacidad de desarrollo y requerimos una solución a la brevedad posible.

    Quedamos atentos a su pronta respuesta.

    Saludos cordiales, Jorge Torres

Assignee
No one
Question details
Labels
None yet
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.1.0-preview. Updated on November 11, 2025, 06:29
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.