詠鉌のIT

The simplest way for software troubleshooting is to obtain important info/logs for analysis. If you do not really know how to read the logs, at least you have to know how to obtain the right logs/info for the professional to help you.
Today, I'm gonna show you on how to gather the log file through VxGather.exe.
Introduction to Symantec Gather Utility (VxGather.exe)
- Gather the common diagnostic & historical files for troubleshooting purpose.
- Will look for Windows Event Logs, BE Installation Logs, BE application logs, and running Bediag.exe when it is necessary.


Steps:
1. Double-click VxGather.exe which located at \Program Files\Symantec\Backup Exec


2. Select the required info by check the checkbox in the Data to gather (if available) as below:

Few weeks back, there is one customer from Taiwan drop me an email with a lot of logs attached. After I read the last line of the content, then only I know he was asking me to analyze the log to ensure whether the storage is working  fine or not. Customer confirm the storage was working time at that time, but the management software: Modular Disk Storage Management (MDSM)

Raw data:

4d 45 4c 48 03 00 00 00 1b 04 00 00 00 00 00 00
0a 21 48 00 4c 99 19 4d 00 00 00 00 00 00 00 00
00 00 00 00 04 00 00 00 08 00 00 00 08 00 00 00
ff ff ff ff 01 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 01 00 00 00 00 00

I do not know how true is that, customer always complaint to me that Dell Server is very sensitive to memory Single-bit Error (SBE) compared to HP and IBM server. Some Dell server with the role of File or Database Server with heavy I/O, which are the most easy to encounter this error/warning at the system status LCD Panel as below:

"E2111 SBE log disabled on DIMM ##. Reseat DIMM."

LCD Panel

"..the memory error logging is as per design, and it wouldn't clear off automatically even if the SBE has been handled by the ECC Memory, unless we clear the hardware error log (can clear through OpenManage Server Administrator(OMSA) or Dell System E-Support Tool (DSET))  or till the system reset. This is because many customer/user would like to use those error for future reference..."  

    i)   Log in to OMSA (with Administrative rights)
    ii)  System -> Log (tab) -> Clear ESM Log
  

Windows Server 2008 already in the market for more than two years, but some of the Server Administrators still not familiar to it, as Windows Server 2003 still perform well in most of the companies nowadays.


The most common question asked by a Server Administrator during the Windows Server 2008 implementation is as below:

"...After Windows Server 2008 installation completed, it will ask to log in with a password, but I can't find any default password from the DVDs case.." 

Dell System E-Support Tool (DSET) is very useful for troubleshooting especially when we deal with non-technical IT Personnel, or 'lazy' customer who totally not cooperative to provide further information. The key features is provides the ability to collect hardware, storage and operating system information of a Dell PowerEdge or PowerVault server.


Compatibility list:
i) PowerEdge Server:

800, 830, 840, 850, 860, 1800, 1850, 1855, 2800, 2850, 6800, 6850, 1900, 1950, 1955, 2900, 2950, 2970, 6950, NX1950, SC1420, SC1425, SC1430, SC1435, SC420, SC430, SC440, R805, R905, R900, T100, T105, T300, T605, R200, R300, M600, M605, M805, M905, R610, T610, R710, M610, M710, R410, T410, T310, R310, R210, T110, R510, R910, R810,R715,R815, R415, R515, M610x, M710HD and M910

100T, 110T, 122T, 124T, 132T,136T, ML6000, 200/210, 220S/221S, MD1000, RD1000 Internal SATA Drive, TL2000,TL4000, MD1120, NF110, DL2100 and DL2200

iii) Microsoft Operating System:

* Microsoft Windows 2003 Server x86 and x64
* Microsoft Windows 2003 Server x86 and x64 R2
* Microsoft Windows 2008 Server 32-bit and 64-bit 
* Microsoft Windows 2008 Server 32-bit and 64-bit SP2
* Microsoft Windows 2008 Server R2

On and off, I still received calls that customer still request support or escalation to Microsoft for Windows 2000. I remember few weeks ago, a Singaporean request support for this Operating System (OS), even though result from the troubleshooting shows that the issue from the OS but not hardware. Furthermore, his server already out-of-warranty but still requesting the support with the arrogant tone.

Finally I have a little time to clean my personal email - Hotmail. I'm did not read the email one by one before I click 'Delete' button, because there are too many spam emails flood the mailbox everyday. However, I'll have a quick look to the email subject before I send them into the dustbin. 
Didn't know why, a subject with "Your Windows Live Space will close on 16 March" attract me to read further. That's how I discover this notification email from Microsoft.

Dear Windows Live Spaces customer, 

You are receiving this note as a follow-up to our communications notifying you that Windows Live Spaces will soon close. If you haven't taken an action yet, please read on to learn how to preserve the content of your space. On March 16th, 2011 your space will be closed. However, you can still preserve the content of your space if you take action now. 

We are collaborating with a premier and innovative blogging service, WordPress.com, to enable Windows Live customers to migrate their Windows Live Spaces blog to WordPress.com where you will get a number of enhancements to your blogging experience. We'll help you migrate your current blog to WordPress.com or download it to save for later. On March 16th, 2011 your current space will be closed and you will no longer have access to the content on your space unless you take action. Click here to begin the migration of your space. 

With the new release of Windows Live services, we've made a series of changes and improvements across the products. We chose to partner with WordPress.com to provide Windows Live users with a fantastic blogging solution. However, we realize they will have an impact on you, so the information in this email aims to clarify what to expect. We thank you for your continued support of Windows Live.

When you visit your space you'll have the following options: 

i)   Upgrade your blog by migrating to WordPress.com - We will provide a simple way to move your blog posts and comments to WordPress.com. 

ii)  Download your blog – You can download your old posts to keep a copy with you. You can also do this and then migrate to WordPress.com. 

iii) Delete your space - If you decide that you do not want to have a space anymore, you have the option to delete it permanently. If you want to save your content, please make sure to do that before deleting your space. 

iv)  Review your blog – Soon your space will close but you still have some time to review your blog and make a decision that's right for you. We're very excited about what you can do on WordPress.com and hope you'll decide to take advantage of this improved blogging experience.

Windows 7, one of my favorite Operating System after Windows XP. Not only come with the impressive user-friendly interface, but also with the very good stability. At least, it is able to run smoothly with only 2GB system memory; this is the main reason I switch from Windows Vista to Windows 7, due to 4GB system memory just enough to support Vista without any other complex applications such as Adobe Photoshop is running.

Recently received a lot of calls regarding memory errors from Power on Self-Test (POST) stage: "Memory Population Error!". To summarize, all these considered as 'hardware fault' is actually due to customer didn't really read the documentation before they add in new memory.


A lot of customers still think that the memory population should start from the first slot, and follow the sequence to the right (if there is only single CPU). As the result, most customers will populate the memory as A1, A4, A7, A2 if they have 4x memory sticks. That is how they get Memory Population Error.


With referring to Table 1, the correct memory population for RDIMM should be on slot : A1, A4, A2, A5.


CPU and Memory layout as below:













Table 1:RDIMM Memory Configurations