Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Cannot Move BEDB Database

Updated: 22 May 2010 | 9 comments
Future5's picture
Future5
0 0 Votes
Login to vote
I am trying to move the BEDB Database from a SQL 2000 Server to a SQL 2005 Server as we have installed a new server and started migrating our applications over.
 
I have tried following the instructions at http://support.veritas.com/docs/275658 but when I select the new location and click OK I get a prompt advising that services will be stopped in order to continue - I click OK to this and after a few seconds the BEUtility application exits without warning.
 
I am running BE 10d SP3 (reported in BEUtility as v10, b5629, r01).
 
Any ideas?
 
Thanks
discussion Filed Under:
, ,

Comments

Al Wilson's picture
29
Oct
2007
0 Votes 0
Login to vote
Al Wilson

Try this:-

http://seer.support.veritas.com/docs/280204.htm



Message Edited by Al Wilson on 10-29-2007 11:11 AM

Future5's picture
29
Oct
2007
0 Votes 0
Login to vote
Future5

Thanks
 
I have had a look at that but my version is already greater than that and I am able to backup SQL 2005 databases without problem.
 
An Application Error is logged when BEUtility exits as follows:
 
Faulting application BEUtility.exe, version 10.1.5629.34, faulting module BEUtility.exe, version 10.1.5629.34, fault address 0x0006cbbf.
Future5's picture
05
Nov
2007
0 Votes 0
Login to vote
Future5

Anyone?
 
I need to do this soon as I will be decomissioning the old SQL server in the near future.
Future5's picture
13
Nov
2007
0 Votes 0
Login to vote
Future5

I guess that the deafening silence means that Symantec support are (as usual) next to useless!
Ken Putnam's picture
13
Nov
2007
0 Votes 0
Login to vote
Ken Putnam
Trusted Advisor

After Symantec bought BackupExec, these "moderated" forums became Peer-to-Peer.
 
Symantec Employees come in as their schedules permit, primarily in the v11d forum
 
Don't have a clue as to why you cannot move the MSDE to SQL 2005, sorry

If this response answers your concern, please mark it as a "solution"

Future5's picture
13
Nov
2007
0 Votes 0
Login to vote
Future5

Thanks for the reply Ken.
Rafal Woz's picture
15
Nov
2007
0 Votes 0
Login to vote
Rafal Woz

Keith, did you find out why BEUtility was termianted while trying to move database from MSDE to SQL2005? I'm having exactly same problem
Future5's picture
18
Nov
2007
0 Votes 0
Login to vote
Future5

Rafal - I have still not found a solution to this problem.  I am not moving from MSDE however, I am moving from full SQL 2000 to full SQL 2005.
 
I need to decomission the old SQL server in the near future so unless I can find a solution, I will have to simply reinstall BE and point it to a new server - although I want to avoid that as I want the history.
Ken Putnam's picture
19
Nov
2007
0 Votes 0
Login to vote
Ken Putnam
Trusted Advisor

If you do the uninstall/re-install thing, see http://seer.entsupport.symantec.com/docs/280710.htm to save all your local info (job defs, selection lists, schedules, etc)
 
Be sure to read the "Do Not Use If ...." near the top



Message Edited by Ken Putnam on 11-19-2007 08:53 AM

If this response answers your concern, please mark it as a "solution"

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
259,054