During one of the activities with the demo environment I faced an issue that I was unable to promote any server to DC, and was giving the errors:
ADPrep execution failed –> System.ComponentModel.Win32Exception (0x80004005): A device attached to the system is not functioning.
Check the log files in the C:\Windows\debug\adprep\logs\20220518075032 directory for detailed information.
By the standard way of imputing the new key into the activation form, you’ll get an error that this edition could not be upgraded. However, the MS guide stands for if you’d like to activate your Azure configuration server you’d need to do that through DISM:
And the command is simple as that:
Continue readingI was set up high availability for brokers with 2019 windows server and faced this error:
Could not create the database <DatabaseName>. Please check that the broker server has access to the SQL server, the path for -DatabaseFilePath parameter exists and contains the SQL Server database file, the connection to SQL database is correct and SQL database is online. See the SQL Server and broker event log for more details.Due to some reasons, I had a task to install JunOS space on our Azure tenant, and that appeared to be not that straightforward as I thought. But definitely fun.
Continue readingAt some point, I had to remote on one of the ancient IBM Remote Supervisor Adapter II consoles, and it turned out that it was not updated since 2009. It was running an ancient version of Java KVM, so I had to do some magic to make it work due to the java security permissions.
For me, it was an error about a weak signature algorithm MD5withRSA.
Here it is if you are after downloading it.
One day I was in need to add backup settings on 140 juniper devices, and to not cause death due to boringness I decided to script up this task, and here is the script:
Continue readingWhile setting up the Xero connector I faced an issue when after 30 minutes connector stopped working and return an error 400:
Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ERROR [HY000] [Microsoft][Xero] (61) API Connection Failed. Bad Request. HTTP Response code: 400\r\nERROR [HY000] [Microsoft][Xero] (61) API Connection Failed. Bad Request. HTTP Response code: 400,Source=Microsoft.DataTransfer.Runtime.GenericOdbcConnectors,''Type=System.Data.Odbc.OdbcException,Message=ERROR [HY000] [Microsoft][Xero] (61) API Connection Failed. Bad Request. HTTP Response code: 400\r\nERROR [HY000] [Microsoft][Xero] (61) API Connection Failed. Bad Request. HTTP Response code: 400,Source=,'",To make our on-prem One Time Secret service to work properly, without expiritng urls I implemented the following on the nginx daemon to filter out link previews request. Guess the same could be done on any HTTP service.
Continue readingTo reset the password for the administrator (11111) account at Xerox\Docucentre you need to first – access the service menu by the following instruction:
Continue reading