Hi Judson,
a few questions & thoughts:
First and most important: Did that ever work?
If yes, what changed?
To verify: the error occurs when you run an ad hoc backup from within SASMC?
(SASMC, Metadata Manager, Metadata Utilities, Server Backup, Backup Now)
If you do not run the backup from within SASMC but via batch/command line, then please
give the SASMC backup a try.
Next, go to Env Manager, log on as sasadm@saspw (or any unrestricted uid/admin id).
In Env Mgr, go to the Admin menu, go to Backup Manager. Can you get there?
Can you navigate around?
When SAS was installed/configured, was a vault location for the backup defined?
Are permissions set correctly on the vault location? (R/W)
If you are on Win, please verify that the Depl Agent is not running as Local System account.
Another thing we could check is:
SASMC - Application Management - Configuration Manager - SAS App Infrastructure:
right click on Backup Manage. Check the tabs and see if it is all ok (for example, internal connection or external,
settings etc). Its a long shot but worth a check
If the backup ever worked but now just stopped working, you could check whether the backup journal files
are updated properly.
One way to do so is to go to configuration-directory\Levn\Backup\backup.journal
As a test, you could copy and save the journal files to another location, then rename the original ones in this folder
(please just make sure that you do have a copy of these files!)
Then try to run the backup again. If the journal files would be the culprit, the ad hoc backup should run without problem.
Hope this helps to do some troubleshooting.
Please let me know what you find out.
If this cannot be resolved, Tech Sup would be the next step. They can help you to further troubleshhoot,
such as web app/web ser logs etc.
Thanks
Anja
... View more
