Conference cookie::archive_backup

The error you are seeing in the LOG file indicates that UBS was not able to
establish a dialog with the NT client.  Also, since we did get this far
we know that the NT Client has been defined and that it has been licensed.

Where to from here???

1) Is the NT Client software installed and if so, what SERVER and PORT number
   where specified?

   In the previous case the SERVER should have been specified as SUOOMS and
   the PORT number, if defaulted, should be 1800. To verify this, use the
   REGEDT32 (Registry Editor) on the NT Client and look under the following
   KEY:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ABSClient\Parameters

	The entries should be:
		Server:	REG_SZ:	 SUOOMS
		Port: REG_DWORD: 0x708			<-- Hex for 1800


2) Is the NT Client SERVICE running?

   This can be checked using the SERVICE CONTROL MANAGER.  Under control
   panel there is a Services icon. Select this and look for "ABS Client Service.
   In the Services dialog box, ABS Client Service will appear near the top,
   alphabetical order.  The "Status" should indicate "Started", if not,
   try starting it with the "Start" button.

3) Check the NT Client's EVENT LOG.

   The ABS Client enters events in the event log under "Application Events".
   Start the "Event Viewer" found in the "Administrative Tools" folder.
   Select "Application" under the "Log" menu option.  You should find at
   least the Event 100 after the Source ABSClient.  This is an informational
   event indicating that the ABS Client Service has started successfully.
   If this is not showing up then the service is NOT starting.
  
   Check for other ABSClient events and check them to see if there are any
   socket errors occurring.  This would indicate that the TCP/IP interface
   is not starting correctly on the client. (Not likely, but check)

3) Check the NT Client's PORT number on the SERVER.

   When adding/configuring an NT Client on the SERVER node you run the
   licensing utility, ABS$SYSTEM:ABS_CLIENT_LICENSE.EXE.  RUN this utility
   and show of the NT Client to check the PORT number that has been assigned.

   $ RUN ABS$SYSTEM:ABS_CLIENT_LICENSE.EXE
   Would you like to Add/Modify/Remove/Show the Client License?: SHOW
   Enter Node Name or [ALL]: ABSCL1
   Client Node Type (UNIX or NT) [UNIX]: NT
   Node Name           Type         Transport    Port
   ---------           ----         ---------    ----
   ABSCL1              Windows NT    TCP/IP      1800

   License Count: 3 used of 191 total

   NOTE, the PORT number, in this case, 1800 which is the installation
   default.

4) Ping the NT Client from the SERVER to ensure that a link is possible.

   $ UCX ping ABSCL1
   %UCX-I-LOOPACT, abscl1.cxo.dec.com is alive


