[ScaleIO] Virtual disk bad block medium error is detected.

Hello all,

We got several [Storage Service Virtual disk bad block medium error is detected.: Virtual Disk X (Virtual Disk X)] logs in scaleIO server.

I believe this disk went bad and it caused unrecovered read error.

What I want to ask is, when I check [query_all_sds] and [query_sds], this sds seems to be healthy and all DISK seems normal.

Is this normal?

Also can you please let me know the details about monitoring disks in SDSs. Does MDM checks all disks in all SDSs frequently? or when SDC cannot connect to Disk, SDC informs MDM , then it changes mapping towards SDCs?



  • No Related Posts

WSS Block executables into zip file

I need a solution

Hello everyone

I need you help, in my portal of WSS I do a rule to block all executable files *.exe, according this KB


The rule work fine, but if the file *.exe is compress in file *.zip don´t work

Any idea of ​​why it does not work like that?


Andres Garcia



  • No Related Posts

7022838: Unable to upgrade iManager plugin for GroupWise.

You can workaround this problem by following steps:

1. Stop tomcat that runs iManager.

2. Go into /var/opt/Novell/imanager/nps/packages and delete anyGroupWise related NPM.

3. Go into /var/opt/Novell/imanager/nps/web-inf/modules/groupwiseand delete all from this directory.

4. Go into /var/opt/Novell/imanager/nps/uninstallerdata directoryand delete GroupWise related items.

Manually installing NPM file on the server:

1. Copy provided NPM file into some dedicated directory on theserver and using roller Linux tool extract it. There will be twodirectories: META-INF and currentwebapp.

2. In META-INF file there is MANIFEST.MF file which you can edit bygedit and correct Implementation-Version field and adjust year. Forinstance it could be listed as You can change itinto, save the file.

3. Copy the META-INF directory into/var/opt/novell/imanager/nps/web-inf/modules/groupwisedirectory.

4. Go now into currentwebapp directory, select both, WEB-INF andportal directories and paste them into /var/opt/novell/imanager/npswith overwrite option.

5. Start tomcat on the server to start iManager.

Once you login into eDir again, you will notice that GroupWiseplugin is listed ow under installed with a info you updated in step2 within the manifest file.


  • No Related Posts

Secure Mail: How to edit the MDX file for enabling/disabling the hidden policy.

Following are the steps for enabling/disabling Android hidden MDX policy:(Please take a backup of the .MDX file prior to making any changes)

1. Rename the .mdx file that you have to a .zip file

2. Unzip it, open the policy_metadata.xml file and look for the policy, here we take “Auto_Populate_username_title” as an example.

3. Change the PolicyHidden tag to true or false.

User-added image

4. Now, select all the files in the folder that has xml and apk tag, along with various properties files, and compress them (To compress we will have to go inside the folder, select all the files -> send to -> Compressed ).

5. Rename the compressed .zip file to a .mdx file

6. Upload this mdx file on your environment

XenMobile How Do I


  • No Related Posts

MDX Toolkit – error when wrapping android app – APKTool Error

MDX Toolkit version: 10.8.5 on-prem and cloud.

-This article explains how to fix the issue on the on-prem version-

When MDX Toolkit is trying to re-compile it shows the following error:

“Re-compile the app using APKTool 2.3.1 and it fails”

Complete log of the error is shown below:

De-Compiling the App using latest apktool 2.3.1 :

E:Workspaceapktool-install-windows>java -jar apktool.jar d -s android_app.apk

I: Using Apktool 2.3.1 on android_app.apk

I: Loading resource table…

I: Decoding AndroidManifest.xml with resources…

I: Loading resource table from file: C:UsersuserAppDataLocalapktoolframework1.apk

I: Regular manifest package…

I: Decoding file-resources…

