Home > Backup Exec > Backup Exec Cannot Connect To Sql Database

Backup Exec Cannot Connect To Sql Database

It could be caused be some network adapter chipsets and you can fix the issue by: Click Start, click Run, type cmd, and then press ENTER. Double click on test.udl file and you'll receive a window titled "Data Link Properties" 5. Make sure that Backup Exec account has the following server roles & privileges on the SQL server while backing up SQL databases: dbcreatorsecurityadminserveradminsysadmin 2. This tends to screw up all sorts of things with unpredictable results - to the point where when doing upgrades on a couple of occasions we've removed Backup Exec, done the http://cmptp.com/backup-exec/backup-exec-cannot-see-sql-database.html

Solution    1. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Create/Manage Case QUESTIONS? This way you can read the SQL statements being send from BENT to the SQL server and back.You may also try to attach as SA user of the SQL database -

Thanks alot, 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision baskervi1 Level 3 ‎01-08-2014 12:13 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thanks for the input, CraigV. Any suggestions?

The server name can be appended manually by adding the (\) backslash followed by the instance name (SQLEXPRESS). First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. The firewall service is enabled, but the firewall configuration is set to permit all traffic. Error: 0x862, state: 3.

Join the community of 500,000 technology professionals and ask your questions. Login. I create a backup account called 'sa' with the sa's password. https://vox.veritas.com/t5/Backup-Exec/Cannot-connect-to-Backup-Exec-2012-Sever/td-p/451152 Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Trying to expand the SQL Server Instance in the backup selection list

Examine the services. If DBCC printed error messages, contact your system administrator. · The recovery of the database ‘BEDB' completed without any issues. Training topics range from Android App Dev to the Xen Virtualization Platform. I read that there is 2 different type of agents for SQL.

Thanks 0 Kudos Reply Yes, bedssql2.dll is on the Gordon_Brown_2 Level 3 Partner ‎10-07-2009 03:13 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Sorry, we couldn't post your feedback right now, please try again later. If yes, please check the virtual node for backup of databases, after making sure that remote agent is installed on all the nodes involved in the cluster. If that is true how do I find out which version I am using.Thanks,G.

CHECKDB found 0 allocation errors and 0 consistency errors in database ‘BEDB'. http://cmptp.com/backup-exec/backup-exec-cannot-find-healthy-copy-database.html Also, make sure correct version of Remote Agent is installed on the target server. There are 0 rows in 0 pages for object "MachineDevice". All rights reserved.

Hence decided to run DBCC CHECKDB(‘BEDB') and check the consistency of the database. · The results turned out to be clean and we confirmed that there is no corruption in the Select TCP/IP if using Backup Exec, select Named Pipes for the Desktop and Laptop Option (DLO) or select TCP/IP and Named Pipes if using Backup Exec and DLO.( figure 2)   BE is on a domain controller so all of the accounts are domain accounts. Check This Out Thanks! 0 Kudos Reply Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business

Refer to the database recovery log for details. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Cannot select remote SQL database for backup VOX : Backup and Recovery : It is possible that updates have been made to the original version after this document was translated and published.

Create/Manage Case QUESTIONS?

more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Go to Solution. Depending on the protocol used for the connection attempt, we get one of the following two errors: When you try to connect to the instance by using the named pipes protocol Run the SQL Server Configuration Manager.

If I look on the media server, I see the SQL option, so the agent is definitely installed. Creating a table with FIXED length column widths What exactly are sleeping stalls versus waiting-rooms, for airport layovers? 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 this contact form Go to Solution.

If I receive written permission to use content from a paper without citing, is it plagiarism? Enroll in a course and start learning today. The permission are perfect. Please check for this file on c:\program files\symantec\backup exec\RAWS folder.

Wait... I fixed it. Should this be sufficient to run a backup? share|improve this answer answered Feb 26 '09 at 16:57 JFV 1,54662035 add a comment| up vote 1 down vote Long shot, but you don't have another instance of SQL Server installed

Storage Storage Hardware Storage Software VMware Virtualization How to replicate SQL 2008 database to SQL 2014 by using Initialize from Backup. The SQL server is a guest VM on a Hyper-V host, though, but I can't see that making a difference. This database is for the core application, so we can't deselect it. The only reason for this to fail is if the SQL Server service or SQL Server Browser services aren't running or if the browser service is misconfigured. ** UPDATE ** Another

add couple of entries such as IP address DC01.domain.local Same IP address DC01 View solution in original post 0 Kudos Reply 4 Replies Please check the sql service sksujeet Level 6 How to deal with a coworker that writes software to give him job security instead of solving problems? Why does Friedberg say that the role of the determinant is less central than in former times? Also, make sure that Backup Exec logon account has local administrator rights on the SQL server.

Solution Details : Backup Exec Version 10.x uses the Microsoft Desktop Engine (MSDE) to connect to BEDB database. How do I calculate passive perception for a monster? It's not a certificates problem (as seen online) as we don't use encrypted connections. Administrator should deregister this SPN manually to avoid client authentication errors. · Found only one user database ‘BEDB' on the server and this is the database used by BackupExec ·

Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We If a custom one, is the name of the SQL server over 15 chars in length ?