If non of this leads to a resolution, then we have a bigger problem on our hands.

    Hi,
    thanks for your "where to from here".
    The entries for server and port number are missing.
    After installing the client the first time, I wondered why there is
    only an icon "readme". After that I started a second installation.
    Doing the first steps I saw that all is done and aborted the
    installation. 
    After reinstalling this morning the following is the result:
    
    $   v = f$verify(0)
    Executing ABS LOGIN.COM
    Completed execution of ABS LOGIN.COM
    $   EXIT
    $! SCHEDULER$SHELL.COM  -- shell for executing Scheduler jobs
    $! POLYCENTER Scheduler V2.1
    $GOTO Start ! Avoid writing copyright all over the place
    $Start:
    $!
    $ nsched_saved_verify = f$verify(0)
    $       if f$mode() .eqs. "BATCH" then nsched_batch_job_number = p1
    $       run nsched$:scheduler$doo_command
    "@abs_system:coordinator.com 2FB78D95-7824-11D0-AF0D-08002B3206B2"
    Executing, o
    ------------------------------------------------------
    ---------------------------------------------------------------
    Starting New Request at 28-JAN-1997 09:29:57.52
       Name:   NTTEST
       UID:    2FB78D95-7824-11D0-AF0D-08002B3206B2
    
    COORDINATOR:  Created new volume set: SLS001
    COORDINATOR:  Mounting volume set member: SLS001 RVN 1
    COORDINATOR:     (Selected drive SUOOMS$RDEVA0:)
    COORDINATOR:  Initializing scratch volume SLS001
    %MOUNT-I-MOUNTED, SLS001 mounted on _SUOOMS$RDEVA0:
    COORDINATOR:  Skipping SUOOMS$RDEVA0: to End of Tape...
    THREAD #1:  Agent information has been altered
    THREAD #1:  Facility ABS:  ABS_AGENT_INFO_ALTERED, Agent information
    has been a
    THREAD #1:     Line = 326, File = RESD$:[SRC]CHECKSUM_AGENT.C;1
    THREAD #1:  Facility ABS:  ABS_AGENT_CHECKSUM_ERROR, Error checksumming
    agent i
    THREAD #1:     File: ABS$TEMPLATES:NT_GTAR-1.PARSE_TEMPLATE
    THREAD #1:
    
    Operation #1 starting at 28-JAN-1997 09:32:42.40
    
       Data Movement Type:    SELECTIVE_SAVE
       Incremental Level:     Selective Operation
    
       Object Set:
          Object Type:        Windows NT Files gtar
          Include List:       C:\
          Exclude List:
    
       Archive Information:
          Storage Class Name: SYSTEM_BACKUPS
          Saveset Location:   SLS001
          Saveset Name:       28JAN19970929577.
    
       Execution Environment:
          Name:               SYSTEM_BACKUPS_ENV
          Number of retries:  0
          Retry Interval:     0 minute(s)
    
    
    THREAD #1:  $
    THREAD #1:  SET NOON
    THREAD #1:  $ DEFINE SYS$COMMAND sys$input:
    THREAD #1:  $ ubs := $ABS$SYSTEM:ABS$UBS.EXE
    THREAD #1:  $ ubs n?SUOMS1 u?"root" l?_MBA1121: -
    THREAD #1:  _$ "d?SUOOMS$RDEVA0:28JAN19970929577." -
    THREAD #1:  _$ a
    THREAD #1:  f?SLS os?"Windows NT" s -
    THREAD #1:  _$ "c?ABSgtar -cvPpb20 --totals --same-owner  -f -  |C:\|"
    THREAD #1:  %ABS-I-STARTED, ubs agent is started
    THREAD #1:  ABSgtar: can't add file C:\pagefile.sys:  : Permission denied
    THREAD #1:  ABSgtar: can't add file C:\WINNT35\system32\config\admin000:  : Per
    ...
    ...
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    ...
    ...
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  Total bytes written: 256921600
    THREAD #1:  %%Status 2
    THREAD #1:  %ABS --UBS SUCCESS-- Gtar status may vary
    THREAD #1:  $
    THREAD #1:  Normal successful completion
    THREAD #1:
    COORDINATOR:  Completed with failure status
    COORDINATOR:  Facility ABS:  ABS_XN_FAILED, Completed with failure status
    COORDINATOR:     %%Status 2
    COORDINATOR:  Facility ABS:  ABS_XN_FAILED, Completed with failurestatus
    COORDINATOR:     Line = 1463, File = RESD$:[SRC]COORD_THREAD_MANAGEMENT.C;1
    COORDINATOR:  Dismounting volume set member: SLS001 RVN 1
    COORDINATOR:  Final status is Completed with failure status
    %SYSTEM-F-OPINCOMPL, operation is incomplete
      ABS          job terminated at 28-JAN-1997 13:10:49.69
    <CR><LF>  Accounting information:
      Buffered I/O count:       1985         Peak working set size:  9744
      Direct I/O count:          705         Peak page file size:   68320
      Page faults:              6369         Mounted volumes:           1
      Charged CPU time:      0 00:00:05.15   Elapsed time:     003:41:46.18
    [EOB]

Let's take these one at a time:


    THREAD #1:  ABSgtar: can't add file C:\pagefile.sys:  : Permission denied

The pagefile.sys is always open for read/write access.  This error indicates that this file was
not added to the archive, therefore it can not be restored.  This is normal operational procedure.


    THREAD #1:  ABSgtar: can't add file C:\WINNT35\system32\config\admin000:  : Per
    ...
    ...
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    ...
    ...
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory
    THREAD #1:  ABSgtar: can't add file :  : No such file or directory


Any disk under normal operation will have files that are created and disappear.  The backup process
does a complete scan of the disk to pick up file names before actual save operation begins.
This error indicates that files are that were intialing scanned and listed in the directory are now
gone.  This does point to a problem in the error reporting mechanism that I was QAR.  The name
of the missing file should appear in the output.

    THREAD #1:  Total bytes written: 256921600
    THREAD #1:  %%Status 2
    THREAD #1:  %ABS --UBS SUCCESS-- Gtar status may vary
    THREAD #1:  $
    THREAD #1:  Normal successful completion

The total bytes is obvious.  A status of 2 indicates that there were some recoverable errors
during the SAVE operation.  A status of 3 indicates unrecoverable errors.\