Skip to main content

Powershell - The profile for the user is a temporary profile

Today I investigated an issue we had in one of our build pipelines. For an unknown reason the build suddenly started to fail.

In the build logs we found the following error message:

==============================================================================

Generating script.

Arguments passed sanitization without change.

Formatted command: . 'D:\b\2\_work\135\s\Certificates\Import-PfxCertificate.ps1' -PfxFilePath ***2024.pfx -Password ***

========================== Starting Command Output ===========================

"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\b\2\_work\_temp\e3fa7d9e-bd6e-490f-8f71-182a958e03d7.ps1'"

Importing store certificate 'D:\b\2\_work\135\s\Certificates\***2024.pfx'...

Exception calling "Import" with "3" argument(s): "The profile for the user is a temporary profile.

"

At D:\b\2\_work\135\s\Certificates\Import-PfxCertificate.ps1:10 char:1

+ $cert.Import($absolutePfxFilePath, $Password, [System.Security.Crypto ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException

+ FullyQualifiedErrorId : CryptographicException

Here is the powershell script that was called:

This script is used to import a certificate in the local certificate store that is later used inside the build pipeline to sign a clickonce package.

Based on the error message, it seems that there is something wrong with the build service user profile. A temporary profile doesn’t have it’s own certificate store so that would explain the error.

But until that time the user profile was always loaded correctly. What happened that made this profile corrupt?

Inside the event viewer we noticed the following event:

Probably due to a memory usage the user profile service can no longer load the user profile for the build service account. We fixed it by restoring a backup from the ntuser.dat file for this specific profile.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...