Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Unable to push managed client to Citrix Presentation Server

Created: 15 Oct 2009 • Updated: 21 May 2010 | 5 comments
This issue has been solved. See solution.

I have installed on all the other servers and workstations without any real issues but Citrix refuses. Been trying for a while now.

Will not even install client on push of just antivirus package. Any other issues I had with client installs was communication realted and would at least install the client but just not communicate with server for updates. Something is stopping the install, shows push successful from Deployment wizard.

IT see a folder in C:temp on the Citrix server called Clt-Inst
3 files instide that directory = steup.exe, vpremote.dat, vpremote.exe
This should be the cleint push but does not install
I even tried to run the setup.exe after and nothing
no services install or show

There are no firewalls or ports blocked on or between servers, there even patched into the same switches, no VLAN differences, both on default VLAN 1, servers are on same subnet

Can ping both ways (DNS or IP)
Can open TCP/8014 when telnet testing (update port)

http://172.16.30.204:8014/secars?hello,secars = OK

I performed the standard Citrix application install commands to lock out users and put it in install mode

Like so:
change logon /disable
change user /install

EP = 11.0.4202.75
Citrix = Metaframe 4.0.6 on Win2k3 Standard SP2

I am out of ideas and need this installed and working for PCI audit on Monday

I also read the best practices and while some good info jack about install on citrix itself

Any help/suggestions/same experience would be nice!

Comments 5 CommentsJump to latest comment

Vikram Kumar-SAV to SEP's picture

 can you post the 10 lines above the 1st return value 3 from the SEP_INST.log which is located in %temp%

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.

Aspired's picture

Yeah I read that document as I noted in my original post. Nothing good about install issues, more about resource usage issues which I can mess with later. Just need it installed for audit right now! Still something that should be read before installation is attempted.
 
Yeah I can drop the log:
 
FYI for others the log location = C:windows\temp
not C:\temp as I refered to in my original post above
Well my OS was R: but that shouldn't matter
 
So issue with that is there are no instances of "return value 3" in the document (lots of return value 1 though) 
 
(I see some concerning info at the end that seems relavent with failures and hold ups. 
Seems to think required files are in use by another application best I can tell
Nothing in Windows event viewer logs at time I tried last push of cleint 
 
Log seems to say ssawrapper is holding iteself - HUH? and that's a symantec process?
 
Maybe I can find what other processes where in use, stop them, push client install and then reboot the server tonight when users are not connected and it is not being backed up. Small window of time!
 
Ok well here is the log where I see issues:

MSI (s) (D8:60) [20:31:40:783]: Failed to generate hash for file 'R:\Program Files\Common Files\Symantec Shared\Help\CCLGVIEW.CHM'. Error: 0x3
MSI (s) (D8:60) [20:31:40:985]: Failed to generate hash for file 'R:\Program Files\Common Files\Symantec Shared\SPManifests\dec_abi.grd'. Error: 0x3
MSI (s) (D8:60) [20:31:40:985]: Failed to generate hash for file 'R:\Program Files\Common Files\Symantec Shared\SPManifests\dec_abi.spm'. Error: 0x3
MSI (s) (D8:60) [20:31:40:985]: Failed to generate hash for file 'R:\Program Files\Common Files\Symantec Shared\SPManifests\dec_abi.sig'. Error: 0x3
MSI (s) (D8:60) [20:31:41:001]: Failed to generate hash for file 'R:\Program Files\Common Files\Symantec Shared\SPManifests\SPBBC.grd'. Error: 0x3
MSI (s) (D8:60) [20:31:41:001]: Failed to generate hash for file 'R:\Program Files\Common Files\Symantec Shared\SPManifests\SPBBC.sig'. Error: 0x3
MSI (s) (D8:60) [20:31:41:001]: Failed to generate hash for file 'R:\Program Files\Common Files\Symantec Shared\SPManifests\SPBBC.spm'. Error: 0x3

Info 1603.The file R:\WINDOWS\TEMP\Symantec\setup.exe is being held in use by the following process: Name: setup, ID: 2104, Window Title: (not determined yet).  Close that application and retry.
Info 1603.The file R:\WINDOWS\TEMP\Symantec\setup.exe is being held in use by the following process: Name: setup, ID: 2064, Window Title: (not determined yet).  Close that application and retry.
MSI (s) (D8:60) [20:31:43:970]: 3 application(s) had been reported to have files in use.
Info 1603.The file R:\WINDOWS\TEMP\Symantec\SsaWrapper.exe is being held in use by the following process: Name: SsaWrapper, ID: 6140, Window Title: (not determined yet).  Close that application and retry.

Vikram Kumar-SAV to SEP's picture

 1. Create Non-Single exe package and try installing with MSI.
2. Open Device Manager-View-Show Hidden Devices-Non Plug and Play devices-SPBBCDrv
Right Click Uninstall.
Reboot if required
Install again.

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.

Aspired's picture

Ok so I was pushing the client from enpoint while RDP'd into the endpoint server and watching while RDP's into the citrix server (non console sessions)

I went to login to end all citrix services a decided I better grab the console seat when remoting.

Low and behold there where some popup messages on my console session about endpoint.
FYI the server was not in execute mode since last ngiht after I did not see it install I ran commande to pull it back out of instal and into execute mode.

So I just closed the application it was barking about being open (like the log showed) and told the setup to try again.

Installed, showed communication with server, retreived updates and is running initial scan.

FYI - use console session and not 2 built in RDP sessions when doinf Citrix installs.

My bad!

Thanks for time guys I do apprecicate it!

SOLUTION