SCOM 2012 SP1 - PowerShell Script failed to run - 3 alerts appear after every reboot of the SCOM Server

Brand new SCOM 2012 SP1 install with Update Rollup 1 applied
Single server, local SQL install, SQL Server 2012 SP1
Hyper-V VM running on Server 2012. VM has 8GB Ram, single vCPU
Going through initial management pack importing and configuration, at this point I have the Windows Server 2012 and SQL 2012 MP's installed.
See screenshot
http://i.imgur.com/l0Molh1.png
I am getting the following alerts in my SCOM console and cannot find a resolution to fix the issue. I don't want to set an override, as an override will prevent the PowerShell alert in other instances, where I might want to receive an alert.
Looking at the alert description, it states "The Data Access service is either not running or not yet initialized"
The SCOM Console launches and responds fine, and I get no other errors. I check the Data Access service and it is online. I have left the system alone for a couple of hours and no other errors. I then closed those alerts and restarted the
server, and they came right back in, so I know that this is something that is happening at either server startup of during the start of the SCOM services.
Is it possible that SCOM is trying to execute these scripts and the Data Access service has not come online yet?
Has anyone else come across this before?

Please try the method in the following thread:
Note: As there is operations related to Registry, please perform a backup before doing this.
OpsMgr 2012 - Power Shell Script failed to run
http://social.technet.microsoft.com/Forums/de-DE/systemcenterde/thread/4be37f8d-1e7b-450c-8cb9-f1e95f3b2bd0/
Thanks.
Nicholas Li
TechNet Community Support

Similar Messages

Object failed to run due to an error while processing on the Job Server

when i am scheduling a report ith email notification i am getting below error
error msg: Object failed to run due to an error while processing on the Job Server
i have configured email notification in bo cmc and server also SMTP enabled. while scheduling report to ueser i am getting error and even mails are delivered to users as well.

hi prithvi,
i am able to schedule reports to other destinations and reports are delivered as per the requirement.
i am able to telnet SMTP server from Adaptive job server machine on SMTP port.
have to check errors on log file....
@ COULD YOU PLEASE LET ME KNOW USER CAN SEND A MAIL TO USER IN SAME DOMAIN . WHILE SCHEDULING A REPORT AND AS OPTION AVAILABLE IN 4.0 LAUNCH PAD CAN HE SEND A MAIL DIRECTLY AFTER RUNNING REPORT.

SCOM 2012 SP1 "Task invocation failed with error code -2146232576"

