SVS Installation Error Workaround
Filed under:
Software Virtualization Solution
Installation
Submitted by Swami on 28 January, 2008 - 09:29.
If you are getting an error during installation of Altiris SVS this tip may be for you. In some old computers (not a clean machine - a machine that has been used for some time) you might get an error saying something like, "some files are in use" and it may ask you to reboot. If after several reboots, you are get the same error, try this tip.
STEP 1) Get the SVS installation EXE, execute it, provide the key, and check all the 4 check boxes when prompted. At this point, if you the error message, don't worry about it -- we'll take care of it.
STEP 2) Now you have an ".MSI" file in the same folder.
- Copy the line of code we've listed here:
msiexec.exe /qn /i software_virtualization_agent.msi PRODUCT_KEY=[your license key, without brackets] D_FSLRDR="[Full path name without spaces and long name of the Folder where you want the virtual contents to be, without brackets]" INSTALL_ADMIN=1 REBOOT=ReallySuppress
- Edit the code to suit your needs.
- Save the file as Install.bat and copy it into the same folder where you have the setups (.MSI).
STEP 3) This is will NOT prompt you nor will a GUI be shown, but your mouse cursor will look busy for around 2 minutes. After that, if you check your start menu > programs, you will see Altiris there. Perform a Reboot. Now you are done.
(32 votes)
- Login or register to post comments
- 2468 reads
- Printer-friendly version
Very very good
You probably posted one of the best SVS tricks ever. I use this for over one year, because especially when you install svs on a server or on a pc with lot's of network connections, svs keeps snagging for this.
Regards
Erik
www.deltaisis.nl
And it's safe.
We've confirmed with Support and Engineering that bypassing the "files are in use" install block in this manner is perfectly safe. The SVS Agent install will be valid. Apparently the cause of the message is some sort of Wise Installer for Windows quirk. We'll have to workaround it ourselves in a future release (unless of course they fix it by then).
Scott Jones
Product Manager
Altiris, Inc.
Now Part of Symantec
Thanxsss Scott
Thanxss for you're comment Scott, i already thougt it is safe, but it is good hearing this from you.
Regards
Erik
www.deltaisis.nl
Thanks for your support!
Hello All,
This is my first Tip, which got published. I’m very much encouraged by the user’s comments & Thanks every one who has voted for this tip. I’m very happy that even my tip is useful for many people.
Thanks & Best Regards,
Swami.
Keep going on
Swami, keep going on.
The easiest tips are of the most value.
Regards
Erik
www.deltaisis.nl
Thanks Erik
Erik,
Thank you very much.
Definitely I will keep sharing as much I can.
Best Regards,
Swami.
ERROR "1089"
Hi,Erikw
I'm very new to SVS..just today i started
Why i'm getting this error..while installing an application
Cheers Tillu
1089 is wrong or missing
1089 is wrong or missing lincese key.
Go to Help>About in SVS Admin. If nothing is listed for registration key, click register and add your key. There is not key validation in this dialog so make sure you type carefully.
1089 error
Jordan,
If there is a wrong or not valid license, then SVS functions, but only in Runtime mode.
In the older versions that did not have the VRA (Virtual Runtime Applikation) the 1089 eroor could indeed mean that there is a license error. I did not see this behaviour in the 2084 version.
Regards
Erik
www.dvs4sbc.nl
You'll get a 1089 without a
You'll get a 1089 without a regkey if you try to do anything with a non-runtime layer or action (like capture, export and so fourth).
1089 error is Driver is in an invalid state and using a regular layer in runtime is just that, the SVS driver is in runtime mode and can't do anything with a VSA.
1089 error explained
When getting the 1089 error, there can be some things go wrong. They are all the same. The fslx.sys driver is not loaded.
There are several way's to get this settled.
1)Don't install it on a 64Bit machine. The driver is not ready for 64 bit.
2) Make sure the machine is rebooted after installing SVS
3) Check if the driver is located in c:\windows\systemn32\drivers\fslx.sys.
I saw some older version of SVS that placed it in c:\windows\system32, and that is definetly the wrong place.
Hope this helps.
Regards
Erik
www.dvs4sbc.nl
update on error workaround
One update. The "t" is missing in software_virtualization_agent.msi.
Hence, the correct script should be as below:
msiexec.exe /qn /i software_virtualization_agent.msi PRODUCT_KEY=[your license key, without brackets] D_FSLRDR="[Full path name without spaces and long name of the Folder where you want the virtual contents to be, without brackets]" INSTALL_ADMIN=1 REBOOT=ReallySuppress
Thanks,
Swami
Corrected Above
Thank you!
Scott Jones
Product Manager
Altiris, Inc.
Now Part of Symantec