[Bug 48163] New: Launching VMWare vSphere 5.5 fails with error.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48163

Bug ID: 48163
           Summary: Launching VMWare vSphere 5.5 fails with error.
           Product: Wine
           Version: 4.20
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 65792
  --> https://bugs.winehq.org/attachment.cgi?id=65792
WINEDEBUG=warn+all,+loaddll

After installing dependencies (dotnet35sp1 msxml3 vcrun2005 vcrun2008
vcrun2010) that were necessary to get previous wine versions to work with
VMWare vSphere Client 5.5
(http://vsphereclient.vmware.com/vsphereclient/4/0/3/2/3/6/5/VMware-viclient-...),
the launcher opens but fails to load the client. It returns the following error
after entering credentials:

Object reference not set to an instance of an object

Included a windebug output.

antiX 19 Core (based on Debian Testing).

[Bug 48163] Launching VMWare vSphere 5.5 fails with error.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48163

Jérôme  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Jérôme  ---
Created attachment 66349
  --> https://bugs.winehq.org/attachment.cgi?id=66349
Screenshots

I have the same problem...

[Bug 48163] Launching VMWare vSphere 5.5 fails with error.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48163

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |http://vsphereclient.vmware
                   |                            |.com/vsphereclient/4/0/3/2/
                   |                            |3/6/5/VMware-viclient-all-5
                   |                            |.5.0-4032365.exe
     Ever confirmed|0                           |1
           Keywords|                            |download
                 CC|                            |[e-mail]
             Status|UNCONFIRMED                 |NEEDINFO

--- Comment #2 from Louis Lenders  ---
(In reply to Jérôme from comment #1)
> Created attachment 66349 [details]
> Screenshots
>
> I have the same problem...

Hi Jerome,

OP said he installed dotnet35sp1, but yet the attached log shows fixme`s from
mscoree: 
0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element
L"configSections" in state 2

Could you (or OP) check that mscoree.dll is set to native in winecfg`s library
tab (and otherwise set it to native) and then report back please.

I tried the app, and got to the login screen without any errors

[Bug 48163] Launching VMWare vSphere 5.5 fails with error.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48163

Yaron Shahrabani  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Yaron Shahrabani  ---
Created attachment 66423
  --> https://bugs.winehq.org/attachment.cgi?id=66423
Screenshot of 6.0 running with win32 environment

I managed to get to the login screen, I can type server address, username and
password but when I hit the Login button this message appears.

Now there's a known bug on the VMware side stating that this bug is caused by a
misinterpretation of some character inside the config (or config filename) and
it crashes.

This is also mentioned in VMware's knowledge base:
https://kb.vmware.com/s/article/1038260

I tried searching for the locations and mentioned filenames but couldn't find
any.

Furthermore, there's an option to set the server and username automatically by
editing VpxClient.exe.config and setting these values, this caused the error
message to appear sooner than before, now it happens even before I'm hitting
Login right when the application starts.

I'm guessing that if all the configuration files where in place or I had access
to the logs (I tried enabling them but so far I couldn't find them) I'll
probably be able to show some more insights about this issue.

[Bug 48163] Launching VMWare vSphere 5.5 fails with error.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48163

--- Comment #4 from themainliner  ---
(In reply to Louis Lenders from comment #2)
> (In reply to Jérôme from comment #1)
> > Created attachment 66349 [details]
> > Screenshots
> >
> > I have the same problem...
>
> Hi Jerome,
>
> OP said he installed dotnet35sp1, but yet the attached log shows fixme`s
> from mscoree: 
> 0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element
> L"configSections" in state 2
>
> Could you (or OP) check that mscoree.dll is set to native in winecfg`s
> library tab (and otherwise set it to native) and then report back please.
>
> I tried the app, and got to the login screen without any errors

I had to add mscoree.dll which I then set to Native. I made no difference I'm
afraid.

Thanks for your input though.

[Bug 48163] Launching VMWare vSphere 5.5 fails with error.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48163

--- Comment #5 from Yaron Shahrabani  ---
(In reply to themainliner from comment #4)
> (In reply to Louis Lenders from comment #2)
> > (In reply to Jérôme from comment #1)
> > > Created attachment 66349 [details]
> > > Screenshots
> > >
> > > I have the same problem...
> >
> > Hi Jerome,
> >
> > OP said he installed dotnet35sp1, but yet the attached log shows fixme`s
> > from mscoree: 
> > 0009:fixme:mscoree:ConfigFileHandler_startElement Unknown element
> > L"configSections" in state 2
> >
> > Could you (or OP) check that mscoree.dll is set to native in winecfg`s
> > library tab (and otherwise set it to native) and then report back please.
> >
> > I tried the app, and got to the login screen without any errors
>
> I had to add mscoree.dll which I then set to Native. I made no difference
> I'm afraid.
>
> Thanks for your input though.

My comment contains a link to VMware's KB, it's not wine specific:
https://kb.vmware.com/s/article/1038260

[Bug 48163] Launching VMWare vSphere 5.5 fails with error.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48163

--- Comment #6 from Jérôme  ---
Hello, I abandoned the idea of ​​using vsphere with wine. I installed
virtualbox. Thanks for your help.

[Bug 48163] Launching VMWare vSphere 5.5 fails with error.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48163

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                URL|http://vsphereclient.vmware |https://web.archive.org/web
                   |.com/vsphereclient/4/0/3/2/ |/20140411010657/http://vsph
                   |3/6/5/VMware-viclient-all-5 |ereclient.vmware.com/vspher
                   |.5.0-4032365.exe            |eclient/1/2/8/1/6/5/0/VMwar
                   |                            |e-viclient-all-5.5.0-128165
                   |                            |0.exe