Exception during execution ошибка - Не ошибается лишь тот, кто ничего не делает!

Troubleshooting
Issues with Cisco UCS B-Series Operation

This chapter includes the following sections:

Troubleshooting Cisco UCS Manager Initial Configuration

Verify Console
Setup

You can verify that
both fabric interconnect configurations are complete by logging into the fabric
interconnect via SSH and verifying the cluster status through CLI. For this
procedure, you can watch
Cisco UCS Manager Initial Setup part 3.

Use the following
commands to verify the cluster state:

Command	Purpose	Sample Output
show cluster state	Displays the operational state and leadership role for both fabric interconnects in a high availability cluster.	The following example displays that both fabric interconnects are in the Up state, HA is in the Ready state, fabric interconnect A has the primary role, and fabric interconnect B has the subordinate role: `UCS-A# show cluster state Cluster Id: 0x4432f72a371511de-0xb97c000de1b1ada4 A: UP, PRIMARY B: UP, SUBORDINATE HA READY`
show cluster extended-state	Displays extended details about the cluster state and typically used when troubleshooting issues.	The following example shows how to view the extended state of a cluster: UCSC# show cluster extended-state 0x2e95deacbd0f11e2-0x8ff35147e84f3de2Start time: Thu May 16 06:54:22 2013Last election time: Thu May 16 16:29:28 2015System Management Viewing the Cluster State A: UP, PRIMARY B: UP, SUBORDINATE A: memb state UP, lead state PRIMARY, mgmt services state: UP B: memb state UP, lead state SUBORDINATE, mgmt services state: UP heartbeat state PRIMARY_OK HA READY Detailed state of the device selected for HA quorum data: Device 1007, serial: a66b4c20-8692-11df-bd63-1b72ef3ac801, state: active Device 1010, serial: 00e3e6d0-8693-11df-9e10-0f4428357744, state: active Device 1012, serial: 1d8922c8-8693-11df-9133-89fa154e3fa1, state: active

Command

Purpose

Sample
Output

show cluster state

Displays the
operational state and leadership role for both fabric interconnects in a high
availability cluster.

The
following example displays that both fabric interconnects are in the Up state,
HA is in the Ready state, fabric interconnect A has the primary role, and
fabric interconnect B has the subordinate role:

UCS-A# show cluster state 
Cluster Id: 0x4432f72a371511de-0xb97c000de1b1ada4 

A: UP, PRIMARY 
B: UP,
SUBORDINATE HA READY

show cluster
extended-state

Displays
extended details about the cluster state and typically used when
troubleshooting issues.

The
following example shows how to view the extended state of a cluster:

UCSC# show cluster extended-state 0x2e95deacbd0f11e2-0x8ff35147e84f3de2Start time: Thu May 16 06:54:22 2013Last election time: Thu May 16 16:29:28 2015System Management
Viewing the Cluster State
A: UP, PRIMARY
B: UP, SUBORDINATE

A: memb state UP, lead state PRIMARY, mgmt services state: UP
B: memb state UP, lead state SUBORDINATE, 
mgmt services state: UP heartbeat state PRIMARY_OK 
HA READY 
Detailed state of the device selected for HA quorum data: 
Device 1007, serial: a66b4c20-8692-11df-bd63-1b72ef3ac801, state: active 
Device 1010, serial: 00e3e6d0-8693-11df-9e10-0f4428357744, state: active 
Device 1012, serial: 1d8922c8-8693-11df-9133-89fa154e3fa1, state: active

Troubleshooting Boot Issues

Reboot Warning Does Not Display

Problem—The system fails to produce a reboot warning that lists any dependencies.

Possible Cause—This problem can be caused by changes to a vNIC template or a vHBA template. Reboot warnings occur when the
back-end returns a list of dependencies. When you update the template type for a vNIC or vHBA template and make changes to
any boot-related properties without applying changes between steps, the back-end systems are not triggered to return a list
of dependencies.

Procedure

Step 1

Launch the Cisco UCS Manager GUI.

Step 2

In the vNIC template or vHBA template included in the service profile, do the following:

Change the template type from
Initial Template to
Updating Template.
Click
Save Changes.

Step 3

Make any additional changes to the reboot-related values and
click Save Changes.

A reboot warning and the list of dependencies are displayed.

Server Does Not Boot
from OS Installed on eUSB

Problem—The eUSB
embedded inside the Cisco UCS server includes an operating system. However, the
server does not boot from that operating system.

Possible Cause—This
problem can occur when, after associating the server with the service profile,
the eUSB is not at the top of the actual boot order for the server.

Procedure

Step 1	Launch the Cisco UCS Manager GUI.
Step 2	On Servers, do the following to verify the boot policy configuration: Navigate to the service profile associated with the server. In the Work pane, click the Boot Order tab Ensure that Local Disk is configured as the first device in the boot policy.
Step 3	On Equipment, do the following to verify the actual boot order for the server: Navigate to the server. On the General tab, expand the Boot Order Details area and verify that the eUSB is listed as the first device on the Actual Boot Order tab. For example, the first device should be VM eUSB DISK.
Step 4	If the eUSB is not the first device in the actual boot order, do the following: On the General tab for the server, click the following links in the Actions area: Click KVM Console to launch the KVM console. Click Boot Server to boot the server. In the KVM console, while the server is booting, press `F2` to enter the BIOS setup. In the BIOS utility, click on the Boot Options tab. Click Hard Disk Order. Configure Boot Option #1 to the eUSB. For example, set this option to `VM eUSB DISK`. Press `F10` to save and exit.

Server Does Not Boot
After RAID1 Cluster Migration

Problem—The server
does not boot from the operating system after a RAID1 cluster migration. The
RAID LUN remains in “inactive” state during and after service profile
association. As a result, the server cannot boot.

Possible Cause—This
problem can occur if the local disk configuration policy in the service profile
on the server is configured with
Any
Configuration mode rather than RAID1.

Procedure

Step 1

In
Cisco UCS Manager GUI,
click
Servers.

Step 2

Navigate to the
service profile associated with the server and click the
Storage tab.

Step 3

Do one of the
following:

Change the
local disk configuration policy included in the service profile to the same
policy included in the service profile associated with the server prior to the
migration, as follows:
- In the
  Actions area, click
  Change Local Disk Configuration Policy.
- From the
  Select the Local Disk Configuration Policy drop-down
  list, choose the appropriate policy.
- Click
  OK.
Change the
mode property in the local disk configuration policy included in the service
profile, as follows:
- In the
  Local Disk Configuration Policy area of the
  Storage tab, click the link in the
  Local Disk Policy Instance field.
