locked
Problem sequencing IE addon Cisco WebEx RRS feed

  • Question

  • Hello,

    I tried to sequence the Cisco WebEx Plugin for Internet Explorer. But I discovered the same problem, when trying to join a test meeting ( www.webex.com/test-meeting.html ) I get the error message:

    C:\PROGRA~3\WebEx\atcliun.exe
    The filename, directory name, or volume label syntax is incorrect.
    I tried to sequence the package as standalone for IE and even as a addon package. During sequencing I am opening the website and install the plugin over the webpage.

    Also I played with settings of COM and local interaction with out success.


    Do you have additional tipps for me what I can also try?

    • Edited by wavefront6 Wednesday, March 19, 2014 5:18 PM Format
    Wednesday, March 19, 2014 5:16 PM

Answers

  • So good and bad news...

    The Good-
    I was able to successfully and consistently get the package to work making the PVAD C:\Programdata\Webex.  Below is exatcly what I did;

    Started Sequencer 5 SP2, on Win 764 bit (we only have Win 7 x64, so we both sequence and test there)

    Opened IE, browsed to test page
    Installed Active X and waited until I was joined to test meeting
    Closed browser
    Relaunched browser and again launched the site
    Closed browser

    Stopped sequencing

    Additionally I DID check both com options under advanced (named objects, COM objects).  I also did my testing with an admin account as I don't have a normal user available to be easily.

    I don't believe the COM options matter at all, or that I tested with admin rights.

    The Bad-
    I was able to reproduce your issue sequencing the app to the VFS (making PVAD C:\packagename).  I didn't see anything obvious in procmon, but this screenshot shows something that I can't give an answer for.

    If I repeat the same test with the correct PVAD, I get no error.  I don't know what would cause DOS to catch an error like that, I've never seen that.  I'd be happy to attach procmons, etc, if anyone wants to look, unfortunately I don't have time right now to start looking in procmon and App-V debug logs.
    I'm of the opinion that I like to open tickets for possible issues being that App-V 5 is so new.  I can't come up with any answer why capture to PVAD would work, while VFS doesn't (while producing an error like this, that isn't a rights issue, etc).  In fact, many times it seems capturing to the VFS works better.  Maybe someone else here can help point us both towards an answer, but if you decide to open a ticket to MS let us know what they say. 

    • Proposed as answer by znack Sunday, March 23, 2014 11:04 PM
    • Marked as answer by wavefront6 Wednesday, July 23, 2014 3:11 PM
    Friday, March 21, 2014 7:06 PM

