Andy M

I ran into an issue where the Window search service would constantly crash. The Event viewer showed the error below, and the crashdumps folder has a ton of SearchProtocolHost.exe.21580.dmp files. Faulting application name: SearchProtocolHost.exe, version: 7.0.9600.19660, time stamp: 0x5e4586a5 Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5e8a785b Exception code: 0x0241938e Fault offset: 0x00196a44 Faulting process id: 0x24a4 Faulting application start time: 0x01d617e35d974e4f Faulting application path: C:\windows\sysWow64\SearchProtocolHost.exe Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll Report Id: b5c9d48f-83d6-11ea-80fa-000c290a7afd Faulting package full name:  Faulting package-relative application ID:  Analyzing the crash dumps pointed to MSPST32.DLL but none of the users had PSTs loaded. I found this article , but it did not resolve the issue. Eventually the f...

I have been dealing with an issue where a user's outlook would switch to online mode at random. The only way to resolve the issue was to log the user out of the computer and back in. Re-creating the account resolved the issue, but it came back the next day. Procmon and ProcExp didn't point to any clear causes. Eventually I was able to find the root cause by looking at the permissions of the mailboxes. The two mailboxes had Full Access to each other and auto mapping (never use auto mapping!) was enabled. This resulted in a situation where the mailboxes were fighting for who would be the primary mailbox, and who would be the secondary. Removing the permissions resolved the issue and both mailboxes worked correctly inside of Outlook. 

Have an issue you can't solve? I offer consulting engagements and can be reached here: consulting[а 𝐭 ]amorales[․]org This article will cover some common issues I have ran into, and steps on how to resolve them. The guide should be followed  in order  since most of the advanced items are usually not the cause of a problem. If you just set up FSLogix, make sure that you followed every step under  Deploying FSLogix Office 365 Containers  and  Deploying FSLogix Profile Containers Terminology ODFC = Office Data File Containers This is there Office (Outlook, Teams, Licensing) data is stored This can be used in conjunction with UPDs FSL Profiles Replacement for UPDs User profiles are stored here (Office data is stored in the ODFC) Cannot  be used in conjunction with UPDs Non-Issues The items below should be ignored when troubleshooting Local_ files under C:\Users If FSLogix profiles are enabled, these folders can be ignored. They...

KB4541329 Appears to be the cause of this issue. Uninstalling it should permanently fix the issue. Just ran into an issue where a user kept getting a "COM Surrogate has stopped working" every time they tried to print from Windows Photo Viewer. They also kept running into an issue where Excel, Word, and RDP connections would crash when launched. Analyzing the crash dump that was generated (dllhost.exe) revealed the issue. The application was not able to find the default printer. Trying to set the default through Devices and Printers in control panel resulted in another crash. The fix was to run the command below: (New-Object -ComObject WScript.Network).SetDefaultPrinter('PRINTER NAME') The crashes went away once the default printer was set.

After a bad activation of BitLocker a Dell computer started giving a "no boot device found" error. I tried to re-image the computer but kept getting the error below: Windows Deployment Services Encountered an Error 0xc0000225 Resetting all BIOS settings and clearing the TPM didn't do anything. Eventually I found that Dell computers have an option to wipe all drives. After enabling the option and wiping the drive the laptop was able to boot into WDS again.

Just ran into an issue where Office apps would not open any documents saved in my OneDrive folder.  I would get the "Starting..." screen and then it would just close. Opening those same files from other locations like the desktop worked fine. The event log had some errors, but they didn't really point to a specific item: SettingSyncHost (14848) An attempt to open the file "C:\windows\system32\edbtmp.log" for read / write access failed with system error 5 (0x00000005): "Access is denied. ".  The open file operation will fail with error -1032 (0xfffffbf8). SettingSyncHost (14848) {9842A2DC-6CA6-48E2-924F-3ECFD7461AD8}: Database recovery/restore failed with unexpected error -1216. SettingSyncHost (14848) Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032. Running ProcMon revealed that Excel and Word did not have access to %l...

I recently ran into an issue where I did not have the option to delete an Organizational unit. I made sure to uncheck "Protect Object From Accidental Deletion", and I had the appropriate permissions on the security tab. Attempting to delete from ADSI edit resulted in the error below: Operation failed. Error code: 0x20ce The requested delete operation could not be performed.  000020CW: SvcErrL DSID-0315370F, problem 5003 (WILL_NOT_PERFORM), data 0 The solution was to use redircmp to redirect new PCs to a different OU. redircmp "OU=Servers,OU=Computers,DC=example,DC=com" Restart Active Directory Users and Computers, and the delete option should be available for the OU.