- In the
  Mode field, ensure that the
  Raid 1 Mirrored option is chosen.
- Click
  Save Changes.

Troubleshooting KVM Issues

BadFieldException When Launching the KVM Viewer

Problem—The BadFieldException error appears when the KVM viewer is launched.

Possible Cause—This problem can occur because the Java Web Start disables the cache by default when it is used with an application
that uses native libraries.

Procedure

Step 1	Choose .
Step 2	Click on the General tab.
Step 3	In the Temporary Internet Files area, click Settings.
Step 4	Click the Keep temporary files on my computer check box.
Step 5	Click OK.

KVM Console Failure

Problem—The KVM console fails to launch and the JRE displays the following message:


Unable to launch the application.

Possible Cause—This problem can be caused if several KVM consoles are launched simultaneously.

Procedure

Step 1	If possible, close all of the open KVM consoles.
Step 2	Relaunch the KVM consoles one at a time.

KVM Fails to Open

Problem—The first time you attempt to open the KVM on a server, the KVM fails
to launch.

Possible Cause—This problem can be caused by a JRE version incompatibility.

Procedure

Step 1	Upgrade to JRE 1.6_11.
Step 2	Reboot the server.
Step 3	Launch the KVM console.

Troubleshooting VM issues

No Ports Available
for Distributed Virtual Switch

Problem—The
following error displays:


Currently connected network interface x uses Distributed Virtual Switch (uusid:y) which is 
accessed on the host via a switch that has no free ports.

Possible Cause—This
problem can be caused by one of the following issues:

After powering
off or migrating a VM from one host to another, the vSphere server fails to
recompute the numPortsAvailable property in the hostProxySwitch object.
The cumulative
number of vNICs for the VMs powered on an ESX host matches or exceeds the
number of dynamic nVINCs configured in the server’s service profile.
After migrating
a VM from one data-store to another data-store on the same server, the server
incorrectly detects an increase in the number of DVS ports being used by all of
the VMs powered on the host.

Procedure

Step 1

Identify what
you were doing when the error displayed.

Step 2

If the error
resulted from powering off a VM, or from migrating a VM from one host to
another, do the following:

Migrate a
second VM from the ESX host to another system.
When a
second port is made available, do one of the following:
- Power on
  a VM.
- Migrate
  a VM back to the ESX host.

Step 3

If the error
resulted from migrating a VM instance from one data-store to another data-store
on the same server, do the following:

Shut down
all of the VMs on the ESX host.
Retry the
migration.

Troubleshooting Cisco UCS Manager Issues

DME Process Timed Out

Problem—When you run Cisco UCS Manager CLI commands, Cisco UCS Manager CLI displays the following message:

Software Error: Exception during execution: [Error: Timed out communicating with DME]

Possible Cause—This problem occurs when the DME process on the primary fabric interconnect is either unresponsive or has
crashed, and is not in the running state. Other symptoms that appear when the DME is down are:

Cisco UCS Manager GUI becomes unresponsive
Connectivity to Virtual IP goes down

Procedure

Step 1	Gather information on the sequence of events, such as upgrade of Cisco UCS Manager and configuration changes, that lead the system to this state.
Step 2	Connect to each fabric interconnect by using its individual IP address, and verify the cluster status, process and core dumps by using the following commands: UCS-A# connect local-mgmt Enters local management mode for the cluster. UCS-A (local-mgmt) # show cluster extended-state Displays the state of fabric interconnects in the cluster and whether the cluster is HA ready. UCS-A(local-mgmt)# show pmon state Displays the state of all processes within Cisco UCS Manager. UCS-A(local-mgmt)# ls workspace:/cores Displays a list of all core dumps in workspace.
Step 3	Identify the primary fabric interconnect, and whether HA election is incomplete.
Step 4	Review NXOS logs for fabric interconnect hardware issues by using the following commands: UCS-A# connect nxos {a \| b} Enters NX-OS mode for the fabric interconnect. UCS-A(nxos)# show logg Displays details about log files.
Step 5	Collect technical support information for Cisco UCS Manager from local-mgmt CLI by using the following commands: UCS-A# connect local-mgmt Enters local management mode for the cluster. UCS-A(local-mgmt)# show tech-support ucsm detail Displays technical support information for Cisco UCS Manager.

What to do next

Contact TAC with these logs and information to further investigate the failure.

Event Sequencing Fatal Error

Problem—After coming back from sleep mode, the Cisco UCS Manager GUI displays the following message:


Fatal error: event sequencing is skewed.

Possible Cause—This problem can be caused if the Cisco UCS Manager GUI was running when the computer went to sleep. Since
the JRE does not have a sleep detection mechanism, the system is unable to retrack all of the messages received before it
went into sleep mode. After multiple retries, this event sequencing error is logged.

Note

Always shut down Cisco UCS Manager GUI before putting your computer
to sleep.

Procedure

In Cisco UCS Manager GUI, if a
Connection Error dialog box is displayed, click
one of the following:

Click
Re-login to log back in to the Cisco UCS
Manager GUI.
Click
Exit to exit the Cisco UCS Manager GUI.

Troubleshooting Fabric Interconnect Issues

Recovering a Fabric Interconnect from the Boot Loader Prompt

If the fabric interconnect fails to start, you may have one of the following issues:

The kickstart image is corrupted or non-functional for other reasons
The file system on the bootflash memory is corrupted

If either of these issues exist, you might need to use the boot loader prompt to recover the fabric interconnect.

Procedure

Contact Cisco Technical Assistance Center to obtain the firmware recovery images and information about how to recover the fabric interconnect from the boot loader
prompt.

Resolving Fabric Interconnect Cluster ID Mismatch

Problem—When you set up two fabric interconnects to support a high availability cluster and connect the L1 ports and L2 ports,
a fabric interconnect cluster ID mismatch can occur. This type of mismatch means that the cluster fails and Cisco UCS Manager
cannot be initialized.

Procedure

Step 1

In Cisco UCS Manager CLI, connect to fabric interconnect B and
execute
erase configuration .

All configuration on the fabric interconnect is erased.

Step 2

Reboot fabric interconnect B.

After rebooting, fabric interconnect B detects the presence of
fabric interconnect A and downloads the cluster ID from fabric interconnect A.
You need to configure the subordinate fabric interconnect for the cluster configuration.

Step 3

When the unconfigured system boots, it prompts you for the setup
method to be used. Enter

console
to continue the initial setup using the
console CLI.

Note

