VMware Horizon Community
fletch00
Enthusiast
Enthusiast

View Client disappears after login

Hi, I can connect via the web interface, but when establishing a connection via the 14Mb View client, I get the Blue Title Bar for the remote desktop for about 10 seconds with a black inside, then the client disappears without any error at all.

The web interface gives me a chance to authenticate against the VM, but the 14Mb client does not - maybe its passing bad credentials, then timing out?

Is there a way to turn on logging and see why this is happening on the client side?

thanks

VCP

VCP5 VSP5 VTSP5 vExpert http://vmadmin.info
Reply
0 Kudos
25 Replies
lnairn
VMware Employee
VMware Employee

Hi,

Logs can be found on C:\Documents and settings\All Users\Program Data\VMware\VDM\logs

Try uninstalling the web-client, and then installing the client (14MB), again.-

From Vmware:

Microsoft Remote Desktop Connection (RDC) 6.1 is recommended, RDC 5.0 and

RDC 6.0 are supported—you must have at least RDC 6.0 installed in order to have

multiple monitor support. RDC 6.1 can be downloaded from the following location:

http://microsoft.com/downloads/details.aspx?familyid=6E1EC93D‐BDBD‐4983‐92F7‐4

79E088570AD

The following 32‐bit operating systems can be downloaded and used by View Client

with Offline Desktop:

Windows XP Professional SP2

Windows XP Professional SP3

Reply
0 Kudos
Linjo
Leadership
Leadership

Hi Fletch.

What protocol are you trying to use?

If you are trying to connect with PCoIP you need to install the full windows client.

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

Best regards, Linjo Please follow me on twitter: @viewgeek If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
broets
Contributor
Contributor

I receive the same thing when using PCoIP after connecting to the VM using RDP. I rebooted the VM and seems to resolve the issue. It appears that the VM will not reconnect using the PCoIP protocol after an RDP connection has been establishe to a VM.

Hardware was upgraded on the VM to version 7

Any resolution to this would be helpful.

Reply
0 Kudos
billmaxpowers
Contributor
Contributor

I have also run into this same issue on a Windows XP Guest. The reboot is the only thing that fixes this so far.

Reply
0 Kudos
admin
Immortal
Immortal

This issue is listed in the release notes http://www.vmware.com/support/view40/doc/releasenotes_viewmanager40.html

This issue is specific to switching between RDP and PCoIP. It is specific to RDP not entirely and gracefully shutting down and releasing things. It essentially ends up blocking further connections and the only way to clear it is to reboot the machine.

If you can try and avoid switching back and forth.

WP

Reply
0 Kudos
fletch00
Enthusiast
Enthusiast

I rebooted the Windows 7 64 bit desktop - avoided any RDP

I still get the same behavior: PCoIP blue frame appears for about 10 seconds, then disappears without an error.

I try a RDP session with the same client and it connects (although prompts me for the correct auth) - maybe the PCoIP connection is passing my auth and giving up without asking me for the auth manually?

Where is the option to not pass auth automatically, but prompt for it every time?

thanks

VCP

VCP5 VSP5 VTSP5 vExpert http://vmadmin.info
Reply
0 Kudos
admin
Immortal
Immortal

Win7 64 bit is likely the issue. Win 7 is tehnology preview with View 4 and 64bit is not part of that at the moment.

WP

Reply
0 Kudos
john_gallucci
Enthusiast
Enthusiast

I can confirm, I am only having this problem with Windows 7 x64 guests using PCoIP. It works fine with RDP.

It's good to know that x64 is not officially supported because there are major problems installing the video drivers for VMware View. First off, the agent cannot update the SVGA graphics automatically.

These instructions appear:

These instructions ask you to install a 32-bit graphics driver onto a 64-bit machine (say what?!)

Anyways it fails with this message:

Out of curiosity, what is the exact Driver and Version installed on your Windows 7 x64 guest? I went ahead and installed the wddm_video drivers for 64-bit systems (found in C:\Program Files\Common Files\VMware\drivers\wddm_video), but this is where I failed with PCoIP