I: Decoding values */* XMLs…

I: Copying raw classes.dex file…

I: Copying assets and libs…

I: Copying unknown files…

I: Copying original files…

Re-compile the app using APKTool 2.3.1 and it fails :

E:Workspaceapktool-install-windows>java -jar apktool.jar b android_app

I: Using Apktool 2.3.1

I: Copying android_app classes.dex file…

I: Checking whether resources has changed…

I: Building resources…

W: E:Workspaceapktool-install-windowsandroid_appreslayout-v26abc_screen_toolbar.xml:5: error: No resource identifier found for attribute ‘keyboardNavigationCluster’ in package ‘android

Exception in thread “main” W:

brut.androlib.AndrolibException: brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:UsersuserAppDataLocalTempbrut_util_Jar_3317229960825218523.tm

, p, –forced-package-id, 127, –min-sdk-version, 19, –target-sdk-version, 25, –version-code, 12640, –version-name, 3.4.0, –no-version-vectors, -F, C:UsersuserAppDataLocalTempAPKTOOL449

799333282341642.tmp, -0, arsc, -0, webp, -0, arsc, -I, C:UsersuserAppDataLocalapktoolframework1.apk, -S, E:Workspaceapktool-install-windowsandroid_appres, -M, E:Workspacea


at brut.androlib.Androlib.buildResourcesFull(Androlib.java:492)

at brut.androlib.Androlib.buildResources(Androlib.java:426)

at brut.androlib.Androlib.build(Androlib.java:305)

at brut.androlib.Androlib.build(Androlib.java:270)

at brut.apktool.Main.cmdBuild(Main.java:227)

at brut.apktool.Main.main(Main.java:75)

Caused by: brut.androlib.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [C:UsersuserAppDataLocalTempbrut_util_Jar_3317229960825218523.tmp, p, –forced-package

id, 127, –min-sdk-version, 19, –target-sdk-version, 25, –version-code, 12640, –version-name, 3.4.0, –no-version-vectors, -F, C:UsersuserAppDataLocalTempAPKTOOL4492799333282341642.tmp,

0, arsc, -0, webp, -0, arsc, -I, C:UsersuserAppDataLocalapktoolframework1.apk, -S, E:Workspaceapktool-install-windowsandroid_appres, -M, E:Workspaceapktool-install-windows


at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:456)

at brut.androlib.Androlib.buildResourcesFull(Androlib.java:478)

… 5 more

Caused by: brut.common.BrutException: could not exec (exit code = 1): [C:UsersuserAppDataLocalTempbrut_util_Jar_3317229960825218523.tmp, p, –forced-package-id, 127, –min-sdk-version, 19,

-target-sdk-version, 25, –version-code, 12640, –version-name, 3.4.0, –no-version-vectors, -F, C:UsersuserAppDataLocalTempAPKTOOL4492799333282341642.tmp, -0, arsc, -0, webp, -0, arsc, -I,

C:UsersuserAppDataLocalapktoolframework1.apk, -S, E:Workspaceapktool-install-windowsandroid_appres, -M, E:Workspaceapktool-install-windowsandroid_appAndroidMani


at brut.util.OS.exec(OS.java:95)

at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:450)

… 6 more



  • No Related Posts

Smarts NCM: Unexpected Policy Reference in Device Detail

Article Number: 504501Article Version: 3 Article Type: Break Fix

Smarts Network Configuration Manager 9.4.1

In device properties under the Audit Trail tab, policies may be listed that do not apply to the device. The policies may show ‘(NotAudited)’.

In 9.4.1 patch 20, views that are assigned under ‘Area’ in a policy will show as selected, but are not properly applied.

No changes were made prior to seeing the issue.

A patch has been created to resolve the issue. The attached file is the services jar of patch build with the code changes.

1. Replace this jar at “smarts-ncm/ncmcore/webapps/ncm-webapp/WEB-INF/lib”

Take a backup of the old services jar and replace with the new one.

2. Run chown root:voyence services- to change the jar ownership details.

3. Restart ncm-as service ‘service ncm-as restart’

This patch is only for 9.4.1 environments. If a patch is needed for another version, please open a case with Support and reference this KB.



  • No Related Posts

7022207: “GAS.process (super) threw ServletException java.lang.NullPointerException” Error and Administrative WebStation Server Is Unresponsive

This document (7022207) is provided subject to the disclaimer at the end of this document.


Reflection for the Web 2014 (All Editions)

Reflection for the Web 2011 Build 521 or higher

Reflection Security Gateway 2014 (All Editions)



  • You have Reflection for the Web configured to use SiteMinder for Access Control authentication.
  • You upgraded to Reflection for the Web 2014, Reflection for the Web 2011 Build 521, or Reflection Security Gateway 2014.
  • The Administrative WebStation is unresponsive. Administrative WebStation is inaccessible by both the administrative account and end users.
  • The links list, created by the Launcher applet, is not rendered.
  • The following error is reported in the Administrative WebStation trace.log file:
GAS.process (super) threw ServletException java.lang.NullPointerException

By default, the trace.log file is written to the log directory in the ReflectionData directory, for example:



You must re-add the SiteMinder Agent JAR file to the Reflection server’s classpath and restart Tomcat. The SiteMinder Agent JAR can be copied from a SiteMinder Web Agent or SDK installation. For more information, refer to Technical Note 2591.


This issue occurs because Reflection no longer includes the SiteMinder JAR file in the Reflection server’s classpath. The JAR file was removed from the installation images to adhere to licensing restrictions imposed by Computer Associates (CA) and applies to all CA providers, including Attachmate.

Additional Information

Legacy KB ID

This article was originally published as Attachmate Technical Note 2593.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


  • No Related Posts

Driver Disk for Emulex be2net – For XenServer 7.0

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.0 who use Emulex ‘s be2net driver and wish to use the latest version of the following:

Driver Module Version

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use the XenServer CLI to install this driver disk. Once the driver has been installed, the server must be restarted, in order for the driver to be loaded. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

The file with filename ending metadata.md5 contains the checksum of the driver disk’s metadata. If, when you install the driver disk, you elect to verify the driver disk when prompted, you should check that the checksum presented by the installer is the same as that in the metadata MD5 checksum file included in this download.

Also present in the zip file is an MD5 checksum for the ISO image named be2net.iso. This will allow you to verify that your download has been successful. This checksum is of the ISO only, and can be verified by following the instructions at CTX116166: How to verify downloaded ISO images.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:


  3. You will now be presented with a command prompt. Type the following:

    rmmod be2net

    If this succeeds (i.e. there are no error messages printed),the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type


    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing onto a Running XenServer System

  1. Download the driver disk directly to the XenServer host to be updated (Citrix recommends storing it in the /tmp/ directory), or first download the file to an Internet-connected computer, and burn the ISO image to a CD.
  2. Use XenCenter to access the XenServer host’s console, or log in directly using SSH.
  3. Mount the driver disk image. The directory being mounted varies depending on whether the driver disk is still in ISO form, or was burnt to CD. For a CD-ROM, use:

    mkdir -p /mnt/tmp

    mount /dev/<path to cd-rom> /mnt/tmp

    cd /mnt/tmp/


    cd /

    umount /mnt/tmp

    If instead, the ISO file is used, the steps are:

    mkdir -p /mnt/tmp

    mount /tmp/<path to ISO> /mnt/tmp -o loop,ro

    cd /mnt/tmp/


    cd /

    umount /mnt/tmp

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.




Driver Disk Files

File Name MD5 Checksum
be2net.iso ccd161f26432894727709dfb8c3c1c9a
be2net.metadata.md5 0b3e33847b40f765e7b41f764e3d5c64
be2net- 18e8686b5b1bb2d595837a3c15d8b8b3

RPMs Provided

Name Version RPM Name
be2net-modules be2net-modules-
be2net-3.10.0+10-modules be2net-3.10.0+10-modules-

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer 7.0 Supplemental Packs & the DDK .


  • No Related Posts

7022220: Installing Reflection for the Web or Reflection Security Gateway with WebSphere Application Server

Before You Begin

Before installing Reflection for the Web or Reflection Security Gateway (hereinafter referred to as Reflection), you must have all of the following installed and configured on your host.

  • WebSphere Application Server 5.0.2 or higher.
  • Java Developer Kit 1.5 or higher.
  • Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. For details, see Applying the JCE Unlimited Strength Jurisdiction Policy Files.
  • The most recent WebSphere cumulative and group program temporary fixes (PTFs) must be applied.
  • Reflection requires 220 MB of free disk space in the hosts /tmp file during installation.
  • If you want to use security (HTTPS, SSL) with the WebSphere Application Server (WAS), refer to your IBM documentation to properly configure the WAS.

Installing Reflection for the Web

After the WebSphere Application Server has been properly installed and tested, follow the steps below to install Reflection.

Prepare the rweb.war File

Follow these steps to prepare the rweb.war file:

  1. Copy the rweb.war file located with the downloaded product files to a temporary folder on your PC. The file location depends on your Reflection product:

Reflection for the Web 2014 or 2011 or Reflection Security Gateway 2014: /install_manual/components/rweb.war

Reflection for the Web 2008: /nonautomated/rweb.war

  1. During download, the rweb.war file may be named rweb.war.zip. If so, rename rweb.war.zip to rweb.war.

Note: When renaming the file, you may receive an error stating that the file may become unstable. Click Yes to proceed.

Update the WebSphere Server Settings

Follow the steps below to update the WebSphere Server settings:

  1. Open the WebSphere Administration Console. By default, this is accessed from http://<myserver>:9060/admin or http://<myserver>: 9060/ibm/console.
  2. On the left-navigation bar, expand Applications, and then click Install New Application.
  3. In the main window, select the “Local file system” radio button and enter the path to the rweb.war file. For example:

C:Temprweb.war –or– /u/local/rweb.war

  1. Select the “Show me all installation options and parameters” radio button.
  2. In the Context root entry field, enter /rweb, and then click Next.
  3. Select the “Generate Default Bindings” check box, leave all other values at default, and then click Next.
  4. Click Next through the Install New Application dialog box, accepting defaults.
  5. Select the rweb.war check box, make sure the Virtual Host is set to default_host, and then click Next.
  6. Print the Summary page for your records, and then click Finish.

The new rweb.war application is installed and the Administration Console screen opens. If you expand the Applications menu and select Enterprise Applications, the application state for rweb should be Stopped.

Click Save to update the master configuration.

Update the web.xml File

There are two copies of the web.xml file, located in the following directories:


– and –


Note: If this is a WebSphere Application Server Network Deployment, there is an additional web.xml that must be updated:


In both (or all three) files, locate the <param-name>ReflectionData</param-name> section and modify the file to include the data in red below, entering your path to ReflectionData (for example, C:ReflectionData or /u/local/ReflectionData), and substituting your own sslport value for 443. Note: If the ReflectionData directory does not already exist, you must manually create it.







Reflection stores configuration information in the ReflectionData directory. If this is a UNIX installation, ensure that rights are set so that Reflection can write to the ReflectionData directory.

Note: In Reflection, the sslport parameter is located in the PropertyDS.xml file, which is located in the ReflectionData folder. If you want to use a port other than default port 443; you must edit PropertyDS.xml after Reflection for the Web is started in WebSphere.

Once you have updated and saved both (or all three) of the web.xml files, return to the Administrative Console window and follow the steps below.

  1. Expand the Applications menu item, and then click Enterprise Applications.
  2. In the Enterprise Applications dialog, select the rweb check box, and then click Start. The application status will change to a started, indicated by a green arrow in the Status field.
  3. Update the sslport parameter in the PropertyDS.xml, if you need to. Once updated, restart the Application Server using the WebSphere Administrative Console, performing steps 1 and 2 above.

Reflection is now installed. To access Reflection, open a browser and enter the URL, WAS port, and context root to your server.

Syntax: http://myserver:default_port/context_root

For example: http://rweb.atm.com:9080/rweb

Applying the JCE Unlimited Strength Jurisdiction Policy Files

Reflection Security Gateway 2014 R2 and Reflection for the Web 2014 R2 require the Java Cryptography Extension (JCE) Unlimited Strength Policy Files. “Unlimited strength” policy files contain no restrictions on cryptographic strengths, in contrast to the “strong” but limited cryptography policy files bundled in a JRE.

To apply the policy files:

  1. Download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files from Oracle or IBM. Be sure to download the correct policy file updates for your version of Java:
  1. Uncompress and extract the downloaded file. The download includes a Readme.txt and two .jar files with the same names as the existing policy files.
  2. Locate the two existing policy files local_policy.jar and US_export_policy.jar in the following directory:

– UNIX:<java-home>/lib/security

– Windows:C:Program FilesJavajre<version>libsecurity

  1. Replace the existing policy files with the unlimited strength policy files you extracted.


  • No Related Posts