How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration for
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with its
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
Tim
Hi
"Tim Meltzer" wrote:

> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manager
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for example
> has nothing where I could configure a port address for communicating with its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did not
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John
|||Hi John,
thanks for input.

> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.

> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.
|||Hi Tim
"Tim Meltzer" wrote:

> Hi John,
> thanks for input.
>
> Which protocol? I tried them all, the error no. 3 remained.
>
> Yes, but I don't no, wether these IP settings are the right ones for Backup
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John

How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration fo
r
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with it
s
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
TimHi
"Tim Meltzer" wrote:

> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manag
er
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration
for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for exampl
e
> has nothing where I could configure a port address for communicating with
its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did n
ot
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John|||Hi John,
thanks for input.

> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.

> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.|||Hi Tim
"Tim Meltzer" wrote:

> Hi John,
> thanks for input.
>
> Which protocol? I tried them all, the error no. 3 remained.
>
> Yes, but I don't no, wether these IP settings are the right ones for Backu
p
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John

How to configure ports in SQL server configuration manager

Hi,
unfortunately I mixed up the ip settings in SQL server configuration manager
(I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
have an event in the application protocol (3), it says that configuration for
SQL instances "bkupexec" and "sqlexpress" are invalid.
I tried 100 different settings in SQL configuratin manager, but the events
are remaining. I cannot find out to configure this. Backup Exce for example
has nothing where I could configure a port address for communicating with its
SQL instance.
Can someone provide me with information about what to configure in SQL
Server Configuration Manager (and probably in Backup Exec - Symantec did not
answer until now) to avoid the error messages?
Thanx in advance,
TimHi
"Tim Meltzer" wrote:
> Hi,
> unfortunately I mixed up the ip settings in SQL server configuration manager
> (I'm running SBS 2003 R1 with Backup Exec 11d and SQL 2005 Express). Now I
> have an event in the application protocol (3), it says that configuration for
> SQL instances "bkupexec" and "sqlexpress" are invalid.
> I tried 100 different settings in SQL configuratin manager, but the events
> are remaining. I cannot find out to configure this. Backup Exce for example
> has nothing where I could configure a port address for communicating with its
> SQL instance.
> Can someone provide me with information about what to configure in SQL
> Server Configuration Manager (and probably in Backup Exec - Symantec did not
> answer until now) to avoid the error messages?
> Thanx in advance,
> Tim
By default SQLExpress will not have remote connections enabled. If you are
using a database on the same server then you should not need to enabled
TCP/IP.
Have you checked these instances of SQL Server are running using the service
applet or typing NET START at a command prompt?
In the Network Protocols branch under SQL Server Configuration Manager, is
the protocol Enabled? If you double click the tcp/ip entry that you will get
the IP and port settings in the properties dialog.
John|||Hi John,
thanks for input.
> In the Network Protocols branch under SQL Server Configuration Manager, is
> the protocol Enabled?
Which protocol? I tried them all, the error no. 3 remained.
> If you double click the tcp/ip entry that you will get
> the IP and port settings in the properties dialog.
Yes, but I don't no, wether these IP settings are the right ones for Backup
Exec, I don't know, what exactly it is what Windows is complaining about.
Finally I uninstalled BE and SQL Server and reinstalled it, but without
success.
You stated, that TCP is not needed if everything is running on one server.
So I think I'm going to ignore the message since everything seems to work.
Thanks again.|||Hi Tim
"Tim Meltzer" wrote:
> Hi John,
> thanks for input.
> > In the Network Protocols branch under SQL Server Configuration Manager, is
> > the protocol Enabled?
> Which protocol? I tried them all, the error no. 3 remained.
> > If you double click the tcp/ip entry that you will get
> > the IP and port settings in the properties dialog.
> Yes, but I don't no, wether these IP settings are the right ones for Backup
> Exec, I don't know, what exactly it is what Windows is complaining about.
> Finally I uninstalled BE and SQL Server and reinstalled it, but without
> success.
> You stated, that TCP is not needed if everything is running on one server.
> So I think I'm going to ignore the message since everything seems to work.
> Thanks again.
It is not clear where exactly where the error message is being displayed! Is
this in Backup exec, SQL Server error log or the Windows Event log?
If after installing Backup Exec again what protocols are enabled?
John

how to comment out a block of codes in SQL Query Analyzer?

Hello,
I know '--' can be used to comment out a single line. I tried /* and */ but
got the follow errors.
/*use master
go
exec sp_addlinkedsrvlogin
@.rmtsrvname = 'access',
@.useself = false,
@.locallogin = 'administrator',
@.rmtuser = 'admin',
@.rmtpassword = NULL
*/
Server: Msg 113, Level 15, State 1, Line 1
Missing end comment mark '*/'.
Server: Msg 170, Level 15, State 1, Line 8
Line 8: Incorrect syntax near '*'.
Thanks,
Bingbing wrote on Tue, 29 Nov 2005 09:02:15 -0800:
> Hello,
> I know '--' can be used to comment out a single line. I tried /* and */
> but got the follow errors.
> /*use master
> go
> exec sp_addlinkedsrvlogin
> @.rmtsrvname = 'access',
> @.useself = false,
> @.locallogin = 'administrator',
> @.rmtuser = 'admin',
> @.rmtpassword = NULL
> */
> Server: Msg 113, Level 15, State 1, Line 1
> Missing end comment mark '*/'.
> Server: Msg 170, Level 15, State 1, Line 8
> Line 8: Incorrect syntax near '*'.
> Thanks,
> Bing
The GO is being interpreted as a batch delimiter. Just add some additional
markers around the GO.
/*
use master
*/
go
/*
exec sp_addlinkedsrvlogin
@.rmtsrvname = 'access',
@.useself = false,
@.locallogin = 'administrator',
@.rmtuser = 'admin',
@.rmtpassword = NULL
*/
Dan|||"Daniel Crichton" wrote:
> bing wrote on Tue, 29 Nov 2005 09:02:15 -0800:
> > Hello,
> >
> > I know '--' can be used to comment out a single line. I tried /* and */
> > but got the follow errors.
> >
> > /*use master
> > go
> >
> > exec sp_addlinkedsrvlogin
> > @.rmtsrvname = 'access',
> > @.useself = false,
> > @.locallogin = 'administrator',
> > @.rmtuser = 'admin',
> > @.rmtpassword = NULL
> > */
> >
> > Server: Msg 113, Level 15, State 1, Line 1
> > Missing end comment mark '*/'.
> > Server: Msg 170, Level 15, State 1, Line 8
> > Line 8: Incorrect syntax near '*'.
> >
> > Thanks,
> >
> > Bing
>
> The GO is being interpreted as a batch delimiter. Just add some additional
> markers around the GO.
> /*
> use master
> */
> go
> /*
> exec sp_addlinkedsrvlogin
> @.rmtsrvname = 'access',
> @.useself = false,
> @.locallogin = 'administrator',
> @.rmtuser = 'admin',
> @.rmtpassword = NULL
> */
>
Ah, ok, thanks much for the heads-up.
Bing