All replies

  • Are you doing this with App-V 4 or 5?  Are you launching IE inside the virtual space correctly?
    Wednesday, March 19, 2014 5:42 PM
  • I just went through a quick sequence with App-V 4.6, and I was able to launch Web Ex test meeting fine, without the error you reported.  I didn't change COM or settings.
    Wednesday, March 19, 2014 5:53 PM
  • Hello,

    Have you monitored the events occuring up to the error message with Process Monitor to determine the flow of the application?


    Nicke Källén | The Knack| Twitter: @Znackattack

    Wednesday, March 19, 2014 9:26 PM
  • I followed following sequence structure:
    1. New package as standard application
    1. No installation,
    2. Cisco WebEx 28_IE1
      PVAD: C:\ProgramData\WebEx
    1. Start of monitoring phase
    2. Opening IE and install WebEx via test-page
    3. Test meeting works
    1. Close IE
    1. Create a shortcut of IE on desktop, name it "IE with WebEx"
    1. End of Monitoring Phase
    2. Start "IE with WebEx" in "Software Configuration" and start again a test meeting, which also works
    1. Customize package
    2. Start "IE with WebEx" in "Prepare Streaming" and start again a test meeting, which also works
    3. Save package (no COM settings changed)
    4. Publish package on AppV5 server

     

    1. Launching "IE with WebEx" from a client
    2. Addon is listed and activated within the IE as "GpcContainer Class from Cisco WebEx LLC"
    3. Goto test meeting website
    4. Error occurs
      "C:\ProgramData\WebEx\WebEx\1324\atinst.exe
      The Syntax for the filename, directory name or the volume label is incorrect."

     

     

    The most significant what I found in the process monitor was:

     

    EXE: IEXPLORE.EXE

    Result: NAME INVALID

    Paths:

    If PVAD is %ProgramData%\WebEx

    • C:\PROGRA~3\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\6DAF92F0-3F84-4C79-AB6F-B828356A8185\989B0B40-1513-4446-8AB1-AADC7C6D055B\
    • C:\PROGRA~3\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\6DAF92F0-3F84-4C79-AB6F-B828356A8185\989B0B40-1513-4446-8AB1-AADC7C6D055B\Root\
    • C:\PROGRA~3\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\6DAF92F0-3F84-4C79-AB6F-B828356A8185\989B0B40-1513-4446-8AB1-AADC7C6D055B\Root\WebEx\
    • C:\PROGRA~3\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\6DAF92F0-3F84-4C79-AB6F-B828356A8185\989B0B40-1513-4446-8AB1-AADC7C6D055B\Root\WebEx\1324\
    • C:\PROGRA~3\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\6DAF92F0-3F84-4C79-AB6F-B828356A8185\989B0B40-1513-4446-8AB1-AADC7C6D055B\Root\WebEx\1324\atinst.exe"
    • C:\PROGRA~3\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\6DAF92F0-3F84-4C79-AB6F-B828356A8185\989B0B40-1513-4446-8AB1-AADC7C6D055B\Root\WebEx\1324\atinst.exe"

     

    If PVAD is to C:\vApps

    • D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\atinst.exe"
    • D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\
    • C:\PROGRA~3\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\atinst.exe"
    • C:\PROGRA~3\WebEx\WebEx\1324\"D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\atinst.exe"
    • C:\Users\sv-i\Desktop\"D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\
    • C:\Users\sv-i\Desktop\"D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\atinst.exe"
    • C:\Users\sv-i\Desktop\"D:\App-V Cache\PackageInstallationRoot\8E4E6D2B-0FA6-436B-BCB3-4D0DBC3D63B6\9BA9D9BB-A1A9-4716-893D-DF76EB48F114\Root\VFS\Common AppData\WebEx\WebEx\1324\atinst.exe"

    Maybe it's a problem with the PackageInstallationRoot, its set up to D:\App-V Cache\PackageInstallationRoot?

    Thursday, March 20, 2014 4:43 PM
  • What service pack of App-V 5 are you using? Also, any chance the app wants write access to that dir?  I did my test with App-V 4.6 and security descriptors unchecked.

    I'll try doing the same test with App-V 5 SP2 later today.

    EDIT:  I tried with App-V 5 SP2 capturing to VFS, and got the same error you have (I tested with an admin account).  I didn't see above that you had captured to PVAD, and when I recaptured it there, I was able to get the package to work.

    The only other thing that I did when capturing to the PVAD was checking both the options under advanced.  Tomorrow I will recapture to VFS with those options to see if those options are what made it work, or something else.

    • Edited by agallucci Thursday, March 20, 2014 9:07 PM
    Thursday, March 20, 2014 5:19 PM
  • We're using App-V 5 SP2.

    Which PVAD you used when you get it to work?

    Thank you for your help!

    Friday, March 21, 2014 9:41 AM
  • So good and bad news...

    The Good-
    I was able to successfully and consistently get the package to work making the PVAD C:\Programdata\Webex.  Below is exatcly what I did;

    Started Sequencer 5 SP2, on Win 764 bit (we only have Win 7 x64, so we both sequence and test there)

    Opened IE, browsed to test page
    Installed Active X and waited until I was joined to test meeting
    Closed browser
    Relaunched browser and again launched the site
    Closed browser

    Stopped sequencing

    Additionally I DID check both com options under advanced (named objects, COM objects).  I also did my testing with an admin account as I don't have a normal user available to be easily.

    I don't believe the COM options matter at all, or that I tested with admin rights.

    The Bad-
    I was able to reproduce your issue sequencing the app to the VFS (making PVAD C:\packagename).  I didn't see anything obvious in procmon, but this screenshot shows something that I can't give an answer for.

    If I repeat the same test with the correct PVAD, I get no error.  I don't know what would cause DOS to catch an error like that, I've never seen that.  I'd be happy to attach procmons, etc, if anyone wants to look, unfortunately I don't have time right now to start looking in procmon and App-V debug logs.
    I'm of the opinion that I like to open tickets for possible issues being that App-V 5 is so new.  I can't come up with any answer why capture to PVAD would work, while VFS doesn't (while producing an error like this, that isn't a rights issue, etc).  In fact, many times it seems capturing to the VFS works better.  Maybe someone else here can help point us both towards an answer, but if you decide to open a ticket to MS let us know what they say. 

    • Proposed as answer by znack Sunday, March 23, 2014 11:04 PM
    • Marked as answer by wavefront6 Wednesday, July 23, 2014 3:11 PM
    Friday, March 21, 2014 7:06 PM
  • @agallucci, In PVAD you've got write access, in the rest of your VFS you don't. Maybe this app needs those acl rights in there (which is bad actually). But anyhow, if the app works after setting the default installdir to PVAD (which also is MS's best practice), why bother?

    About the error: If you get an error like this, most likely some dll's are missing (or can't be found). You could try running dependency walking to see wich dlls are missing and where.

    • Edited by Roy Essers Saturday, March 22, 2014 1:32 PM
    Saturday, March 22, 2014 11:43 AM
  • When I sequenced it to the VFS, I tested with an account that has admin rights and full access to write anywhere on the local machine, and also on my image I have UAC turned off.

    My suggestion to possibly go to MS is that (IMO) the app should work even when sequenced to the VFS, outside of write access issues, etc.  Your point is valid though -- MS may not do anything because packaging to the correct PVAD works.
    And for what its worth, packaging to the VFS in 4.6 works.

    Good suggestion on dependency walker, I'll try to step through that when I have time and post back if I come up with anything.

    Monday, March 24, 2014 7:48 PM
  • Thank you agallucci for your help.

    But it still doesn't work for me:

    • When choosing PVAD to C:\ProgramData\WebEx the website just redirect me, no meeting window is opening (this should work as you pronounced)
    • When choosing different PVAD the error message "The filename, directory name, or volume label syntax is incorrect." is occuring

    Did you do something special, beside of your posted approach in the post?

    P.S.: A third person which I have contacted has exactly the same issues like me.

    Wednesday, April 9, 2014 3:33 PM
  • Sorry to hear its still not working for you.  When you say the website just redirects me, that happens during sequencing or after adding via powershell or management server? 

    Choosing a different PVAD (Installing to VFS) never worked for me, I get the same error as you.

    Choosing PVAD as C:\ProgramData\Webex did work consistently.  Are you sequencing and testing on the same OS and bitness?  One important thing I didn't add is I tested in 5 SP2 HF2.  We have had several packages work in HF2 that didn't work without.

    If all else fails can you email me a direct connection for you and I can send you my working package to see if it works on your environment?  I would ask you don't use that package in production in case it contains any references to our environment, but it would help a lot for troubleshooting.  I have my email in my profile.

    Thursday, April 10, 2014 2:30 PM
  • @agallucci

    The one thing here that I can see is different is that you tested with an account that has admin perms.

    @wavefront6

    I know that the WebEx plugin has some issue with where its cache is stored.  You could try creating a symbolic link pointing to a shares location for the cache to see if that makes a difference.

    MKLINK /D "C:\ProgramData\WebEx\WebEx" "\\server\WebEx"

    I am having to do this in my environment to resolve other issues with this plugin as well.

    Monday, April 14, 2014 8:47 PM
    Moderator
  • I just tested with a non admin account and it also works there.  I am only joining a test meeting and waiting until I am joined, if there is something else you want me to test let me know. 

    @CodyLambert

    Are you having to do that with a lot of plugins or just webex?  Is that a problem caused by App-V 5 security restrictions on write back to the COW user cache (PVAD, can't write dlls, etc), or something else caused by App-V'ing it?

    Tuesday, April 15, 2014 1:18 PM
  • @agallucci

    This is actually the first plugin that I've had to create a symbolic link for to make it work.  If you are able to get this working without doing that, then that tells me that it's most likely something with my configuration (provisioned disks in particular) thats requiring me to do so. 

    Tuesday, April 15, 2014 2:14 PM
    Moderator
  • Ok.  I find that solution very interesting... are you creating the link in the bubble? 

    Also, my offer stands if you want to look at my package.  I don't want to post a link for it publicly (I'm sure there is something quasi sensitive like a user name or something in there) but have no problem emailing it (its 14 MB) or doing something else if you'd like. 

    Tuesday, April 15, 2014 2:29 PM