The fabric interconnect should detect the peer fabric
interconnect in the cluster. If it does not, check the physical connections
between the L1 and L2 ports, and verify that the peer fabric interconnect has
been enabled for a cluster configuration.

Step 4

Enter

y
to add the subordinate fabric interconnect to
the cluster.

Step 5

Enter the admin password of the peer fabric interconnect.

Step 6

Enter the IP address for the management port on the subordinate
fabric interconnect.

Step 7

Review the setup summary and enter

yes
to save and apply the settings, or enter

no
to go through the Setup wizard again to change
some of the settings.

If you choose to go through the Setup wizard again, it provides the values you previously entered, and the values
appear in brackets. To accept previously entered values, press Enter.

Troubleshooting Server Disk Drive Detection and Monitoring

Support for Local
Storage Monitoring

The type of
monitoring supported depends upon the
Cisco UCS
server.

Supported
Cisco UCS
Servers for Local Storage Monitoring

Through
Cisco UCS Manager,
you can monitor local storage components for the following servers:

Cisco UCS
B200 M3 blade server
Cisco UCS
B420 M3 blade server
Cisco UCS
B22 M3 blade server
Cisco UCS
B200 M4 blade server
Cisco UCS
B260 M4 blade server
Cisco UCS
B460 M4 blade server
Cisco UCS
C460 M2 rack server
Cisco UCS
C420 M3 rack server
Cisco UCS
C260 M2 rack server
Cisco UCS
C240 M3 rack server
Cisco UCS
C220 M3 rack server
Cisco UCS
C24 M3 rack server
Cisco UCS
C22 M3 rack server
Cisco UCS
C220 M4 rack server
Cisco UCS
C240 M4 rack server
Cisco UCS
C460 M4 rack server

Note

Not all servers
support all local storage components. For
Cisco UCS
rack servers, the onboard SATA RAID 0/1 controller integrated on motherboard is
not supported.

Supported
Cisco UCS
Servers for Legacy Disk Drive Monitoring

Only legacy disk
drive monitoring is supported through
Cisco UCS Manager
for the following servers:

Cisco UCS
B200 M1/M2 blade server
Cisco UCS
B250 M1/M2 blade server

Note

In order for
Cisco UCS Manager
to monitor the disk drives, the 1064E storage controller must have a firmware
level contained in a UCS bundle with a package version of 2.0(1) or higher.

Prerequisites for
Local Storage Monitoring

These prerequisites
must be met for local storage monitoring or legacy disk drive monitoring to
provide useful status information:

The drive must
be inserted in the server drive bay.
The server must
be powered on.
The server must
have completed discovery.
The results of
the BIOS POST complete must be TRUE.

Viewing the Status of a Disk Drive

Viewing the Status
of Local Storage Components
in the Cisco UCS Manager
GUI

Procedure

Step 1	In the Navigation pane, click Equipment.
Step 2	Expand .
Step 3	Click the server for which you want to view the status of your local storage components.
Step 4	In the Work pane, click the Inventory tab.
Step 5	Click the Storage subtab to view the status of your RAID controllers and any FlexFlash controllers.
Step 6	Click the down arrows to expand the Local Disk Configuration Policy, Actual Disk Configurations, Disks, and Firmware bars and view additional status information.

Interpreting the
Status of a Monitored Disk Drive

Cisco UCS Manager displays the following properties for
each monitored disk drive:

Operability—The operational state of the drive.
Presence—The presence of the disk drive, and whether it can
be detected in the server drive bay, regardless of its operational state.

You need to look at
both properties to determine the status of the monitored disk drive. The
following table shows the likely interpretations of the combined property
values.

Operability Status	Presence Status	Interpretation
Operable	Equipped	No fault condition. The disk drive is in the server and can be used.
Inoperable	Equipped	Fault condition. The disk drive is in the server, but one of the following could be causing an operability problem: The disk drive is unusable due to a hardware issue such as bad blocks. There is a problem with the IPMI link to the storage controller.
N/A	Missing	Fault condition. The server drive bay does not contain a disk drive.
N/A	Equipped	Fault condition. The disk drive is in the server, but one of the following could be causing an operability problem: The server is powered off. The storage controller firmware is the wrong version and does not support disk drive monitoring. The server does not support disk drive monitoring.

Note

The
Operability field might show the incorrect status
for several reasons, such as if the disk is part of a broken RAID set or if the
BIOS power-on self-test (POST) has not completed.

HDD Metrics Not Updated in Cisco UCS Manager GUI

Problem—After hot-swapping, removing, or adding a hard drive, the updated hard disk drive (HDD) metrics do not appear in the
Cisco UCS Manager GUI.

Possible Cause—This problem can be caused because Cisco UCS Manager gathers HDD metrics only during a system boot. If a hard
drive is added or removed after a system boot, the Cisco UCS Manager GUI does not update the HDD metrics.

Procedure

Disk Drive Fault Detection Tests Fail

Problem—The fault LED is illuminated or blinking on the server disk drive, but Cisco UCS Manager does not indicate a disk drive failure.

Possible Cause—The disk drive fault detection tests failed due to one or more of the following conditions:

The disk drive did not fail, and a rebuild is in progress.
Drive predictive failure
Selected drive failure on Disk 2 of a B200, B230 or B250 blade
Selected drive failure on Disk 1 of a B200, B230 or B250 blade

Procedure

Step 1	Monitor the fault LEDs of each disk drive in the affected server(s).
Step 2	If a fault LED on a server turns any color, such as amber, or blinks for no apparent reason, create technical support file for each affected server and contact Cisco Technical Assistance Center.

Cisco UCS Manager Reports More Disks in Server than Total Slots
Available

Problem—Cisco UCS Manager reports that a server has more disks than the total disk slots available in the server. For example, Cisco UCS Manager reports three disks for a server with two disk slots as follows:


RAID Controller 1:
           Local Disk 1:
               Product Name: 73GB 6Gb SAS 15K RPM SFF HDD/hot plug/drive sled mounted
               PID: A03-D073GC2
               Serial: D3B0P99001R9
               Presence: Equipped
           Local Disk 2: 
               Product Name:
               Presence: Equipped
               Size (MB): Unknown
           Local Disk 5:
               Product Name: 73GB 6Gb SAS 15K RPM SFF HDD/hot plug/drive sled mounted
               Serial: D3B0P99001R9
               HW Rev: 0
               Size (MB): 70136

Possible Cause—This problem is typically caused by a communication failure between
Cisco UCS Manager and the server that reports the inaccurate information.

Procedure

Step 1	Upgrade the Cisco UCS domain to the latest release of Cisco UCS software and firmware.
Step 2	Decommission the server.
Step 3	Recommission the server.

