SD Card Reader Not Reading Automatically

So I had this experience with my laptop which runs Windows 10. Every time I insert my SD card, the Windows doesn’t seem to react, or maybe it’s the hardware’s fault. What I did is this:

  1. Go to the Device Manager.
  2. Find the card reader. In my laptop, it’s under Memory technology devices > Realtek PCIE CardReader.
  3. Right-click the particular card reader that you are using then click Disable.
  4. Wait for a second to completely disable. Then right-click again to Enable.
  5. At last! My SD card is now being read.ūüôā

This works for me every time, although I do not know exactly the cause. I haven’t researched anything about it, I just thought of disabling / enabling it via Device Manager.ūüôā

WebSphere Application Server 8.5.5: Changing the console session expiration

The idle period, before the administrative console session expires, is referred to as session timeout. The default session timeout value for the administrative console is 15 minutes. The timeout value can be modified by using a JACL script that is available at the information center. [From: WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile]

Run this JACL script to set how long Integrated Solutions Console can be used until the login session expires.

About this task

The following JACL script serves as an example of how to set the duration that an Integrated Solutions Console can be used until the login session expires. Other scripting types, such as JYTHON, could be used.

Procedure

  1. Copy the following script into a file.
    set dep [$AdminConfig getid /Deployment:isclite/]
    set appDep [$AdminConfig list ApplicationDeployment $dep]
    set sesMgmt [$AdminConfig list SessionManager $appDep] 
    
    # check if existing sesMgmt there or not, if not then create a new one, if exist then modify it
    if {$sesMgmt == ""} {
         # get applicationConfig to create new SessionManager
         set appConfig [$AdminConfig list ApplicationConfig $appDep]
         if {$appConfig == ""} {
             # create a new one
             set appConfig [$AdminConfig create ApplicationConfig $appDep {}]
             # then create a new SessionManager using new Application Config just created
             set sesMgmt [$AdminConfig create SessionManager $appConfig {}]   
         } else {
              #  create new SessionManager using the existing ApplicationConfig
              set sesMgmt [$AdminConfig create SessionManager $appConfig {}] 
    
         }
    }  
    
    # get tuningParams config id
    set tuningParams [$AdminConfig showAttribute $sesMgmt tuningParams]
    if {$tuningParams == ""} {
        # create a new tuningParams 
        $AdminConfig  create TuningParams  $sesMgmt {{invalidationTimeout <timeout value>}}  
    
    } else {
         #modify the existing one
         $AdminConfig modify $tuningParams {{invalidationTimeout <timeout value>}}  
    
    }
    
    # saving the configuration changes
    $AdminConfig save
    
  2. Change the <timeout value> on the two lines of this sample to the new session expiration value. This number specifies the number of minutes the console preserves the session during inactivity.
  3. Save the file to any directory using, for example, the filename timeout.jacl.
  4. Start the wsadmin scripting client from the <WAS-install>/profiles/<profile_name>/bin directory.
  5. Issue the following command.
    wsadmin -f <path to jacl file>/timeout.jacl

Source: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Fisc%2Fcons_sessionto.html

IBM Content Navigator 2.0.2 Ping page

Procedure

To access the Ping page to find version information for IBM Content Navigator:

Enter the URL from any browser with the following format:

http://host_name:port_number/context_root/Ping

By default, the context root is navigator.

Tip: If you are using SSL, the protocol of the URL is HTTPS:

https://host_name:port_number/context_root/Ping

Example:

https://myserver.mycompany.com:9080/navigator/Ping

Source: http://www-01.ibm.com/support/knowledgecenter/SSNW2F_5.1.0/com.ibm.installingeuc.doc/eucts019.htm?lang=en

A user authenticated as anonymous has attempted to access a session owned by

Please see this link for the entire details of the cause and solution.

Resolving the problem

Disable the IBM Websphere Application Server 8.x Security Integration feature for WorkplaceXT:

  1. In the IBM Websphere Administrative Console navigate to Applications->Websphere Enterprise Applications -> WorkplaceXT -> Session Management
  2. Check the Override session Management checkbox
  3. Uncheck the Security integration option
  4. Save the changes
  5. Restart the WorkplaceXT application

Microsoft Web Deploy 3.0: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file

Ervin Loh's space

When you try to install Visual Studio 2012 after October 7, 2013, you receive the following error messages:

Microsoft Web Deploy 3.0
A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file.

These errors occur because of a failed timestamp comparison in the installer that is caused by an improperly signed Web Deploy Package.

If you receive a warning after you successfully complete the installation of Visual Studio 2012, you can fix the problem by installing Web Deploy 3.0.

Download URL:

http://www.microsoft.com/en-us/download/details.aspx?id=30436

View original post

SharePoint 2013: Installing Prerequisites Error

I installed the SharePoint 2013 prerequisites and it could not continue on AppFabric. 1.1. See this link for the solutions.

In my case, here is the solution I applied:

  • Go to¬†My Computer, right-click¬†Properties
  • On the¬†System page, click¬†Advanced System Settings¬†on the left-side pane.
  • If you receive a UAC prompt, click on¬†Yes¬†to launch the¬†System Properties¬†dialog box
  • From the¬†Advanced¬†tab, click¬†Environment Variables
  • Within the¬†System Variables¬†section in the lower half, select¬†PSModulePath¬†and click on¬†Edit¬†(or double-click¬†PSModulePath)
  • Append the following path to¬†PSModulePath¬†entry in the environment variables
C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules
  • Ensure that the¬†PSModulePath¬†entry looks like this:
C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules