Black screen problem

Hi there!

Last week I faced a problem with black screen on server. After I logged on to win 2012R2 server through RDP I got the black screen and that is all I could do. Let’s talk about server configuration:

  • Windows 2012R2 with all patches installed, maybe missing some for last month
  • Hosted on vmware ESX 5.1
  • Server role is file server
  • 8Gb RAM, 1 vCPU, some SAN disks

You know, it happens quite often when you got black screen, normally you need just to force logoff or restart the server.

Logoff was not helpful in my case, so I asked for a service window to restart the server. As you might guess, restart was not helpful at all.

The first article in google for “windows 2012R2 black screen” show us KB2897632 . It was not 100% my case, as I was able to launch CTRL+ALT+DEL. However, I decided to try. I downloaded msu file of KB2887595 and using tried to install it from remote server.

Psexec \\fileserver1 cmd /c “wusa C:\KB2887595v2.msu /quiet /forcerestart”

I got access denied error so had to add –s key to psexec command so it execute as administrator on remote server.

Psexec \\fileserver1 –s cmd /c “wusa C:\KB2887595v2.msu /quiet /forcerestart”

This time I got message that this update was already installed. As the file I downloaded was v2, that usually means that this update should replace previous I uninstalled KB2887595 and installed it again manually.

Psexec \\fileserver1 –s cmd /c “wusa /uninstall /KB 2887595”

Problem was still there. I tried to connect to server using vmware console with same “black screen” result. So after all I decided to blame vmware and reinstall vmware tools. I’m not vmware expert, so I decided to compare different VMs with problematic one. From what I was able to find is that my VM has only 4Mb of video card memory, while other have 8Mb at least. So maybe it has not enough performance to handle display? I added 28Mb more, same result.

There was nothing in windows logs about my problem. From device manager I could see that Monitor was listed with warning along with VMware VMCI Bus Device. I tried to completely uninstall vmware tools and install the latest version. Still no luck.

I started to search on google again. There were no results from MS forums at all, just some sites I do not trust so much. One small comment somewhere stated that it was about missing domain users in local Users group.

I checked that and…bingo my domain profile was created on local computer and I was able to log in fine!


Windows 2012 r2 logon problem

Hi, all.

We’ve faced a problem logging on to Wndows 2012 R2 servers via RDP recently.


The User Profile Service service failed the sign-in.

User profile cannot be loaded.


Fix: Go to \\problematic_server\C$ from another server

Open Security tab in properties of “\Users\Default”  -> Advanced -> Change Permissions -> tick checkbox “Replace all child object permissions with inheritable permissions from this object” and apply changes.

You should be able to log in now.

SSRS Problem

One day we got a problem with SQL Server Reporting Services. When you try to navigate to http://servername/Reports you got internal error 500

2 SQL instances with SQL2008RTM on win 2003 gave same error

appdomainmanager!DefaultDomain!af4!06/17/2015-15:01:33:: e ERROR: AppDomain ReportManager_SIPS_0 failed to start. Error: (0): error CS0016: Could not write to output file ‘c:\Program Files\Microsoft SQL Server\MSRS10_50.TEMP\Reporting Services\rstempfiles\reports_temp\699d5a9d\9f58366e\App_global.asax.mhl7l18r.dll’ — ‘The directory name is invalid. ‘

Both SQL Reporting services instances were running under same domain account domain\SVC-ARB-TEMP-RS

First of all, we tried to give all possible and impossible permissions to c:\Program Files\Microsoft SQL Server\MSRS10_50.TEMP\Reporting Services\rstempfiles\ for accounts:

domain\SVC-ARB-TEMP-RS – Reporting services service account

domain\SVC-ARB-TEMP-RS-EXEC – Reporting services execution account

Network Service


ASP.Net Machine account




I know it sounds weird for some of accounts, but we tried all variants we could find on google. We did restart after any modification done, however it was still the same.

For test purpose we removed content of c:\Program Files\Microsoft SQL Server\MSRS10_50.TEMP\Reporting Services\rstempfiles\reports_temp\ and after SQL Server Reporting services were restarted content appeared again, exactly the same content. So the problem is not with permissions actually!

I tried to filter out all actions that ReportingServicesService.exe(SSRS server executable) perform after start up using procmon. However I haven’t seen there any access to c:\Program Files\Microsoft SQL Server\MSRS10_50.TEMP\Reporting Services\rstempfiles\reports_temp\ . Might be cause this was done using SYSTEM account and it was too much to filter out.

As it was RTM edition we decided to perform upgrade to currently newest available SP3. During update we got error that the certain SQL Server cached updates are missing from server. Most likely, they were removed by other admins to release some space on disk C:

There is a wonderful tool from MS to fix such kind of problems FindSQLInstalls.vbs

Pls read it carefully on how to use it. It found all missing installation files; mostly they were from SQL 2008R2 SP1.

So we downloaded SQL 2008R2 SP1 x86 and extracted it using /x key to D:\SP1 folder

The output of FindSQLInstalls.vbs script provides you with advice on how to fix missing files, like:

Copy “G:\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi”


So we just executed:

Copy “D:\SP1\x64\setup\sql_engine_core_inst_msi\sql_engine_core_inst.msi”


And file was copied to cache, however script did not want to recognize it and after next execution written that it is missing same file. We tried to copy again and it asked to replace file in target location. Even after that script did not recognize that the file was in place

So we created folder with the same path as script has:


And put there files from D:\SP1, after next execution script gave us no errors.
We successfully patched both instances with SQL 2008R2 Sp3 and restarted server as it was prompted.

After server restarted both instances were running fine, error was gone.
As we performed all changes with 1 of instances I decided to check which permissions will Rstempfiles will get now on the secondary instance. Among default accounts, like system, it was:

Network Service – Full permissions
SQLServerReportServerUser$computername$Instancename (local group) – Read/Write permissions
domain\SVC-ARB-TEMP-RS (SSRS service account) – Full permissions

Despite I’m pretty sure those permissions were set before upgrade it did not work. So for reporting services this problem is not correct.

Lessons learned:
! Keep your software with recent service pack level. Even if you will open case to MS they will ask you to patch everything first.

This is the start point


Today is our opening day and starting from here we would publish here some interesting findings, workarounds, problems and so on. We will try to fill it with unique content, something completely different from blogs where people will tell you how to create folder on windowXP.

We are mostly focused on Microsoft technologies starting from all different versions of Windows Server operating systems to MS Exchange, SQL and many many other windows related software.

So this information will be mostly for technical people who are daily facing the same problems as we do. Hope this information will be helpful for others!