WSM Client has encountered an internal error - Wyse WSM - Wyse Software - Dell Community

WSM Client has encountered an internal error

WSM Client has encountered an internal error

This question is not answered

Exclamation WSM Client has encountered an internal error

Hye,

We have an Wyse R00L with Windows 7 SP1 and WSM Client 4.0.1
We always get an error msg after reboot "WSM has encountered an internal Error".
How Resolve this error ?

Thanks.

All Replies
  • Is this happening on the phsical reference device booting the local or OS or withing the streamed OS image?
    What is the exact Error message?
    Have a look at the client side log files in <installdir>Wyse\WSM\log

  • Yes this happen on the Reference Device, and it happen either on local boot or stream OS. I'll check the log file.

  • So, found below the log file on the Reference Device...

    2012-02-01T08:52:22Z (+01:00) [ESUSER] Profile: (machine_GUID) = ({dceb3eef-97eb-ff9e-680e-74114d352111})
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Profile: (client_OS) = (6.1 2 (Service Pack 1))
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Profile: (memory) = (phys: 1688616/1964084k, page: 3649888/3928168k, virt: 2044108/2044108k)
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Profile: (cpu) = (name: AMD Sempron(tm) Processor 210U, speed: 1500, vendor: AuthenticAMD, type: x86 Family 15 Model 111 Stepping 2)
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Profile: (hard_disk) = (system: avail=20666MB total=29996MB free=20666MB)
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Profile: (component_version) = (4.0.1.0)
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Info: *** ESUser.exe invokes ProcessCommand() 
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Info: Perform command startslow; parameter = (null)
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Info: Opened HKLM
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Profile: (machine_GUID) = ({dceb3eef-97eb-ff9e-680e-74114d352111})
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Profile: (client_OS) = (6.1 2 (Service Pack 1))
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Profile: (memory) = (phys: 1694276/1964084k, page: 3659244/3928168k, virt: 2040320/2040320k)
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Profile: (cpu) = (name: AMD Sempron(tm) Processor 210U, speed: 1500, vendor: AuthenticAMD, type: x86 Family 15 Model 111 Stepping 2)
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Profile: (hard_disk) = (system: avail=20666MB total=29996MB free=20666MB)
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Profile: (component_version) = (4.0.1.0)
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Info: *** Client starting up.***
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Info: ECE: Changing from s mode to s mode 
    2012-02-01T08:52:23Z (+01:00) [CLIENT] Info: ECE: Successfully changed from s mode to s mode 
    2012-02-01T08:52:24Z (+01:00) [CLIENT] Info: ECE: Changing from s mode to r mode 
    2012-02-01T08:52:24Z (+01:00) [CLIENT] Info: CUI: In CUIIsProvisionInProgress() ProvisionInProgress = 0 
    2012-02-01T08:52:24Z (+01:00) [CLIENT] Info: Provision is NOT in progress, Wsm client continues ... 
    2012-02-01T08:52:28Z (+01:00) [CLIENT] Info: CoInitialize failed with error: -2147417850. Ignoring.
    2012-02-01T08:52:28Z (+01:00) [CLIENT] Verbose: Default web browser for machine is: Microsoft Internet Explorer.
    2012-02-01T08:52:28Z (+01:00) [CLIENT] Info: CNI_Initialize called
    2012-02-01T08:52:28Z (+01:00) [CLIENT] Info: CheckAndUpdateStreamingServer: OS streaming server = 192.168.10.17
    2012-02-01T08:52:28Z (+01:00) [CLIENT] Info: RequiredAccountURLArray from SlimServerPort = http://192.168.10.17:8080/admin
    2012-02-01T08:52:29Z (+01:00) [CLIENT] Info: calling XPILoadBrowserProxySettings from XPIGetProxyListForUrl( ) 
    2012-02-01T08:52:29Z (+01:00) [CLIENT] Info: calling LoadBrowserProxySettings from XPILoadBrowserProxySettings( ) 
    2012-02-01T08:52:29Z (+01:00) [CLIENT] Info: calling LoadIESettings() from LoadBrowserProxySettings( ) 
    2012-02-01T08:52:29Z (+01:00) [CLIENT] Info: LoadIESettings() entered ... 
    2012-02-01T08:52:33Z (+01:00) [CLIENT] Info: LoadIESettings() exited with success ... 
    2012-02-01T08:52:33Z (+01:00) [CLIENT] Error: Error (3027) returned from synchronous request: admin/streaminghost.xml. Header: 'HTTP/1.1 404 Not Found Server: Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 Content-Length: 1024 Date: Wed, 01 Feb 2012 08:52:30 GMT '. (3027).
    2012-02-01T08:52:33Z (+01:00) [CLIENT] Error: Error (3027) returned from synchronous request: admin/streaminghost.xml. Header: 'HTTP/1.1 404 Not Found Server: Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 Content-Length: 1024 Date: Wed, 01 Feb 2012 08:52:30 GMT '. (3027).
    2012-02-01T08:52:33Z (+01:00) [CLIENT] Error: Error (3027) returned from synchronous request: admin/streaminghost.xml. Header: 'HTTP/1.1 404 Not Found Server: Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 Content-Length: 1024 Date: Wed, 01 Feb 2012 08:52:30 GMT '. (3027).
    2012-02-01T08:52:33Z (+01:00) [CLIENT] Error: Error (3027) returned from synchronous request: admin/streaminghost.xml. Header: 'HTTP/1.1 404 Not Found Server: Apache-Coyote/1.1 Content-Type: text/html;charset=utf-8 Content-Length: 1024 Date: Wed, 01 Feb 2012 08:52:30 GMT '. (3027).
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Info: GetAppStrLoginKey returned status: 2 value: -1
    2012-02-01T08:52:22Z (+01:00) [ESUSER] Info: ProcessCommand() calling XNetClientStart() 




    Regards,

    frederic

  • On the reference device booted from local storage
    1) run wsmclientpostconfig.exe and check your settings are correct.
    2) if your run OSMVdisk.exe, does it show the details of the WSM Server at the top of the screen.

    If you run into error into an error while working from the streamed image there are a couple of things to understand and check:
    - Cannot connect to this account: User account is not imported into WSM from AD. This happens if you are logged on as local user or with an AD account that is not present in WSM console
    - Client can not connect to the server (systray icon stays red). Server side services are down. General communication error. Image is not set to use AD integration. Client side proxy settings
    - Application cannot be run at this time: Forgot to assign the image to a Server Group

  • OK, At the moment the Device is not connected to the AD Domain where the WSM server's. 
    I'll join the device to the domain to check if the problem persist.

    Thanks.

    Regards,

    Frederic