Re-Packaging issues with Symantec NAV client 8.11
Morning all
FOr the last few days i have been trying to re-package the NAV 8.11 client install with Wise Studio from the Exe wrapper provided by Symantec, in order to capture our company specific info. I want to create an MSI install in order for their to be no UI for our tech support team when installing it...
I can create the MSI and the application installs succesfully but during testing, every single time i try to do a local system scan the aplication blows up and gives me a 'Could not Start Scan. Scan Engine returned error 0x2000000046.' message
Has anyone else had difficulty packaging this or any other version of Symantec Norton Anti Virus? If so any suggestions would be greatly appreciated. The only reason i can think of for this happening each time is that the Exe wrapper that i am re-packaging from actaully unwrapps an MSI during the install, and i thought that this could cause a few re-packaging issues?
Please help or advise where possible...
Many Thanks
FOr the last few days i have been trying to re-package the NAV 8.11 client install with Wise Studio from the Exe wrapper provided by Symantec, in order to capture our company specific info. I want to create an MSI install in order for their to be no UI for our tech support team when installing it...
I can create the MSI and the application installs succesfully but during testing, every single time i try to do a local system scan the aplication blows up and gives me a 'Could not Start Scan. Scan Engine returned error 0x2000000046.' message
Has anyone else had difficulty packaging this or any other version of Symantec Norton Anti Virus? If so any suggestions would be greatly appreciated. The only reason i can think of for this happening each time is that the Exe wrapper that i am re-packaging from actaully unwrapps an MSI during the install, and i thought that this could cause a few re-packaging issues?
Please help or advise where possible...
Many Thanks
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
akhlaque
18 years ago
Hi Tom:
Try starting the msi logging option so it u can find the point where the msi engine is getting stopped. Also check event log.
I think u r right when u say that the exe is may b unwrapping another msi.
If this is the case then use custom action Pause Installation.
U can also get help in Windows SDK about this nested installation.
Try starting the msi logging option so it u can find the point where the msi engine is getting stopped. Also check event log.
I think u r right when u say that the exe is may b unwrapping another msi.
If this is the case then use custom action Pause Installation.
U can also get help in Windows SDK about this nested installation.
Posted by:
rikx2
18 years ago
hi Tom,
use the Symantec packager to apply all your company settings. then you can deploy using silent method with all the settings incorporated in the main EXE
regards
rick
use the Symantec packager to apply all your company settings. then you can deploy using silent method with all the settings incorporated in the main EXE
regards
rick
Posted by:
WayneB
18 years ago
Gidday Tom,
The Symantec Packager poses some problems of it's own and I believe Symantec has dropped it's support for the resource. The SAV version 8 client also had issues with ActiveSync 3.8 and below, we are now using AS 4.0 (in msi format). Later versions of SAV (9 and 10) were packaged a little cleaner. We are in the process of removing SAV8 off the lock down desktops and migrating to SAV10. The V8 client requires admin privs to remove and won't allow msiexec.exe run elevated to remove it.
Just my 2c worth
Cheers
WayneB
.
The Symantec Packager poses some problems of it's own and I believe Symantec has dropped it's support for the resource. The SAV version 8 client also had issues with ActiveSync 3.8 and below, we are now using AS 4.0 (in msi format). Later versions of SAV (9 and 10) were packaged a little cleaner. We are in the process of removing SAV8 off the lock down desktops and migrating to SAV10. The V8 client requires admin privs to remove and won't allow msiexec.exe run elevated to remove it.
Just my 2c worth
Cheers
WayneB
.
Posted by:
tomwoollard
18 years ago
Thanks all for your suggestions. I have now actually fixed the error i had with my resulting package
Basically Mav was installing from my MSI but the local system scan kept bombing out every time i tried to run it. It all came down to the local Symantec System Service which needed to have the 'allow service to interact with desktop' radio button checked. (found this out after much web hunting!!)
Anyway i re-packaged the WSI project with the new option specified in the service feature and all is now working okay
Regards
Basically Mav was installing from my MSI but the local system scan kept bombing out every time i tried to run it. It all came down to the local Symantec System Service which needed to have the 'allow service to interact with desktop' radio button checked. (found this out after much web hunting!!)
Anyway i re-packaged the WSI project with the new option specified in the service feature and all is now working okay
Regards
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.