AS2000 Workgroup Ed., Win2K and Citrix MetaFrame

[RSherwood]

After MANY attempts at getting phone and e-mail assistance from CA regarding my two installations of AS2000 Workgroup Edition, Windows 2000 Server and Citrix MetaFrame, I am near the end of my rope. Both installations are designed to backup local resources to a local Compaq AIT drive.

On one box, after having an installation fail after working reliably for months, I have made repeated attempts to remove and reinstall (ininstall ARCServe, remove remaining reg. entries, delete leftover folders then attempt reinstall) and the result after confirmation of a SUCCESSFUL re-registration of the product, that the Job Engine dies as if I was dealing with a trial edition instead of the legal product we own.

The other box had similar issues and is a very similar implementation (different purpose though) but after reinstallation (successful that time), ASRUNJOB.EXE generates an application error which stops the system from backing up.

On CA's recommendation, I use a copy of ARCServe Manager on my management workstation to access the one remote installation, while I work at the console of the other. I'd prefer to use Terminal Services, but I have yet to see a meaningful fix from CA regarding how ARCServe interoperates with Terminal Services inplementations. BTW -- ARCServe Manager on my W/S does not let me modify a job and re-save to the server, so it's usefulness is limited to monitoring jobs and doing the odd tape eject...

If CA is listening, I have spoken to folks in Islandia, Bangalore (?) and via e-mail but have yet to get any meaningful solution to the chronic problems I've been experiencing. And I still expect a solution because this was not an insubstantial investment of time and money!

Any comments, solutions?

 

[ARCserveGuru]

Have you applied SP3 to arcserve 2000?

There was a patch that supports proper terminal services however it is now incorporated into SP3.

let me know asap

guru

 

[RSherwood]

Thanks for the reply, but the first implementation cited (Job Engine dying) is with SP3 and the post-SP3 Terminal Services fix installed...I'm not going near the second installation until I get something definitive determined...

 

[kewl]

hi. we are curently working on a project with the same system as yours - windows 2000 and citrix (and ms sql), but with brightstor backup.

we tried using arcserve 2000, but after a failed remote disaster recovery trial, and with arcserve's number of patches, we decided to try brightstor.

basically, the win2k/citrix server is critical, we decided not to install the manager on it, what with all the restart arcserve/brightstor requires. this way, we can isolate any problem between the manager and the client agents.

so now, the manager sits on an nt 4.0 (with tape device)while win2k has agents for win2k, baof and sql. we are now in the process of testing the remote disaster recovery for the win2k machine.

my point is, whether we are using arcserve or brightstor, it would be easier (i hope) to isolate issues/problems in a setup like this.

just a thought.

 

[RSherwood]

Thanks for the comments, kewl -- I know we have a bit of a challenge because this is a complex setup, but since we've made a substantial investment in the Workgroup version of ARCServe (which has worked in the past), it precludes us from spending money on agents and the Advanced Edition. I wouldn't be prepared to deploy another CA product in any form until I have a reasonable assurance that things will work.

I maintain IMHO that CA needs to spend more time in this area (since through patches they do support the use of Terminal Services implementations with the use of their product) to get it right.

 

[ARCserveGuru]

Rsherwood.

Why does the job engine die? I am thinking there are licensing issues, and unfortunately I think I know why, but firstly could you confirm them by checking the event log or the activity log for any license errors.

Secondly, I have seen various scenarios where SP3 will take workgroup edition to advanced edition, and as such leaves you "the user" quite unlicensed.

hope this helps

guru

 

[RSherwood]

There is a license error that occurs on installation, but I use REG_IT to re-register the product.

ARCServe does initially report the installation as a 3NUB installation instead of a 3NUW one right at the end of the setup, which does suggest for some reason it does think it's an installation of Advanced Ed. BTW -- I don't need to install SP3 fo it to behave this way. It does this right out of the box.

You'll note in my original problem description above that I already suggested the installation is working as if it was a "timed out" copy (hence the Job Engine stopping).

FYI on Job Engine event log entry:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 17/01/2002
Time: 3:03:14 PM
User: N/A
Computer: <NAME REMOVED>
Description:
The ARCserve Job Engine service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action.

I have set no rule on recovery on the service and retry if engine crashes in ARCServe itself has no effect.

And yes, I do have a legitimate license for this installation!

 

[montanablue2]

Might want to check that there isn't a &quot;rogue&quot; version of Arcserve running out on your network somewhere that is causing potential licensing issues. The different Arcserve installations communicate with each other and can force job shutdowns if they don't like what they see on the other end of the network... Shot in the dark, but who knows?

 

[ARCserveGuru]

simply reregistering it won't be enough, you'll have to call up computer associates license desk and tell them the sotry and then reregister the product.

Do me a favour, go to the CA_LIC directory and open the ca.olf file. Tell me what the expiration date of the 3NUW lines are. (it's the only date on the whole line and is near the beginning of the line) Do not use wordwrap as it is quite annoying.



let me know how it goes.

guru

 

[RSherwood]

Thanks for the 2 responses -- since this is a Workgroup Edition and the only ARCServe 2000 installation in our environment (the other is co-located at an ISP) I don't think there's an issue with rogue installations, but it's an interesting thought...

As for the contents of the ca.olf file, there are 2 lines referring to 3NUW -- here are their expiry dates:

09-aug-2026
15-feb-2026

R.

 

[ARCserveGuru]

Hang on..... The two lines shouldn't have different dates!!!

That's odd. Confusing. hehehe why don't you try registering with a trial code the 3NUB option (advanced edition). If this works for thirty days then you know you SP3 messed you up.

hehehe, just a thought

guru

 

[RSherwood]

Thanks for the response, but if you review the info. I presented, these issues were occurring pre-SP3, so it's likely immaterial...