Hi,
When I use NET PAUSE in cmd mode, the service pauses successfully but when I
issue NET START again, the service stays in pause state unless I use service
manager to start it.
Any help would be greatly appreciated,
LeilaYou need to use NET CONTINUE
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When I use NET PAUSE in cmd mode, the service pauses successfully but when
> I
> issue NET START again, the service stays in pause state unless I use
> service
> manager to start it.
> Any help would be greatly appreciated,
> Leila
>|||Thanks indeed!
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:#Jdojl8AGHA.360@.TK2MSFTNGP09.phx.gbl...
> You need to use NET CONTINUE
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
when[vbcol=seagreen]
>|||
>Hi,
>When I use NET PAUSE in cmd mode, the service pauses successfully but when
I
>issue NET START again, the service stays in pause state unless I use servic
e
>manager to start it.
>Any help would be greatly appreciated,
>Leila
>
>
You need to use NET CONTINUE. NET START won't do anything - it's already
started.
Cheers -
Simon
Showing posts with label pauses. Show all posts
Showing posts with label pauses. Show all posts
Wednesday, March 21, 2012
Pausing-Restarting SQL Server Service
Hi,
When I use NET PAUSE in cmd mode, the service pauses successfully but when I
issue NET START again, the service stays in pause state unless I use service
manager to start it.
Any help would be greatly appreciated,
LeilaYou need to use NET CONTINUE
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When I use NET PAUSE in cmd mode, the service pauses successfully but when
> I
> issue NET START again, the service stays in pause state unless I use
> service
> manager to start it.
> Any help would be greatly appreciated,
> Leila
>|||Thanks indeed!
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:#Jdojl8AGHA.360@.TK2MSFTNGP09.phx.gbl...
> You need to use NET CONTINUE
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> > Hi,
> > When I use NET PAUSE in cmd mode, the service pauses successfully but
when
> > I
> > issue NET START again, the service stays in pause state unless I use
> > service
> > manager to start it.
> > Any help would be greatly appreciated,
> > Leila
> >
> >
>|||>Hi,
>When I use NET PAUSE in cmd mode, the service pauses successfully but when I
>issue NET START again, the service stays in pause state unless I use service
>manager to start it.
>Any help would be greatly appreciated,
>Leila
>
>
You need to use NET CONTINUE. NET START won't do anything - it's already
started.
Cheers -
Simon
When I use NET PAUSE in cmd mode, the service pauses successfully but when I
issue NET START again, the service stays in pause state unless I use service
manager to start it.
Any help would be greatly appreciated,
LeilaYou need to use NET CONTINUE
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When I use NET PAUSE in cmd mode, the service pauses successfully but when
> I
> issue NET START again, the service stays in pause state unless I use
> service
> manager to start it.
> Any help would be greatly appreciated,
> Leila
>|||Thanks indeed!
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:#Jdojl8AGHA.360@.TK2MSFTNGP09.phx.gbl...
> You need to use NET CONTINUE
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> > Hi,
> > When I use NET PAUSE in cmd mode, the service pauses successfully but
when
> > I
> > issue NET START again, the service stays in pause state unless I use
> > service
> > manager to start it.
> > Any help would be greatly appreciated,
> > Leila
> >
> >
>|||>Hi,
>When I use NET PAUSE in cmd mode, the service pauses successfully but when I
>issue NET START again, the service stays in pause state unless I use service
>manager to start it.
>Any help would be greatly appreciated,
>Leila
>
>
You need to use NET CONTINUE. NET START won't do anything - it's already
started.
Cheers -
Simon
Pausing-Restarting SQL Server Service
Hi,
When I use NET PAUSE in cmd mode, the service pauses successfully but when I
issue NET START again, the service stays in pause state unless I use service
manager to start it.
Any help would be greatly appreciated,
Leila
You need to use NET CONTINUE
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When I use NET PAUSE in cmd mode, the service pauses successfully but when
> I
> issue NET START again, the service stays in pause state unless I use
> service
> manager to start it.
> Any help would be greatly appreciated,
> Leila
>
|||Thanks indeed!
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:#Jdojl8AGHA.360@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> You need to use NET CONTINUE
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
when
>
|||
>Hi,
>When I use NET PAUSE in cmd mode, the service pauses successfully but when I
>issue NET START again, the service stays in pause state unless I use service
>manager to start it.
>Any help would be greatly appreciated,
>Leila
>
>
You need to use NET CONTINUE. NET START won't do anything - it's already
started.
Cheers -
Simon
sql
When I use NET PAUSE in cmd mode, the service pauses successfully but when I
issue NET START again, the service stays in pause state unless I use service
manager to start it.
Any help would be greatly appreciated,
Leila
You need to use NET CONTINUE
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When I use NET PAUSE in cmd mode, the service pauses successfully but when
> I
> issue NET START again, the service stays in pause state unless I use
> service
> manager to start it.
> Any help would be greatly appreciated,
> Leila
>
|||Thanks indeed!
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:#Jdojl8AGHA.360@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> You need to use NET CONTINUE
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
when
>
|||
>Hi,
>When I use NET PAUSE in cmd mode, the service pauses successfully but when I
>issue NET START again, the service stays in pause state unless I use service
>manager to start it.
>Any help would be greatly appreciated,
>Leila
>
>
You need to use NET CONTINUE. NET START won't do anything - it's already
started.
Cheers -
Simon
sql
Pausing-Restarting SQL Server Service
Hi,
When I use NET PAUSE in cmd mode, the service pauses successfully but when I
issue NET START again, the service stays in pause state unless I use service
manager to start it.
Any help would be greatly appreciated,
LeilaYou need to use NET CONTINUE
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When I use NET PAUSE in cmd mode, the service pauses successfully but when
> I
> issue NET START again, the service stays in pause state unless I use
> service
> manager to start it.
> Any help would be greatly appreciated,
> Leila
>|||Thanks indeed!
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:#Jdojl8AGHA.360@.TK2MSFTNGP09.phx.gbl...
> You need to use NET CONTINUE
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
when
>|||
>Hi,
>When I use NET PAUSE in cmd mode, the service pauses successfully but when
I
>issue NET START again, the service stays in pause state unless I use servic
e
>manager to start it.
>Any help would be greatly appreciated,
>Leila
>
>
You need to use NET CONTINUE. NET START won't do anything - it's already
started.
Cheers -
Simon
When I use NET PAUSE in cmd mode, the service pauses successfully but when I
issue NET START again, the service stays in pause state unless I use service
manager to start it.
Any help would be greatly appreciated,
LeilaYou need to use NET CONTINUE
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Leila" <Leilas@.hotpop.com> wrote in message
news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
> Hi,
> When I use NET PAUSE in cmd mode, the service pauses successfully but when
> I
> issue NET START again, the service stays in pause state unless I use
> service
> manager to start it.
> Any help would be greatly appreciated,
> Leila
>|||Thanks indeed!
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:#Jdojl8AGHA.360@.TK2MSFTNGP09.phx.gbl...
> You need to use NET CONTINUE
> --
> HTH
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Leila" <Leilas@.hotpop.com> wrote in message
> news:%23eb9TK6AGHA.984@.TK2MSFTNGP12.phx.gbl...
when
>|||
>Hi,
>When I use NET PAUSE in cmd mode, the service pauses successfully but when
I
>issue NET START again, the service stays in pause state unless I use servic
e
>manager to start it.
>Any help would be greatly appreciated,
>Leila
>
>
You need to use NET CONTINUE. NET START won't do anything - it's already
started.
Cheers -
Simon
Pauses in SQL 2000
I am running SQL 2000 SP3 on a Windows 2003 server. I am
having problems with pauses in my application software. I
put a protocol analyzer on the switch and I am getting no
data error but I am getting a large amount of SQL
retries. It this normal? Has anyone seen this problem
before?
Thanks,
Jason Mobley
Technology Director
NWFL Daily NewsRetries sound like client connection issues. What I would do is try and
isolate a client machine, and see if you could load SQL client tools. Then
you could run SQL Client Network Utiltiy and compare it to SQL Server
Network Utility on the server. Sometimes the TCP/IP sockets port gets
changed from the default port of 1433, or firewalls block it. In that case,
the clients will switch from TCP/IP sockets to Named Pipes, or conceivably
keep trying to connect. I would investigat that. Even though Named Pipes
seems to be a default, I've seen a lot of clients out there default to
TCP/IP sockets, especially when going to ODBC Data Sources in control panel
and configuring a SQL Server System DSN (client configuration on the login
credential screen shows you what is being used for connections as well).
Read this article for information on Named Pipes and TCP/IP sockets
http://msdn.microsoft.com/library/d.../>
1a_7fcj.asp
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Jmobley" <anonymous@.discussions.microsoft.com> wrote in message
news:6e1801c3e75a$3c080fa0$a301280a@.phx.gbl...
having problems with pauses in my application software. I
put a protocol analyzer on the switch and I am getting no
data error but I am getting a large amount of SQL
retries. It this normal? Has anyone seen this problem
before?
Thanks,
Jason Mobley
Technology Director
NWFL Daily NewsRetries sound like client connection issues. What I would do is try and
isolate a client machine, and see if you could load SQL client tools. Then
you could run SQL Client Network Utiltiy and compare it to SQL Server
Network Utility on the server. Sometimes the TCP/IP sockets port gets
changed from the default port of 1433, or firewalls block it. In that case,
the clients will switch from TCP/IP sockets to Named Pipes, or conceivably
keep trying to connect. I would investigat that. Even though Named Pipes
seems to be a default, I've seen a lot of clients out there default to
TCP/IP sockets, especially when going to ODBC Data Sources in control panel
and configuring a SQL Server System DSN (client configuration on the login
credential screen shows you what is being used for connections as well).
Read this article for information on Named Pipes and TCP/IP sockets
http://msdn.microsoft.com/library/d.../>
1a_7fcj.asp
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Jmobley" <anonymous@.discussions.microsoft.com> wrote in message
news:6e1801c3e75a$3c080fa0$a301280a@.phx.gbl...
quote:
> I am running SQL 2000 SP3 on a Windows 2003 server. I am
> having problems with pauses in my application software. I
> put a protocol analyzer on the switch and I am getting no
> data error but I am getting a large amount of SQL
> retries. It this normal? Has anyone seen this problem
> before?
> Thanks,
> Jason Mobley
> Technology Director
> NWFL Daily News
>
Subscribe to:
Posts (Atom)