SQL Server problem with event IDs: 823

Situation: the client has a SQL server 2008 R2. They had a problem to access some of database. There are some Events:

Event ID:      823
Description:
The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x00000000322000 in file ‘R:\MSSQL\HSADB DATA\M846_Sub.mdf’. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

Troubleshooting: The Database is located in EqaulLogic SAN. There are 4 NICs connecting to the SAN. However, EqualLogic SAN Management shows there are only two are active.

<

High CPU issues being used by Azure AD DirSync

Situation: The client has an Azure AD DirSync server version 1.1.819.0 running on Windows server 2012 r2. After installing the latest cumulative Windows Update patch, the server is experiencing high CPU issues being used by the “Azure AD Connect Health Sync Monitor”

Resolutions 1. Install the latest version (1.1.880.0) of Microsoft Azure Active Directory Connect.

2. If for some reasons you can’t install the new version, stop the Azure AD Connect Health Sync Monitor Service. Here is how:

  • Click on Start and search for Services
  • Find the Azure AD Connect Health Sync Monitor service
  • Right click on it and click Stop
  • Right click on the same service and go to Properties
  • Change the Startup Type to Manual.

3. Uninstall the KB4338814 Windows Update. The next option is to uninstall the Windows Updates that caused the problem. In my case, it was the KB4338814 “2018-07 Cumulative Update for Windows Server”. Some other people have reported success by uninstalling any or all of these updates: KB4103725, KB4096417, KB4095875, KB4054566, KB4338815, KB4338419, KB4340558, KB4338605, KB4339093, KB4340006, or KB4338824.
•Click on Start and go to Settings
•Go to Windows Update
•Go to Update History
•Click on Uninstall Updates
•Find the KB updates you want to uninstall
•Click on the update then click Uninstall

Uninstall .NET Framework 4.7.2 Update

Restarting server never comes back

Situation: The client has a server running Windows 2008 R2 server. Whenever they restart the server, it shutdown but never comes back. They need to turn it off manually and then turn it on. In other words, warm reboot doesn’t. It works only cool reboot.

Troubleshooting: We find there is a dead USB drive connecting to the server. Removing it from the server fixes the problem.

RA Web site going down for no reason

Q: We are running RA 2017.3. We are having a problem with our RA Web site going down for no reason. No log information amd restarting IIS doesn’t help either. We need to do a total server restart. Any ideas on what we can do?

A: Change Maximum Worker Processes to 2 and lets see if that helps. To do that, please open IIS. Navigate to Server name>Application Pools>Advanced Settings, change Maximum Worker Processes to 2.

 

 

Windows 10 blue screen with error code 0x000000e after cloning

Situation: the client tries to clone his Laptop Windows 10 with HDD disk to a SDD disk. However, it gets Windows Recovery blue screen with error code 0x000000e.

Resolution: Restore BCD by downloading and creating the disc image from Microsoft. Boot from windows installation media/command prompt and execute: bootrec /rebuildbcd.

My Laptop is so hot and what can I do?

  1. Use a Lap Desk with fan.
  2. Install a program like SpeedFan (for Windows) or smcFanControl(for OS X).
  3. Lighten the Load – Use Windows Task Manager to see what’s using your CPU so intensively. Disable some programs you don’t need to run on the background.
  4. Fix or clean the fans.
  5. Updating the BIOS.
  6. It could be a hardware issue, for example the battery is dying.
  7. You may want to change the power option to balance.

拍鸟笔记-蜂鸟 Where to find Hummingbirds in Chicago Area

芝加哥什么地方可以拍到蜂鸟?

Chicago Botanic Garden, Morton Arboretum, River Trail Nature Center, Crabtree Nature Center. 很多繁花似锦的地方都可能会有蜂鸟。

芝加哥拍蜂鸟的最佳季节是什么时候?

一般在四月底五月初到秋季。据专家说目前(2018年八月以前)芝加哥植物园蜂鸟比较少的原因主要有两个。一是天气,第二是与种植的花品种有关。

那么蜂鸟喜欢什么花?

Bee balm, Delphiniums Butterfly bush, Delphiniums, Larkspur, Iris, Lilies, Columbine, Petunias, Salvia, Phlox, Scarlet sage as shown in this page.

Veeam Backup error with Event ID: 150 and 190

Situation: The Veeam backup has a problem to backup one of VM with these Event IDs:

Log Name:      Veeam Backup
Event ID:      150
Level:         Error
Description:
VM HSAProcess0708 – W2012R2 task has finished with ‘Failed’ state.
Task details: Failed to get unaccounted changes for disk W2012R2-Test.vhdx. Change tracking is disabled
Error: Snapshot with id ‘{7ee49be4-4ab7-4e0d-ad67-32fa58123b2b}’ was not found.
–tr:Failed to complete VM backup. Snapshot id: ‘{7ee49be4-4ab7-4e0d-ad67-32fa58123b2b}’.
Snapshot with id ‘{7ee49be4-4ab7-4e0d-ad67-32fa58123b2b}’ was not found.

Log Name:      Veeam Backup
Event ID:      190
Description:
Backup job ‘BackupHos02’ finished with Failed.
Job details: Processing HSAProcess0708 – W2012R2 Error: Snapshot with id ‘{7ee49be4-4ab7-4e0d-ad67-32fa58123b2b}’ was not found.
–tr:Failed to complete VM backup. Snapshot id: ‘{7ee49be4-4ab7-4e0d-ad67-32fa58123b2b}’.
Snapshot with id ‘{7ee49be4-4ab7-4e0d-ad67-32fa58123b2b}’ was not found.

Possible Cause: The Volume Shadow Copy Service is unable to allocate disk space to create a shadow copy because the maximum size of the shadow storage area is too small.

Solution: Increase the shadow copy storage area for the volume listed in the error event, or set the maximum size to “No limit” by following these steps:

  1. Right click any volume and choose Configure Shadow Copies.
  2. With the Shadow Copies utility open, select the volume with insufficient space;
  3. Click Settings…
  4. In the “Maximum size” box, either increase the limit, or choose “No limit”.

 

 

How to export/import domain account information

  1. Export from DomainA:

csvde -f C:\Rename\export_AD.csv -m -n -o “primaryGroupID,lockoutTime” -j C:\Rename\Logs

Where:

-f filename to export to

-m do not export SAM values, e.g. objectSID

-n do not export binary values

-o exclude named columns

-j folder to log to (produces csv.log, plus csv.err if any errors occured)

2. Edit the export_AD.csv file as follows:

Delete the lines beginning:

o   “CN=Builtin …       (1 expected)

o   “CN=Infrastructure… (1 expected)

Delete all lines containing:

o   ,samServer,     (1 expected)

o   ,rIDSet,           (1 expected)

o   ,secret,           (4 expected)

o   ,rIDManager,       (1 expected)

Remove any ‘box’ (ASCII 13) characters in the text:

o   Unfortunately these cannot be searched for in Notepad

o   There may be one in the commas at the end of each of the last 50 lines in the file

Replace all instances of ‘PCOld’ with ‘PCNew’

o   Where PCOld is part of the machine name and domainname

3. Import into DomainB:

csvde -i -f C:\Rename\export_AD.csv -k -j C:\Rename\Logs

o   -i import

o   -f filename to export to

o   -k ignore non-serious errors (e.g. object, attribute or value already exists)

o   -j folder to log to (produces csv.log, plus csv.err if any errors occured)