I understand that this is an old post, but as there are basically no other results for this black screen issue I figured I'd share what we just learned about this recently. Skip to the end for solution.
In our environment, the black screen was ultimately being caused by a permissions error, but one that was not readily apparent. The traces were showing a number of access denied errors at the root of our profile store that looked something like this:
java.io.FileNotFoundException: \\contoso.com\DfsRoot\users$\%FILE.EXT% (Access is denied)
Now, this made no sense to me. Why is it trying to save files to the root of the profile share? I started looking through ProcMon results and found similar errors. I compared against the ProcMon results for a working user and think I've worked out what's happening.
Problematic User: CreateFile || \\contoso.com\DfsRoot\Users$ || NAME NOT FOUND || Disposition: Open
Working User: CreateFile || \\contoso.com\DfsRoot\Users$ || SUCCESS || Disposition: Open QueryDirectory || \\contoso.com\DfsRoot\Users$\username || SUCCESS ...
From this I gathered that the issue was being caused because communicator couldn't open the user share in order to check for the existence of the user's profile folder. I suspect that it was then failing to append the path for the user's roaming app data to the root file path above.
Granted Creator Owner full access to subfolder and files at the root of the profile share. Granted Everyone Read access to the root of the profile share (but not to subfolders).
There are cases/situations where we have to configure custome CPTONE to resolve FXO disconnect issue. Following are situations which can arise due to FXO disconnect issue:
Phone A calls Phone B, Phone B does not answer. Phone A then goes on-hook but Phon...
Cisco announced major enhancements today to Webex Contact Center. Learn more about the highlights including
better support for the needs of large contact centers worldwide
improvements in the agent and cust...
SymptomsI’m doing a factory reset on the mobile board and it’s giving me the same issues that I wasn’t able to also send over last time. It says that it can’t connect to the server because of a firewall (we don’t have one) and then sometimes it...