Troubleshooting Post-Upgrade IQN Issues

Clearing the
Duplicate IQN Fault and Reconfiguring IQN Initiator Names

Problem—After an
upgrade from
Cisco UCS, Release 2.0(1) to Release 2.0(2),
Cisco UCS Manager raises an IQN-related fault on one or more service profiles when
you attempt to perform an action on a service profile, such as modifying the
host firmware package.

Possible Cause—One
or more iSCSI vNICS used within a single service profile or across multiple
service profiles did not have a unique IQN initiator name.

Procedure

Step 1

Log into the
Cisco UCS Manager CLI.

Step 2

Run the
following command to view a list of the IQNs in the
Cisco UCS domain:

UCS-A#
show identity iqn |
include iqn name

Step 3

In
Cisco UCS PowerTool, run the script to identify the iSCSI vNICs which include the
duplicate IQNs.

Step 4

In the service
profile to which the IQN initiator name is not registered, change the initiator
identity to the default IQN pool or manually assign a unique IQN.

Step 5

In the service
profile in which you changed the initiator identity, change the initiator
assignment to the name or pool you assigned, as follows:

UCS-A #
scope org org-name

Enters
organization mode for the specified organization. To enter the root
organization mode, type
/ as the
org-name.
UCS-A /org #

scope
service-profile profile-name

Enters
service profile organization mode for the service profile.

UCS-A/org#
scope
vnic-iscsi
iscsi_vnic_name

Enters the
mode for the specified iSCSI vNIC.

Note

This vNIC
is not registered or visible through
show identity
iqn .

UCS-A
/org/service-profile/vnic-iscsi* #

set
iscsi-identity {initiator-name
initiator-name |
initiator-pool-name
iqn-pool-name}

Specifies
the name of the iSCSI initiator or the name of an IQN pool from which the iSCSI
initiator name will be provided. The iSCSI initiator name can be up to 223
characters.
UCS-A
/org/service-profile/vnic-iscsi #
commit-buffer

Commits the
transaction to the system configuration.

Note

Changing
initiator names also involves storage side configuration, which is beyond the
scope of this document.

Step 6

Perform an
action on the service profile to register the initiator names in the
Cisco UCS database.

For example, you
can upgrade the firmware on the associated server or modify the description or
label of the service profile.

Step 7

Run the
following command to verify that the IQN changes were registered:

UCS-Ashow identity iqn |
include iqn name

Obtaining
Cisco UCS PowerTool and Running the Duplicate IQN Script

If a
Cisco UCS domain is configured for iSCSI boot, before you upgrade from
Cisco UCS,
Release 2.0(1) to
Cisco UCS,
Release 2.0(2) or higher, you must ensure that all iSCSI vNICs used across
multiple service profile have unique initiator names.

You can use a script
that runs in the
Cisco UCS PowerTool to determine whether a
Cisco UCS configuration for iSCSI boot includes duplicate IQNs.

Procedure

Step 1	To download Cisco UCS PowerTool, do the following: In your web browser, navigate to the following website: http://developer.cisco.com/web/unifiedcomputing/microsoft Scroll down to the Cisco UCS PowerTool (PowerShell Toolkit) Beta Download area. Download the CiscoUcs-PowerTool-0.9.6.0.zip file. Unzip the file and follow the prompts to install Cisco UCS PowerTool. You can install Cisco UCS PowerTool on any Windows computer. You do not need to install it on a computer used to access Cisco UCS Manager.
Step 2	To launch Cisco UCS PowerTool, enter the following at a command line: C:Program Files (x86)CiscoCisco UCS PowerTool>C:WindowsSystem32windowspowe rshellv1.0powershell.exe -NoExit -ExecutionPolicy RemoteSigned -File .StartUc sPS.ps1 Example: The following example shows what happens when you launch Cisco UCS PowerTool: `C:Program Files (x86)CiscoCisco UCS PowerTool>C:WindowsSystem32windowspowershellv1.0powershell.exe -NoExit -ExecutionPolicy RemoteSigned -File .StartUcsPS.ps1 Windows PowerShell Copyright (C) 2009 Microsoft Corporation. All rights reserved.`
Step 3	In Cisco UCS PowerTool, do the following: Connect to Cisco UCS Manager, as follows: PS C:> Connect-Ucs `IP_address` Enter your username and password when prompted for your credential as shown in the following example: `cmdlet Connect-Ucs at command pipeline position 1 Supply values for the following parameters: Credential` Cisco UCS PowerTool outputs the following to your screen after you log in. `Cookie : 1331303969/2af0afde-6627-415c-b85f-a7cae6233de3 Domains : LastUpdateTime : 3/9/2012 6:20:42 AM Name : 209.165.201.15 NoSsl : False NumPendingConfigs : 0 NumWatchers : 0 Port : 443 Priv : {admin, read-only} RefreshPeriod : 600 SessionId : web_49846_A TransactionInProgress : False Ucs : ucs-4 Uri : https://209.165.201.15 UserName : admin VirtualIpv4Address : 209.165.201.15 Version : 2.0(2i)3.0(1a) WatchThreadStatus : None`
Step 4	In the Cisco UCS PowerTool, run the following script to validate your iSCSI boot configuration and check for duplicate IQNs : PS C:> Get-UcsServiceProfile -type instance \| Get-UcsVnicIScsi \| ? { $_.InitiatorName -ne «» } \| select Dn,InitiatorName \| group InitiatorName \| ? { $_.Count -gt 1 } \| % { $obj = New-Object PSObject ; $obj \| Add-Member Noteproperty Count $_.Count; $obj \| Add-Member Noteproperty InitiatorName $_.Name; $obj \| Add-Member Noteproperty Dn ($_ \| select -exp Group \| % { $_.Dn } ); $ob j } Cisco UCS PowerTool outputs the results to your screen, as follows: `Count InitiatorName Dn ----- ------------- -- 2 iqn.2012-01.cisco.com:s... {org-root/ls-SP_1_6/is... 2 iqn.2012-01.cisco.com:s... {org-root/ls-SP_2_1/is... 2 iqn.2012-01.cisco.com:s... {org-root/ls-SP_2_41/i... 4 iqn.2012-01.cisco.com:s... {org-root/ls-SP_2_7/is... 2 iqn.2012-01.cisco.com:s... {org-root/org-sub1/ls-... 2 iqn.2012-01.cisco.com:s... {org-root/org-sub2/ls-...`
Step 5	(Optional) If you have .NET Frame work 3.5 Service Pack 1 installed, you can use the following script to view the output in the GUI: PS C:> Get-UcsServiceProfile -type instance \| Get-UcsVnicIScsi \| ? { $_.InitiatorName -ne «» } \| select Dn,InitiatorName \| group InitiatorName \| ? { $_.Count -gt 1 } \| % { $obj = New-Object PSObject ; $obj \| Add-Member Noteproperty Count $_.Count; $obj \| Add-Member Noteproperty InitiatorName $_.Name; $obj \| Add-Member Noteproperty Dn ($_ \| select -exp Group \| % { $_.Dn } ); $obj } \| ogv
Step 6	Disconnect from Cisco UCS Manager, as follows: PS C:>Disconnect-Ucs

