mountainbrother
commented
5 years ago i could fix this with this workaround: create a new Userprofile and start from the scratch with the old Armprofile. finally it works perfect with a "old " 99 bootstrap and admin.json
AUSFÜHRLICH: 01:47:09 : AUSFÜHRLICH: 01:47:09 : Executing Script DeployMySQLProvider.ps1 1.1.24.0 AUSFÜHRLICH: 01:47:09 : AUSFÜHRLICH: PSBoundParameter are: AUSFÜHRLICH: { "VMLocalCredential": { "UserName": "MySQLRPadmin", "Password": { "Length": 9 } }, "CloudAdminCredential": { "UserName": "azurestack\cloudadmin", "Password": { "Length": 10 } }, "PrivilegedEndpoint": "azs-ercs01.azurestack.local", "DefaultSSLCertificatePassword": { "Length": 9 }, "DependencyFilesLocalPath": ".\cert", "AcceptLicense": { "IsPresent": true }, "AzCredential": { "UserName": "mymailadress", "Password": { "Length": 11 } } } AUSFÜHRLICH: 01:47:09 : AUSFÜHRLICH: 01:47:09 : **** AUSFÜHRLICH: 01:47:09 : Checking for Azure Stack Powershell Module ... AUSFÜHRLICH: 01:47:09 : **** Nuget Package provider found. Azure Powershell Module with 2.3.0 version found. Need Azure powershell compatible with stack. Use ArmProfile 2017-03-09-profile. Please uninstall the current version and rerun the RP setup PS>TerminatingError(): "ScriptHalted" AUSFÜHRLICH: 01:47:11 : AUSFÜHRLICH: 01:47:11 : **** AUSFÜHRLICH: 01:47:11 : MySQLAdapter installation failed. Check logfile C:\Temp\MySQL\Logs\DeployMySQLProvider.ps1_20181108-014709.txt for details AUSFÜHRLICH: 01:47:11 : **** PS>TerminatingError(DeployMySQLProvider.ps1): "Der ausgeführte Befehl wurde beendet, da die Einstellungsvariable "ErrorActionPreference" oder ein allgemeiner Parameter auf "Stop" festgelegt ist: ScriptHalted."
Ende der Windows PowerShell-Aufzeichnung Endzeit: 20181108014711
It seems that we have an mixed with the Use ArmProfile 2017-03-09-profile and the new one 2018-03-01-hybrid. What is now the solution ? run the bootstrap with the old Profile first and try to push the RP again
BR Günter