It looks like I am going to have to create a 32-bit template of Windows 7 for my guests.

Reply
0 Kudos
admin
Immortal
Immortal

I actually do not have a Win 7 x64 guests since its not support yet and I know there is still work that needs to be done before it will work.

WP

Reply
0 Kudos
fletch00
Enthusiast
Enthusiast

I re-did everything with windows 7 32 bit for the VM, no RDP, reboot etc - and I get the same behavior - the view client disappears without any errors after about 10 seconds!

VCP

VCP5 VSP5 VTSP5 vExpert http://vmadmin.info
Reply
0 Kudos
RobBuxton
Enthusiast
Enthusiast

Hi All,

I'm seeing a similar issue, but only when I come in via the Security Server. Connecting via the V4 Client using the internal connection broker works okay.

The desktop is just 32bit XP with the v4 agent installed.

I am seeing a Java Tunnel IO Problem in the debug log file on the security server, but I'm not picking up any obvious denies in the firewall.

I see the error in the info.log file on the internal server: EXITING: java.io.IOException: channel reports end-of-stream

Oh yes, tried the reboot of the desktop as well, but that made no difference.

cheers,

Rob.

Reply
0 Kudos
RobBuxton
Enthusiast
Enthusiast

Ah, my mistake on that one. PCoIP is not supported using the external server yet.

Reply
0 Kudos
YoMarK
Contributor
Contributor

I'm having the same issue(Windows 7 32 bit guest, and windows 7 32bit VM). Connecting using PCoIP results in a black screen for a few seconds, and then the Vmware View clients closes itself.

I can workaround this problem by just clicking in the black screen and resize the client window(start in small windowed mode) while the screen is black. After this: windows 7 screen appears and everything works fine, however, when changing to fullscreen, the screen turns black again.

Reply
0 Kudos
fletch00
Enthusiast
Enthusiast

I just opened a P2 case - PCoIP is just not functioning - will update how it goes

thanks

VCP

VCP5 VSP5 VTSP5 vExpert http://vmadmin.info
Reply
0 Kudos
easytranxition
Contributor
Contributor

Same result here with PCoIP... The View client window appears with a blank screen for a few seconds and then disappears. Using Windows 7 x64 on the client side and Windows 7 x86 Ultimate virtual desktop. If I watch the console of the VM at the same time, I see a logon occurr on the console but the client side closes after a brief amount of time. RDP connection works fine. I tried rebooting a few times. Clicking in the window and resizing as YoMarK indicated does not seem to work for me.

I also noticed that after upgrading the hardware to VM version 7 nothing is visible in the console window - it is just a blank screen whether or not a remote session exists.

I get the same results if I create the VMs manually or use composer to deploy the VMs. Seriously, it sounds like others have Win7 working. What's going on in these cases?

Reply
0 Kudos
grossag
VMware Employee
VMware Employee

If single sign-on fails, then there is the chance of the user being disconnected because of session management issues. That is why connecting to Windows x64 is dodgy; we don't have single sign-on components for 64-bit agents because we don't support them. The easiest way to verify is like you said, watching in vSphere client. Given that single sign-on is working but the connection is failing, I would suggest checking other things like firewall and routing settings. It may also be helpful to post your PCoIP logs or PM them directly to me; the log files are in %TEMP% on both the client and agent and I think they are of the form "pcoip_server.txt", "pcoip_agent.txt", and "pcoip_client.txt".

Reply
0 Kudos
fletch00
Enthusiast
Enthusiast

I did a repair install of Tools, reboot, repair install of Agent, reboot (this worked for someone else) - but I still have the issue - error logs are below:

12/09/2009, 14:51:34> LVL:0 RC: 0 IMG_FRONTEND :configure_displays: 1 display(s) initially reported!

12/09/2009, 14:51:34> LVL:0 RC: 0 IMG_FRONTEND :configure_display[0]--* id: 2 mon_id: -1 pos: (0,0) w: 1024 h: 768