What to do next

If duplicate IQNs exist across multiple
service profiles in the
Cisco UCS domain, reconfigure the iSCSI vNICs with unique IQNs in
Cisco UCS Manager before you upgrade to
Cisco UCS, Release 2.1 or greater.

If
you do not ensure that all iSCSI vNICs are unique across all service profiles
in a
Cisco UCS domain before you upgrade,
Cisco UCS Manager raises a fault on the iSCSI vNICs to warn you that duplicate IQNs
are present. Also, if you do not ensure that there are no duplicate IQN names
within a service profile (for example, the same name used for both iSCSI
vNICs),
Cisco UCS reconfigures the service profile to have a single IQN. For
information on how to clear this fault and reconfigure the duplicate IQNs, see
the
Cisco UCS B-Series
Troubleshooting Guide.

Reconfiguring IQN Initiator Names on a Service Profile Bound to an Updating Service Profile Template

Problem—After an upgrade from Cisco UCS, Release 2.0(1) to Release 2.0(2), Cisco UCS Manager raises an IQN-related fault on one or more service profiles and you cannot reconfigure the duplicate IQN initiator name
on the service profile.

Possible Cause—The service profile that does not have a unique IQN initiator name is based on an updating service profile
template.

Procedure

Step 1	Log into the Cisco UCS Manager CLI.
Step 2	UCS-A # scope org `org-name` Enters organization mode for the specified organization. To enter the root organization mode, type / as the `org-name`.
Step 3	UCS-A /org # scope service-profile `profile-name` Enters service profile organization mode for the service profile.
Step 4	UCS-A/org# scope vnic-iscsi `iscsi_vnic1_name` Enters the mode for the first iSCSI vNIC assigned to the service profile.
Step 5	UCS-A /org/service-profile/vnic-iscsi* # set iscsi-identity {initiator-name `initiator-name` \| initiator-pool-name `iqn-pool-name`} Specifies the name of the iSCSI initiator or the name of an IQN pool from which the iSCSI initiator name will be provided. The iSCSI initiator name can be up to 223 characters.
Step 6	UCS-A /org/service-profile/vnic-iscsi* # exit Exits the mode for the specified iSCSI vNIC
Step 7	UCS-A/org# scope vnic-iscsi `iscsi_vnic2_name` Enters the mode for the second iSCSI vNIC assigned to the service profile.
Step 8	UCS-A /org/service-profile/vnic-iscsi* # set iscsi-identity {initiator-name `initiator-name` \| initiator-pool-name `iqn-pool-name`} Specifies the name of the iSCSI initiator or the name of an IQN pool from which the iSCSI initiator name will be provided. The iSCSI initiator name can be up to 223 characters.
Step 9	UCS-A /org/service-profile/vnic-iscsi # commit-buffer Commits the transaction to the system configuration.
Step 10	In the Cisco UCS Manager GUI, unbind the service profile from the updating service profile template.

Troubleshooting Issues with Registering Cisco UCS Domains in Cisco UCS Central

…

Date and time mismatch
is the most common issue with registration.

To ensure that the
date and time between
Cisco UCS Central
and
Cisco UCS domains are in sync, try the following:

Ensure that you
have a valid NTP configuration with
Cisco UCS Central
and the
Cisco UCS domains.
Ensure that
Cisco UCS Central
is running behind the time for the
Cisco UCS domains. This ensures that the start date of a certificate issued by
Cisco UCS Central
is not in the future.

If the
certificate is not valid, regenerate the default keyring certificate from
Cisco UCS Central
using the following commands:

UCSC # connect policy-mgr
UCSC(policy-mgr)# scope org
UCSC(policy-mgr) /org# scope device-profile
UCSC(policy-mgr) /org/device-profile # scope security
UCSC(policy-mgr) /org/device-profile/security # scope keyring default
UCSC(policy-mgr) /org/device-profile/security/keyring* # set regenerate yes
UCSC(policy-mgr) /org/device-profile/security/keyring* #commit-buffer

If you have
issues after correcting the configuration, you may need to update the shared
secret in
Cisco UCS Manager.

UCSM# scope system
UCSM /system # scope control-ep policy
UCSM /system/control-ep # set shared-secret
     Shared Secret for Registration:
UCSM /system/control-ep* # commit-buffer

Important

Before calling
Cisco TAC, make sure that:

You
synchronize the date and time in
Cisco UCS Central
and registered
Cisco UCS domains.
Cisco UCS Domain is not in suspended or lost visibility state.
The
registration status for the domain displays
Registered.

Источник

I’ve been trying to find out more about this problem and I’m not having much luck. I keep reading that applications should not have this error come up and although that’s all fine and dandy, it doesn’t tell me what can cause this error to show up.

I know this question is very broad as I’m sure there can be multiple causes for this error so I’ll try to narrow it down a bit.

I’m working in VS2003 developing an application that uses C++.NET

The application uses mostly unmanaged code and little managed code (due to heavy interference by the garbage collector). So I’d rate it 95% unmanaged, 5% managed

I’ve read somewhere that unstable/buggy/incorrect unmanaged code can mess up parts of the CLR memory rendering it corrupt and throwing this error.

Since 95% of the application is unmanaged, I’m not sure where to start looking.
Maybe the few classes that interact between managed and unmanaged?
What about marshalling data from managed to unmanaged?
Can a bad null pointer cause this failure?
What other problems can cause this? Array Index out of bounds? What about a Null Object?

Any information/paper/article that can give a nice list of possible causes for the System.ExecutionEngine failure would be appreciated!

Based on answers this exception can be caused in multiple scenarios, mentioning them here in the question for better visibility.

List of possible causes/scenarios:

Argument mismatch between C++ and C#
While using reflection
WCF service tries to return an IList or IEnumerable here here
Using Profiling tools
using the std instruction in assembler
calling ::FreeLibrary() multiple times
.NET Clipboard calls
using the Unity Framework
Using the wrong marshaling
Using INotifyPropertyChanged

