Problem installing on 2003 x64

[Daniel_Lane]

I've got a server that's been reloaded with 2003 x64 to support exchange 2007. Installing backup exec 11 on this server has been problematic.

Installation appears to complete successfully. However the Device & Media service will NOT start. Upon checking it failing in a "Database Recovery". The database is as far as I can tell fine.

I am using the included SQL server.


The Database Recovery Log follows:

Backup Exec Database Recovery
01/17/07 11:58:05
-----------------------------
Initializing...
BEGetComputerName = 'SERVER2'
GetBeVirtualServerName = ''
Using node name for media server
Data for BE database:
Structure size: 6504
Media Server : SERVER2
Node, if clust:
SQL Server : SERVER2
Instance Name : BkupExec
SQL Instance : SERVER2\BkupExec
SQL Service : MSSQL$BkupExec
Database : BEDB
App Data Path : C:\Program Files\Symantec\Backup Exec\Data
Database Path :
Database Log :
Database File : C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
Database Log : C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf
Backup File : C:\Program Files\Symantec\Backup Exec\Data\BEDB.bak
Base File : C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.bak
Base Log File : C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.bak
Is Local : TRUE
IsDatabaseMgr : TRUE
Recover database using best method..
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=server2\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80040154
Error connecting to master database: hr = 0x80040154
OS ERROR: 0x80040154 (-2147221164)
Status of database BEDB is unknown
Fixing up any database linkage problems for 'BEDB'
Execute command: declare @@stemp as varchar(32)
select @@stemp = isnull(convert(varchar,databasepropertyex('BEDB','status')),'NOT EXIST')
print 'Database status: ' + @@stemp
if @@stemp <> 'ONLINE' and @@stemp <> 'NOT EXIST'
begin
print 'Forcing database detach'
EXEC sp_detach_db 'BEDB'
end

OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=server2\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80040154
Error connecting to master database: hr = 0x80040154
Execute command failed: 0x80040154
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=server2\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80040154
Error connecting to master database: hr = 0x80040154
OS ERROR: 0x80040154 (-2147221164)
Status of database BEDB is unknown
File Exist Check: \\SERVER2\C$\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
File Exist: TRUE
Attach database BEDB
File Exist Check: \\SERVER2\C$\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
File Exist: TRUE
File Exist Check: \\SERVER2\C$\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf
File Exist: TRUE
Execute command: sp_attach_db 'BEDB','C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf','C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf'
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=server2\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80040154
Error connecting to master database: hr = 0x80040154
Execute command failed: 0x80040154
OS ERROR: 0x80040154 (-2147221164)
Deinitialize...

-----------------------------
Process completed
01/17/07 11:58:05
Status: DBU_ERROR_DATABASE_ATTACH_FAILED
-----------------------------

[Rich_Weber]

I have added the Registry values as string values and given them the appropriate values, paths, instance names etc.

I am still getting the same errors. I do notice that I have more than one database. One is just BEDB, and is formatted the way one would expect. Servername\bkupexec, etc. However, the other ones are formatted reportserver$bkupexec, and reportserver$bkupexectempdb respectively. Not sure if this is per design or not. I believe it is though.

Bediag still gives the same errors and beutility.exe says, "cannot create blank document."

The event log error is 58086, and reads as follows:

"The Backup Exec Device and Media Service could not start because the database recovery has failed. Refer to the database recovery log for details."

I also randomly receive error 17806 from source mssql$backupexec that reads:

SSPI handshake failed with error code 0x80090302 while establishing a connection with integrated security; the connection has been closed.

However this is odd because I have no instance name in sql server like this.

Regards,

Rich

Message Edited by Rich.Weber on 09-25-2007 10:02 AM

[JT_T]

:)
Over two years old problem, might not exist anymore.

[joydeepdutt]

...

[joydeepdutt]

...was posted by mistake :) ..it was not for this link
My mistake :)