Link to home
Start Free TrialLog in
Avatar of devruiz
devruiz

asked on

Veritas BackUp Exec 9.1 install dies at MSDE portion of setup - LONG STORY

Here's one that has been giving me trouble, and I REFUSE to pay Veritas Support $250 (weekend rate)  or $89 (Weekday Rate) for them to help me with something that SHOULD work after spending $3k on Software and Options. I have 6+ years experience with Veritas, and have never encountered a problem like this, let me be specific as to how I arrove at this question/point in time.

Roughly 1 month ago, I went to a client who uses Veritas BackUp Exec 9.1, with Exchange Option, 2 Remote Server Options,  2 Advanced Open File Options, and 1 Disaster Recovery Option. I was FIXING the Backup <hadn't worked for months> and doing requested maintenance (which was to make sure EVERY Application/Bios was 100% current on update), so I ran into the Veritas BackUp Exec Service Pack 2, and Installed it. After RESTARTING after the update, My AD was CAPUT! Nothing, Nada, Zilch. I almost had a heart attack. I called Microsoft at 7:00am on a Saturday asking them for help, because i was lost. Fast forward to 7:30 PM <almost 13 hours later>, when Microsoft told me they had exhausted EVERYTHING (including myself), and my only choice was to reload. That was our ONLY DC, and we had exchange and three other member servers looking for their Daddy DC. Long Story Short at this point everything was reloaded, and is 100%, I am now almost permanently scarred from my experience. Putting in 30 Straight hours, so that Monday Morning 50 Users don't notice anything, is NO easy task.


We do Daily backup's with NTBackup, but just got a DAT72 6 Tape Autoloader, and I have pushed them into using Veritas again. When I went to install it today, it kept getting stuck at the MSDE portion of the install, and would fail. I researched Veritas Support, and this site and others, tried everything, but came up short. HELP! How do I manually install MSDE? I have tried all the line commands, with no luck. Can someone write the command line for me, I must be doing something wrong.

I've tried :

Setup.exe INSTANCENAME=BKUPEXEC DISABLENETWORKPROTOCOLS=0 SAPWD=mypassword TARGETDIR="C:\PROGRAM FILES\VERITAS\MSDE"

Since backups are the heart of sole of the network, this is a 500 pointer, I'd love it fixed by Monday Morning.

Thanks ahead of time,
D
SOLUTION
Avatar of gpriceee
gpriceee

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of devruiz
devruiz

ASKER

Actually this is more like what I'm getting

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

D
Avatar of devruiz

ASKER

and this one too

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

....am I doing something wrong? It was not a system wipe, I just reloaded on top of the old system, so there is still resident files from the previous install. Although the registry is new, could some old sql/msde files be hindering the install of the new msde? Where would those files be located if this is the case?

D
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of devruiz

ASKER

30 Hours rebulding the entire network which was probably 100+ hours to other tech's I've seen....I have just now started tapping the BackUpExec portion since I was bitten so hard, I had them go to NTBackUp until now....The Registry would be replaced with the new install, so I wouldn' t think that would be an issue, I looked for references to sql (file/folderwise) and renamed them, still no luck.....ODBC, I don't know crap about Databases, so I suppose that's the next place I should look....any other suggestions? I'll be in there tomorrow morning at 6:00am sharp <it's now 4:51pm>

D
In the meantime, take a look at these comments from a guy with similar problems back in Feburary:

http://www.mcse.ms/archive91-2004-2-351344.html

Specifically:

Setup.exe INSTANCENAME=instance_name SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=1 SAPWD=sa_pwd l*v c:\MSDESTP.LOG

If setup fails again, you want to look at the C:\MSDESTP.LOG in notepad
(notice I had to specify L*V <filename> to have setup create a log). In
MSDESTP.LOG do a find for "return value 3". A "return value 3" is the
fatal error value that returns for an action. Based on the failed action,
you can continue to determine the reason why your MSDE 2000 setup failed.
And this one blew my mind!  You just gotta read some of the comments here!

http://forums.veritas.com/discussions/thread.jspa?forumID=18&threadID=37429&messageID=4331533

Right now it's a little after 2:00 AM here (Germany) so I'll be signing off till tomorrow.

Best of luck!
SOLUTION
Avatar of Ron Malmstead
Ron Malmstead
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of devruiz

ASKER

After messing with the MSDE again, and again; and arriving at the same result, FAILURE,  I threw in the towel, and told the client we had no other choice but to contact Veritas. After about 1 hour, of attempted installs, and looking at the MSDE install log, the return value 3 error was focused on (like I did as well prior to calling them). I was told to go to a command line, and type this, the $250 command line which fixed everything:

lodctr /r:perfstringbackup.ini

after that, it installed without incident....UNF*****BELIEVEABLE, he told me to reference Microsoft Article ID: 315083 , I haven't had a chance yet

Thank you to all of you who contributed in trying to help with this pain in the butt task. I hope this helps ANYONE else running into this problem and saves them a few bucks and HOURS.  I definitely feel like it was a scam, being there was NO reference to this in Veritas's OWN knowledgebase on MSDE install problems.....Kind of Microsoftish in a way....  ;)

D
Glad you got it worked out!
I followed that link you mentioned, and guess what I found:

To resolve a corrupted registry problem, run the following at the command prompt:

lodctr /r:PerfStringBackup.ini

Wonder why Microsoft didn't or couldn't find one of their own listings in the first place!
Hi D!  You'll either have to award some points or just close this one out.  Hope everything is back up and running :-)

Rick
Avatar of devruiz

ASKER

Points were awarded on this based on Participation/Support not correct answers. This was a PAQ which cost $250 from Veritas. Hopefully someone else will need this, and save time and money. Thanks especially to huntersvcs who was extremely helpful in trying to help!

D
Avatar of devruiz

ASKER

I still think it's unbelieveable that this solution wasn't readily available in Veritas' Knowledgebase. What a load.....
We just went through this whole process, we were able to get it installed by downloading the latest MDAC (vesion 2.8) from MS and installing it.  After the MDAC was re-installed, Veritas installed lickity split!