Problem with application after upgrade to 4.5 Client
-
Thursday, December 03, 2009 5:20 PMHi,
After upgrading to AppV Client 4.5 (SP1) from 4.2 we have had some problems with a couple of applications. One of them, Swift Alliance Workstation, tries to connect to a host server with user/pwd credentials but get an error that it cannot connect (it does not log anything on the server). This workes well with version 4.2 and does also works during sequencing (in sequencer 4.5). For some reason it cannot connect to the host server when run from the AppV Client 4.5 and i have not been able to find anything in procmon, procexplorer, network utilities. Any ideas in what can change between the 4.2 and 4.5?
I have tried both MNT and VFS installs.
Any ideas would be greatly appreciated!
Kind Regards
eo
All Replies
-
Thursday, December 03, 2009 9:41 PMHello,
One of the major changes between 4.2 and 4.5 is how .NET is handled. Does the application use .NET?
/Znack -
Thursday, December 03, 2009 9:52 PM
Where is the server information located? Is it maintained in registry (hklm/hkcu) or files inside AppData folder?
-
Friday, December 04, 2009 12:23 PMHi and thanks for the quick replys.
The server information is located in registry HKLM, not in appdata.
The application does not use .NET framework. I have tested to uninstall all .NET versions on a Windows XP machine and the application works and can connect to database, during sequencing for example.
Now i actually found an "access denied" message in process monitor from process explorer.exe trying to write to an exe-file included in this application. This may have to do with it. This only comes up in the 4.5 client version.
Any ideas on how to troubleshoot more?
eo -
Friday, December 04, 2009 12:44 PMHello,
Have you turned off the security descriptors before saving a new package?
Have you tried to open the previous package with a 4.5 and re-saving it?
/Znack -
Friday, December 04, 2009 1:01 PMHi znack,
The answer is yes to both questions and it does not change anything unfortunately, what i can see.
I just tested to install 4.5 SP1 sequencer (on the same machine) and now it does not work even in sequencing! With 4.5 CU1 sequencer it works just fine. It seems to be something between 4.5.1 and 4.5.2! (CU1 to SP1)
My first thought is that it must be something in the c++ runtime library files. I do see that the application have some mfc dlls in its application directory (!) and wonder if the 4.5 SP1 sequencer (and client) handles these files in different ways.
eo -
Friday, December 04, 2009 4:37 PMEO, what is the exact error you are experiencing? Check the Event Viewer and see if anything is capture there.
-
Monday, December 07, 2009 8:53 AMHi!
The error is a generic errormessage from the Swift application that says "Unable to connect to server". It cannot connect to server and does not show anything in the server logs (no failure messages, it does not reach the server). No suspicious errors in Event Viewer nor the Process Monitor. When I compare a log (process monitor) from a working (in 4.2 or 4.5 CUI sequencer) version with a non-working (4.5. SP1 sequencer) version i find that it just stops logging from the application when the one that works starts reading server names and more from registry and connects. Besides from the AppV Sequencer version the sequencer machine and the package is exactly the same.
eo -
Monday, December 07, 2009 5:07 PM
During sequencing with 4.5 sequencer, are you able to ping/telnet the server address? Can you try sequencing on another box which does not have any sequencer before? It's best if you can sequence on a vmware or virtual pc.
-
Wednesday, December 09, 2009 12:38 PMHi,
Yes, i am able to ping the server adress, no problems. I have tried to sequence from a clean machine that hasn´t got any other version of sequencer before. Still same problem, as soon as it is the SP1 version i get the "unable to connect" message. if i uninstall 4.5 SP1 and install CU1 on that same machine it starts working immidiately.
eo -
Wednesday, December 09, 2009 2:39 PMHello,
OK - so connecting via the client works just fine...
Any chance of knowing what it actually does while connecting? Perhaps the Sp1-client had a change with how IT uses the network and that interferes?
Any chance of performing ping / telnet / port testing from within the virtual environment?
/Znack -
Wednesday, December 09, 2009 7:53 PMfor me, that sounds like a perfect scenario to contact MS Support...
Falko -
Monday, December 14, 2009 8:57 AMPing works fine but a telnet cannot connect to the port from inside the virtual environment. I´ll open a case at Microsoft to see if they can help.
Thanks everyone for all input and help. I´ll post if i get any good answer from MS.
Kind Regards,
Eo
eo -
Sunday, February 21, 2010 11:07 PMHi E.O,
Did you get a resolution to this issue?
Kind Regards, -
Friday, March 05, 2010 12:12 PMHi, not yet unfortunately.
I will make a new effort on this soon, i´ll come back with my findings.
/E.Osorio
eo -
Monday, September 20, 2010 12:41 PM
Closing this case since Microsoft have repaired this bug in their newest versions (also patch for 4.5). It was a bug in the App-V Client.
/E.Osorio
eo- Marked As Answer by E.O Monday, September 20, 2010 12:41 PM
-
Tuesday, October 05, 2010 10:16 AM
Hi, I have same problem with 4.6 version of client App-V. Patch existing of this version ?
Thanks
-
Monday, October 11, 2010 2:51 PM
Hi,
If you haven´t already tested with following update, try it out:
http://support.microsoft.com/kb/983173
Regards,
E.O
eo
.png)
