Exchange test mailbox script fails to run

Hi,
We are using System Center Operations Manager 2012 R2 (SCOM) and Exchange 2010 in our environment. We get several messages within SCOM saying that it failed running the new-TestCasConnectivityUser.ps1 script and some other Exchange related scripts.
I have searched for an answer but none of them seem to work. I ran the script manually using the Exchange Management Shell and tried with different OU's but I keep getting the default error telling me that either the password does not meet the requirements
or it can not find the OU. I am 100% sure it is not the password requirement issue because I have tried several passwords and they are all very complex. I tried changing the OU naming to domain.local/Users or other OU's that we have but none of them work.
The problem is simular to this:
http://theucguy.net/new-testcasconnectivityuserps1-script/.
I am not sure what the problem is and how I can resolve it. I am hoping that anyone could help me with this problem.
Thanks in advance,
Bram

Hi,
Please try to modify the New-TestCasConnectivity.Ps1 script and remove the parameter '-OrganisationalUnit:$OrganisationalUnit'
This parameter is responsible for specifying the OU that the new account will be created into and when it is
removed from the script, the script simply runs and installs the account into the default 'Users' OU as it should.
Quote from:
SCOM and the Exchange Test CAS Connectivity User Account
http://kevingreeneitblog.blogspot.com/2011/06/scom-and-exchange-test-cas-connectivity.html
Regards,
Yan Li
Regards, Yan Li

