ARC serve 11 job holding on win2003

[DwayneL]

Hello

I have Arcserve 11.1 running with the updates on a win 2003 macine with sp1. It works fine backing up win 2000 files. When I go to packup files from another win 2003 machine the job always get hung up. I have the right secuirty information entered in. I can access the data by going \\machine name\share but can't seem to bring it accross in Arcserve. I am not using a the firwall. I had this problem before I ran the arcserve updates and still have the problem know.

Any ideas?

Any help would be awsome, i am pulling out my hair

thanks

dwayne

 

[DwayneL]

did a log on the tape engine

Client Set DebugLevel: 1
09/13 06:02:32 [0394] Loading Changer.dll: Date[Jul 21 2004] Time[18:59:10]
09/13 06:02:32 [07f8] DB: Database Library not ready.
09/13 06:02:32 [07f8] DB:: SetDummyEntryPoints:: Executing SetDummyEntryPoints. error = 1
09/13 06:02:32 [07f8] DB:: SetHooks:: Error in DB_GetEntryPoints. error = 1
09/13 06:02:32 [07f8] DB:: SetHooks:: Retrying. count = 1
09/13 06:02:32 [07f8] DB: Database Library not ready.
09/13 06:02:32 [07f8] DB:: SetDummyEntryPoints:: Executing SetDummyEntryPoints. error = 1
09/13 06:02:32 [07f8] DB:: SetHooks:: Error in DB_GetEntryPoints. error = 1
09/13 06:02:32 [07f8] DB:: SetHooks:: Retrying. count = 2
09/13 06:02:32 [0394] TapeDrive[2] ABSL:2160 <DLT VS80 5E40> S/N[PHM051818M]
09/13 06:02:32 [0394] ABSL = 0 0 0 0, adapterTransferSize = 61440
09/13 06:02:32 [0394] ABSL = 2 0 6 0, adapterTransferSize = 69632
09/13 06:02:32 [0394] ABSL = 2 1 6 0, adapterTransferSize = 69632
09/13 06:02:32 [0394] ABSL = 2 2 57 0, adapterTransferSize = 69632
09/13 06:02:32 [0394] ABSL = 2 3 0 0, adapterTransferSize = 69632

 

[vschumpy]

Make sure you have the ARCserve support patch for Win2003 SP1 installed both on the host server and on the remote machine. The fact that your changer.dll is Jul 21 2004 in the above log tells me you probably aren't patched up to that level.

The tape log isn't really going to help you out here as it sounds like a remote or RPC remote call, or other network communication is getting hung up somewhere - you're more likely to find more useful information in the regular activity log in this case or the tskjobxx.log's