cancel
Showing results for 
Search instead for 
Did you mean: 

error with MSSQL after installtion of BackupExec 10

Christian_Inner
Level 3
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.
7 REPLIES 7

priya_khire
Level 6
Hello,

Backup exec installs an MSDE instance which keeps the Backup exec database. Thus even if you don't have MSSQL installed, backup exec installs the MSDE.

In case you have problems installing this, look for any other specific errors in the MSDE_BKUPEXEC log. Also check for errors in the Windows event logs.Try installing it separately as per the steps in the technote below:

http://support.veritas.com/docs/263147

After installing MSDE, retry the installation of Backup exec.

Revert with details if issue persists.


Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.

Regards.

Christian_Inner
Level 3
I installed the MSDE separately as described in the previous answer. Everything went fine, no errors occured. I restarted the computer. No errors either in the Windows events log. Under services I checked and the MSSQL service was started automatically.

I then started BackupExec setup and followed all the steps. It did discover and instance of the MSSQL databse ("BackupExec") and proceeded with the installtion. After restart, however, the same error as always appeared and Windows reported that a service could not be started.

Again, I have no idea what the service that could not be started does. I don't even know whether it is a problem or not. But that just can't be right, can it?

Below I will put the MSDE_BACKUPEXEC log (again, my IP is xxx'ed):

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. Lock Blocks, 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'.

-chris.

shweta_rege
Level 6
Hello,


- What is the exact error message do you receive now?


******************************************************************
*****************************************************************

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.


Thanks.

Christian_Inner
Level 3
The exact error message in the windows log is:

18205:
ksconsole: Could not initialize console operation

And this has been the very exact error I always get after remove/reinstall of BackupExec.
The other log looks like what I've posted before.

-chris.

Deepali_Badave
Level 6
Employee
Hello,

Can you start the MSSQL$Bkupexec service?

Or Are you getting any error while starting it?

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

Christian_Inner
Level 3
I have walked through various possible solutions now with someone from Veritas support.
Sadly enough, we did not find any.
However, we have now set up BackupExec to backup data and that always worked without any problem.
So the Support Agent concluded that the error was maybe not an error but more of a warning.
I still think that's pretty odd. But since everything seems to work OK, I will rest content with that explanation for now.
Thanks for all the help offered here.
-chris.

shweta_rege
Level 6
Hello,


- Thank you for the update. Can we close the post now?


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered
and would be moved to answered questions pool.

*************************************************
************************************************