Ok, so complicated title but what I’m describing here is that the runbook is triggered from the Service Manager Self-Service Portal and shows that it’s running with no entry under the log portion of the runbook designer, and it may or may not show that it’s in pending state in the Orchestration Console. Here’s a visual of what I’m talking about:
Thankfully, this is an easy fix. Check your inputs from the Service Manager Self-Service Portal, if you entered &, <, or >, Orchestrator interprets what you’ve entered as a command and freezes execution. You simply can’t use these characters in your Service Manager Self-Service Portal inputs. So remove these, replace them with other character(s) and the problem will go away.
Until next time!
287 total views, 1 views today
I came across an interesting issue this week while applying System Center 2016 Update Rollup 4 to my company’s System Center Orchestrator instance. After the install, you are required to re-associate the Orchestrator database with the Orchestrator instance by using the ‘Data Store Configuration’ tool found in the management service’s installation folder. In my case, I would type in the name of my SQL Server instance and on the second page when trying to select the Orchestrator database, I would receive a BLANK error. That’s it, no information presented to me or input to any log file that I could find.
I was planning on reinstalling everything, as I have my runbooks backed up every night, when I had an idea: my Orchestrator server does not have SQL Server installed, and since I was trying to reach out to a SQL Server instance, it made sense to me that I may be missing required files in order to make this tool work. So, before I went through the process of reinstalling everything, I downloaded and installed SQL Server 2014 Express edition to the Orchestrator management server. After the install, I went back to the ‘Data Store Configuration’ tool and…IT WORKED!!!
So, long story short… if you are having issues with the ‘Data Store Configuration’ tool provided with System Center Orchestrator, try installing an Express version of SQL Server (or really any modern version of SQL Server would likely work) to install any missing dependencies that are not documented.
Until next time!
619 total views, no views today
Worked through this error the other day. Received this error when trying to use the back-tick character for multi-line commands in PowerShell. The good news is that it’s easy to fix. My issue was that I had a space character after the back-tick that was apparently interfering with command execution. Simply remove this space and the code will execute as expected.
Until next time,
567 total views, no views today
You can now find me on GitHub! I will post code here fairly frequently, and I have a pretty large backlog of stuff to post so check back regularly.
You can find my PowerShell repo here: https://github.com/masorensen/PowerShell
153 total views, no views today