SQL Browser Errors Pain Domain Controller with BackupExec - sqlserver-tools
This is a discussion on SQL Browser Errors Pain Domain Controller with BackupExec - sqlserver-tools ; I have spend endless hours with Symantec Tier 2 support resolving the > SQL server issue but so no result. We have installed Backup Exec 12.0 > and all other componenets several time, Uninstall SQL server instance > and reinstall ...
![]() |
| | LinkBack | Thread Tools | Display Modes |
|
#1
| |||
| |||
| > SQL server issue but so no result. We have installed Backup Exec 12.0 > and all other componenets several time, Uninstall SQL server instance > and reinstall it but the error don't go away even with Fresh install > of SQL instance. > > The SQL configuration for SQL is inaccessible or invalid. Event ID:1 > > The configuration of the SQL instance MSSQLServer is not valid. Event > ID:2 > > The configuration of the AdminConnection\TCP protocol in the SQL > instance > BKUPEXEC is not valid. > Event ID:3 > Please Help !!!!!! > > Symantec have given up and asking me to contact Microsoft. Symantec > Technician told me that Microsoft will tell you to download the Latest > MSDE and attach the BACKUPEXE database to it. They like to know why > Fresh install of MSDE instance that is installed during the Backup > Exec installiong don't work? > |
|
#2
| |||
| |||
|
Not enough info to go on here. I understand that Backup Exec is a Symantec product. What version of SQL Server are you using. Since you say MSDE, does that mean you have SQL Server 2000 MSDE? Does the MSSQLServer service appear in the Services.msc applet? Is it started? What operating system are you using? Is any other version of SQL Server installed on this computer? Can you connect to the MSDE by using OSQL? -- Rick Byham (MSFT), SQL Server Books Online This posting is provided "AS IS" with no warranties, and confers no rights. "Kashif" news:5D592213-822E-4EFC-8EE6-48B6168B195A@microsoft.com... >I have spend endless hours with Symantec Tier 2 support resolving the >> SQL server issue but so no result. We have installed Backup Exec 12.0 >> and all other componenets several time, Uninstall SQL server instance >> and reinstall it but the error don't go away even with Fresh install >> of SQL instance. >> >> The SQL configuration for SQL is inaccessible or invalid. Event ID:1 >> >> The configuration of the SQL instance MSSQLServer is not valid. Event >> ID:2 >> >> The configuration of the AdminConnection\TCP protocol in the SQL >> instance >> BKUPEXEC is not valid. >> Event ID:3 >> Please Help !!!!!! >> >> Symantec have given up and asking me to contact Microsoft. Symantec >> Technician told me that Microsoft will tell you to download the Latest >> MSDE and attach the BACKUPEXE database to it. They like to know why >> Fresh install of MSDE instance that is installed during the Backup >> Exec installiong don't work? >> > |
|
#3
| |||
| |||
|
I am seeing the same thing, so i would be interested if anyone has some experience resolving this. Win Server 2k3 r2 standard x64 SP2 (NOT domain controller) bkupexec 12 sp2 quantum lto3 tape drive (dell autoloader atached via scsi to the server) I started researching this error message because the local full back up of c+sys state that I run on this server results in the server rebooting itself, in fact it rebooted itself 7 times over a 17 minute period last night. The sql error is one that shows after each reboot. "Rick Byham, (MSFT)" wrote: > Not enough info to go on here. I understand that Backup Exec is a Symantec > product. > What version of SQL Server are you using. Since you say MSDE, does that mean > you have SQL Server 2000 MSDE? > Does the MSSQLServer service appear in the Services.msc applet? Is it > started? > What operating system are you using? > Is any other version of SQL Server installed on this computer? > Can you connect to the MSDE by using OSQL? > -- > Rick Byham (MSFT), SQL Server Books Online > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Kashif" > news:5D592213-822E-4EFC-8EE6-48B6168B195A@microsoft.com... > >I have spend endless hours with Symantec Tier 2 support resolving the > >> SQL server issue but so no result. We have installed Backup Exec 12.0 > >> and all other componenets several time, Uninstall SQL server instance > >> and reinstall it but the error don't go away even with Fresh install > >> of SQL instance. > >> > >> The SQL configuration for SQL is inaccessible or invalid. Event ID:1 > >> > >> The configuration of the SQL instance MSSQLServer is not valid. Event > >> ID:2 > >> > >> The configuration of the AdminConnection\TCP protocol in the SQL > >> instance > >> BKUPEXEC is not valid. > >> Event ID:3 > >> Please Help !!!!!! > >> > >> Symantec have given up and asking me to contact Microsoft. Symantec > >> Technician told me that Microsoft will tell you to download the Latest > >> MSDE and attach the BACKUPEXE database to it. They like to know why > >> Fresh install of MSDE instance that is installed during the Backup > >> Exec installiong don't work? > >> > > > |
![]() |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
| |
All times are GMT -4. The time now is 03:36 AM.




Linear Mode