backup exec 9.1 install fails at MSDE2000 installation.m 3

[joenok]

We're trying to install backup exec 9.1 on Windows 2000 server and it fails at the MSDE2000 installation.m point during the install. Any suggestions?

Is this part of the Windows installer? Or do I need to load the MSDE2000 separately? How do I do that? Thanks for any suggestions.

 

[justin2000]

joenok

look in c:\winnt\msde_bkupexec.log file, search for return value 3, and look a couple of lines up, it will give the error.

post it here, so we can help.

 

[joenok]

I found 2 Return Value 3. errors.

Hope this helps!

thanks for any suggestions

TempFolder is C:\DOCUME~1\ADMINI~1.DEW\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}Loading extended custom action library C:\DOCUME~1\ADMINI~1.DEW\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (FTS4,LocalSystem,87).
Action ended 17:49:27: InstallFinalize. Return value 3.

Rollback: RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B
MSI (s) (10:A8): Executing op: ActionStart(Name=RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (10:A8): Executing op: CustomActionRollback(Action=RollbackDeferProperties.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1281,Source=BinaryData,Target=DeferProperties,)
MSI (s) (10:A8): Creating MSIHANDLE (843) of type 790536 for thread 2472
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Start custom action DeferProperties
Defer Properties returns: 0
MSI (s) (10:A8): Executing op: End(Checksum=0,ProgressTotal=0)
MSI (s) (10:A8): Error in rollback skipped. Return: 5
MSI (s) (10:A8): FEATURECACHE: Entering Invalidate
MSI (s) (10:A8): Unlocking Server
Action ended 17:49:37: INSTALL. Return value 3.

 

[justin2000]

Your error is here..

InstallSQLAgentSecurity failed (FTS4,LocalSystem,87).
Action ended 17:49:27: InstallFinalize. Return value 3.

The MSDE install is having trouble finding the PDC master of the domain.

To get this to work, you need to transfer the role of PDC master to this server, install Backup Exec, then transfer it back - to do follow this technote -

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

 

[joenok]

That worked. I had used your first post to find the error then did a search on veritas site and it was the PDC problem. Someone had typo'd the name, I fixed it and reran and it worked! Thanks Very Much!

 

[dandl]

Hi justin2000

I am having the same problem here is my log file, can you give me any pointers on this one.

SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (EXCHANGE-SERVER,LocalSystem,87).
Action ended 16:24:46: InstallFinalize. Return value 3.

any help would be greatly appreciated.

Thanks
dandl

 

[justin2000]

dandl

Same technote will apply here as well -

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

 

[h11]

We're trying to install backup exec 9.1 on Windows 2000 server and it fails at the MSDE2000 installation.m point during the install. Any suggestions? Here is my log any help woul be appreciated thanks in adv.

=== Verbose logging started: 10/6/2004 11:04:37 Build type: SHIP UNICODE 2.00.2600.01 Calling process: C:\WINNT\system32\msiexec.exe ===
MSI (c) (94:54): Resetting cached policy values
MSI (c) (94:54): Machine policy value 'Debug' is 0
MSI (c) (94:54): ******* RunEngine:
******* Product: F:\seagate\WINNT\INSTALL\MSDE\Setup\SqlRun01.msi
******* Action:
******* CommandLine: **********
MSI (c) (94:54): Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (94:54): Grabbed execution mutex.
MSI (c) (94:54): Cloaking enabled.
MSI (c) (94:54): Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (14:4C): Resetting cached policy values
MSI (s) (14:4C): Machine policy value 'Debug' is 0
MSI (s) (14:4C): ******* RunEngine:
******* Product: F:\seagate\WINNT\INSTALL\MSDE\Setup\SqlRun01.msi
******* Action:
******* CommandLine: **********
MSI (s) (14:4C): Machine policy value 'DisableUserInstalls' is 0
MSI (s) (14:4C): Note: 1: 2318 2: F:\seagate\WINNT\INSTALL\MSDE\Setup\SqlRun01.msi
MSI (s) (14:4C): MainEngineThread is returning 1603
MSI (c) (94:54): Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (94:54): MainEngineThread is returning 1603
=== Verbose logging stopped: 10/6/2004 11:04:37 ===

 

[h11]

I have figured it out. I copied the whole cd to c:\ and executed from c:\veritas the setup command and it worked with out a problem. thanks

 

[Southdraw]

Sounds like I'm not the only person with these issues, can anyone suggest a resolution to this problem?

I have been back and forth through at least 20 tech documents, edited the registry, deleted folders and files, ran utilities and still it errors to the same desktop engine failure.


This is version 9.1 of Veritas backup exec on Server 2003.
It was installed and errored to event code 1065 "Specified Database does not exist" during a backup Monday night.

After several troubleshooting repair and reinstalls
Backup install log:

4-22-2005,16:10:17 : Install Summary XML File:
04-22-2005,16:10:17 : C:\DOCUME~1\exadmin\LOCALS~1\Temp\1\{201E698C-B88E-41AE-8C46-3BBACADCD6E7}\InstallReview.xml
04-22-2005,16:10:17 : Install Summary XSL File:
04-22-2005,16:10:17 : C:\DOCUME~1\exadmin\LOCALS~1\Temp\1\{201E698C-B88E-41AE-8C46-3BBACADCD6E7}\InstallReview.xsl
04-22-2005,16:10:17 : Install Summary HTML File:
04-22-2005,16:10:17 : C:\DOCUME~1\exadmin\LOCALS~1\Temp\1\{201E698C-B88E-41AE-8C46-3BBACADCD6E7}\InstallReview.htm
04-22-2005,16:10:17 : MDAC 2.82.1830.0 is installed on this system.
04-22-2005,16:10:17 : Executing CRegistryOperations::EnumRegMultiValue
04-22-2005,16:10:17 : 
04-22-2005,16:10:59 : Executing InstallJRE
04-22-2005,16:10:59 : Required version of JRE is already installed. Exiting InstallJRE_MSI
04-22-2005,16:10:59 : Executing BE_InstallMDAC.
04-22-2005,16:10:59 : MDAC 2.82.1830.0 is installed on this system.
04-22-2005,16:11:04 : Installing MSDE 2000 BKUPEXEC instance.
04-22-2005,16:11:04 : C:\WINNT\INSTALL\MSDE\setup.exe /wait /qn /l*v "C:\WINDOWS\MSDE_BKUPEXEC.log" INSTANCENAME=BKUPEXEC SAPWD=**** DISABLENETWORKPROTOCOLS=0 REBOOT=ReallySuppress
04-22-2005,16:11:53 : ERROR: Failed to install MSDE 2000 BKUPEXEC instance.
04-22-2005,16:11:53 : Please review C:\WINDOWS\MSDE_BKUPEXEC.log for more details.
04-22-2005,16:11:53 : Failed to install third party products.


MSDE

InstallSQLAgentSecurity succeeded
MSI (s) (50:14) [16:11:20:359]: Executing op: CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,Source=BinaryData,Target=SkuIt,)
MSI (s) (50:C0) [16:11:20:359]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI7E.tmp, Entrypoint: SkuIt
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\exadmin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1\exadmin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
MSI (s) (50:14) [16:11:20:453]: Executing op: ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397B...
Starting custom action SkuIt
MSI (s) (50:14) [16:11:20:453]: Executing op: CustomActionSchedule(Action=ConfigServer.2D02443E_7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (50:04) [16:11:20:468]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI7F.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\exadmin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1\exadmin\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
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 "SQL_Latin1_General_CP1_CI_AS""
MSI (s) (50!BC) [16:11:46:906]: 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.

Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
MSI (s) (50:14) [16:11:46:921]: User policy value 'DisableRollback' is 0
MSI (s) (50:14) [16:11:46:921]: Machine policy value 'DisableRollback' is 0
Action ended 16:11:46: InstallFinalize. Return value 3.
>
>
>
Property(S): ACTION = INSTALL
Property(S): AgentServiceName = SQLAgent$BKUPEXEC
Property(S): InstanceRegKey = Microsoft SQL Server\BKUPEXEC
Property(S): InstanceSubDir = MSSQL$BKUPEXEC
Property(S): SqlPerfMonRegKey = SQLCTR$BKUPEXEC
Property(S): SQLServiceName = MSSQL$BKUPEXEC
Property(S): SqlStates = 0
Property(S): ROOTDRIVE = Z:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
Property(S): SOURCEDIR = C:\WINNT\INSTALL\MSDE\Setup\
Property(S): SourcedirProduct = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductToBeRegistered = 1
MSI (s) (50:14) [16:11:52:875]: Note: 1: 1708
MSI (s) (50:14) [16:11:52:875]: Product: Microsoft SQL Server Desktop Engine -- Installation operation failed.

MSI (s) (50:14) [16:11:52:890]: Cleaning up uninstalled install packages, if any exist
MSI (s) (50:14) [16:11:52:890]: MainEngineThread is returning 1603
MSI (s) (50:50) [16:11:52:890]: Destroying RemoteAPI object.
MSI (s) (50:C8) [16:11:52:890]: Custom Action Manager thread ending.
=== Logging stopped: 4/22/2005 16:11:52 ===
MSI (c) (FC:58) [16:11:52:921]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (FC:58) [16:11:52:921]: MainEngineThread is returning 1603
=== Verbose logging stopped: 4/22/2005 16:11:52 ===

 

[justin2000]

Southdraw, the error you will need to look for is in C:\program files\microsoft sql server\mssql$bkupexec\install\cnfgsvr.out you may want to post it here.

 

[Southdraw]

Thanks Justin2000, but I actually did that after reading other threads which contained that information. I have the Backup exec reinstalled, but it is still failing to the linkage error.

Apparently after working 70 hours and testing with Vertias, they feel this is an MS issue and they recommended opening a ticket with Microsoft. Trouble was I did that two days prior and was still waiting for a response from them.

The error I am currently experiencing is a Microsoft Data link error, ODBC Databases are good to link but I get an OLE DB error that "Provider is no longer available" everytime I try to start the media server service for Veritas BE or any other OLE DB link.

While I wait on the MS techs I am scouring the network for any clue on this. If I find any better information I'll post it for future reference.

 

[Southdraw]

H11,

Dario Petkovik a Verita's Technician in the Australia branch was the only one that was able to get past my installation errors. One of the recommendations he made was not installing the DLO option, if you have it, at the inital setup. The other modifications he made went by way to fast at 4AM for me to keep good notes. I only know the system is reinstalled and I am on to fix the other errors we have been experiencing.

Dial the Veritas technician line and asked to have your ticket referred to him.

 

[Southdraw]

Justin2000

here is the cnfgsvr.out file, it couldn't hurt to have an extra set of eyes. Appreciate the help and I found a lot of good tips in some of these threads.


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


Starting Service ...

SQL_Latin1_General_CP1_CI_AS

-m -Q -T4022 -T3659

Connecting to Server ...

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

Configuring Server ...

EXEC sp_grantlogin N'BUILTIN\Administrators'

[Microsoft][ODBC SQL Server Driver][SQL Server]Granted login access to 'BUILTIN\Administrators'.

EXEC sp_addsrvrolemember N'BUILTIN\Administrators', 'sysadmin'

[Microsoft][ODBC SQL Server Driver][SQL Server]'BUILTIN\Administrators' added to role 'sysadmin'.

update master.dbo.spt_server_info set attribute_value = @@version where attribute_id = 2

EXEC sp_detach_db 'pubs'

EXEC sp_detach_db 'Northwind'

EXEC sp_addserver N'EINSTEIN\BKUPEXEC', local

[Microsoft][ODBC SQL Server Driver][SQL Server]Password changed.

EXEC sp_configure 'allow updates', 1

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.

reconfigure with override

update master.dbo.sysaltfiles set size=1024 where name=N'tempdev'

EXEC sp_configure 'allow updates', 0

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator.

[Microsoft][ODBC SQL Server Driver][SQL Server]Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.

reconfigure with override

Disconnecting from Server ...

Stopping Service ...

SQL Server has been successfully configured!

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

 

[Alex1250]

I had the same problem. I finally copied the entire contents of the CD to a folder on the desktop and ran it from there with no errors. It seems the install is looking for a certian drive on some servers and fails.

Hope this helps!

 

[Southdraw]

After much trouble, I did get the backup exec reinstalled but could not get ole dc linkage because the files were corrupted for the ole db provider for sql server.

here is the final step that resolved my problem.


MS Help Desk:
Here is the case information for your records and for ease of reference should you need to re-open the issue.

Problem Description:

===========================================================

Unable to use a Data Link file to connect to a SQL Server database.

Cause:

============================================================

We concluded that the registry entries were corrupted, possibly by a 3rd party application.

Resolution:

============================================================

Replaced all the dll files in the Program Files\Common Files\System\Ole Db folder and registered all the dll files.


Problem fixed after 9 days and backups are running again.