Hi,
I`m trying to discover a Linux RHEL 5.9 Server which is in another untrusted domain and from the Discovery wizard I receive the following error:
Task invocation failed with error code -2146232576. Error message was 0x80131700.
Any ideas ?
Greetings.

Hi,
@Simon, I restart the SCOM services and I also verify the UAC and it's disabled.
@Mai Ali, thank you for you reply. I don't have a "&" symbol in my password, but only a "$" ..I hope it's fine.
If the SCOM discovery doesn't work, I installed the agent manually on the Linux server.
BTW I also use a "monuser" account configured using this procedure:
http://social.technet.microsoft.com/wiki/contents/articles/7375.configuring-sudo-elevation-for-unix-and-linux-monitoring-with-system-center-2012-operations-manager.aspx
I also verify the ports 22 and 5723 and are opened, but I also noticed that if you restart the scxadmin, is listening on HTTPS on port 1207.
Now..if I try to re-discover the Linux server from SCOM, I receive the following error:
"The pool managing the instance is not available or the location monitoring object cannot be found"
Regards.

SCOM 2012 SP1 failed to send notifications by IM Channel

Hello, I have a problem with my SCOM 2012 SP1. When it tries to send notification by IM Channel I get the following alert in SCOM:
Notification subsystem failed to send notification using
device/server 'live.august.ru:5060' over 'sip' protocol to
'sip:[email protected]'.
Microsoft.Rtc.Signaling.OperationFailureException: The GetInbandDataAsyncResult
operation has failed with message: "The data session subscription to server
failed.". See the InnerException and FailureReason properties as well as the
logs for additional information. . Rule id:
Subscription077dc311_59c0_4ba5_a432_072b486cd287
At the same time the following event in the Application Event Log generates on the server with IM service:
Event Type: Warning
Event Source: Live Communications Server Authentication
Event Category: (1003)
Event ID: 16435
User: N/A
Computer: LCS
Description:
At least one invalid authentication signature was detected.
There were 2 messages with invalid signatures in the last 7112 minutes. The last one had the FROM header: sip:[email protected]
Cause: This could be due to a client or server which is not handling authentication correctly, or it could be due to an attacker.
Resolution:
None needed unless the failure count is high (>100). Check your network for any rogue clients. Restart the server if problem persists.
Notifications sent by the SMTP channel work fine!
I Have the following Servers:
LCS (live.august.ru) - Win 2003 EE SP2 + Live Communication Server 2005 SP1
SCOM - Win 2012 + SCOM 2012 SP1
Also I have a third server (Win 2003 + SCOM 2007 R2) and it sends notifications to the same VMLCS server successfully. The configurations of IM Channels are identical on both servers:
IM server: live.august.ru
Return address: sip:[email protected]
Protocol option: TCP
Authentication method: Kerberos
IM port: 5060
I tried to change the Authentication method to NTLM, and the port to 5061, but it doesn't help...

Hi,
Please refer to these following articles to configure IM channel correctly:
How to Create and Configure the Notification Action Account
http://technet.microsoft.com/en-us/library/hh212835.aspx
How to Enable an Instant Message Notification Channel
http://technet.microsoft.com/en-us/library/hh212690.aspx
Enabling Instant Messaging Notifications in System Center 2012 Operations Manager
http://opsmgrunleashed.wordpress.com/2012/02/24/enabling-instant-messaging-notifications-in-system-center-2012-operations-manager/
Alex Zhao
TechNet Community Support

Power shell script failed to run - reasons for it and some background?

Hi there
I have been receiving some alerts with high repeat count that Powershell script failed to run.
All of them are coming from one server and all of them are related to SQL2012 installation. The following scripts generate alerts:
CPUUsagePercentDataSource.ps1
StolenServerMemory2012.ps1
DBDiskLatencyDataSource.ps1
I am quite new to SCOM and still trying to find my way around conveniently - I would appreciate your help if you could explain me one thing: are these scripts executed locally or through remote PSSession to the target? The point is I couldn't find any of
these scripts on my server to re-run them (and possibly catch exceptions).
The repeat count for past two months is quite high, for 8 alerts between 25 / 80.
Thanks in advance!
AlexP

The agent downloads the script and it is run locally on the agent machine, in your case the SQL Server. Usually most of these type scripts are held in the Agent folder under scritp/downloads, (sorry dont have the full path in front of me or I would give
it to you).
These errors are probably due to the fact that SQL 2012 does not give any rights to the Local System Account which is the context in which the SCOM agent runs scripts as, and is unable to access SQL information due to this fact. The easiest way to fix this
is to setup a run as account, which would be an account on your domain that has local admin access to the SQL box and has SA rights to the instance of SqL running on that box. See the following blog posts on how to fix this.
http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
Hope this helps! this will probably create more questions...
Scott Moss MVP (Operations Manager) President - System Center Virtual Users Group |Vice President - Atlanta Southeast Management Users Group (ATL SMUG)
Please remember to click “Mark as Answer” on the post that helps you!
my new blog om2012.wordpress.com

SCOM 2012 SP1 Upgrade

Hello,
I have a SCOM 2007 R2 CU7 server that I upgraded to SCOM 2012. I am running Windows Server 2008 R2 SP1 and SQL Server 2008 R2 SP2. I tried twice to upgrade it to SCOM 2012 SP1 and it failed both times. In the OpsMgrSetupWizard.log file,
I see this error:
: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Incorrect syntax near 'MERGE'. You may need to set the compatibility level of the current database to a higher value to enable this feature.
See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
Incorrect syntax near the keyword 'AND'.
Incorrect syntax near the keyword 'THEN'.
[10:58:04]: Error: :StackTrace:   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.DBConfigurationHelper.DBConfiguration.RunSqlCommandsList(IEnumerable`1 sqlCommands)
[10:58:04]: Error: :RunStandardScripts failed with the following exception: : Threw Exception.Type: System.Reflection.TargetInvocationException, Exception Error Code: 0x80131604, Exception.Message: Exception has been thrown by the target of an invocation.
[10:58:04]: Error: :StackTrace:   at System.RuntimeMethodHandle._InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.RuntimeMethodHandle.InvokeMethodFast(IRuntimeMethodInfo method, Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeType typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.Action.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
   at Microsoft.EnterpriseManagement.SetupFramework.ActionEngine.InstallStep.Run(String displayStringNamespace, ProgressData progressData, Func`2 progressDelegate)
[10:58:04]: Error: :Inner Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131604, Exception.Message: Incorrect syntax near 'MERGE'. You may need to set the compatibility level of the current database to a higher value
to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
Incorrect syntax near the keyword 'AND'.
Incorrect syntax near the keyword 'THEN'.
After both failed upgrades, I had to re-install SCOM 2007. How can I get the upgrade to complete? The prerequisites have been installed.

So try to change the SQL database Compatibility Level to SQL 2008 (100):
1. Open SQL Server Management Studio
2. Connect to the SQL server hosting the Operations Manager Databases
3. Expand Databases, Right Click on OperationsManager and click properties
4. Click Options, Change the Compatibility level: drop down to SQL Server 2008 (100), Click OK
5. Right Click on OperationsManagerDW and click properties, Click Options
6. Change the Compatibility level: drop down to SQL Server 2008 (100), Click OK
Niki Han
TechNet Community Support

Intermittent "Power Shell Script failed to run" after installing SQL MP 6.5.4.0

We recently installed the SQL MP. One thing I am struggling with is this "Power Shell Script failed to run" that occasionally comes up, but, not always on the same server, and not always at the same time.
It says it ran past the configured timeout of 300 seconds.
The post that seemed to have me on the right track was
https://social.technet.microsoft.com/Forums/en-US/c539a55d-dd48-438f-b7d5-06ed2cecf6e9/powershell-script-failed-to-run-alerts-from-sql-management-pack-6410?forum=operationsmanagergeneral
However, even after getting one of the several scripts that have been generating the error, out of the extract management pack, it has parameters that need to be fed to it that I have no idea what they are....
Example. ActiveRequestsDataSource.ps1 requires $computername, $connectionstring, $tcpport, $sql_wmi_namespace, and $servicename.
The computername is easy enough... so is tcpport. but, the others... not so much.
I am fairly certain I will be able to run these manually, if I just knew the parameters... I am also fairly certain we are getting these because at the time of the check, resources on that server are tied up for one reason or another.
Can someone please help? This is killing me.

Hi,
As this issue happens after you installing SQL MP, so from my point of view, it seems like caused by the runas account for the SQL MP is not configured well, I would like to suggest you follow the article below to configure runas account for the management
pack:
Configuring Run As Accounts and Profiles in OpsMgr – A SQL Management Pack Example
http://blogs.technet.com/b/kevinholman/archive/2010/09/08/configuring-run-as-accounts-and-profiles-in-r2-a-sql-management-pack-example.aspx
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCOM 2012 SP1/R2 Monitoring of IBM Bladecenter doesn´t work

We tried the IBM Hardware Management Pack 4.0 and 4.5 and configured everything according to the guide. The Bladecenter is discovered correctly but we dont get any health data or Module Information. It´s almost the same as in this thread:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/ceda483b-9500-4831-869c-4b3d0f178924/cant-get-scom-2012-sp1-to-monitor-ibm-bladecenter?forum=operationsmanagerdeployment
But this problem was resolved through rediscovering the Bladecenter with SNMP v1 or v2 instead of v3 which we did right from the start. We had this Problem with SCOM 2012 SP1 and IBM HMP 4.0/4.5. Since then we upgraded to SCOM 2012 R2 and IBM HMP 4.5 and
ist still the same issue. Everything else works fine like the Hardware Management Packs for various IBM Storage etc...
Thank you.

Hi,
Do you mean the issue is gone after you rediscover the blade center with SNMP v1 and v2? If so, I will record this.
Juke Chou
TechNet Community Support

Manage DPM servers, running DPM jobs, etc from SCOM 2012 SP1

Hi,
Little background about our systems.
We have a dedicated SCOM 2012.
We have 22 DPM servers, DPM 2010 and DPM 2012 (we are upgrading to 2012 SP1, we have customers that still using Windows 2003 servers) to be managed by SCOM
We have a few DPM servers that are not located on the same domain as the SCOM server (untrusted domain).
Some problem we have
1. When we try to manage the DPM servers from the SCOM server.
From SCOM 2012 server I can “Manage DPM server” that are located in our domain but I cannot manage DPM servers located on untrusted domains (customer’s domains). I receive the below error message
"Unable to connect to <untrusted domain DPM SERVER> ID: 948
Verify that the DPM service is running on this computer"
I guess it’s because the account that I’m using to run SCOM server located in our domain and does not have the permission to open the DPM console on the untrusted domain. So I wonder if it is possible to use “RUN AS profiles/accounts”
to solve this issue, and how?
2. I have installed SCOM 2012 Operations Manager Console on my computer and then installed DPM Central Console.
When I select one dpm server (from my computer), that is on our domain, and then click “Manage DPM server” I got this error message
"Unable to connect to <our domain DPM SERVER> ID: 33333
1. Verify that the DPM service is running on this computer (YES)
2. Verify that the current user has been added to at least one of the roles in Operations Manager. (YES)
3. Open Operations Manage console and then try launching the DPM Console (THAT IS WHAT I AM TRYING TO DO)
4. If you have re-imported the management pack recently, the role configuration may be corrupt. Open the DPM-specific roles and check if the roles have task assigned to them. If not, delete the roles and recreate the...."
When I click on “Get more information” I get this error message.
"You don´t have access permission to connect to the System Center Data Access service on <SCOM SERVER>. Please check if it is a permission issue".....
Do you know why I cannot connect to any DPM server on our own domain?
Why do I get access permission error on my computer but not on the SCOM server (using the same account)?
What should we do to be able to connect to DPM servers that are on untrusted domain?
3. Is it possible to see Last Recovery Point date/time in SCOM alerts?
For me it is the first thing I look at. If it has failed 10 min ago it is not critical.
But if it is a date and time more than 1 day old, then it is critical.
I hope someone can help us with this
Br
SvBoho

Hi,
To manager DPM, I think we may need to add the account to local admin group of the DPM server.
In addition, to connect to DPM the user needs permissions to DPM/SQL Server DPMDB.
For your DCs, have your enabled agent proxy option? If not, please enable that option for all DCs.
To monitor DPM with SCOM, please also go through the below links:
http://kevingreeneitblog.blogspot.com/2011/10/managing-and-monitoring-system-center.html
http://damatisystemcenter.com/2013/10/14/monitor-data-protection-manager-2012-using-scom-2012-sp1/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Yan Li
Regards, Yan Li

SCOM 2012 SP1 : Update rollup installation failed

Hello,
I'm trying to update SCOM 2012 SP1 with UR7 but the installation rollback automatically.
Same error with others UR.
LOG MSP :
MSI (c) (08:1C) [14:49:24:772]: Product: System Center Operations Manager 2012 Server - Update 'System Center 2012 - Operations Manager SP1 UR7 Update Patch' could not be installed. Error code 1603. Additional information is available in the log file c:\logs3.log.
MSI (c) (08:1C) [14:49:24:772]: Windows Installer installed an update. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.0.9538.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: System Center 2012 - Operations
Manager SP1 UR7 Update Patch. Installation success or error status: 1603.
MSI (c) (08:1C) [14:49:24:772]: Note: 1: 1729
MSI (c) (08:1C) [14:49:24:772]: Product: System Center Operations Manager 2012 Server -- Configuration failed.
MSI (c) (08:1C) [14:49:24:772]: Windows Installer reconfigured the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.0.9538.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error
status: 1603.
MSI (c) (08:1C) [14:49:24:772]: Attempting to delete file C:\Users\ADMINJ~1\AppData\Local\Temp\10c36d.msp
MSI (c) (08:1C) [14:49:24:772]: Unable to delete the file. LastError = 32
MSI (c) (08:1C) [14:49:24:772]: Grabbed execution mutex.
MSI (c) (08:1C) [14:49:24:772]: Cleaning up uninstalled install packages, if any exist
MSI (c) (08:1C) [14:49:24:772]: Attempting to delete file C:\Users\ADMINJ~1\AppData\Local\Temp\10c36d.msp
MSI (c) (08:1C) [14:49:24:772]: MainEngineThread is returning 1603
=== Verbose logging stopped: 15/10/2014 14:49:24 ===
MOMPerfCtrsInstall.log
The uninstall is beginning.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
The uninstall has completed.
The uninstall is beginning.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.EnterpriseManagement.HealthService.Modules.DataWarehouse.InstallLog.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
The uninstall has completed.
Running a transacted installation.
Beginning the Install phase of the installation.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
An exception occurred during the Install phase.
System.FormatException: Input string was not in a correct format.
The Rollback phase of the installation is beginning.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\Microsoft.Mom.DatabaseWriteModules.InstallLog.
The Rollback phase completed successfully.
The transacted install has completed.
Running a transacted installation.
Beginning the Install phase of the installation.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
An exception occurred during the Install phase.
System.FormatException: Input string was not in a correct format.
The Rollback phase of the installation is beginning.
See the contents of the log file for the D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.dll assembly's progress.
The file is located at D:\Program Files\System Center 2012\Operations Manager\Server\APMDOTNETAgent\Microsoft.EnterpriseManagement.OperationsManager.Apm.PerformanceCounters.InstallLog.
The Rollback phase completed successfully.
The transacted install has completed.
Maybe someone have a idea about that ?
Thank you !
Jérémy

Hi,
Have your tried to review the c:\logs3.log for any potential error or indication of cause?
For more information, please review the link below:
Update Rollup 7 for System Center 2012 Operations Manager Service Pack 1
http://support.microsoft.com/kb/2965420
Update rollup packages for System Center 2012 Operations Manager
http://support.microsoft.com/kb/2906925
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCOM 2012 SP1 Update Rollup 5 - DB and DW SQL script and the Management Packs

Hi,
I am applying SCOM 2012 SP1 update rollup 5 from KB article : 2904680.
Step# 4 and 5 from the "Installation Information" sections says to run the SQL queries(UR_Datawarehouse.sql and Update_rollup_mom_db.sql) located at "%SystemDrive%\Program Files\System Center 2012 SP1\Operations
Manager\Server \SQL Script for Update Rollups\."
But I do not have "System Center 2012 SP1\Operations Manager\Server \SQL Script for Update Rollups\." folder location on my SCOM Management Servers. Similarly I do not have the MPs given in Step #6.
Can someone please let me know from where else can I get these SQL scripts and the MPs. What if I don't run these SQL scripts. Is that OK?

You will find it on below path%SystemDrive%\Program Files\System Center 2012\Operations Manager\Server \SQL Script for Update Rollups\.
inside system center 2012 folder> search to Server folder and inside it you will find SQL Script
Please remember, if you see a post that helped you please click (Vote As Helpful" and if it answered your question, please click (Mark As Answer).

SCOM 2012 SP1 is failing to install - SQL not compatible

I'm getting an error when installing SCOM 2012 SP1 stating the SQL is not supported. I have seen a few posts on the forum about this error message but so far none of the resolutions resolved my issue.
Using named instance on port 2433. Entering SQL\instance and port 2433 yields same message as seen in another post:
"The installed version of SQL server is not supported. Verify that the computer and installed version of SQL Server meet the minimum requirements for installation. Please see the Supported Configurations document for further information."
I noticed I get this in my OpsMgrSetupWizard.log
[15:03:28]: Error: :StackTrace:   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObjectSearcher.Initialize()
   at System.Management.ManagementObjectSearcher.Get()
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.Common.SetupValidationHelpers.GetRemoteOSVersion(String remoteComputer)
[15:03:28]: Debug: :IsSQLOnAValidComputer: remote OS version string was null or empty.
Notice the last line - IsSQLOnAValidComputer is null/empty. The solutions I found are to open the ports between these servers but the SQL server and SCOM server are on the same network - no firewall between them. The registry key for domain firewall
policy to 'EnableFirewall' is 0. The firewall service is disabled on both machines.
I am running the installation as a domain service account - for the DAA. It has local admin on the SQL and SCOM server. It has sysadmin DB access to the instance.
SCOM Server:
Server 2008 R2 Standard SP1
SQL Server:
Server 2008 R2 Enterprise SP1 | SQL 2012 RM 64-bit version 11.0.2100.60
Any help is greatly appreciated.

Glad to hear the issue has been resolved. Thanks for the update.
Niki Han
TechNet Community Support

Create MP via Powershell in SCOM 2012 SP1

Is it possible to create MP via Powershell in SCOM 2012 SP1? If so, how?
(New-SCOMManagementPack is unrecognized cmdlet)

$name="NewMP"
$displayname="NewMP"
$mpStore = New-Object Microsoft.EnterpriseManagement.Configuration.IO.ManagementPackFileStore
$mp = New-Object Microsoft.EnterpriseManagement.Configuration.ManagementPack($name, $displayName, (New-Object Version(1, 0, 0,0)), $mpStore)
import-scommanagementpack $mp

Power Shell Script failed to run - GetMGAlertsCount.ps1

Our SCOM 2012 R2 is getting the following script error every 45 minutes...
The PowerShell script failed with below exception
System.Management.Automation.PropertyNotFoundException: The property 'Name' cannot be found on this object. Verify that the property exists.At line:57 char:3
+ $firstLvlClass = Get-SCOMClass -Id $firstLvlMember.Name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
at CallSite.Target(Closure , CallSite , Object )
at System.Dynamic.UpdateDelegates.UpdateAndExecute1[T0,TRet](CallSite site, T0 arg0)
at CallSite.Target(Closure , CallSite , Object )
at System.Management.Automation.Interpreter.DynamicInstruction`2.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
Script Name: GetMGAlertsCount.ps1
One or more workflows were affected by this.
Workflow name: ManagementGroupCollectionAlertsCountRule
Instance name: All Management Servers Resource Pool
Instance ID: {4932D8F0-C8E2-2F4B-288E-3ED98A340B9F}
Management group: NCA2
On the management server seeing corresponding 22406 errors
System
Provider
[ Name]
Health Service Modules
EventID
22406
[ Qualifiers]
49152
Level
2
Task
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2015-04-21T18:44:03.000000000Z
EventRecordID
1303964
Channel
Operations Manager
Computer
PKSWSM001.ad.nca.com
Security
EventData
NCA2
ManagementGroupCollectionAlertsCountRule
All Management Servers Resource Pool
{4932D8F0-C8E2-2F4B-288E-3ED98A340B9F}
GetMGAlertsCount.ps1
300
System.Management.Automation.PropertyNotFoundException: The property 'Name' cannot be found on this object. Verify that the property exists.At line:57 char:3 + $firstLvlClass = Get-SCOMClass -Id $firstLvlMember.Name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ at CallSite.Target(Closure , CallSite , Object ) at System.Dynamic.UpdateDelegates.UpdateAndExecute1[T0,TRet](CallSite site, T0 arg0) at CallSite.Target(Closure , CallSite , Object ) at System.Management.Automation.Interpreter.DynamicInstruction`2.Run(InterpretedFrame
frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
System.Management.Automation.PropertyNotFoundException
I'm at a bit of a loss to troubleshoot this error. I cannot find the "GetMGAlertsCount.ps1" script to execute manually and don't have much else I can find to troubleshoot.
Thanks for your help!

1) Please check Event Log on the management server and see if there are any related errors.
Nothing
interesting found
2) On the management server, please ensure the following key exists:
HKLM:\SOFTWARE\Microsoft\System Center Operations Manager\12\Setup\Powershell\V2
Two entries found underneath this key;
(Default) (value not set)
InstallDirectory C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Powershell\
3) Action Account has access to the resources used by the PowerShell script.
is LocalSystem
4) Make sure that the computer is not over utilized.
No indication of overutilization
Thank you for the suggestions! Do you know of anything else to check?

SCOM 2012 R2 agent upgrade fails crippling agents

Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
Keith

Hi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCOM 2012 SP1 - PowerShell Script failed to run - 3 alerts appear after every reboot of the SCOM Server

Similar Messages

Maybe you are looking for