Instance = "BkupExec" Error

Question

Post reply

Instance = "BkupExec" Error

SQL Galaxy

One Orange Chip

Points: 29472
More actions
December 20, 2010 at 2:12 am

#242536

Hi,
Two days back upgrade to SQL 2008 from SQL 2000. In task manager there are two sqlsrve.exe are running, I stoped one the the sql exe process. I thought this is backup exe process.
How to clear this error? I found in Application error log.
Date12/18/2010 8:31:14 AM
LogWindows NT (Application)
SourceBackup Exec
Category(0)
Event2684387712
Message
Adamm Database Error: Driver Connect Failure!
Error = ERROR_DATABASE_DOES_NOT_EXIST
Server = "JGSRVR55"
Active Node = ""
Instance = "BkupExec"
Database = "BEDB"
Thanks
ananda

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Bhuvnesh SSC Guru Points: 59351 More actions · Answer 1

Did you that exe restart it again ?

-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

SQL Galaxy One Orange Chip Points: 29472 More actions · Answer 2

Thanks for reply...

I don't want restart again that "BkupExec" Instance.

I don't know what is use of that instance, already running local instance in production database. so i want to uninstall "BkupExec", how to do that?

If I restart service "BkupExec" again this error will be gone.

Thanks

ananda

Cath Trimble SSCarpal Tunnel Points: 4201 More actions · Answer 3

To answer your question of why the instance is there, during BackupExec installation, unless it's pointed at an existing SQL Server instance to create the BEDB database it will install its own instance called BkupExec. If you're still using BackupExec to back that server up then either restart the BkupExec instance or reconfigure the application to use a different instance.