How to convert Windows error code into Simple English description ?

How to convert Windows error code into Simple English description ?

  07:06    Cloud Technet

---

While troubleshooting, most of the times you can see Windows OS is throwing error in Hexadecimal code. You may find this error in event viewer or msi logs, or CBS logs. Most of the time there wont be any description for this error code in the logs or events. You can convert this error codes into Simple error description. Here I am going to show how to do this. Lets take the below error code as an example.

You can see from the above error message that calling of vbscript.dll was failed with error code 0x80004005. The error code is in Hexadecimal. You have to convert the code into decimal before finding out its error description. Lets convert the code 0x80004005 in to decimal. You donot need to convert whole number into decimal. Take only last four or three last digits from the error code. Here we are going to convert last 3 digit of the error code "005". 

Open the calculator in Programmer mode.  

Enter the value in Hexadecimal

Click on Decimal to get the decimal value

Copy the decimal value. Open a command prompt and run the command net helpmsg <decimalnumber>
in our example command will be net helpmsg 5

You can see the error description for decimal value 5 as "Access is denied". You can further investigate the issue according to the error description. There might be permission issue to access the regitsry location of vbscript.dll in our example, hence the windows throwed the error. Below are some more error codes and its description

0x80070490 - Element not found. 

0x80004005  -  Access is denied. 

0x8007054f  -  An internal error occurred. 

0x80070bc2   -  The requested operation is successful. Changes will not be effective until the system is rebooted. 

0x80070643  -  Fatal error during installation. 

Read More

VMware 6 Maximums

VMware 6 Maximums

  02:46    Cloud Technet

---

https://drive.google.com/file/d/0B3fb_0spL4QTOEhCWVo5NkRVcEU/view?usp=sharing 

Read More

What is Session Lingering in Citrix ?

What is Session Lingering in Citrix ?

  05:14    Cloud Technet

---

Session lingering prevents a session from closing as soon as the user ends the last published application in a session. It is assumed that a users may have closed the last published application unknowingly. Instead of logging off, the session is silently retained to provide very short startup times for future published applications.

Session lingering kicks in as soon as a session is meant to be terminated. This may be caused by the user ending the last published application in a session or if both pre-launch timeouts occured (see above).

Session lingering uses two timers to determine whether the lingering session is kept available:

• Disconnect Timer: After the configured time interval, the session is disconnected. A disconnect timer of zero forces the decision about the session's fate on the terminate timer.
• Terminate Timer: When this timer runs out, the session is terminated and the users will have to suffer the logon time when launching a published application.

The Citrix eDocs contain a short description of both timers. The above video also provides a walkthrough for setting up session lingering.

 

 

 

Read More

What is Session Pre-Launch in Citrix ?

What is Session Pre-Launch in Citrix ?

  05:12    Cloud Technet

---

Session pre-launch allows a user (or rather Citrix Receiver) to silently connect to a XenApp farm assuming that the session will be required in the near future. When a user actually starts an application, the startup time is dramatically reduced because a logon is not necessary and session sharing allows published application to be launched inside the active session. As soon as Citrix Receiver starts on the client device, a pre-launch session is created in the background. As soon as a published application is requested by the user, XenApp can immediately start it in the existing session using session sharing.

Session Pre-Launch uses two timers to determine whether the pre-launched session is kept available:

• Disconnect Timer: Once this timer runs out, the session is disconnected. If the disconnect timer is set to zero, the terminate timer determines the fate of the pre-launched session.

• Terminate Timer: When a terminate timeout occurs, the pre-launch session is terminated. But this may still result in the session to be retained if session lingering is configured (see below). Without session lingering, the session is ended and the user will have to suffer the logon time when launching a published application.

The Citrix eDocs contain a short description of both timers as well as more information about the hidden pre-launch application. In addition, this video below provides a walkthrough for setting up session pre-launch. Citrix employee David Gaunt has published a very detailed article about session pre-launch and what it looks like in AppCenter.

Read More