How to reset Elasticsearch completely from Windows 10 PC including the accounts that I have generated with a elasticsearch-setup-passwords auto - elasticsearch

I am completely new to using Elasticsearch and I am having problems running scripts on my windows 10 PC ever since running the command to generate accounts for ELK stack with passwords.
elasticsearch-setup-passwords auto
Running to random errors like writing access disabled to 'missing authentication credentials for REST request' , I just want to completely reset all these to the state it was after the first time I installed elasticsearch. Because I have tried uninstalling elasticsearch but it does not remove the account information that were generated. Please help me out.
Please note that I am using the Basic version.

Related

Windows Process Activation Service (WAS) will not start

IIS 10 will not restart on my PC. When I navigate to localhost, I get a 'localhost refused to connect' message. After looking through the event viewer, it turns out that the issue is that the Windows Process Activation Service (WAS) will not start.
The error message given is:
'The Windows Process Activation Service (WAS) encountered an error while handling key generation. This will prevent WAS from starting corrently. The data field contains the error number.'
When I try to start the service manually from the services app, I get the following:
Has anyone experienced this issue before? Any help would be greatly appreciated, I've been trawling the internet for several days trying to find a solution to no avail.
We've run into this issue several times after recent Windows Updates. In all cases, the following worked (got from a Microsoft support rep):
Run the following from an admin Powershell prompt:
reg delete HKLM\SYSTEM\CurrentControlSet\Services\WAS\Parameters /v GenerateKeys /f
net start w3svc
The keys will be regenerated, then the IIS AppPools can be started
According to your error message, WAS can not access the machine key when start up. Usually, machine keys are used to encrypt sensitive information in config file, WAS will not be able to start if there is no machine key to use.
The easiest and most common method is to try to uninstall and reinstall WAS.
If it still can not start, try to delete the registry entry NanoSet with cmd.
If the above two methods are useless, you can refer to this to delete machine keys, let WAS create new one while starting.
If somebody is still fighting with this issue, please check Event Viewer under System filter and check for any logs related to WAS. In my case I found the following entry:
The Windows Process Activation Service (WAS) encountered an error while handling key generation. This will prevent WAS from starting currently. The data field contains the error number.
So I just started again CNG Key Isolation service and everything is working now.

DB2 - User Id disabled or restricted on Windows

I have DB2 11.1 installed on Windows 7. 'db2admin' user account was created to access this. I was able to create, select and perform all necessary actions. Everything was working properly, until one fine morning it started giving me this error while connecting to database.
SQL30082N Security processing failed with reason "19" ("USERID DISABLED or
RESTRICTED"). SQLSTATE=08001
I performed below things:
Reset the password
Verified if the user account is disabled on Windows.
Account is not disbaled
Verified if the account is part of appropriate groups and ensured it has all necessary privileges on Windows
User groups
Deleted the 'db2admin' account and created a new one.
None of them worked and am still unable to figure out the reason for this error.
Is the error misleading? If so, any suggestions to verify logs or anything to figure out the root cause?
Any help in resolving this is highly appreciated

After update to 6.5 no users except Administrator in Administration/Security/Users

I have 40 users in my sonarqube instance.
After updating to Sonarqube 6.5 in Administration/Security/Users there is only Administrator.
Sonarqube connected to PostgreSQL database and table users contains all 40 users. Also they can login. Creating missing users fails with message: An active user with login 'XXXX' already exists.
I tried REINDEX DATABASE sonarqube; with no result.
How can I solve this problem?
The list of users is by default not shown completely in newer versions of SonarQube. Start typing a user's name or email in the filter input box to find the users you are looking for.
While a list of 40 users would be easy to display, some instances of SonarQube have thousands of users. The new behaviour of the user list improves the user experience on such systems.
Side note: If an unexpected error occurred during startup you indeed might have to reindex the database once. To do this stop SonarQube, make a backup of everything, remove the data/es directory and start SonarQube again.

remote wevtutil "The account is not authorized to log in from this station."

I am responsible for running centralized backups of Windows Security logs on a network of ~15 Windows boxes. To automate this task, I have been writing a Powershell script that utilizes wevtutil's /r parameter to do it all remotely. All of the boxes are connected to a Sharepoint network drive that I was hoping to copy the logs to so that I could centralize all of the logs, but I've run into some trouble.
The script runs fine when I pass it the ip of the Windows box that it's running on. The logs are copied to the Sharepoint without a hitch. The script also runs fine when I just tell it to copy the logs locally. However, when the script trys to remotely copy the computer's log to the sharepoint, I get a Failed to Archive Security log. The account is not authorized to log in from this station. error.
The format of the command is
wevtutil epl Security \\path\to\sharepoint\[hostname]-[datetime]Security.evtx /r:[hostname]
I am running the script as a domain admin. I have also ran the script with the credentials of a local admin and I got a generic access denied error.
A google search for the error message mostly includes computers not being able to access network drives (not remote wevtutil specifically) and include a lot of messing around in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
which have not yielded any results. I am also restricted to Powershell 1, so I cannot use Powershell itself remotely AFAIK.
I could just put the script on each machine and run it locally with task scheduler, but I was hoping for a more elegant solution. Does anyone have experience with using wevtutil in this way and can point me in the right direction, or perhaps even suggest a better technique/tool?
How much latitude do you have to implement another solution?
If you wanted to do something with the logs, or make them easily searchable, you could set up a free Splunk server and either use a Splunk forwarder to ship the logs off box, or you could also use Powershell to send the logs to Splunk's HTTP event collector.

Could not obtain information about Windows NT group / user, error code 0x3a

I am trying to deploy a SQLCLR library to SQL Server 2008 R2. In visual studio I have set up the data connection and it works correctly (I can run queries), but when I try to deploy I get the message "Error: Could not obtain information about Windows NT group / user , error code 0x3a."
This is strange because I have set up the data connection to use SQL server authentication on a different user name.
I receive the same error when I run CREATE ASSEMBLY while logged in to the SQL management studio with the different user name.
To add to the mystery, when I deploy using permission set SAFE everything is fine. However my assembly requires EXTERNAL ACCESS.
What could be the problem with deploying my assembly?
This issue wasted so much time I feel compelled to share the solution so that nobody else falls into the same trap.
Issue was resolved by setting the SQL Server Active Directory Helper service to run on Manual, then rebooting the server.
This issue arose in a different environment for me:
Windows 10 box;
The user Windows complained about was an AZUREAD user;
On my Win10 box there was no SQL Server Active Directory
Helper service, so I couldn't try the original solution posted by
ose.
I was able to work round the issue by removing the AZUREAD user as a SQL Server user while I added the assembly.
In my case that user was not essential to have as a SQL Server user, but I dare say it would be possible to re-add the user back later should this be required.

Resources