Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

SVS 2.1 error code 1053

Updated: 29 Jul 2010 | 5 comments
icc's picture
0 0 Votes
Login to vote

Hi,

I am new to the forum, and to SVS. I have been recently given the task to start and vitalize some of our companies software.

I began with creating a full capture install of PC anywhere (the install is configured specific to the company), this was done using a virtual PC, with the minimum Windows XP components installed. The capture was created with my admin account, and appears to work fine. However after I have exported the layer and imported it onto a working PC using a different account (non admin), once running, trying to deactivate the layer or reset (using the admin account), it prompts a message indicating a process is still running and needs to be terminated, click yes to continue. Once I click yes an error message 'Error code 1053' appears and does not deactivate the layer.

I can manually kill the process with both my non admin and admin account (via task manager) and SVS is then able to deactivate the layer, but I was wondering if there was a way around having to do that, and be able to have the process terminated by SVS when deactivating the layer or resetting it? When I created the package on the Virtual PC, SVS was able to deactivate the layer (and kill the running process)  with the account I had created it with.

Any suggestions would be much appreciated?

Comments

marcoh's picture
08
Sep
2009
0 Votes 0
Login to vote

try autocloseapps

Hi,

The AutoCloseApps setting usually helps.
www.symantec.com/connect/blogs/auto-closing-applications-running-layer

Deactivate force (svscmd * d -f) should also do the trick as it would literally kill all running layer processes.

Hope it helps,
Marco

icc's picture
14
Sep
2009
0 Votes 0
Login to vote

Hi, I tried doing what you

Hi,

I tried doing what you suggested, but got the same error meaaages, using both the registry changes and the cmd prompt. It just does not seem to be able to kill the running process.

Any other suggestions would be really helpful?

Jordan's picture
14
Sep
2009
0 Votes 0
Login to vote

use the task manager to

use the task manager to manually kill the process.

What version of SWV\SVS are you using?  There were some instances in older versions where you could get a layer into a state where you couldn't deactivate it if a process was running in the layer.

If a forum post solves your problem please flag is as the solution

icc's picture
14
Sep
2009
0 Votes 0
Login to vote

Hi, I am using SVS 2.1.3062,

Hi,

I am using SVS 2.1.3062, I don't want to have to use Task Manager to manually kill the process, as after the packages have been created and tested, it will be our support desk who will manage first user issues and want to keep things as simple as possible for them (I know killing the process is an easy thing to do), but I ideally want the layer to completely deactivate or reset when the command is executed?

Jordan's picture
15
Sep
2009
0 Votes 0
Login to vote

Try recapturing the layer, as

Try recapturing the layer, as I said above that usually this happens because the layer gets messed up.  The only other reason you wouldn't be able to deactivate a layer is if it had something running as SYSTEM in side of it.

Also, if you can, try updating to SWV 6.1.

If a forum post solves your problem please flag is as the solution