-1

I have a sudden problem publishing a database for unit tests (C#, .NET app) by Jenkins on server (Windows Server 2016, Visual Studio 2022,Microsoft SQL Server Express 15.0.4153.1). Sorry if this is trivial question but I'm out of ideas.

This is log from Jenkins:

2023-08-31T09:06:04.518Z] Publishing to database 'Tiger4Test' on server '(localDb)\MSSqlLocalDb'.
[2023-08-31T09:06:04.518Z] Initializing deployment (Start)
[2023-08-31T09:07:12.201Z] Initializing deployment (Failed)
[2023-08-31T09:07:12.201Z] powershell.exe : *** Could not deploy package.
[2023-08-31T09:07:12.201Z] At C:\Jenkins\workspace\tiger4_release@tmp\durable-e0bb6632\powershellWrapper.ps1:3 char:1
[2023-08-31T09:07:12.201Z] + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ...
[2023-08-31T09:07:12.201Z] + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[2023-08-31T09:07:12.201Z]     + CategoryInfo          : NotSpecified: (*** Could not deploy package.:Str    ing) [], RemoteException
[2023-08-31T09:07:12.201Z]     + FullyQualifiedErrorId : NativeCommandError
[2023-08-31T09:07:12.201Z]  
[2023-08-31T09:07:12.201Z] Unable to connect to target server '(localDb)\MSSqlLocalDb'. Please verify the connection information such as the server name, login credentials, and firewall rules for the target server.
[2023-08-31T09:07:12.201Z] Wystąpił błąd związany z siecią lub 
[2023-08-31T09:07:12.201Z] wystąpieniem podczas ustanawiania połączenia z serwerem programu SQL Server. Nie można odnaleźć serwera lub jest on niedostępny. Sprawdź, czy nazwa wystąpienia jest poprawna i czy konfiguracja
[2023-08-31T09:07:12.201Z]  serwera programu SQL Server zezwala na połączenia zdalne.  (provider: SQL Network Interfaces, error: 50 - Wystąpił błąd programu Local Database Runtime. Error occurred during LocalDB instance
[2023-08-31T09:07:12.201Z]  startup: SQL Server process failed to start.
[2023-08-31T09:07:12.201Z] )
[2023-08-31T09:07:12.201Z]

This is log from SQL:

2023-08-31 11:07:04.02 spid14s     Starting up database 'mssqlsystemresource'.
2023-08-31 11:07:04.03 spid14s     The resource database build version is 15.00.4153. This is an informational message only. No user action is required.
2023-08-31 11:07:04.03 spid23s     Starting up database 'msdb'.
2023-08-31 11:07:04.03 spid22s     Starting up database 'Tiger4Test'.
2023-08-31 11:07:04.05 spid14s     Starting up database 'model'.
2023-08-31 11:07:04.08 spid22s     Parallel redo is started for database 'Tiger4Test' with worker pool size [2].
2023-08-31 11:07:04.08 spid14s     Clearing tempdb database.
2023-08-31 11:07:04.11 spid14s     Error: 9003, Severity: 20, State: 15.
2023-08-31 11:07:04.11 spid14s     The log scan number (36:2416:37) passed to log scan in database 'model' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
2023-08-31 11:07:04.11 spid14s     Error: 5901, Severity: 16, State: 1.
2023-08-31 11:07:04.11 spid14s     One or more recovery units belonging to database 'model' failed to generate a checkpoint. This is typically caused by lack of system resources such as disk or memory, or in some cases due to database corruption. Examine previous entries in the error log for more detailed information on this failure.
2023-08-31 11:07:04.11 spid14s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the operating system error log that may indicate why the tempdb files could not be initialized.
2023-08-31 11:07:04.11 spid14s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

I did so far:

  1. server name, login credentials, and firewall rules, connection strings are ok.
  2. there is no shortage of disk space
  3. the database publishes locally without any problems (when I choose publish via visual studio)
  4. I deleted Jenkins workspaces. It did not help.
  5. There was no changes in code between succesful job and with error.
malaver
  • 1

0 Answers0