12/09/2009, 14:51:34> LVL:0 RC: 0 IMG_FRONTEND :configure_display[0]--bpp: 32 --pitch: 4096 --map size: 1552 --fb size: 3145728

12/09/2009, 14:51:34> LVL:0 RC: 0 IMG_FRONTEND :configure_displays: frontend motion is enabled

12/09/2009, 14:51:34> LVL:0 RC: 0 IMG_FRONTEND :flip_frame_buffer: error result - level 1=4001, level 2=0

12/09/2009, 14:51:34> LVL:0 RC: 0 MGMT_IMG :cSW_HOST_IPC::enable_frontend failed. Retry...

12/09/2009, 14:51:35> LVL:0 RC: 0 IMG_FRONTEND :Calling open display

12/09/2009, 14:51:35> LVL:0 RC: 0 IMG_FRONTEND :configure_displays: 1 display(s) initially reported!

12/09/2009, 14:51:35> LVL:0 RC: 0 IMG_FRONTEND :configure_display[0]--* id: 2 mon_id: -1 pos: (0,0) w: 1024 h: 768

12/09/2009, 14:51:35> LVL:0 RC: 0 IMG_FRONTEND :configure_display[0]--bpp: 32 --pitch: 4096 --map size: 1552 --fb size: 3145728

12/09/2009, 14:51:35> LVL:0 RC: 0 IMG_FRONTEND :configure_displays: frontend motion is enabled

12/09/2009, 14:51:35> LVL:0 RC: 0 IMG_FRONTEND :flip_frame_buffer: error result - level 1=4001, level 2=0

12/09/2009, 14:51:35> LVL:0 RC: 0 MGMT_IMG :cSW_HOST_IPC::enable_frontend failed. Retry failed 5 time.

12/09/2009, 14:51:35> LVL:2 RC: 0 MGMT_IMG :Resetting codec (end_to_end=0)

12/09/2009, 14:51:35> LVL:0 RC: 0 MGMT_IMG :CODEC: State change from CODEC_CFG_EXCHANGE to CODEC_DISABLED

12/09/2009, 14:51:35> LVL:0 RC:-500 MGMT_IMG :ACTIVE: Fatal error happend. Notifying session manager.

12/09/2009, 14:51:35> LVL:2 RC: 0 MGMT_SSIG :Request to reset session (PRI: 0)

12/09/2009, 14:51:35> LVL:2 RC: 0 MGMT_SSIG :Session closed locally (192.168.45.128, 00-0F-01-01-01-00, PRI: 0)

12/09/2009, 14:51:35> LVL:1 RC:-500 VGMAC :tera_sock_recv() failed - Interrupted system call (10004)!

12/09/2009, 14:51:35> LVL:2 RC: 0 VGMAC :PCoIP UDP RX thread exiting

12/09/2009, 14:51:35> LVL:1 RC: 0 MGMT_DDC :mgmt_ddc_fcc_callback: queuing TERA_MGMT_FCC_EVENT_RESET

12/09/2009, 14:51:35> LVL:2 RC: 0 MGMT_VCHAN :>>> app_reset: Session has been dropped. Forcing all channels to close!

12/09/2009, 14:51:35> LVL:2 RC:-503 MGMT_VCHAN :>>> Failed to close chan 0 because channel is already closed!

12/09/2009, 14:51:35> LVL:1 RC:-500 VGMAC :tera_sock_send() failed - Socket operation on non-socket (10038)!

12/09/2009, 14:51:35> LVL:1 RC:-500 MGMT_PCOIP_DATA :Tx thread error: failed to send packet to VGMAC

12/09/2009, 14:51:35> LVL:1 RC:-500 MGMT_PCOIP_DATA :Tx thread error: failed to encode and queue media packet!

12/09/2009, 14:51:35> LVL:1 RC:-500 MGMT_PCOIP_DATA :Tx thread: error while servicing media channel

12/09/2009, 14:51:35> LVL:2 RC: 0 MGMT_PCOIP_DATA :Reset control block

