Home > Backup Exec > Backup Exec Cannot Complete The Operation. Contact Technical Support

Backup Exec Cannot Complete The Operation. Contact Technical Support

The infomation store backup will allow you to restoresingle mail message,as well as mailbox and public folder . Other issues may include tape drives or tape libraries that are offline, storage devices that are not found, recognized, or detected. Create/Manage Case QUESTIONS? The caller now needs to enumerate the files to find the changes. 1051 A stop control has been sent to a service that other running services are dependent on. 1052 The have a peek here

Please contact your system administrator. 1269 The smartcard certificate used for authentication was not trusted. See the Library Expansion Option (LEO) article for more information on LEO.   Ensure that Microsoft default drivers are installed for a medium changer (Robotic Library devices only) Navigate to Device Title Windows System Error Codes (exit codes) Date Updated 03/24/2006 Versions affected Automize 4.x+ OS affected Windows Description The Command and WinCommand task sometimes do not return any error messages, when Contact your support personnel for assistance. 1602 User cancelled installation. 1603 Fatal error during installation. 1604 Installation suspended, incomplete. 1605 This action is only valid for products that are currently installed.

Use your global user account or local user account to access this server. 1810 The name or security ID (SID) of the domain specified is inconsistent with the trust information for Use your global user account or local user account to access this server. 1809 The account used is a server trust account. I also tried this solution: Dev T 6 weeks 1 day ago Create a new account in AD Create a new account in AD named : symantec with following settings: Contact the application vendor to verify that this is a valid Windows Installer package. 1621 There was an error starting the Windows Installer service user interface.

Click Start > Control Panel > Add/Remove Programs (or Programs and Features)Select the third-party backup application or tool, and then click Uninstall.Repeat for all third-party backup applications or tools.   If Veritas does not guarantee the accuracy regarding the completeness of the translation. No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities So that you dont see the individual mailboxes and public folder in the backup selection list 0 Kudos Reply Re: Backup Exec 12.5 Exchange Issue - Can not expand Mailboxes or

Normally caused by an uninitialized register. You may also refer to the English Version of this knowledge base article for up-to-date information. Thank You! https://www.veritas.com/support/en_US.html Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

Install the appropriate Backup Exec agent for the resource, and then run the job again" occurs when using the option  "Enable the restore of individual objects ..."  when backing up or Use your global user account or local user account to access this server. 1808 The account used is a computer account. Solution Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Contact your support personnel. 1611 Component qualifier not present. 1612 The installation source for this product is not available.

Go to System in the Control Panel to change the computer name and try again. 53 The network path was not found. 54 The network is busy. 55 The specified network Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-917 Backup- \\ExchangeServer\Microsoft Information Store\Mailbox Database V-79-57344-917 - Unable to complete the operation. If you run LiveUpdate regularly, or if you have the latest Backup Exec Service Pack or Hotfix installed, your Backup Exec installation should have the latest tape device drivers. Sorry, we couldn't post your feedback right now, please try again later.

For information about network troubleshooting, see Windows Help. 1233 The network location cannot be reached. http://cmptp.com/backup-exec/backup-exec-2012-cannot-backup-exchange-2010.html Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Contact Technical Support." Error Message Solution Note: This issue appears to be related to the credential check only, backups and restores of Legacy Exchange Mailboxes and Public are not affected Disable legacy mailbox support and enable GRT.

Note the jobs that are affected and move the jobs back to the original device after resolving the issue with the device.Stop the Backup Exec services.Navigate to X:\Program Files\Symantec\Backup Exec, and then You may also refer to the English Version of this knowledge base article for up-to-date information. Install the appropriate Backup Exec agent for the resource, and then run the job again. Check This Out This may happen during a join operation if the cluster database was changing during the join. 5084 The resource monitor will not allow the fail operation to be performed while the

The LAN Manager password returned is a NULL string. 1305 The revision level is unknown. 1306 Indicates two revision levels are incompatible. 1307 This security ID may not be assigned as If a removal storage service error appears, ignore it; it should not occur after subsequent restarting of the server. Email Address (Optional) Your feedback has been submitted successfully!

In this scenario, Backup Exec was installed in evaluation mode, which will install all the agents and options.

Review the resource credentials for the job, and then run the job again. Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Backup Exec 12.5 Exchange Issue - Can not The value provided as the current password is incorrect. 1324 Unable to update the password. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem "This operation requires that the Backup Exec Virtual File Filter (VFF) driver

If Windows still cannot find the network path, contact your network administrator. 52 You were not connected because a duplicate name exists on the network. Do one of the following: - In the Enable Robotic Library Support option, check to install the robotic library support option or - Uncheck to uninstall the robotic library support option Email Address (Optional) Your feedback has been submitted successfully! this contact form Article:000026013 Publish: Article URL:http://www.veritas.com/docs/000026013 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in

However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please Now I face to another problem, I backup the Exchange information store with GRT enable and the job successful with condition : "The Backup Exec Remote Agent on the resource does Contact your support personnel. 1622 Error opening installation log file. These task return error codes, which do not mean much to the user.

No Yes How can we make this article more helpful? Thank You! Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview For information about network troubleshooting, see Windows Help. 1257 The security identifier provided is not from an account domain. 1258 The security identifier provided does not have a domain component. 1259

Disconnect all previous connections to the server or shared resource and try again. 1220 An attempt was made to establish a session to a network server, but there are already too