#1579 Black screen - Error code 1008

[Piotr Hofi]

Hello,
fresh install of 2.8.63 on Windows 10. After connecting from another station I only get a black screen. Here is tvnserver.log:

[10080/ 9924] 2022-03-04 09:33:52 ! Set socket idle timeout, 0 ms
[10080/ 9924] 2022-03-04 09:33:52 ! Client #6 connected
[10080/ 3924] 2022-03-04 09:33:52 ! write() function stopped because transport has not been initialized yet.
[ 6916/ 3512] 2022-03-04 09:33:52 ! WTSQueryUserToken error: (system error: Error code 1008)
[ 6916/ 3512] 2022-03-04 09:34:08 ! AnonymousPipe::read() failed (m_hRead = 0000000000000008)
[ 6916/ 3512] 2022-03-04 09:34:08 ! The DesktopServerApplication dispatcher has failed with error: The Pipe's write function failed after ReadFile calling(pipe handle is 0000000000000008, total read 3148369, try to read 1) (<<cannot get="" text="" error="" describing="">> (109))
[ 6916/ 3512] 2022-03-04 09:34:08 ! An error has been occurred in the desktop server. Application will be closed.
[ 6916/ 5452] 2022-03-04 09:34:08 ! WTSQueryUserToken error: (system error: Error code 1008)
[10080/ 9996] 2022-03-04 09:34:08 ! AnonymousPipe::read() failed (m_hRead = FFFFFFFFFFFFFFFF)
[10080/ 9996] 2022-03-04 09:34:08 ! The Pipe's write function failed after ReadFile calling(pipe handle is 0000000000000624, total read 1, try to read 1) (<<cannot get="" text="" error="" describing="">> (109))
[10080/ 9996] 2022-03-04 09:34:08 ! The DesktopServerApplication dispatcher has failed with error: The ReconnectingChannel::read() function failed.
[10080/ 9996] 2022-03-04 09:34:08 ! onAbnormalDesktopTerminate() called
[10080/ 9996] 2022-03-04 09:34:08 ! Forced closing of pipe conections</cannot></cannot>

I've read about black screen problems caused by no monitors attached or power settings. Well - power settings are changed to those "recommended" and other similar servers work normally despite having no monitors attached... I only have problems with this one.

[Josh Sharpe]

I'm seeing a very similar issue and wanted to check if there was any update on this or a potential work around. My details and log.

TightVNC is installed on a remote Windows Virtual Machine.

• Processor: Intel(R) Xeon(R) CPU @ 2.20GHz 2.20 GHz
• OS: Windows Server 2022 Datacenter
• TightVNC version: 2.8.63 (Build Aug 9, 2021)
• Standard Installation

Behavior:
Running as a server seems to work flawlessly. However, running as a service does not. I get a black screen and the error message in logs section below. Icon turns inverted, indicating connection is successful. Selecting "Connect to RDP session" does get the service option to work when connected to via RDP in parallel. I've tried numerous things at this point, including increasing permissions and changing any possible configuration option.

Logs (Some differences in OP's but similar enough that seemed connected):

[ 6800/ 5512] 2023-02-15 19:42:02 ! Set socket idle timeout, 0 ms
[ 6800/ 5512] 2023-02-15 19:42:02 ! Client #0 connected
[ 6800/ 6804] 2023-02-15 19:42:02 ! write() function stopped because transport has not been initialized yet.
[ 4968/ 7116] 2023-02-15 19:42:10 ! AnonymousPipe::read() failed (m_hRead = 0000000000000008)
[ 4968/ 7116] 2023-02-15 19:42:10 ! The DesktopServerApplication dispatcher has failed with error: The Pipe's write function failed after ReadFile calling(pipe handle is 0000000000000008, total read 1229077, try to read 1) (The pipe has been ended. (109))
[ 4968/ 7116] 2023-02-15 19:42:10 ! An error has been occurred in the desktop server. Application will be closed.
[ 6800/ 7872] 2023-02-15 19:42:10 ! AnonymousPipe::read() failed (m_hRead = FFFFFFFFFFFFFFFF)
[ 6800/ 7872] 2023-02-15 19:42:10 ! The Pipe's write function failed after ReadFile calling(pipe handle is 000000000000040C, total read 1, try to read 1) (The pipe has been ended. (109))
[ 6800/ 7872] 2023-02-15 19:42:10 ! The DesktopServerApplication dispatcher has failed with error: The ReconnectingChannel::read() function failed.
[ 6800/ 7872] 2023-02-15 19:42:10 ! onAbnormalDesktopTerminate() called
[ 6800/ 7872] 2023-02-15 19:42:10 ! Forced closing of pipe conections
[ 6800/ 5512] 2023-02-15 19:42:11 ! Set socket idle timeout, 0 ms
[ 6800/ 5512] 2023-02-15 19:42:11 ! Client #1 connected
[ 6800/ 4484] 2023-02-15 19:42:12 ! write() function stopped because transport has not been initialized yet.