Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem Installing Backup Exec

Status
Not open for further replies.

AllUserNamesAreTaken

IS-IT--Management
Jan 17, 2005
149
GB
Why do these problems always happen to me?

I purchased three seperate VERITAS Products;

Full 10d Backup Software (for windows servers)
Exchance Agent
Remote Agent

I'm attempting to install Backup EXEC 10d as a default installation, on an Exchange Server. The Server has no other software apart from Exchange and Symantec Mail Security.

After approximately 30 seconds, an error occurs and a log file is created. The last couple of lines in the log are:

"ERROR: Failed to install MSDE 2000 BKUPEXEC instance.08-11-2006,10:08:47 : Please review C:\WINDOWS\MSDE_BKUPEXEC.log for more details.08-11-2006,10:08:47 : Failed to install third party products."

The full log can be viewed here:
If anyone requires the MSDE_BACKUPEXEC.log, just let me know.

I've called Symantec regarding this, and they want $$$$ before they'll give me a support case - so I thought I'd try here first.

Thanks in advance for any input..
 
Please upload the msde install log. Since MSDE wont install its really not a Symantec issue its a microsoft issue.
 
Here is the failure in the msde log

SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "BKUPEXEC" -Q "Latin1_General_CI_AS""
MSI (s) (14!40) [10:08:42:614]: Product: Microsoft SQL Server Desktop Engine -- Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.

I have to tell you it probably some MDAC issues on the server. Try stopping all third party services and re-apply the latest mdac version. Also log in program files\microsoft sql server\mssql$bkupexec\log or install. I can remember but there is a file called configsvr.out You have to open it up and determine the error and search symantec site or microsoft site
 
Steve,

I'm not really quite sure what you mean.

Where do I get the latest MDAC version from and what services do I stop exactly?
 
It seems the issue I'm having is this:


And, Vertias says rebuild the performance counter library values, which is documented in Microsoft's KB300956 which can be found here:


Has anyone done this? - Since I'm getting stuck on the first part where it says expand the two .dat files that are in a .da_ extension on the CD. Unfortunately,I don't really know how to decompress them from the CD, so I can't overwrite them in the System32 directory. What a polava !
 
Ok, I followed the instructions for manually rebuilding the performance counters and I still get exactly the same problem.

Should I not be installing Vertias Exec Backup on an Exchange Server or something?

If anyone has any further input, I'd love to hear it !
 

###############################################################################


Starting Service ...

Latin1_General_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

driver={sql server};server=EXCHANGE\BKUPEXEC;UID=sa;PWD=;database=master

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

driver={sql server};server=EXCHANGE\BKUPEXEC;UID=sa;PWD=;database=master

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

driver={sql server};server=EXCHANGE\BKUPEXEC;UID=sa;PWD=;database=master

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

SQL Server configuration failed.

###############################################################################

 
Check the following registry key


HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\SQL Server

Is it empty?
 
in the ODBC.INI container, there is only one more container - called ODBC Data Sources.

Both Containers are empty (No registry keys) - only (Default) REG_SZ (Value not set)
 
Ok, do you have another server around and take a look at the key. That is the problem MDAC is corrupt or not installed properly. You may be able to import the key from another server. But at this point I would contact Microsoft .

 
Steve, much appreciated input first let me say.

Secondly, I do have another Server that I've had a look at and indeed there is a container there for the SQL Server - I could well copy the keys, more to the point, should I?

Like you said, try and contact Microsoft, but if I were to tell them that I'm trying to install Backup EXEC and having problems with installing an MS Desktop Engine, they'd probably end up saying contact Vertias instead.

Catch 22 !

Plus, If I were to change keys on this server and something was to go wrong, how could I possibly restore it without a backup? - Catch 22 !

MDAC installed seems to be 2.8SP2 and up to date. I don't know much about MDAC at all.

Another question - Should I be installing Vertias Backup Exec on an Exchange Server? - Because the Server that has the keys in place is just a Windows 2003 Box. Esentially, my Exchange 2003 is just a Windows 2003 box, but with Exchange 2003 installed onto it. Why the Exchange server doesn't have the keys and the standard box does have the keys I'm not so sure.

Still no furth with this problem.
Looking like I may have to bite the bullet and pay up $$$$$ to get Vertias to help, unless anyone has any further suggestions before I do?

Thanks a lot.
 
if you called Veritas they wont help. Its a Microsoft problem. Backup Exec gets installed into a Micorsoft MSDE SQL instance. If you look on the Veritas CD its just the Micorosoft MSDE 2000 you can download from Microsoft web site. So if you call Veritas they will tell you to contact microsoft and have them install a MSDE named SQL instance for Veritas to run on. During the installaton of Veritas you can pick the MSDE instance to install on

I would download MSDE 2000 SP4 and trying installing it manually.

Follow this technote

If that doesnt work it still something broker with MDAC on that server. Nothing to do with Veritas.
 
Ok, update:

It's definately only that Server that has the issue as I just installed a default installation of Backup Exec from the same disk onto another identical Server in terms of Operating System and setup.

Microsoft want £199+VAT (USD$375) for Support.
 
You can install msde manually on another server



Then when you install backup exec on you problem server you can pick the option to install backup exec into and 'exsiting instance" and pick the server you install msde manually on. So the application reside on you problem server but database resides on another
 
Solution:

HKEY_LOCAL_MACHINE > Software > Microsoft > ODBC > ODBCINST.INI key was missing (The whole folder)

Copied the ODBCINST.INI key including all subkeys/values into the server.

Restarted Windows.

Start > Cmd > Odbcconf.exe /f odbcconf.rsp

Restarted Windows.

Reinstalled MSDE, problem solved.


Thanks for everyones help in this case.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top