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.

Is this a bug ? - a .net2 dependent layer causing reboot via the RPC service

Updated: 29 Jul 2010 | 3 comments
vjuhasz's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hello,

I just upgraded from SWV 6.1.4063 to 6.1.4113.

I had an app layer with the following properties with which I encountered the following problems:
- the layer was originally created in SVS 2.1.XXXX (I think SP1)
- the same layer was imported into 6.1.4063 then re-saved in the new layer format. So far so good, no problems.
- after the upgrade to MP1 (6.1.4113) my layer stopped working: I received an error about the stopped RPC (Remote Procedure Call) Service, and the system went into a forced automatic reboot after a 1 minute countdown.

Basically I was not able to use that layer after the upgrade unless I modified the RPC service properties from "system restart" to "restart service".

To debug if this was a bug in 6.1.4113 I did the following:
- I re-captured the application in 6.1.4063. It worked fine in 6.1.4063.
- Then after upgrading to 6.1.4113, the newly captured layer stopped responding, gave the same RPC service error and went into reboot.

The problem layer depends on the .net 2 SP2 framework, which I captured with an older version of SVS (I think SVS 2.1.1404). I used this .net layer with various apps without any problems, everything worked fine up to SWV 6.1.4063. After upgrading to SWV 6.1.4113 problems started.

The problem might be in the app layer or in the dependent .net 2 sp2 layer. I had captured some time ago the .net 2 sp1, I tried that too, but it makes no difference.

Any ideas what might be wrong here?

Thanks,
Val

Comments

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

If it worked in one release

If it worked in one release and then broke in the next it's a bug.

I'd contact support because they'd be able to get your layers from you and start working on seeing what's wrong.

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

vjuhasz's picture
20
Oct
2009
0 Votes 0
Login to vote

SWV 6.1.5104 solved the

SWV 6.1.5104 solved the problem!

Jordan's picture
21
Oct
2009
0 Votes 0
Login to vote

That's good to hear. I'm

That's good to hear.

I'm thinking this issue may be related to LSASS which we use to ignore, then didn't and now do again because of some issues that popped up.

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