Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NHA lab, failed to start MSSQL Server #259

Open
eltchard opened this issue Aug 3, 2024 · 4 comments
Open

NHA lab, failed to start MSSQL Server #259

eltchard opened this issue Aug 3, 2024 · 4 comments

Comments

@eltchard
Copy link

eltchard commented Aug 3, 2024

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: at , : line 1064
fatal: [srv02]: FAILED! => {"changed": false, "msg": "Unhandled exception while executing module: Failed to start service 'SQL Server (SQLEXPRESS) (MSSQL$SQLEXPRESS)'."}
How would i fix this issue?

@haraldaarz
Copy link

This is also an issue using Vmware with Docker on SRV03.

@haraldaarz
Copy link

This is also an issue using Vmware with Docker on SRV03.

For anyone else with the same issue as me, the fix was simply to delete everything, and reinstall.

@CalfCrusher
Copy link

CalfCrusher commented Oct 13, 2024

I also tried deleting and reinstalling, but the same problem persists. Goad, GoadLight, SSCM, NHA—nothing works. Everything is completely broken and bugged. I’m not sure what the point is of destroying something that previously worked; I really don’t know. Maybe someone could upload the older versions? Because this repo is a mess now.

@chrisrc05
Copy link

I was able to resolve this error in my lab (GOAD-Light). srv02 was failing with sql service error.
I attempted to start the SQL server (SQLEXPRESS) service manually, but the service would start then immediately stop.

Solution steps taken:

  1. uninstalled sql server from srv02 system.
  2. rebooted srv02 system.
  3. reinstalled sql server application. all default install settings.
  4. Confirmed the SQL server (SQLEXPRESS) was able to run successfully. re-ran the ansible script -t install. I no longer see the sql error in the ansible playbook output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants