Author: Bob Lin

Bob Lin, Chicagotech-MVP, MCSE & CNE Data recovery, Windows OS Recovery, Networking, and Computer Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

Windows 2008 R2 crashed because modifying registry

Situation: After modifying registry in a windows server 2008 R2, we can’t login Windows. The keyboard doesn’t work and we don’t have login screen. It is freezing. We have tried Safe mode, but that doesn’t work.

Troubleshooting: We have following this article

How to recover a Windows system that does not start because of corruption in the registry http://www.howtonetworking.com/winissues/recoverwin1.htm

to copy registry files from c:\windows\system32\repair. However, it doesn’t have repair folder.

After searching for system, default, sam and security files, we find them under c:\windows\system32\config\regbackup. Copying latest those files into c:\windows\system32\config fixes the problem and we can login the windows.

Windows backup failed: has failed with following error code ‘2155347997’

Situation: the client use Windows backup tp backup their windows 2008 R2 server. It failed with this message: has failed with following error code ‘2155347997’. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.”

Troubleshooting: We fix this problem by making sure the Volume Shadow Copy is running.

Anyone is grayed out in OneDrive share

Situation: We have enabled OneDrive Anyone share in Office 365. However, when users go to Onedrive to share, the Anyone is grayed out.

Troubleshooting: 1. Login Office 365>Admin>OneDrive>Share, check the Shareable: Anyone with link.

 

2. If that doesn’t fix the problem, In the same page: Admin>OneDrive>Share, make sure External share bar is in the top.

3. If you can set SharePoint Most permissive to top bar, Anyone, but not OneDrive, you may need to check the SharePoint share settings as shown below.

 

 

“A Remote Desktop Services deployment does not exist in the server pool…”

Situation: the client just installs Remote desktop server in his Windows 2016 server. When he goes to Server Manager>Remote Desktop Services, he gets this message: “A Remote Desktop Services deployment does not exist in the server pool…”

Resolution:

  1. Go to Add Roles and Features.

2. Follow the Add Roles and Features Wizard. Then check Remote Desktop Services installations.

3. Check Quick Start or Standard deployment if you want to deploy for multiple servers.

4. Check Session-based desktop deployment.

5. Make sure the server is selected and click on Next.

6. Check Restart the deployment server automatically if required, and then click on Deploy. 

7. If all of them are Succussed, clock Close to complete the deployment.

 

 

 

 

Can’t install SQL 2014 Express because of long password

Situation: the client is trying to install Relius Administration 2018 Component with SQL 2014 Express. It completed the installation, but it doesn’t install SQL 2014 Express.

The SQL 2014 Express limits password 10 characters. The company password policy requires 12 characters. Temporary disable password policy or change it to 10 characters fix the problem. Note: you need to run gpupdate /force or restart each workstation.

 

SQL Backup failed with Event ID 18204

Situation: The client us running SQL 2008 R2 and failed to use SQL Backup. The event view shows this message:

Log Name:      Application
Source:        MSSQL$CRM
Date:          10/21/2018 10:45:03 PM
Event ID:      18204
Task Category: (2)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SQLserver03
Description:
BackupDiskFile::CreateMedia: Backup device ‘\\backupnas\backups\SQLServer03.bak\SQLDATA\SQL_Backup\distribution_backup_201810212245.bak’ failed to create. Operating system error 5(Access is denied.).

Troubleshooting: this is permission issue. Please make sure the computer login account has full permissions to access \\backupnas\backups\SQLServer03.bak\SQLDATA. For a test, you can assign full permissions to everyone.