Forum Widgets
Latest Discussions
Windows 11 :: Return Code: 13631746
Hi Trying to install Cache Node on Windows 11 and it fails with the below error: System.Management.Automation.RuntimeException: Failure: MCC failed to install during provisioning command line, please check install from registered task install logs to diagnose issue and retry, Return Code: 13631746 Checked the log "WSL_Mcc_Install_FromRegisteredTask_Transcript_01-13-2025_03-19-26.txt" and last few lines shared below Get:37 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 c-n-f Metadata [224 B] Fetched 15.2 MB in 2s (7274 kB/s) Reading package lists... E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 1934 (unattended-upgr) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 1934 (unattended-upgr) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? ./installiotedge.sh: line 352: /etc/docker/daemon.json: No such file or directory ./installiotedge.sh: line 353: /etc/docker/daemon.json: No such file or directory ./installiotedge.sh: line 355: /etc/docker/daemon.json: No such file or directory Failed to restart docker.service: Unit docker.service not found. Hit:1 https://packages.microsoft.com/ubuntu/22.04/prod jammy InRelease Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Reading package lists... E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 1934 (unattended-upgr) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? Rules updated Rules updated (v6) Rules updated Haven't faced this error in other installation done on the same type of configuration
edgehub container not deploying
"MessageBody">Hello, We are currently trying to deploy Microsoft Connected cache for enterprise in public preview running on Windows. Installation is on Windows Server 2022 Standard and every time facing the same issue, edgeagent container is deployed correctly but edgehub or mcc containers are never deployed. When I run sudo iotedge check --verbose everything is checked correctly only with one exclusion: × production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error Could not check current state of edgeHub container caused by: Could not check current state of edgeHub container caused by: docker returned exit status: 1, stderr = Error: No such object: edgeHub Which is caused by missing edgehub container. In edgeagent.log is occurring this warning: [Microsoft.Azure.Devices.Edge.Agent.Core.ConfigSources.BackupConfigSource] - Empty edge agent config was received. Attempting to read config from backup (/tmp/edgeAgent/backup.json) instead It seems to me that edgeagent connects to IOT Hub successfully but cannot find/download the deployment manifest and because of that will not even try to install edgehub and mcc container/module. I already tried deployment many times, even manually from the docker, verified firewall ACLs and no blocked communication is happening there. I also tried to switch from AMQP to HTTPS via proxy, but the state is still the same. Reprovision or restart also doesn't help.
WSL MCC setup requires a runtime account with proper formatting for setting MCC scheduled tasks
Attempting to provision a cache node, failing with the below error. WSL MCC setup requires a runtime account with proper formatting for setting MCC scheduled tasks WSL MCC install failed (ReturnCode: 13631570) Runtime account is gMSA with the format of "domain\gMSAaccount". Tried several variations, with/without quotes but none are accepted. Error is too vague and documentation for this is lacking.
Error while configuring MCC Cache Node on Windows 11 Entra ID joined PC.
HelloAndy Rivas and All, Any Idea about this error message. I was trying to configure setup MCC Cache node on a Windows 11 Entra ID joined PC with local account. All prerequisites has been installed. Not sure why the below error message talking about WSL requires runtime account configured as domain\username on a Windows 11 Entra ID joined PCI see "Failure: WSL MCC install failed with exception during installation, Return Code: 13631495"
If you hit this error, or other errors during the install on Windows, the MCC installer will write logs to the installation folder specified in the installation command (C:\mccwsl01\InstallLogs by default). Please inspect the installation logs for self-help. There are three types of log files that will be appended with the dat and time of they are written: WSL_Mcc_Install_Transcript This log file records the lines printed to the command prompt when running the installation script. This is where you will see the initial error which may not include all the details you need. WSL_Mcc_Install_FromRegisteredTask_Status This log file records the high-level status that is written during the registered tasks install WSL_Mcc_Install_FromRegisteredTask_Transcript This log file records the detailed status that is written during the registered tasks install. This log file will include the most detailed information of the install, including the installation details for the Linux portion of the install. WSL_Mcc_Monitor_FromRegisteredTask_Transcript The log file records "Monitor" scheduled task which ensures Connected Cache is running. Watch out for errors when passwords change. You'll need to update the user in this schedule task, all of them actually, when passwords change.
Error installation MCC on Server 2022
I installed a couple of MCC for customers. But for 1, I still get this error : This is the end of my text file : Restarting WSL to apply new configuration file, please wait while WSL is restarted...... [12/11/2024 13:05:01] . . . . . . . . . . . . . . . [12/11/2024 13:05:15] Completed WSL restart [12/11/2024 13:05:15] Completed restart and successfully applied new configuration file [12/11/2024 13:05:15] Setting LastCompletedInstallStep [12/11/2024 13:05:15] Registering the MCC Monitoring scheduled task [12/11/2024 13:05:15] Register scheduled task MCC_Monitor_Task (mccscheduletask.ps1) [12/11/2024 13:05:15] Registering scheduled task as local account [12/11/2024 13:05:16] Completed registering scheduled task for MCC monitoring [12/11/2024 13:05:16] Completed registering task to monitor MCC and ensure it is running [12/11/2024 13:05:16] Registering the MCC Uninstall scheduled task [12/11/2024 13:05:16] RegisterScheduledTask_UninstallWsl (uninstallwsl.ps1) [12/11/2024 13:05:16] Registering scheduled task as local account [12/11/2024 13:05:16] Completed registering scheduled task for MCC uninstall [12/11/2024 13:05:16] Completed registering task to uninstall MCC manually, if needed in the future [12/11/2024 13:05:16] Setting LastCompletedInstallStep [12/11/2024 13:05:16] Registering MCC install task and waiting for compleition [12/11/2024 13:05:16] RegisterScheduledTask_InstallMccOnWsl (InstallMccOnWsl.ps1) [12/11/2024 13:05:16] Registering scheduled task as local account [12/11/2024 13:05:16] Completed registering scheduled task for MCC Install [12/11/2024 13:05:16] Setting LastCompletedInstallStep [12/11/2024 13:05:16] Successfully registered MCC Install Scheduled task [12/11/2024 13:05:17] System.Management.Automation.RuntimeException: Impossible d’appeler une méthode dans une expression Null. à System.Management.Automation.ExceptionHandlingOps.CheckActionPreference(FunctionContext funcContext, Exception exception) à System.Management.Automation.Interpreter.ActionCallInstruction`2.Run(InterpretedFrame frame) à System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) à System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) [12/11/2024 13:05:17] [2024-12-11] [01:05:17 ] [12/11/2024 13:05:17] WSL MCC install failed (ReturnCode: ) [12/11/2024 13:05:17] [2024-12-11] [01:05:17 ] PS>Erreur de terminaison (SetDWordRegistryValue) : « Impossible de lier l'argument au paramètre « Value », car il s'agit d'une chaîne vide. » [12/11/2024 13:05:17] Setting InvocationEndTime [12/11/2024 13:05:17] Setting InvocationState [12/11/2024 13:05:17] Installer return code 0 ********************** Fin de la transcription Windows PowerShell Heure de fin : 20241211130517 **********************
Trying to install to Windows Server + WSL error
I am trying to deploy to a Windows Server running WSL. I built a new Server 2025 VM and then enabled nested virtualization and installed WSL. I ran the provisioning script and am getting an error message. Successfully imported MCC Ubuntu Image into WSL Validating imported MCC Ubuntu Image : Ubuntu-22.04-Mcc-Base is running as expected in WSL... Failure: WSL MCC install failed with exception during installation, Return Code: 13631495 System.Management.Automation.RuntimeException: ScriptHalted [2024-12-10] [11:53:55 AM] WSL MCC install failed (ReturnCode: ) [2024-12-10] [11:53:55 AM] Setting InvocationEndTime Setting InvocationState Installer return code 0 Any hints on what is going wrong?Welcome to the Connected Cache for Enterprise and Education Discussion Forum!
Hello All! Welcome to the new discussion board for Microsoft Connected Cache for Enterprise and Education! Here you can engage in conversations with your peers around configuration and deployment of cache nodes, Connected Cache CLI, reporting and monitoring, troubleshooting issues, post questions for our product team or other users of the product. We will have a separate "Ideas Board" where you can share ideas for the future of Connected Cache for Enterprise and Education. So look for this announcement coming soon. Thanks for being a part of our community!
