Re: MSSQL problem with BackupExec

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I have uninstalled BackupExec with its own Uninstaller and removed all
components as far as I could see. The server rebooted normally afterwards
with no errors.
I then installed the MSDE separately as suggested in a BackUpExec newsgroup.
And that went fine as well and no errors occurred.
When I then reinstalled BackupExec, it did find the instance of the MSSQL
database and continued with the installtion without any error.
But after another required reboot, I got back the same error as before and
the MSSQL log looks the same as before.

I attach it here (IP x'ed out)
2006-04-19 09:54:05.46 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: Service Pack 1)

2006-04-19 09:54:05.46 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-04-19 09:54:05.46 server All rights reserved.
2006-04-19 09:54:05.46 server Server Process ID is 1260.
2006-04-19 09:54:05.46 server Logging SQL Server messages in file
'N:\Programme\veritas\msdeMSSQL$BKUPEXEC\LOG\ERRORLOG'.
2006-04-19 09:54:05.48 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-04-19 09:54:09.42 server SQL Server configured for thread mode
processing.
2006-04-19 09:54:09.45 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-04-19 09:54:09.81 spid2 Starting up database 'master'.
2006-04-19 09:54:21.75 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-04-19 09:54:21.75 spid5 Starting up database 'model'.
2006-04-19 09:54:21.79 server SQL server listening on xxx.xxx.xxx.xxx:
1053.
2006-04-19 09:54:21.79 server SQL server listening on 10.0.1.210: 1053.
2006-04-19 09:54:21.79 server SQL server listening on 127.0.0.1: 1053.
2006-04-19 09:54:21.79 spid2 Server name is 'ITONOTES\BKUPEXEC'.
2006-04-19 09:54:21.79 spid2 Skipping startup of clean database id 4
2006-04-19 09:54:21.79 spid2 Skipping startup of clean database id 5
2006-04-19 09:54:21.93 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-04-19 09:54:21.93 server SQL Server is ready for client connections
2006-04-19 09:54:25.85 spid5 Clearing tempdb database.
2006-04-19 09:54:29.31 spid5 Starting up database 'tempdb'.
2006-04-19 09:54:29.60 spid2 Recovery complete.
2006-04-19 09:54:29.60 spid2 SQL global counter collection task is
created.
2006-04-19 09:54:31.40 server ksconsole: Could not initialize console
operation.
2006-04-19 09:54:31.65 spid51 Starting up database 'BEDB'.:

I want to stress again, that my installation of the windows server is
standard and I have previously only installed a Lotus Domino server. And
everything was always fine and I never had any errors of any kind.

-UPI.


Hmmm. Googling turns up nothing obviously useful.

I'd try uninstalling BackupExec, making sure there are no traces of it,
rebooting and verifying that the SBS works properly with no unexpected
errors, and then try reinstalling it.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

.