Not really a question this, but I thought I'd share. I just installed the beta of Internet Explorer 9. I love it, it's really fast. Unfortunately it breaks the View 4.5 Client. It hangs while trying to connect. I installed it on Windows 7 x64. Removing IE9 fixed my problems immediately. So watch out for this, and warn your users.
I hope either VMware or Microsoft fixes this.
Thanks for the heads up. I haven't installed IE9 yet but I know some of our users probably will try to get it. At least now I know where to start if they are having issues.
If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points
Twitter: http://twitter.com/mittim12
Just a FYI but I just installed IE9 and ran into some issues as well. When tring to connect to the View server from the client I received the error "The View Connection Server connection failed. (null)". This issue went away after removal of IE9.
If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points
Twitter: http://twitter.com/mittim12
That doesn't sound good. I will take a look at this and see if I can figure out what's going on here. Thanks for reporting this.
It appears this issue also happens with the Windows 7 SP1 beta. I looked into this today and it is due to a change in wininet.dll (the IE9 beta places a new version of wininet.dll). There is no workaround for this issue. I reported the issue to Microsoft and will let you know when I have a resolution.
Is there no way you can use the new wininet.dll?
if it uses new function names or classes ask MS what changed so you can make VM View compatible.
Or am i talking crap now?
Function names are the same, but the issue is that we try and unload and reload all of our copies of wininet in memory when connecting to a server, so we can clear any cached server data like whether to use a certificate (wininet does a poor job of this itself). This version of wininet reports success upon that operation but actually fails to unload itself so our code keeps trying. Then, the next time we call into a wininet function, it crashes. So there's no clear workaround, as we still need to be unloading it or our server connection code will have tons of regressions. And any workarounds in terms of detecting the same module handle and not freeing it anymore will similarly regress the code.
The only thing I haven't tried is making a backup of wininet.dll before IE9 is installed and then overwriting the newly installed wininet with the old one. But I'm assuming that isn't something that Microsoft would support.
And if you place the old wininet.dll in vmware view folder and rename it so you have infact 2 wininet.dll files?
I am not sure if it works but you could atleast try.
I just installed the beta of Internet Explorer 9
This is par for the course...
You install beta of ANY (blah blah) product, it will NORMALLY break (blah blah). That's the nature of BETA.
BETA, in case you didn't know, means it hasn't been FULLY tested yet. so why would you consider it ready? that's why you NEVER test production with BETA stuff.... you can break something.
yup indeed but the W7 SP1 is nearly at its rtm version so you would expect it to work.
Yes, I know what a BETA is. I wasn't complaining about it, I just reported it. I'm not using IE9 on production at all. But reporting issues,that's what people do on forums like this one. It's meant to help others. If you're informed about issues like this, you can warn your users. I also think that VMware would like to know. So I'm not sure what you're so worked up about.
I had the same problem and solved it by making a thinapped View 4.5 client. Included wininet.dll in the package (placed in system32). Works like a charm!
FYI we have published KB article 1028650 about this at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102865...
I have the IE 9 Beta installed on my Win7 machines and running the View Client in compatibility mode for Windows Vista (Service Pack 2) has worked for me. Not sure if this will solve the issue if you are running the SP1 beta or not, but it's worth a shot.
Could you please be more specific about exactly where in the capture folder you put that file. I am trying to make a view client thinapp also.
Awesome the compatibility mode fix by jrthin did the trick!!
Same problem with win 7 machines after today's updates. The compatibility trick works, but please release an update of the View Client
See http://communities.vmware.com/thread/302164 for more info. An update was released yesterday and that thread discusses it.
I have the same issues with the 4.5 client but have downloaded the new 4.6 client using eval and can confirm it appears to be sorted in this release.
This issue appears to be related to the installation of some MS patches, this is explained further in the following KB1034262. There is an updated 4.5 client that also works but 4.6 did the job for me.