12/09/2009, 14:51:35> LVL:1 RC:-503 MGMT_PCOIP_DATA :Tx thread error: failed to free small descriptor in control block reset i=0 tx_cblk=144e980

12/09/2009, 14:51:35> LVL:1 RC:-503 MGMT_PCOIP_DATA :Tx thread error: failed to free small descriptor in control block reset i=1 tx_cblk=144e980

12/09/2009, 14:51:40> LVL:1 RC:-500 COMMON :poll_sockets failed to generate 1 callbacks!

12/09/2009, 14:51:40> LVL:1 RC: 0 COMMON :TERA_PCOIP: SESSION_EVENT=TERA_MGMT_SYS_SESS_EVENT_RESETVCP

VCP5 VSP5 VTSP5 vExpert http://vmadmin.info
Reply
0 Kudos
fletch00
Enthusiast
Enthusiast

I just got around to trying Windows XP - and I'm getting the same black screen disappearing after 10-20 seconds - errors from the XP agent below - thanks for any tips!:

12/16/2009, 10:39:11> LVL:0 RC: 0 MGMT_IMG :set_display_topology: display[0]: (0, 0) 800 x 600

12/16/2009, 10:39:11> LVL:2 RC:-500 MGMT_IMG :Error in VMwareResolutionSet_SetDisplayTopology: 1 displays requested, trys remaining 0.

12/16/2009, 10:39:11> LVL:2 RC: 0 RTOS :tera_query_performance_frequency(): frequency is 2826.258021MHz

12/16/2009, 10:39:12> LVL:0 RC:-500 MGMT_IMG :Error in set_display_topology: 1 displays requested.

12/16/2009, 10:39:12> LVL:0 RC:-500 IMG_FRONTEND :open_displays(): No valid displays reported from svga devtap.

12/16/2009, 10:39:12> LVL:0 RC: 0 MGMT_IMG :cSW_HOST_IPC::enable_frontend failed. Retry...

12/16/2009, 10:39:13> LVL:0 RC: 0 IMG_FRONTEND :Calling open display

12/16/2009, 10:39:13> LVL:0 RC: 0 IMG_FRONTEND :configure_displays: 0 display(s) initially reported!

12/16/2009, 10:39:13> LVL:0 RC: 0 MGMT_IMG :set_display_topology: display[0]: (0, 0) 1280 x 1024

12/16/2009, 10:39:13> LVL:2 RC:-500 MGMT_IMG :Error in VMwareResolutionSet_SetDisplayTopology: 1 displays requested, trys remaining 0.

12/16/2009, 10:39:14> LVL:0 RC:-500 MGMT_IMG :Error in set_display_topology: 1 displays requested.

12/16/2009, 10:39:14> LVL:0 RC: 0 MGMT_IMG :set_display_topology: display[0]: (0, 0) 1024 x 768

12/16/2009, 10:39:14> LVL:2 RC:-500 MGMT_IMG :Error in VMwareResolutionSet_SetDisplayTopology: 1 displays requested, trys remaining 0.

12/16/2009, 10:39:15> LVL:0 RC:-500 MGMT_IMG :Error in set_display_topology: 1 displays requested.

12/16/2009, 10:39:15> LVL:0 RC: 0 MGMT_IMG :set_display_topology: display[0]: (0, 0) 800 x 600

12/16/2009, 10:39:15> LVL:2 RC:-500 MGMT_IMG :Error in VMwareResolutionSet_SetDisplayTopology: 1 displays requested, trys remaining 0.

12/16/2009, 10:39:16> LVL:0 RC:-500 MGMT_IMG :Error in set_display_topology: 1 displays requested.

12/16/2009, 10:39:16> LVL:0 RC:-500 IMG_FRONTEND :open_displays(): No valid displays reported from svga devtap.

12/16/2009, 10:39:16> LVL:0 RC: 0 MGMT_IMG :cSW_HOST_IPC::enable_frontend failed. Retry failed 5 time.

12/16/2009, 10:39:16> LVL:2 RC: 0 MGMT_IMG :Resetting codec (end_to_end=0)

