Skip to content

BA1005: A popup was detected, and if configured, will have been cleared

End of life

BackupAssist v8 and later don't use NTBackup. This article applies to BackupAssist v7 and earlier, which reached end of life on 30 September 2016 and no longer receive technical support. See Software end of life.

Error code Product Applies to
BA1005 BackupAssist BackupAssist v4 and later

Description

The error message indicates that a popup message was detected and cleared so the backup could continue to run. In this case the backup could not continue after the popup message was cleared, resulting in backup failure.

The message in the popup (which is in the details section of the error in the backup report) is the message that is reported back from NTBackup

Resolution

Known cause 1 - this popup appears

"Runtime Error! The application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."

This error is caused when NTBackup does not have sufficient rights to log into the machine and display a window on the screen. Most often this is caused by having multiple backup jobs that overlap (that is, multiple jobs that run concurrently).

The best solution to this is to schedule your jobs such that there is no overlap between any of the jobs, and to allow ample time between successive jobs. An alternative solution is to use the Local System account to perform the backups, but doing so may mean that you cannot backup network resources like network shares, remote Exchange Servers, etc.

Known cause 2 - there is a scheduling conflict

This section explains VSS and device conflicts. Refer to the section applicable to your issue.

VSS conflicts: Having two backup jobs running at the same time within BackupAssist can cause errors if both backup jobs are trying to run VSS. Ensure that only one backup job is running at any one time.

Hardware conflicts: Conflicts with backup devices can occur when another process is trying to use the backup destination at the same time as BackupAssist. Make sure that there are no scheduled tasks, particularly backup tasks, that run at the same time as your scheduled backups.

To confirm that this is a scheduling issue try running a backup during the day, or try changing the scheduled time of your backup by a few hours. If these backups work, the problem is likely to be a scheduling conflict.

Known cause 3 - a popup appears

A pop up appears with a message similar to "Waiting for tape...", "Mounting the media...", "Please load Media ***", or with some other reference to loading, mounting or tapes.

This error is often found in tape drive backup reports, where the popup message is requesting another tape. If you are backing up to tape please refer to the article 'The media is full or faulty and failed to mount'.

Known cause 4 - A pop up appears similar to "Found free media..."

Make sure that the Device name and Media Pool within the 'Destination' section of the backup job match those in the Removable Storage section of Windows (Right click My Computer > Manage > Removable Storage). If it doesn't match you can manually enter the correct details within BackupAssist and this should resolve the pop-up.

Last updated Created Further assistance
3rd Mar 2016 16th Mar 2007 BackupAssist Support page