800xA Backup Error 0x8abb003a
Our 800xA backup creates 6 errors with code "0x8abb003a". All of the errors is coming from the Visuel Basic Graphic Library called "Special". The problem has been there for a couple of weeks, before that the backup was was working correctly. We have not made any changes to the "Special" library.
Hope you can help
Using the built-in afwerrorlookup.exe tool you can translate error code to a human readable error text (that in turn may need expert skills to be dissected).
8abb003a - E_AFW_FSD_NO_ITEM
This file set is unknown to the server.
Most likely, one or more of the VB6 graphic aspects in the Special library have been corrupted in FSD (which is the Afw-service running in aspect servers nodes responsible for storing the sometimes bulky VB6 project files, source code, ActiveX, etc).
I also assume we are dealing with the factory supplied version of "Special" which is located in the Graphics Structure (see image below taken from an untampered 5.1 FP4 RevD system).
Since the error is "rather new", I assume you will find graphic aspects inside the Special library with a modification time and modifying user corresponding to when the problem started. Expect ABB 800xA Base as creating and last modifying user.
The factory default version of Special is located in this AFW file which you may attempt to restore the object from:
C:\Program Files\ABB Industrial IT\Operate IT\Process Portal A\import\11\PgGraphicsSpecialPrimitives.afw
A side effect from importing the above AFW file is that the current user will replace the "ABB 800xA Base" user that indicates that the aspect has not been modified by any local user.
If you can not find any modified aspect, the fileset can still have been corrupted by a failed harddisk or problems with the Windows filesystem.
Do you have a redundant system? Do you get this error regardless of from what aspect server you are running the backup service in? You can easily test the other redundant FSD service providers by manually exporting the object or aspects while locally logged in to each aspect server. Eg. if "AS2" is OK you could try to cold reset FSD in "AS1" to have AS1 synchronize a valid copy from AS2.
I also suggest that you contact your regional ABB support center in case you need further advice on how to recover from this problem.