Month: November 2016

Windows 10 – Windows Explorer not responding when creating or renaming a folder on a Server 2012 Essentials R2 network share

Windows 10 – Windows Explorer not responding when creating or renaming a folder on a Server 2012 Essentials R2 network share

Problem:

I recently had an issue with a Windows 10 PC. Windows Explorer stops responding when creating or renaming a folder on a Server 2012 Essentials R2 network share.

Client Spec:
Windows 10 64-Bit
Version 1607
Build 14393.351
4GB RAM
i5 Processor

Issue explained:

When the user tries to create or rename a folder on a network share (UNC Path/Mapped Drive or IP Address), Windows explorer stops responding for about 30-60 seconds. Eventually the folder does get created or renamed. Viewing this from the server shows the old folder name until about 30-60 seconds later. No error is displayed client end other than the not responding of Windows Explorer.

Resolution:

For me the only resolution for this issue was to stop and disable the ‘Windows Search’ service on the server. As soon as the service is disabled the folders can be created and renamed without delay. Restarting the service caused the problem to come back immediately.

As far as I am aware, Microsoft has yet to create a patch for this issue.

Property Owner is not available for Database ‘[SUSDB]’. This property may not exist for this object, or may not be retrievable due to insufficient access rights.

Property Owner is not available for Database ‘[SUSDB]’. This property may not exist for this object, or may not be retrievable due to insufficient access rights.

Problem:

Unable to access the WSUS Database (SUSDB) from Microsoft SQL Management Studio.

Error:

When selecting properies on the SUSDB you get the below error message

Property Owner is not available for Database ‘[TEST]’. This property may not exist for this object, or may not be retrievable due to insufficient access rights.

error-propertyowner

Resolution:

Run Microsoft SQL Server Management Studio as Administrator
Connect to the WSUS SQL instance by putting the following into the servername: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
Create a new query and type the following:

USE SUSDB
EXEC sp_changedbowner ‘DOMAN\Username’

Obviously change the DOMAIN\Username to you’re own… Execute the query. You should get a message below the query (Output window) saying that it completed successfully.

completedquery

Command Description:

USE SUSDB – This selects the Database SUSDB (The WSUS Database)
EXEC sp_changedbowner ‘DOMAN\Username’ – This changes the owner of the Database to your Admin account. Obviously replace the DOMAIN\USERNAME with your own details