App reg secret and cert expiry script errors

Question

App reg secret and cert expiry script errors

Keagan Kennedy 5

Hello, I am using the script from here: https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/scripts/powershell-export-apps-with-expiring-secrets
and it worked fine the past couple days but I just logged on today on my local machine and now I am getting an entry point not found error when running it and also on a runbook I am getting a

Connect-AzAccount : Method 'get_SerializationSettings' in type 'Microsoft.Azure.Management.Internal.Resources.ResourceManagementClient' from assembly 'Microsoft.Azure.PowerShell.Clients.ResourceManager, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does not have an implementation. At line:3 char:1 + Connect-AzAccount -Identity + ~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Connect-AzAccount], TypeLoadException + FullyQualifiedErrorId : System.TypeLoadException,Microsoft.Azure.Commands.Profile.ConnectAzureRmAccountCommand

Absolutely nothing has changed about the code, I logged off when it was working and logged back in for it to not work

EPNAdam 50 Reputation points

2024-09-11T10:49:22.9633333+00:00

Sounds like an module version issue. Has any modules in your runtime environment been upgraded recently?

https://learn.microsoft.com/en-us/answers/questions/1299863/how-to-fix-method-get-serializationsettings-does-n
Keagan Kennedy 5 Reputation points

2024-09-11T11:24:03.19+00:00

@EPNAdam Hey if it's module issue why would it suddenly stop working on my runbook? my runbook has used the same version for weeks and only broke few days ago and isn't runbook modules always up to date or?

1 answer

Your answer

EPNAdam 50 Reputation points

2024-09-11T10:49:22.9633333+00:00

Sounds like an module version issue. Has any modules in your runtime environment been upgraded recently?

https://learn.microsoft.com/en-us/answers/questions/1299863/how-to-fix-method-get-serializationsettings-does-n
Keagan Kennedy 5 Reputation points

2024-09-11T11:24:03.19+00:00

@EPNAdam Hey if it's module issue why would it suddenly stop working on my runbook? my runbook has used the same version for weeks and only broke few days ago and isn't runbook modules always up to date or?

Answer 1

Darshida Das 15

This error typically occurs due to:

Version Mismatch: The Azure PowerShell module or its dependencies might be outdated or incompatible with your current setup.

Corrupted Installation: The Azure PowerShell module might be corrupted or incomplete.

Update Azure

Uninstall-Module -Name Az -AllVersions -Force

Install-Module -Name Az -AllowClobber -Scope CurrentUser

Remove Conflicting Modules:

Get-Module -ListAvailable -Name Az* | Uninstall-Module -Force

Reinstall Azure PowerShell:

Install-Module -Name Az -AllowClobber -Scope CurrentUser

Check Azure PowerShell Version:

Get-Module -Name Az -ListAvailable

Use Azure CLI as an Alternative:

az login

Keagan Kennedy 5 Reputation points

2024-09-11T11:24:53.0533333+00:00

Hey, how would I do this for runbook? cause the error also happening on azure runbook
EPNAdam 50 Reputation points

2024-09-11T11:28:39.8966667+00:00

Please see: https://learn.microsoft.com/en-us/azure/automation/shared-resources/modules

Runbooks executes in a runtime environment and a runtime environment has its modules. The modules can be managed (added/updated).

Darshida Das 15

In a runbook, you should ensure that the Azure modules are up-to-date. Use the following PowerShell script to update the Azure modules

# Uninstall existing Az module versions
Uninstall-Module -Name Az -AllVersions -Force -ErrorAction SilentlyContinue

# Install the latest Az module
Install-Module -Name Az -AllowClobber -Scope CurrentUser

# Import the module
Import-Module -Name Az

Share via

App reg secret and cert expiry script errors

1 answer

Your answer