Similar Messages

  • SQL MP script failed to run

    Hi! I have installed the SQL MP 6.5.1.0 for SQL2005,SQL2008,SQL2012 and SQL2014. I know that I need to use one SQL RunAsAccount and add that account in the SQL RunAsProfiles to have the correct access to run the SCOM SQL scripts and get the correct
    monitoring. We have give this SQL RunAsAccount the "Local Administrator" and "sysadmin" rights on all instances through a group. This SQL servers also use UAC, then we tested to add this SQL RunAsAccount directly with sysadmin
    rights on one SQL servers instances instead through a group. But still the same problem... I haven't test the new SQL MP version 6.5.4.0 yet and I know that there is one fix for "Fixed
    Timeout error in CPU utilization monitoring scenario"
    The SQL RunAsAccount use "More Secure" and we are running the SQL RunAsProfiles target type against a Group with "Windows Computers" for all the SQL servers that we want to run this RunAsAccount against. We have the same problem
    when we tested to change the target type to "SQL Computers" 
    At most of our customer it works fine but at one customer we still get all this SQL monitor related errors:
    Power Shell Script failed to run (timeout 200 sec)
            - scriptname=CPUUsagePercentDataSource.ps1
            - workflow=Microsoft.SQLServer.2008DBEngine.ThreadsCountMonitor
    Operations Manager failed to start a process
           - command=GetSQL2008DBWinServStat.js
           - workflow=Microsoft.SQLServer.2008.Database.ServiceMonitor
    Operations Manager failed to start a process due to lack of Resources
           - command=GetSQL2012DBFreeSpace.vbs
    Operations Manager failed to run a WMI Query
             - workflow=Microsoft.SQLServer.2012.Database.ServiceMonitor
    Someone with any idea what's the problem can be?

    Hi,
    >At most of our customer it works fine but at one customer we still get all this SQL monitor related errors
    Do you mean only one SQL server has this error message poped out? If that is the case, then you may check whether the runas account configured has proper permissions on that server. You may add the account to local admin group.
    Please also go through the link below:
    http://blogs.technet.com/b/kevinholman/archive/2013/10/24/opsmgr-sql-mp-version-6-4-1-0-capabilities-and-configuration.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 - 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

  • 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]

  • 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

  • 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?

  • Exchange 2013 - Mailbox Setup Failed "The following error was generated when "$error.Clear()" 7 of 14

    I am getting the following error when I'm setting up the mailbox server as I'm currently doing a test virtual machine throughHyper-V, it seems to happen during the transport service phase of the installation which is 7/12
    Do i know need a D:\ drive for the mailbox server to work? as in my test i only have a c:\ drive but no d:\ drive
    Error:
    The following error was generated when "$error.Clear();
                if ($RoleProductPlatform -eq "amd64")
                    $useAttachMode = $false;
                    $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                    $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                    $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                    $dataFolderPath = $fastDefaultDataFolderPath;
                    if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                        $useAttachMode = $true;
                    else
                        if ($RoleIsDatacenter -eq $true)
                            $preferredDataFolderPathRoot = "D:\";
                            if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                                $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                                if ([System.IO.Directory]::Exists($dataFolderPath))
                                    $useAttachMode = $true;
                    if ($useAttachMode -eq $true)
                        &$command -action a -dataFolder $dataFolderPath -silent;
                    else
                        try
                            &$command -action i -dataFolder $dataFolderPath -silent;
                        catch
                            $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $errorMsg;
                            &$command -action u -silent;
                            try
                                if ([System.IO.Directory]::Exists($dataFolderPath))
                                    [System.IO.Directory]::Delete($dataFolderPath, $true);
                            catch
                                $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath
    + " - " + $_.Exception.Message;
                                Write-ExchangeSetupLog -Error $deleteErrorMsg;
            " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".
    Warning:
    An unexpected error has occurred and a Watson dump is being generated: The following error was generated when "$error.Clear();
                if ($RoleProductPlatform -eq "amd64")
                    $useAttachMode = $false;
                    $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                    $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                    $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                    $dataFolderPath = $fastDefaultDataFolderPath;
                    if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                        $useAttachMode = $true;
                    else
                        if ($RoleIsDatacenter -eq $true)
                            $preferredDataFolderPathRoot = "D:\";
                            if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                                $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                                if ([System.IO.Directory]::Exists($dataFolderPath))
                                    $useAttachMode = $true;
                    if ($useAttachMode -eq $true)
                        &$command -action a -dataFolder $dataFolderPath -silent;
                    else
                        try
                            &$command -action i -dataFolder $dataFolderPath -silent;
                        catch
                            $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $errorMsg;
                            &$command -action u -silent;
                            try
                                if ([System.IO.Directory]::Exists($dataFolderPath))
                                    [System.IO.Directory]::Delete($dataFolderPath, $true);
                            catch
                                $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath
    + " - " + $_.Exception.Message;
                                Write-ExchangeSetupLog -Error $deleteErrorMsg;
            " was run: "Couldnít attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnít contain old nodes belonging to the system 'Fsis'.".
                     

    Hi 
    Most likely for these kind of issues its better you can  delete the hyper-v machine and create a new  os , ensure all the prerequisite are met and install the Exchange since this is a new installation.
    But as a try you can try giving full access to the admin account to the data folder  'C:\Program
    Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. which is giving the error and rerun the setup 
    Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

  • Exchange 2013 mailbox restore fails cannot open mailbox microsoft system attendant

    I am having problems when trying to restore a mailbox.
    I get an error:
    Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MBXsvr/cn=Microsoft System Attendant
    This is the first time I have tried restoring mailbox on this 2013 Server. This 2013 server is from a recent 2010 migration.
    I also recently lost Discovery Search mailbox and had to recreate it.
    I found an article on 2010 that says to set the homeMDB, but I am not sure if that is needed in 2013. There is none set in this AD.

    Hi,
    I searched and found that someone got the same error and resolved it by repairing the recovery database.
    Please repair your recovery database to check result.
    Instead of using the production space, try moving the RDB over to a test environment and running the New-MailboxRepairRequest there, then move it back
    to the production environment. To repair recovery database, you can follow steps below.
    1. Spin up a test environment.
      ○ Create a test-production DB in the test environment.
      ○ Dismount the DB in the test environment and rename it
    to old (or just delete it if it has no data that needs
    to be kept).
    2. Bring over the recovery DB to the test environment.
      ○ Rename it to match the test-production DB and put it in the test-productionDB location.
      ○ Mount the RDB in the test environment (as if it were the test-productionDB)
      ○ Run the New-MailboxRepairRequest to repair the affected mailbox
      ○ Once complete, dismount the recoveryDB.
    3. Bring the recovery DB back to the production environment.
      ○ Rename it to it's original name and put it back in it's original location.
      ○ Mount the RDB in it's original (rdb) location with it's original RDB name.
      ○ Run the New-MailboxRestoreRequest to merge the affected mailbox back into the production space.
    Hope this is helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Root.sh script failed to run after 11gR2 grid installation

    Hi,
    I am trying to install 11gR2 on RHEL 5.3 . however I have problems running th post install script on both nodes.
    here is the output of the root.sh script on the first node :
    [root@rac1 grid]# ./root.sh
    Running Oracle 11g root.sh script...
    The following environment variables are set as:
    ORACLE_OWNER= oracle
    ORACLE_HOME= /u01/app/11.2.0/grid
    Enter the full pathname of the local bin directory: [usr/local/bin]:
    Entries will be added to the /etc/oratab file as needed by
    Database Configuration Assistant when a database is created
    Finished running generic part of root.sh script.
    Now product-specific root actions will be performed.
    Can't locate auto/DynaLoader/dl_findfile.al in @INC (@INC contains: /u01/app/11.2.0/grid/perl/lib/5.10.0/x86_64-linux-thread-multi /u01/app/11.2.0/grid/perl/lib/5.10.0 /u01/app/11.2.0/grid/perl/lib /u01/app/11.2.0/grid/crs/install /u01/app/11.2.0/grid/perl/lib/5.10.0/x86_64-linux-thread-multi /u01/app/11.2.0/grid/perl/lib/5.10.0 /u01/app/11.2.0/grid/perl/lib/site_perl/5.10.0/x86_64-linux-thread-multi /u01/app/11.2.0/grid/perl/lib/site_perl/5.10.0 /u01/app/11.2.0/grid/perl/lib/5.10.0/x86_64-linux-thread-multi /u01/app/11.2.0/grid/perl/lib/5.10.0/x86_64-linux-thread-multi /u01/app/11.2.0/grid/perl/lib/5.10.0 /u01/app/11.2.0/grid/perl/lib/site_perl/5.10.0/x86_64-linux-thread-multi /u01/app/11.2.0/grid/perl/lib/site_perl/5.10.0 /u01/app/11.2.0/grid/perl/lib/site_perl . /u01/app/11.2.0/grid/crs/install) at /u01/app/11.2.0/grid/perl/lib/5.10.0/x86_64-linux-thread-multi/DynaLoader.pm line 171
    BEGIN failed--compilation aborted at /u01/app/11.2.0/grid/perl/lib/5.10.0/x86_64-linux-thread-multi/Fcntl.pm line 216.
    Compilation failed in require at /u01/app/11.2.0/grid/perl/lib/5.10.0/Net/Ping.pm line 10.
    BEGIN failed--compilation aborted at /u01/app/11.2.0/grid/perl/lib/5.10.0/Net/Ping.pm line 10.
    Compilation failed in require at /u01/app/11.2.0/grid/crs/install/rootcrs.pl line 218.
    BEGIN failed--compilation aborted at /u01/app/11.2.0/grid/crs/install/rootcrs.pl line 218.
    I found the required auto/DynaLoader/dl_findfile.al file :
    [root@rac1 grid]# find /. -name dl_findfile.al
    /./orainst/app/crs/perl/lib/5.8.3/x86_64-linux-thread-multi/auto/DynaLoader/dl_findfile.al
    /./usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/auto/DynaLoader/dl_findfile.al
    but I don't know how or where to change the perl include libraries.
    Please Advise

    Hi,
    no I don't have PERL5LIB environment set to some value for root.
    I added the path in the root.sh file to the system perl-5.8.8 include file and change the perlbin to use the system /usr/bin/perl executable and then the root.sh file did run and finished succesfully.
    However other utilities have the same problems . like running asmcmd.
    Do you have any idea how to fix it globally?
    Thanks

  • Root.sh script fail to run on OEL5.4

    hi, I am trying to install Grid Infrastructure for a Standalone Server on Oracle Enterprise Linux 5.4. i have a problem when i run root.sh script through root user its not execute successufly the error is "error while loading shared libraries" Please give any soluciton.
    Here is the execution of root.sh script
    [root@ws1 OraGrid11gR2]# ./root.sh
    Running Oracle 11g root.sh script...
    The following environment variables are set as:
    ORACLE_OWNER= grid
    ORACLE_HOME= /opt/grid/OraGrid11gR2
    Enter the full pathname of the local bin directory: [usr/local/bin]:
    Copying dbhome to /usr/local/bin ...
    Copying oraenv to /usr/local/bin ...
    Copying coraenv to /usr/local/bin ...
    Creating /etc/oratab file...
    Entries will be added to the /etc/oratab file as needed by
    Database Configuration Assistant when a database is created
    Finished running generic part of root.sh script.
    Now product-specific root actions will be performed.
    2009-11-02 18:18:28: Checking for super user privileges
    2009-11-02 18:18:28: User has super user privileges
    2009-11-02 18:18:28: Parsing the host name
    Using configuration parameter file: /opt/grid/OraGrid11gR2/crs/install/crsconfig_params
    Creating trace directory
    /opt/grid/OraGrid11gR2/bin/ocrconfig.bin: error while loading shared libraries:/opt/grid/OraGrid11gR2/lib/libclntsh.so.11.1: cannot restore segment prot after reloc: Permission denied
    Failed to create or upgrade OLR
    Please give any solution

    This installation should be very very simple and straight-forward but it has taken me over a week to sort it out.
    What nobody pointed out is the fact that the best way to go about it is:
    1. Deinstall the install
    2. Make sure SELINUX=disabled is set in /etc/selinux/conf ....bounce it if necessary
    3. Do the install again afresh
    I didn't know it can be this easy.....I have gone thru every note and onto Metalink without any luck. Now I am delighted and can go on with my practices.

  • Power Shell Script failed to run

    Hi
    I think this alert is due to a faulty management pack, specifically in the module mentioned. I'm trying to investigate further. We have this on multiple
    servers and across different roles. 
    How do I get access to this script so I can find out what it is timing out on? Where's the output of this script kept? 
    I'm still new to SCOM2012 and think while its and improvement its still got bugs left over from 2007.
    Alert description: Forced to terminate the following PowerShell script because it ran past the configured timeout 300 seconds.
    Script Name:    CheckMaxConcurrentAPI.ps1
    One or more workflows were affected by this.
    Workflow name: Microsoft.Windows.Server.2008.MaxConcurrentAPI.Monitor
    Instance name: Microsoft Windows Server 2008 R2 Enterprise
    Instance ID: {81CDE473-D76E-3459-58B1-5DB67AC6B574}
    Management group: OM2012

    This workflow came from Windows Server 2008 Max Concurrent API Monitor.
    The most likey cause of tmeout is due to permission issue.
    Please make sure that your default action account has the following right on local mcahine
    • Member of the local users group
    • Member of the local Performance Monitor Users group
    • Granted Log On Locally rights
    Beside, you can find the script on
    SCOM 2012 R2
    c:\Program Files\Micosoft Monitoring Agent\Agent\Health Service state
    SCOM 2012
    c:\program Files\System Center Operations Manager\Agent\Health Service state
    Roger

  • Powershell startup scripts fail on Windows 8.1 with error 267

    GPO Powershell startup script fails to execute on Windows 8.1, but does run on Windows 8 and Windows 7. Powershell logon scripts run normally on all versions of Windows.
    The event log contains entries with event ID 1130 from the GroupPolicy source. The log entries claim error 267 "directory name is invalid".
    Running cmd.exe on Windows 8.1 under the computer's account (NT Authority\SYSTEM) confirms that the Powershell script's path in SYSVOL is valid and the script executes normally.
    Running procmon on Windows 8.1 while the startup script is being run on a computer shows that the computer caches the files and folders for this GPO into C:\Windows\system32\GroupPolicy.
    I am not sure why these scripts are failing to execute on Windows 8.1 when they run on Windows 8 and the same set of GPOs are applied to both Windows 8.1 and Windows 8 computers.

    These are all good suggestions, but I have already tried to eliminate:
    All environment variables
    All network paths
    Setup the GPO to reference the script by the file name and with a full absolute path. Neither worked.
    Tried copying the scripts to multiple folders inside the policy, since the event log message reports only the root path of the policy.
    I also used procmon to monitor how the computer handles the startup scripts. I found that the computer caches them into a folder under C:\Windows\System32, but never runs any of them. I never found an error that I could correlate with the event log.
    For instance the following one line scripts failed to run:
    'I AM HERE.' | sc -path C:\Windows\TEMP\TEST.txt
    write-host 'I AM HERE.'
    As far as I can see the first script relies on the existence of C:\Windows\TEMP and write permission to it, which SYSTEM should have.
    The second one liner has no dependencies at all and it doesn't run with the same error.
    I have created multiple GPOs and scripts, so if there was a problem in creating these files and folders it is happening over and over. I checked the permissions and computer accounts have read and execute permissions all throughout the GPOs.
    Everything works perfectly on Windows 7 and 8, just not on 8.1.

  • CodedUI script fails in MTM will pass in VSTS

    Coded UI scripts fail when running on agent Machine but passes when running on Local System. Need help to identify the root cause

    Hi yellesh,
    Based on your issue, please you provide the detail error message and the Test Run log to me after you run coded UI test script fail from MTM.
    I suggest you could refer the following MSDN document to check about how to run a automated test case from MTM.
    https://msdn.microsoft.com/en-us/library/dd380741.aspx
    Since I know that when MTM run the Coded UI test on test agent machine, the test agents are set up in the lab environment. Please do not lock or have an active screen saver on the test agent. For more information, you can refer to
    http://msdn.microsoft.com/en-us/library/ee291332.aspx
    Therefore, please you refer the above document to check if you set up your agent to run as a process instead of a service.
    If the above suggestion could not help you, please share me more message about your issue.
    Best Regards,
    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.
    Click
    HERE to participate the survey.

  • Exchange 2010 MP : Some Client Access test cmdlets failed to run

    Hi all,
    This error is triggered in SCOM 2012 R2 about a single Exchange 2010 SP3 server :
    Exchange 2010 MP : Some Client Access test cmdlets failed to run.
    When I dig into the error context, I can see it's about the cmdlet "Test-CalendarConnectivity -TestType:External".
    The TechNet
    https://technet.microsoft.com/en-us/library/hh377605(v=exchg.140).aspx proposes to verify that the URL for the external virtual directory can be accessed by running the Test-OwaConnectivity.
    OK.
    But what sould I specify for the parameter -MailBoxCredential required for Test-OwaConnectivity -URL my_url -MailBoxCredential ?
    Thank you.
    Have a good day.
    FXE

    Hi,
    Under Administration, run as configuration, profiles, you can check Default action account.
    Local system is the account account for agents by default, you can change to use another account.
    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]

  • Exchange mailbox script

    Hi,We have been successfully using the attached script with Exchange 2013. Each time we upgraded Spiceworks all we had to do was change the spiceworks version number in the script. Since upgrade 7.4.00070 the script no longer works. Has anything changed in this latest version that would cause the script to stop working? I haven't done any Windows updates on the Exchange server or made any changes since it last successfully worked. When I manually run it I can't see any errors occurring either, it gets to mailboxes found 107 then disappears. Something else I've noticed since the upgrade is that the scheduled scans just about grind the server to a halt. Could it be a memory issue effecting the script? We have 4 admins but there is only 1-2 logged in at a time and not everyday. We have 247 devices and the server is a VM 2012 64bit R1 with...
    This topic first appeared in the Spiceworks Community

    Hi,
    Please try to modify the New-TestCasConnectivity.Ps1 script and remove the parameter '-OrganisationalUnit:$OrganisationalUnit'
    This parameter is responsible for specifying the OU that the new account will be created into and when it is
    removed from the script, the script simply runs and installs the account into the default 'Users' OU as it should.
    Quote from:
    SCOM and the Exchange Test CAS Connectivity User Account
    http://kevingreeneitblog.blogspot.com/2011/06/scom-and-exchange-test-cas-connectivity.html
    Regards,
    Yan Li
    Regards, Yan Li

Maybe you are looking for