Layer doesn't show up in SVSAdmin after 'successful' import
rpfenninger
July 20th, 2009
Hi everyone, from time to time we encounter the issue, that a layer doesn't show up after 'successful' import. This happens on SVS 2.1.3064 (or older) up to the current version 2.1.3071. So it seems, it's not a problem of a specific SVS version. It is also layer independent. It happens with any of our 100 layers, whereas all of them work fine on other workstations. Sometimes, an upgrade to the current version helps, sometimes it doesn't. How can I troubleshoot this one? I don't want to reinstall the workstation because of this. Yesterday it even happened on a clean reinstalled one.
Thanks in advance.
I've never seen this and it
I've never seen this and it looks like the import, for some reason, is failing.
There has to be something else on the machine, like AV or other secuirty software, or some rights or priviliages aren't there that SVS requires--but we should error out import in that instance.
The only way to troubble shoot is to check to see if everything is in the registry after import at HKEY_LOCAL_MACHINE\SYSTEM\Altiris\FSL
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
Same problem
I have the same problem on one of my machines
Regards
Erik
www.DinamiQs.com
Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)
does the layer exist in the
does the layer exist in the FSLRDR folder and in the registry? This is somethign that really needs to go to support so we can track it better.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
It does not
It actually imports and then its just gone.
No traces can be found
It is a somewhat odd bug.
I have 5 machines that are almost identical because they are clones from each other.
Then suddenlu it appears.
Strange.
I will dive deeper in it when im back in the netherlands
Regards
Erik
www.DinamiQs.com
Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)
I've seen the same issue and
I've seen the same issue and not determined a root cause. Is anyone aware of a resolution??
try upgrading to the hotfix
try upgrading to the hotfix released (6.1.4013), the only change there was the temp file that import uses but that might resolve the issue.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
Another thing to look for is
Another thing to look for is if the import temp folder exists under c:\FSLRDR. What I'm thinking is going on is something is preventing the temp folder from getting renamed--which is why I think 4113 might resolve the issue.
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
How are people importing the
How are people importing the layer? SVScmd, SVSadmin or using NS or DS?
If a forum post solves your problem please flag is as the solution
I you like an article, blog post or download vote it up
No NS or DS available here
Since we have no NS or DS available here we import it either through SVSAdmin or SVSCmd. It doesn't matter. It happens either way.
Having similar problem
I have (had?) Altiris SVS v2.1.3064 installed and everything was working perfectly fine. I had several applications installed and running, and I could activate/deactivate/reset individual apps at will.
This morning, my system got infected by a Trojan virus (don't remember which) so I deleted all the infected files using AVG Anti-Virus. It required several reboots and things are working now, at least from a virus point of view.
I noticed that the apps I had installed on virtual layers we no longer there. When I opened the SVS Admin console, the layers were listed and were listed as active. But a search for the program files or registry keys showed that the layers were not. I tried to deactivate/reactivate and as per the Admin console, it was working. But the programs were not there.
I did a layer reset, and although the console acted like it was working, the apps were still not there.
I deleted the layer, and re-imported the layer from a saved VSA I had as a backup, still nothing.
I uninstalled the SVS Agent, and reinstalled. Rebooted at each step as required. Still no effect. I did notice that all the virtual layers were still listed after the reinstall. (Shouldn't have this been a blank list and I would need to re-import my layers?)
I deactivated all my layers, and tried to create a new layer and install a fresh copy of the software on that layer. During the process, everything looked normal. I even had the spinning SVS icon on my task list by the clock. But after I stopped the capture, I tried to deactivate the software/layer, but the icon was still on my desktop and the software could run, indicating that the software did not install on a virtual layer but installed just like a non-virtualized software.
When I try to call the SVSCMD agent from a command window, it gives me an error window. Any SVSCMD command causes the error.
As a fix, I tried to update to SWV v6.1.4113. I imported the SVA files I had and it was still doing the exact same thing.
No matter what I do, it looks like the SVS agent isn't running at all.
Any ideas as to what can I do to get it running again? How do I do a FULL uninstall? (after a re-install my old layer list is still there so there must be something getting left behind)
Would you like to reply?
Login or Register to post your comment.