Possible workarounds/solutions:

Disable concurrent garbage collection

StayOnTarget

11.5k10 gold badges50 silver badges78 bronze badges

asked Jun 8, 2009 at 21:08

This should not be taken too seriously, but I managed to get this exception while having some fun with reflection:

typeof(IntPtr).GetField("Zero").SetValue(null, new IntPtr(666));

answered Apr 24, 2012 at 16:22

Danië1Danië1

811 silver badge2 bronze badges

Had the same problem — my bug turned out to be an argument mismatch between my C# code and my C++ native dll. I had added an argument to the C++ function and failed to add it to the C# side.

answered Mar 19, 2010 at 19:15

AnnAnn

511 silver badge2 bronze badges

answered Mar 2, 2010 at 21:09

JimtronicJimtronic

1,1791 gold badge9 silver badges22 bronze badges

I encountered it when calling a function in an unmanaged library when my managed code was compiled for release. The error goes away when compiled for debugging.

answered Dec 2, 2010 at 14:24

Quoted from the MSDN reference page for System.ExecutionEngineException:

The exception that is thrown when there is an internal error in the execution engine of the common language runtime. This class cannot be inherited.

There is no non-obsolete alternative to ExecutionEngineException. If further execution of your application cannot be sustained, use the FailFast method.

Tip

In some cases, an application that targets the .NET Framework may throw an ExecutionEngineException exception during garbage collection when an application or the system on which it is running is under a heavy load. In this case, To work around this issue, you can disable concurrent garbage collection by modifying the application’s configuration file. For more information, see How to: Disable Concurrent Garbage Collection.

answered Nov 16, 2011 at 19:04

Honestly, the only time I’ve ever seen this exception is when I was using the Compuware DevPartner tools to do some profiling and code analysis. DevPartner hooks deep into the core of the CLR to do it’s work, but it’s full of bugs, so screws the CLR up.
I had to reboot my machine (and remember to never click the DevPartner toolbar buttons ever again) to get things to go back to normal.

If you’re not using devpartner, then you most likely have some unmanaged code which is trashing some memory used by the CLR.
I’d advise first doing a reboot, and then trying to track down whichever bug you have which is trashing the memory. Look for buffer overruns, writing to uninitialised pointers, and all the other usual suspects.

answered Jun 8, 2009 at 21:40

Orion EdwardsOrion Edwards

121k63 gold badges236 silver badges328 bronze badges

I am getting this ExecutionEngineException when just using standard .NET Clipboard calls.
My code is 100% managed. So, it seems the .NET Framework has issues.

PastedData = Clipboard.GetDataObject();
object imageObj = PastedData.GetData(dataType);

where data type is «EnhancedMetafile«, which was in the list of formats on the Clipboard.

akjoshi

15.3k13 gold badges103 silver badges120 bronze badges

answered Aug 28, 2012 at 13:53

Brian KennedyBrian Kennedy

3,4693 gold badges21 silver badges27 bronze badges

I recently discovered that using the std instruction in assembler to set the direction flag without clearing it when you’re done (cld) can cause this error. I’m using .Net 4.0.

akjoshi

15.3k13 gold badges103 silver badges120 bronze badges

answered Jul 18, 2010 at 7:30

BrentBrent

4,0834 gold badges28 silver badges63 bronze badges

I’ve come across this exception while developing a ArcGIS extension, written with VB.NET (Visual Studio 2005). ArcGIS relies heavily on the COM technology, therefore .NET-COM interop is involved. I haven’t found the cause of the exception until now, but I suppose it might have to do with a building-up of un-released COM object instances, since the exception only ever occurs after the software has been crunching geometries and numbers for some time.

StayOnTarget

11.5k10 gold badges50 silver badges78 bronze badges

answered Mar 23, 2010 at 20:05

I’ve just come across this exception while working on WPF application. VS showed that it happened while notifying property change through NotifyPropertyChanged call(INotifyPropertyChanged).

Looks very strange to me and it happened only once; it stopped the debugging session and didn’t happened after running the application again.

answered Oct 12, 2012 at 9:56

akjoshiakjoshi

15.3k13 gold badges103 silver badges120 bronze badges

One more case when System.ExecutionEngineException is thrown is when an unhandled exception is thrown in delegate provided to ThreadPool.QueueUserWorkItem() function.

akjoshi

15.3k13 gold badges103 silver badges120 bronze badges

answered Oct 10, 2013 at 15:25

MitaMita

2435 silver badges11 bronze badges

I got one of these when my C# module (invoked by a C++/MFC app built with /CLR) inadvertently de-referenced a null pointer. So it is possible for the exception to occur due to a bug in the «user code».

Kevin

answered Sep 2, 2009 at 14:59

I had this exception when running unmanaged code in a different version, than I compiled it with.

Maybe that helps someone…

answered Jun 18, 2010 at 13:45

toba303toba303

931 silver badge5 bronze badges

I’ve just come across this exception while writing a c# programme using the Unity Framework.

I’m using VS 2010, and .NET 3.5

Basically if you register a type in a UnityContainer:

container.RegisterType<IAClass, AClass>();

but AClass doesn’t have a constructor that takes no arguments

class AClass : IAClass
{
   private int a;
   public in A { get { return a; } }
   public AClass(int a)
   {
       this.a = a;
   }
}

then when you come to instantiate the class you’ll get the System.ExecutionEngineException

IAClass A = container.Resolve<IAClass>(); //throws System.ExecutionEngineException

answered Sep 30, 2010 at 13:51

Matt EllenMatt Ellen

11.2k4 gold badges68 silver badges90 bronze badges

I get this Exception when viewing pdf files with an external viewer. I think the viewer itself is the root of all evil. It has to be something outside of the .NET framework obviously.

answered Nov 29, 2011 at 14:12

JowenJowen

5,1731 gold badge43 silver badges41 bronze badges

Using the wrong marshaling causes me this exception.
I’ve had a pure C *.dll to use; I write a wrapper around it in C#, using DllImport; then I used marshaling to let out string parameters to fill a StringBuilder, like this:

    [DllImport("old.dll", CallingConvention = CallingConvention.Winapi, CharSet = CharSet.Ansi)]
    public static extern UInt32 GetMessage([MarshalAs(UnmanagedType.LPStr)] out StringBuilder message);

Using UnmanagedType.LPStr causes me that exception; using UnmanagedType.BStr, the right string marshal in this case, solved me the problem.
Just my 2 cent.

answered Jan 5, 2012 at 17:31

