My Daily Cloud Blog

Home

Christian Marrero
1–2 minutes

  • HTTP Status 404 – /triton/pages/eipProductContainer.jsf on Triton Websense Security Appliance Portal

    HTTP Status 404 – /triton/pages/eipProductContainer.jsf on Triton Websense Security Appliance Portal

    After Rebooting a Websense Triton Web Security Appliance, I was unable to access the web portal due to the following error:

    HTTP Status 404 – /triton/pages/eipProductContainer.jsf


    Very frustrating specially when your IT VP needs to get a site blocked right away! So after many trial and error, I found this great respond from the Websense Forum with someone else having the exact issue, here is the link:  http://community.websense.com/forums/t/32246.aspx 

    I put together the steps I followed to get the portal back online:

     1. Stop
    TRITON Web Security     Stop
    TRITON Unified Security Center Stop TRITON Web Server Stop TRITON Settings    Database

    2. Start TRITON Settings
    Database Start TRITON Web Server Start TRITON Unified Security Center Start
    TRITON       Web Security Wait for the services to fully start.

    3. You should now be
    able to connect to TRITON.


    NOTE: Please, start and stop each service in the same sequence mention on each steps.


     After I followed this steps, I was able to access the web portal no issues. If none of this steps resolved the issue, I suggest to visit the link I posted for other steps to follow since this steps once again, were able to resolved my current issue.
    ,

  • How to Modify the Management Port IP Address on a NetApp FAS 8020

    How to Modify the Management Port IP Address on a NetApp FAS 8020

     I few weeks ago NetApp Support contact us asking if were having issues with the Auto Support on both of our DR controllers. First they ask us to create a connector on our Exchange with the Node Management IP Addresses with Anonymous Authentication, even to verify that the ports on the switch were the e0M ports were plug in are on the same VLAN as the IP Addresses.

     After doing some research around both controllers, the e0M ports have the wrong IP Addresses, how that I find that our, I ran the following command from the CLI network interface show -curr-port e0M
    which display the E0M ports configuration with the IP Addresses of the Management Logical Interface:

    GEEK-CLUST::> network interface show -curr-port e0M
                Logical    Status     Network            Current       Current Is
    Server      Interface  Admin/Oper Address/Mask       Node          Port    Home
    ———– ———- ———- —————— ————- ——- —-
    GEEK-NODE1
                     
    mgmt1      up/up      192.168.164.58/24    GEEK-NODE1   e0M    true
    GEEK-NODE2
    mgmt1      up/up      192.168.164.59/24    GEEK-NODE2   e0M    true


    2 entries were displayed.




    So how we can Re-IP those Management Logical Interface? Here are the Steps:

    1. SSH to the Cluster’s CLI by using the Cluster’s Management IP Address.

    2. Once on the CLI, we need to set the Advance Options by typing set advance


    Note: a warning alert will come up as shown below:

     These advanced commands are potentially dangerous; use them only when directed to do so by
             NetApp personnel.
    Do you want to continue? {y|n}:

    If you don’t feel comfortable, please type n otherwise type y and hit enter.

    3. Once the Advance Options are set, we can now proceed to change the Management Logical Interface IP Address by typing the following command:

    network interface modify -vserver <node_name> -lif mgmt1 -home-node <node_name> -home-port e0M -address <ip_address> -netmask <netmask>

    4. Now re run the network interface show -curr-port e0M to verify the IP Address has changed.


    Once I did the changes, Auto Support start working no problem. So next time you are breaking your head on why no Auto Support can be send, verify the Management Logical Interface as well the e0M port are configure properly with the correct IP Address as well connected on the back of the controllers.


    Warning: You can also use this same commands to configure any other Interface as well however, this post was only intended to the Management e0M port.

  • Cache Mode is gray out on Outlook 2010

    Cache Mode is gray out on Outlook 2010

    Details:
    This article will provide a workaround to enable or disable Cache Mode on Outlook 2010 when the check box is gray out.
    Solution:
    To Enable Cache Mode on:

    1. Open REGEDIT
    2. navigate to the following registry: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\outlook\cached mode
    3. Modify Value on dword “Enable”=dword to 1

    4. Close Registry Editor

    5. Restart Outlook

     
    To Disable Cache Mode on:

    1. Open REGEDIT
    2. navigate to the following registry: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\outlook\cached mode
    3. Modify Value on dword “Enable”=dword to 0

    4. Close Registry Editor

    5. Restart Outlook
    ,

  • How to clear the Email Cache in Outlook 2010 & 2013

    How to clear the Email Cache in Outlook 2010 & 2013

    Details:
    E-mail
    Address Auto-Complete

    Outlook 2010 & Outlook 2013 have a feature called “Email Address
    Auto Complete”. This feature allows you to type an email address into
    the “TO:”, “CC:”, or “BCC” fields.

    Outlook will display a list of corresponding e-mail addresses from the
    auto-complete cache. For example, e-mail addresses that you have
    already used.
    Solution:
    To Clear the E-Mail Cache:


    Solution 1:   Manually Delete    (For ALL Versions of Outlook)
    1. Open Outlook.
    2. Type the e-mail address you wish to clear from the cache.
    3. Press the Down-Arrow button (on the keyboard) to select the e-mail address.
    4. Press the Delete button (on the keyboard).
    5. That e-mail entry is now removed from the Outlook Auto-complete cache.
    Solution 2:  Empty Auto-Complete List Button    (ONLY for Outlook Versions 2010 & 2013)
    1. Open Outlook.
    2. Click File | Options.
    3. Click on the Mail tab on the right.
    4. Scroll down to Send messages and click the Empty Auto-Complete List button.
    ,

  • Removing Foreign Aggregate on NetApp ONTAP 8.2.1 Cluster Mode

    Removing Foreign Aggregate on NetApp ONTAP 8.2.1 Cluster Mode

    So After installing a SAS Disk Shelf and assign ownership for all new disk, I notice that old aggregates from the previous filer were created as Foreign, This is a big problem. After doing some research, I was able to find the solution on a great KB from NetApp KB 1013046 using the Aggregate Destroy Command.

    Note: Be very careful while going through this process as you can delete the wrong aggregate and it almost near impossible or impossible to restore an aggregate.

    Here are the steps I follow it:

    1. SSH to the Cluster.

    2. Then Run the system
    node run -node * -command sysconfig -r     command to identify the aggregate on Foreign State:

    If the above output is to overwhelm, you can also uses the aggr status for each node by running the following command:

    system node run -node -command aggr status

    Notice that the Output is more clear to identify does foreign aggregates.

    3. Now that we identify does Foreign aggregates as well on which node, first we need to enable the Aggregate Destroy command since by default is not enable. To do so we will need to run the following command:

    node run -node options nodescope.reenabledcmds ‘aggr=destroy’


    4. Once Aggregate Destroy is enable, we are deleting does aggregate by typing the following command:

    system node run -node -command aggr destroy

    5. Confirm by selecting yes

    6. After removing those aggregates, we will disable the Destroy command option. This will bring back the other command options that were locked previously such aggregate status. To do so, run the following command:

    node run -node options
    nodescope.reenabledcmds ‘ ‘

    7. Let confirm if those foreign aggregates were remove. Run the following command:

    system node run -node -command aggr status



    As you notice on the above image, those foreign aggregates are now gone.

    8. After I deleted those aggregates, I proceed to verify the status of my SAS disk by running the command disk show -type SAS





    Notice all my disks are now spare and they are not part of an aggregate.

    If you are running OPTAP 8.3 and later versions, please refer to the NetApp KB 1013046.

    ,

  • Troubleshooting HTTP 500.19 Errors in IIS 7

    Troubleshooting HTTP 500.19 Errors in IIS 7

    I few month ago, I was configuring a management software for Dell servers on IIS. Once I finish the all configuration, I decide to run the web app and I got the following error message:

    HTTP Error 500.19 – Internal Server Error
    The requested page
    cannot be accessed because the related configuration data for the page
    is invalid. Module DynamicCompressionModule
    Notification SendResponse
    Handler StaticFile
    Error Code 0x8007007e
    Requested URL http://localhost:80/
    Physical Path C:\inetpub\wwwroot
    Logon Method Anonymous
    Logon User Anonymous

    O no, now what? Well after doing some research, I was able  to find a solution. The reason of the error message  is the DynamicCompressionModule module is causing the trouble. This is because
    of the XPress compression scheme module (suscomp.dll) which gets
    installed with WSUS and this server is also a Distribution Point for SCCM so WSUS role is install for update catalog . Since Compression schemes are defined globally and
    try to load in every application Pool, it will result in this error when
    64bit version of suscomp.dll attempts to load in an application pool
    which is running in 32bit mode.

    The solution:  Remove / Disable the XPress compression scheme from the configuration using the command  
    C:\Windows\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name=’xpress’]

    OR Add an attribute of “precondition= “64bitness” for this module entry so that it loads only in 64bit application pools.

    OR  Use a 32bit version of suscomp.dll

     Reference
     Link

    ,

  • SQL Translog Shrink Script

    SQL Translog Shrink Script

    Here is a good Script I use to Shrink does SQL Databases Translogs:

    ——————————————————————————
    — Update the line below with the name of the database who’s transaction
    — log you want to shrink.
    ——————————————————————————
    USE name of the database
    ——————————————————————————
    — Don’t change anything below this line.
    ——————————————————————————
    GO
    — Declare variables
    DECLARE @SqlStatement as nvarchar(max)
    DECLARE @LogFileLogicalName as sysname
    — Alter the database to simple recovery
    SET @SqlStatement = ‘ALTER DATABASE ‘ + DB_NAME() + ‘ SET RECOVERY SIMPLE’
    EXEC ( @SqlStatement )
    — Make sure it has been altered
    SELECT [name], [recovery_model_desc] FROM sys.databases WHERE [name] = DB_NAME()
    — Set the log file name variable
    SELECT @LogFileLogicalName = [Name] FROM sys.database_files WHERE type = 1
    — Shrink the logfile
    DBCC Shrinkfile(@LogFileLogicalName, 1)
    — Alter the database back to FULL
    SET @SqlStatement = ‘ALTER DATABASE ‘ + DB_NAME() + ‘ SET RECOVERY FULL’
    EXEC ( @SqlStatement )
    — Make sure it has been changed back to full
    SET @SqlStatement = ‘SELECT [name], [recovery_model_desc] FROM ‘ + DB_NAME() + ‘.sys.databases WHERE [name] = ”’ + DB_NAME() + ””
    EXEC ( @SqlStatement )
    ——————————————————————————

    Were is red, enter the name of the Database that you would like to shink the logs.

    By http://ottoradke.com

    , ,

  • Creating a Shared Mailbox

    Creating a Shared Mailbox

    Recently I was implementing a Fax solution and one of the requirement was to create a Shared Mailbox for Inbound Faxes. If you go to the Exchange Management Console and try to add it from there, you never will find it there. The only way to do so is by running a simple Powershell command:

    New-Mailbox “Mailbox Name” -Shared -UserPrincipalName emailaddress@contoso.com

    Copy this command but remember to replace the Mailbox Name with the name you decide for the Shared Mailbox and the SMTP Address on emailaddress@contoso.com. This will create also a generic account on Active Directory under the Users Container and it will be disable. Please, do not enable the service account since don’t need to.

    , ,
    ,

  • Moving Cluster Group for Exchange 2010

    Moving Cluster Group for Exchange 2010

    In some environment, Moving the DAG from one server to the other is necessary for numerous reasons and one of the task involve is moving the Cluster Group to the active server. Here’s is the how to:

    1. login to the Exchange Server that you want to set as active for the Cluster Group

    2. Open the Command Prompt with the run as administrator

    3. Type the following command

    cluster group “Cluster Group” /move

    4. Then go to EMC and move the Mailbox DB

    5. Finish

    I usually perform this process when the DAG failover to the other exchange server or I loose the server where the file witness reside since it does it on a different server from the Exchange Servers.

    , ,
    ,