Christian_Inner
20 years agoLevel 3
error with MSSQL after installtion of BackupExec 10
Hi there,
I have a Windows Server 2003 installation and have never used MSSQL before.
I just bought the most current version of BackupExec 10 with Lotus Notes Agent and tried to install it. Everything went fine, but after rebooting, the system returned an error that one service could not be started. The actual error is at the end:
Type: error
Source:MSSQL$BKUPEXEC
Category:(2)
ID:17055
Date:06.04.2006
Time:17:59:04
Description:
18205 :
ksconsole: Could not initialize console operation.
The SQL log reads like this (I changed the IP):
2006-04-13 11:37:13.42 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-13 11:37:13.42 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-04-13 11:37:13.42 server All rights reserved.
2006-04-13 11:37:13.42 server Server Process ID is 1100.
2006-04-13 11:37:13.42 server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL$BKUPEXEC\LOG\ERRORLOG'.
2006-04-13 11:37:13.45 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2006-04-13 11:37:13.60 server SQL Server configured for thread mode processing.
2006-04-13 11:37:13.60 server Using dynamic lock allocation. Lock Blocks, Lock Owner Blocks.
2006-04-13 11:37:13.82 spid4 Starting up database 'master'.
2006-04-13 11:37:14.26 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-04-13 11:37:14.26 spid5 Starting up database 'model'.
2006-04-13 11:37:14.54 spid4 Server name is 'ITONOTES\BKUPEXEC'.
2006-04-13 11:37:14.54 spid4 Skipping startup of clean database id 4
2006-04-13 11:37:14.54 spid4 Skipping startup of clean database id 5
2006-04-13 11:37:15.09 server SQL server listening on xx.xx.xx.xx: 1401.
2006-04-13 11:37:15.12 server SQL server listening on 10.0.1.210: 1401.
2006-04-13 11:37:15.12 server SQL server listening on 127.0.0.1: 1401.
2006-04-13 11:37:16.73 server SQL server listening on TCP, Shared Memory, Named Pipes.
2006-04-13 11:37:16.73 server SQL Server is ready for client connections
2006-04-13 11:37:18.18 spid5 Clearing tempdb database.
2006-04-13 11:37:33.56 spid5 Starting up database 'tempdb'.
2006-04-13 11:37:34.23 spid4 Recovery complete.
2006-04-13 11:37:34.23 spid4 SQL global counter collection task is created.
2006-04-13 11:37:36.59 spid51 Starting up database 'BEDB'.
2006-04-13 11:37:41.68 server ksconsole: Could not initialize console operation.
Support from Symanted told me to contact MS.
But I fail to see how that could not be a problem with BackupExec as I've never used MSSQL and have a standard installtion of Windows.
Any ideas? Please help!
-chris.
I have a Windows Server 2003 installation and have never used MSSQL before.
I just bought the most current version of BackupExec 10 with Lotus Notes Agent and tried to install it. Everything went fine, but after rebooting, the system returned an error that one service could not be started. The actual error is at the end:
Type: error
Source:MSSQL$BKUPEXEC
Category:(2)
ID:17055
Date:06.04.2006
Time:17:59:04
Description:
18205 :
ksconsole: Could not initialize console operation.
The SQL log reads like this (I changed the IP):
2006-04-13 11:37:13.42 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-13 11:37:13.42 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-04-13 11:37:13.42 server All rights reserved.
2006-04-13 11:37:13.42 server Server Process ID is 1100.
2006-04-13 11:37:13.42 server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL$BKUPEXEC\LOG\ERRORLOG'.
2006-04-13 11:37:13.45 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2006-04-13 11:37:13.60 server SQL Server configured for thread mode processing.
2006-04-13 11:37:13.60 server Using dynamic lock allocation. Lock Blocks, Lock Owner Blocks.
2006-04-13 11:37:13.82 spid4 Starting up database 'master'.
2006-04-13 11:37:14.26 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-04-13 11:37:14.26 spid5 Starting up database 'model'.
2006-04-13 11:37:14.54 spid4 Server name is 'ITONOTES\BKUPEXEC'.
2006-04-13 11:37:14.54 spid4 Skipping startup of clean database id 4
2006-04-13 11:37:14.54 spid4 Skipping startup of clean database id 5
2006-04-13 11:37:15.09 server SQL server listening on xx.xx.xx.xx: 1401.
2006-04-13 11:37:15.12 server SQL server listening on 10.0.1.210: 1401.
2006-04-13 11:37:15.12 server SQL server listening on 127.0.0.1: 1401.
2006-04-13 11:37:16.73 server SQL server listening on TCP, Shared Memory, Named Pipes.
2006-04-13 11:37:16.73 server SQL Server is ready for client connections
2006-04-13 11:37:18.18 spid5 Clearing tempdb database.
2006-04-13 11:37:33.56 spid5 Starting up database 'tempdb'.
2006-04-13 11:37:34.23 spid4 Recovery complete.
2006-04-13 11:37:34.23 spid4 SQL global counter collection task is created.
2006-04-13 11:37:36.59 spid51 Starting up database 'BEDB'.
2006-04-13 11:37:41.68 server ksconsole: Could not initialize console operation.
Support from Symanted told me to contact MS.
But I fail to see how that could not be a problem with BackupExec as I've never used MSSQL and have a standard installtion of Windows.
Any ideas? Please help!
-chris.