I managed to get this exception while debugging a C# 4.0 web application which uses an assembly that uses an Azure service bus. This assembly has a bug where it will try to loop forever to receive a message from a closed servicebus, but the exception handler captures that exception. However, while debugging the code, it actually killed Visual Studio 2012 with this exception!
Yes, VS2012 was the one that threw the exception.

answered Jul 31, 2013 at 9:01

Wim ten BrinkWim ten Brink

25.8k20 gold badges82 silver badges147 bronze badges

Just to add to the list of possible causes, I’ve had this error when trying to serialise IEnumerable<> containing a complex type.

Changing from IEnumerable<> to List<> resolved the problem.

akjoshi

15.3k13 gold badges103 silver badges120 bronze badges

answered Nov 13, 2009 at 11:59

I had this happen and it was because I was calling ::FreeLibrary() multiple times with the same DLL HANDLE. (The DLL was a managed C++ dll: a managed C++ wrapper over some C# functionality)

akjoshi

15.3k13 gold badges103 silver badges120 bronze badges

answered Aug 2, 2010 at 5:13

Adam TegenAdam Tegen

25.3k33 gold badges124 silver badges153 bronze badges

I’ll add how I hit this.

Using .Net 4 code contacts, a Contract.Ensures(Contract.Result<object>() != null) will throw this exception IIF you have Assert on Contract Failure check in the project properties page for Code Contracts. Disabling this checkbox doesn’t disable the check however. You get the expected «Post condition failed message.»

answered Jul 7, 2011 at 15:00

AndyAndy

8,4126 gold badges38 silver badges75 bronze badges

I got this error when I moved a harddisk from one computer to another (win 8 reinstalled drivers automatically ) but I suspect the native gened exes will not work.

answered Mar 7, 2015 at 2:14

kns98kns98

3302 silver badges7 bronze badges

Getting this problem in pure managed WPF app in a pretty innocent situation it seems to me. I have a control in a grid which I want to display or hide so I’m setting it’s visibility to Visibility.Collapsed or Visibility.Visible. It starts out collapsed. I press a button and it gets set to visible and appears just fine. I press another button and set it to collapsed and boom — big ugly error. Nothing fancy or all that unusual. This is using 4.5. Very odd. When I look at the data for the error it says System.Collections.EmptyReadOnlyDictionaryInternal.

answered May 8, 2015 at 14:32

I get this error in a regular LINQ Query where I am returning FirstOrDefault using VS2010

answered May 11, 2015 at 13:56

Sofia KhwajaSofia Khwaja

1,8593 gold badges17 silver badges20 bronze badges

Using VS2015 ASP.NET Framework 4.5 I just had to rebuild and run again.

answered Mar 1, 2016 at 21:15

AfraAfra

335 bronze badges

Create new Web Forms Application
Open any page (lets say Default.aspx)
Add GridView to the form
Click on the GridView, then on the little arrow (upper right corner). When I click «Edit columns» or «Add new column» or Data Source > New Data Source, Visual Studio 2015 crashes with System.ExecutionEngineException in mscorlib.dll

answered Oct 7, 2016 at 11:02

I am getting this exception in a .NET Framework 3.5 WPF application.

The exception occurs whenever the Close method is called in the Loaded window event. This occurs in a barebones window, as well.

However, the exception only occurs if I set the property SizeToContent="WidthAndHeight" in the xaml of the view. Removing this property fixes the issue.

I was also using the MVVM Light library. However, the exception occurs even after removing references to this library for this WPF window.

answered Dec 3, 2020 at 14:55

On my project I just discovered that using obfuscated DLLs can be a cause of this.

Here is the setup which caused the problem:

Visual Studio startup project produces a C# DLL. It is set to run an external program which will load said DLL + some others.
The external program is located under Program Files along with various .NET DLLs from our last build.
The build includes obfuscating DLLs (using ConfuserEX, though maybe any other obfuscation tool would cause the same problem if it obfuscated in the same way).
At runtime we would immediately get an ExecutionEngineException (preceded by a «Managed Debugging Assistant ‘FatalExecutionEngineError’ has detected a problem…» message).
At that point looking in the Visual Studio Modules you could see that the DLL noted in the exception was being loaded from Program Files — e.g., it was the obfuscated DLL being loaded.

Replacing any of the obfuscated DLLs with their non-obfuscated equivalents disappeared the exception.

Beats me specifically why obfuscation would cause this exception, but I suspect that the debugger trying to attach is unable to reverse engineer the assembly, much like you can’t easily decompile an obfuscated tool by any normal means. This was a case where running with CTRL+F5 (no debugger attached) would NOT have a problem.

answered Jun 2, 2021 at 16:38

StayOnTargetStayOnTarget

11.5k10 gold badges50 silver badges78 bronze badges

Источник

During install of SqlServer Express 2008 (also I tried Developer Edition 2008 R2 with same error) I have error:

2014-05-01 17:13:52 Slp: Running Action: Install_WatsonX86_Cpu32_Action
2014-05-01 17:13:52 Slp: Error: Action «Install_WatsonX86_Cpu32_Action» threw an exception during execution.
2014-05-01 17:13:52 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: C:WINDOWSInstaller7affd.msi —> System.IO.FileNotFoundException: C:WINDOWSInstaller7affd.msi
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetSummaryInformationStringProperty(ServiceContainer context, String pathToMsi, SummaryInformationStreamPropertySet propertyId)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:52 Slp:    — Конец трассировки внутреннего стека исключений —
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()Error: Action «MsiTimingAction» threw an exception during execution.
2014-05-01 17:13:52 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: C:WINDOWSInstaller7affd.msi —> System.IO.FileNotFoundException: C:WINDOWSInstaller7affd.msi
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetSummaryInformationStringProperty(ServiceContainer context, String pathToMsi, SummaryInformationStreamPropertySet propertyId)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet propertyId)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:52 Slp:    — Конец трассировки внутреннего стека исключений —
2014-05-01 17:13:52 Slp:    в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:52 Slp: Received request to add the following file to Watson reporting: C:Documents and SettingsmeLocal SettingsTemptmp1C4.tmp
2014-05-01 17:13:52 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2014-05-01 17:13:52 Slp: Inner exceptions are being indented
2014-05-01 17:13:52 Slp:
2014-05-01 17:13:52 Slp: Exception type: System.IO.FileNotFoundException
2014-05-01 17:13:52 Slp:     Message:
2014-05-01 17:13:52 Slp:         C:WINDOWSInstaller7affd.msi
2014-05-01 17:13:52 Slp:     Stack:
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetSummaryInformationStringProperty(ServiceContainer context, String pathToMsi, SummaryInformationStreamPropertySet
propertyId)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetInstalledSummaryInformationStringProperty(ServiceContainer context, String productCode, SummaryInformationStreamPropertySet
propertyId)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia,
InstallAction pkgAction)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2014-05-01 17:13:52 Slp:         в Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2014-05-01 17:13:56 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftMicrosoft SQL Server to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20140501_171325Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-05-01 17:13:56 Slp: Sco: Unable to write hklm registry key SOFTWAREMicrosoftMicrosoft SQL Server to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20140501_171325Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32 error
2
2014-05-01 17:13:56 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftWindowsCurrentVersionUninstall to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20140501_171325Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-05-01 17:13:56 Slp: Sco: Attempting to write hklm registry key SOFTWAREMicrosoftMSSQLServer to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20140501_171325Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-05-01 17:13:56 Slp: Sco: Unable to write hklm registry key SOFTWAREMicrosoftMSSQLServer to file C:Program FilesMicrosoft SQL Server100Setup BootstrapLog20140501_171325Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2