12/16/2009, 10:39:16> LVL:0 RC: 0 MGMT_IMG :CODEC: State change from CODEC_CFG_EXCHANGE to CODEC_DISABLED

12/16/2009, 10:39:16> LVL:0 RC:-500 MGMT_IMG :ACTIVE: Fatal error happend. Notifying session manager.

12/16/2009, 10:39:16> LVL:2 RC: 0 MGMT_SSIG :Request to reset session (PRI: 0)

12/16/2009, 10:39:16> LVL:2 RC: 0 MGMT_SSIG :Session closed locally (192.168.45.128, 00-0F-01-01-01-00, PRI: 0)

12/16/2009, 10:39:16> LVL:2 RC: 0 MGMT_PCOIP_DATA :Reset control block

12/16/2009, 10:39:16> LVL:1 RC:-500 VGMAC :tera_sock_recv() failed - Interrupted system call (10004)!

12/16/2009, 10:39:16> LVL:2 RC: 0 VGMAC :PCoIP UDP RX thread exiting

12/16/2009, 10:39:16> LVL:2 RC: 0 MGMT_VCHAN :>>> app_reset: Session has been dropped. Forcing all channels to close!

12/16/2009, 10:39:16> LVL:2 RC:-503 MGMT_VCHAN :>>> Failed to close chan 0 because channel is already closed!

12/16/2009, 10:39:16> LVL:1 RC: 0 MGMT_DDC :mgmt_ddc_fcc_callback: queuing TERA_MGMT_FCC_EVENT_RESET

12/16/2009, 10:39:21> LVL:1 RC:-500 COMMON :poll_sockets failed to generate 1 callbacks!

12/16/2009, 10:39:21> LVL:1 RC: 0 COMMON :TERA_PCOIP: SESSION_EVENT=TERA_MGMT_SYS_SESS_EVENT_RESET

12/16/2009, 10:39:21> LVL:0 RC: 0 SERVER :server main: notify_session_status called 10.

12/16/2009, 10:39:21> LVL:0 RC: 0 SERVER :server main: TERA_MGMT_SYS_SESS_EVENT_RESET.

12/16/2009, 10:39:21> LVL:1 RC: 0 MGMT_SYS :SESSION_ACTIVE: UNRECOGNIZED EVENT: 0x100 (MGMT_SESS)!

12/16/2009, 10:39:21> LVL:0 RC: 0 SERVER :server main: exiting

12/16/2009, 10:39:21> LVL:0 RC: 0 SERVER :server main: tearing down the blob and waiting

12/16/2009, 10:39:21> LVL:0 RC: 0 MGMT_SESS :Tearing down the session

12/16/2009, 10:39:21> LVL:2 RC: 0 MGMT_VCHAN :>>> app_reset: Session has been dropped. Forcing all channels to close!

12/16/2009, 10:39:21> LVL:2 RC:-503 MGMT_VCHAN :>>> Failed to close channel because session is not connected!

12/16/2009, 10:39:21> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Closing plugin 'VMware_Server'.

12/16/2009, 10:39:22> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Plugin 'VMware_Server' is closed.

12/16/2009, 10:39:22> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Closing plugin 'mksvchanserver'.

12/16/2009, 10:39:22> LVL:2 RC:-503 MGMT_VCHAN :>>> Failed to close channel because session is not connected!

12/16/2009, 10:39:22> LVL:2 RC: 0 MGMT_VCHAN :>>> Connect callback 0 has been un-registered (mksvchan).

12/16/2009, 10:39:22> LVL:2 RC: 0 MGMT_VCHAN :VChanPluginExit: Plugin 'mksvchanserver' is closed.

12/16/2009, 10:39:22> LVL:1 RC: 1 MGMT_VCHAN :=> Successfully exited all the VChan plugins

VCP

VCP5 VSP5 VTSP5 vExpert http://vmadmin.info
Reply
0 Kudos
JasonCheung
Contributor
Contributor

You can try this setting

Automatic logoff after disconnect -- Never

Reply
0 Kudos