jdietz

Patrick,

I appreciate the response. I probably will not have time to work through this until next week.

One thing from what you wrote however was about the jobs being "scheduled". The scripts I have that called the MCM module were not scheduled. They were being tested and ran on demand. Even after restarting the service and rebooting the Powershell Universal server......the service would crash without me running that script.

I do agree the MCM module was doing this. I have removed the console / module from the server for now and I am looking for a way to work around it.

Adam,

I assume you wanted the SCCM module version.

Get-Module -Name *Admin* -ListAvailable did not show me this and same with Get-Module -Name ConfigurationManager

The module should be version 5.2603.1035.1000. I am on the latest SCCM current branch of 2603 w/ hotfix installed.

I did uninstall the Configuration Manager console from the server and this appears to have stopped the issue.

However, I am attempting to move all my jobs off System Center Orchestrator to Powershell Universal and automating a lot of SCCM is done there.

Let me know what other information you need to hopefully fix this and I can then reinstall the Admin Console. If a call / screenshare is needed just email me.

Files are uploaded

we are pretty new customers and I do not have a ton of experience yet with this product.

installed on Windows Server 2025

I was writing some scripts and running tests yesterday fine.

I did install August Microsoft monthly updates yesterday afternoon. Now today when i'm in the portal trying to work it keeps locking up and I find the service is stopped.

I have tried restarting the service / restarting the server with no improvement.

I do see the following log on the server. ......

Faulting application name: Universal.Server.exe, version: 1.0.0.0, time stamp: 0x69970000

Faulting module name: coreclr.dll, version: 9.0.1426.11910, time stamp: 0x699753ca

Exception code: 0xc00000fd

Fault offset: 0x0000000000047037

Faulting process id: 0xC0C

Faulting application start time: 0x1DD35886A7A1D32

Faulting application path: C:\Program Files (x86)\Universal\Universal.Server.exe

Faulting module path: C:\Program Files (x86)\Universal\coreclr.dll

Report Id: 68b019eb-342e-4a82-82b0-a9cd8a2623eb

Faulting package full name:

Faulting package-relative application ID:

and since I got back into the portal and tried to work with it I have received this log about 15 times on the server....

The PowerShell Universal service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

Anyone else seeing this after Microsoft Patching this month? It may not be that but it's the only thing that has changed since it seemed to work fine.

Also i am using New-UDStepper. So i just saw it has "-OnValidateStep". so maybe there is where i need to define these conditions to display to the end user that certain fields are required. I will give that a go.

I've tried this....but I can leave the box empty and move on without anything stopping me.

New-UDTextBox -Id 'emailAddress' -Label 'Email Address' -Placeholder 'Enter your email address' -FullWidth -OnValidate {

If ($EventData -eq $null)

{

New-UDValidationResult -ValidationError "Email Address is a required field."

}

}

Is that what you were thinking?

Very new Powershell Universal User here. Being using in DEV and company is about to purchase the license.

I'm creating an app that has several types of inputs to collect. I need some of the input to be required by the end user. How can I make New-UDTextbox a required field?

AI suggested there is a -Required switch....but looking at the cmdlet documentation I don't see that or any other switch that might help me here.

Curious if anyone has a solution.