I checked C:WINDOWSInstaller for «7affd.msi» — there is no such file. Also I checked same folder on Win7-64 machine and Notebook WinXP-Pro — there is no such file. I was able to install Express on both Win7-64 and Notebook, but not on this machine.
I’ve tried searching for «7affd.msi» on internet without luck. Also I removed all Visual Studio Express 2010 and used any «Fix-It» utilities to check files and registry. And still have same error.

How to fix it?

Источник

December 13, 2018
MSSQL

ERROR MESAGGE:

“Error: Action “LaunchLocalBootstrapAction” threw an exception during execution.”

EXPLANATION:

On a system where Microsoft Cluster Services is installed, you may experience this error when you install a SQL Server Instance.

The reason for this problem that I experienced was the presence of the “&” character in a Group Name used in Cluster Services.

SOLUTION:

In Cluster Services, use the “and” connector or other appropriate characters instead of “&” characters.

Источник

2018-05-22 13:29:33,712 INFO: Failed to import patroni.dcs.consul
2018-05-22 13:29:33,720 INFO: Selected new etcd server http://10.10.10.10:2379
2018-05-22 13:29:33,734 INFO: Lock owner: None; I am pgsql02
2018-05-22 13:29:33,746 INFO: trying to bootstrap a new cluster
2018-05-22 13:29:33,748 ERROR: Exception during execution of long running task bootstrap
Traceback (most recent call last):
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/async_executor.py», line 97, in run
wakeup = func(*args) if args else func()
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/postgresql.py», line 1561, in bootstrap
return do_initialize(config) and self.write_pg_hba(pg_hba) and self.save_configuration_files()
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/postgresql.py», line 546, in _initdb
os.write(fd, self._superuser[‘password’].encode(‘utf-8’))
AttributeError: ‘int’ object has no attribute ‘encode’
2018-05-22 13:29:33,751 INFO: removing initialize key after failed attempt to bootstrap the cluster
2018-05-22 13:29:34,237 INFO: Lock owner: None; I am pgsql02
Traceback (most recent call last):
File «/usr/local/bin/patroni», line 11, in
load_entry_point(‘patroni==1.4.3’, ‘console_scripts’, ‘patroni’)()
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/init.py», line 176, in main
return patroni_main()
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/init.py», line 145, in patroni_main
patroni.run()
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/init.py», line 114, in run
logger.info(self.ha.run_cycle())
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/ha.py», line 1164, in run_cycle
info = self._run_cycle()
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/ha.py», line 1077, in _run_cycle
return self.post_bootstrap()
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/ha.py», line 976, in post_bootstrap
self.cancel_initialization()
File «/usr/local/lib/python2.7/dist-packages/patroni-1.4.3-py2.7.egg/patroni/ha.py», line 971, in cancel_initialization
raise PatroniException(‘Failed to bootstrap cluster’)
patroni.exceptions.PatroniException: ‘Failed to bootstrap cluster’

Источник

Troubleshooting Issues with Cisco UCS B-Series Operation

Verify Console Setup

Reboot Warning Does Not Display

Procedure

Server Does Not Boot from OS Installed on eUSB

Procedure

Server Does Not Boot After RAID1 Cluster Migration

Procedure

BadFieldException When Launching the KVM Viewer

Procedure

KVM Console Failure

Procedure

KVM Fails to Open

Procedure

No Ports Available for Distributed Virtual Switch

Procedure

DME Process Timed Out

Procedure

What to do next

Event Sequencing Fatal Error

Procedure

Recovering a Fabric Interconnect from the Boot Loader Prompt

Procedure

Resolving Fabric Interconnect Cluster ID Mismatch

Procedure

Support for Local Storage Monitoring

Supported Cisco UCS Servers for Local Storage Monitoring

Supported Cisco UCS Servers for Legacy Disk Drive Monitoring

Prerequisites for Local Storage Monitoring

Viewing the Status of Local Storage Components in the Cisco UCS Manager GUI

Procedure

Interpreting the Status of a Monitored Disk Drive

HDD Metrics Not Updated in Cisco UCS Manager GUI

Procedure

Disk Drive Fault Detection Tests Fail

Procedure

Cisco UCS Manager Reports More Disks in Server than Total Slots Available

Procedure

Clearing the Duplicate IQN Fault and Reconfiguring IQN Initiator Names

Procedure

Obtaining Cisco UCS PowerTool and Running the Duplicate IQN Script

Procedure

Example:

What to do next

Reconfiguring IQN Initiator Names on a Service Profile Bound to an Updating Service Profile Template

Procedure

…

ERROR MESAGGE:

EXPLANATION:

SOLUTION:

Troubleshooting
Issues with Cisco UCS B-Series Operation

Verify Console
Setup

Server Does Not Boot
from OS Installed on eUSB

Server Does Not Boot
After RAID1 Cluster Migration

No Ports Available
for Distributed Virtual Switch

Support for Local
Storage Monitoring

Supported
Cisco UCS
Servers for Local Storage Monitoring

Supported
Cisco UCS
Servers for Legacy Disk Drive Monitoring

Prerequisites for
Local Storage Monitoring

Viewing the Status
of Local Storage Components
in the Cisco UCS Manager
GUI

Interpreting the
Status of a Monitored Disk Drive

Cisco UCS Manager Reports More Disks in Server than Total Slots
Available

Clearing the
Duplicate IQN Fault and Reconfiguring IQN Initiator Names

Obtaining
Cisco UCS PowerTool and Running the Duplicate IQN Script