I have an MSDE 2000 installation on Windows 2000 Pro.
Can anyone give me any ideas why when I execute this command
RAISERROR('Test Error', 16, 1)
The corresponding severity level 16 Alert isn't fired?
Thanks
Phill
hi Phill,
Phill wrote:
> I have an MSDE 2000 installation on Windows 2000 Pro.
> Can anyone give me any ideas why when I execute this command
> RAISERROR('Test Error', 16, 1)
> The corresponding severity level 16 Alert isn't fired?
please modify your code as
RAISERROR('Test Error', 16, 1) WITH LOG
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Ok, that still doesn't fire the alert though.
"Andrea Montanari" wrote:
> hi Phill,
> Phill wrote:
> please modify your code as
> RAISERROR('Test Error', 16, 1) WITH LOG
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Phill,
Phill wrote:
> Ok, that still doesn't fire the alert though.
>
is th SQL Server Agent running?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Yes the Agent is running.
It has 3 scheduled jobs that run every night. One of the jobs performs a
DBCC DBREINDEX as one one of 6 steps. This step fails because the database
size has reached 2gb. The other 2 jobs run without problems.
However as far as the server is concered the alerts didn't happen.
"Andrea Montanari" wrote:
> hi Phill,
> Phill wrote:
> is th SQL Server Agent running?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Hello,
For a stored procedure in vb6, I know that the first line of the stored
procedure must be
SET NOCOUNT ON
if there is more than one select. If you don't do it, vb 6 can't receive
the error in a stored procedure.
Perhaps you can try with that.
Marc Allard
Allcomp
Phill wrote:[vbcol=seagreen]
> Yes the Agent is running.
> It has 3 scheduled jobs that run every night. One of the jobs performs a
> DBCC DBREINDEX as one one of 6 steps. This step fails because the database
> size has reached 2gb. The other 2 jobs run without problems.
> However as far as the server is concered the alerts didn't happen.
>
> "Andrea Montanari" wrote:
>
Showing posts with label installation. Show all posts
Showing posts with label installation. Show all posts
Sunday, March 25, 2012
Friday, February 24, 2012
agent entries in registry missing after restore
Hi,
We had to back-up and restore a server due to an error
during installation regarding disk partitioning.
The server is completely restored where rights to files
have been restred and all files are in the same location
(MS Back-up). Everything seems to be working fine, except
for MS SQL server.
No MS SQL servers are available to log-on to.
Event messages 322, 19011, 208, 203, 17177 etc. appear
sample of event 322:
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: (4)
Event ID: 322
Date: 1/22/2004
Time: 12:50:14 PM
User: N/A
Computer: BLUE
Description:
The description for Event ID ( 322 ) in Source (
SQLSERVERAGENT ) cannot be found. The local computer may
not have the necessary registry information or message DLL
files to display messages from a remote computer. The
following information is part of the event: 19002,
MSSQLSERVER.
---
So the question is: he registry seems to be restored
properly, but somehow SQL server entries are not found. I
did not take a copy of the registry. Prior to deleting it.
Am I suffering a rights problem or a registry restore
problem?
Any ideas are very much appreciated!
Thanks,
SamYou can try to rebuild the registry entries, if this is the problem. When
you start the SQL Server Setup, you will find a
Rebuild Registry Option in the Advanced Setup Options.
Cheers,
Herbert
"Sam Jaarsma" <sam@.grupoamengual.com.nospam> schrieb im Newsbeitrag
news:2bb101c3e191$e3a27c10$a001280a@.phx.gbl...
We had to back-up and restore a server due to an error
during installation regarding disk partitioning.
The server is completely restored where rights to files
have been restred and all files are in the same location
(MS Back-up). Everything seems to be working fine, except
for MS SQL server.
No MS SQL servers are available to log-on to.
Event messages 322, 19011, 208, 203, 17177 etc. appear
sample of event 322:
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: (4)
Event ID: 322
Date: 1/22/2004
Time: 12:50:14 PM
User: N/A
Computer: BLUE
Description:
The description for Event ID ( 322 ) in Source (
SQLSERVERAGENT ) cannot be found. The local computer may
not have the necessary registry information or message DLL
files to display messages from a remote computer. The
following information is part of the event: 19002,
MSSQLSERVER.
---
So the question is: he registry seems to be restored
properly, but somehow SQL server entries are not found. I
did not take a copy of the registry. Prior to deleting it.
Am I suffering a rights problem or a registry restore
problem?
Any ideas are very much appreciated!
Thanks,
SamYou can try to rebuild the registry entries, if this is the problem. When
you start the SQL Server Setup, you will find a
Rebuild Registry Option in the Advanced Setup Options.
Cheers,
Herbert
"Sam Jaarsma" <sam@.grupoamengual.com.nospam> schrieb im Newsbeitrag
news:2bb101c3e191$e3a27c10$a001280a@.phx.gbl...
quote:
> Hi,
> We had to back-up and restore a server due to an error
> during installation regarding disk partitioning.
> The server is completely restored where rights to files
> have been restred and all files are in the same location
> (MS Back-up). Everything seems to be working fine, except
> for MS SQL server.
> No MS SQL servers are available to log-on to.
> Event messages 322, 19011, 208, 203, 17177 etc. appear
> sample of event 322:
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: (4)
> Event ID: 322
> Date: 1/22/2004
> Time: 12:50:14 PM
> User: N/A
> Computer: BLUE
> Description:
> The description for Event ID ( 322 ) in Source (
> SQLSERVERAGENT ) cannot be found. The local computer may
> not have the necessary registry information or message DLL
> files to display messages from a remote computer. The
> following information is part of the event: 19002,
> MSSQLSERVER.
> ---
> So the question is: he registry seems to be restored
> properly, but somehow SQL server entries are not found. I
> did not take a copy of the registry. Prior to deleting it.
> Am I suffering a rights problem or a registry restore
> problem?
> Any ideas are very much appreciated!
> Thanks,
> Sam
>
agent entries in registry missing after restore
Hi,
We had to back-up and restore a server due to an error
during installation regarding disk partitioning.
The server is completely restored where rights to files
have been restred and all files are in the same location
(MS Back-up). Everything seems to be working fine, except
for MS SQL server.
No MS SQL servers are available to log-on to.
Event messages 322, 19011, 208, 203, 17177 etc. appear
sample of event 322:
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: (4)
Event ID: 322
Date: 1/22/2004
Time: 12:50:14 PM
User: N/A
Computer: BLUE
Description:
The description for Event ID ( 322 ) in Source (
SQLSERVERAGENT ) cannot be found. The local computer may
not have the necessary registry information or message DLL
files to display messages from a remote computer. The
following information is part of the event: 19002,
MSSQLSERVER.
---
So the question is: he registry seems to be restored
properly, but somehow SQL server entries are not found. I
did not take a copy of the registry. Prior to deleting it.
Am I suffering a rights problem or a registry restore
problem?
Any ideas are very much appreciated!
Thanks,
SamYou can try to rebuild the registry entries, if this is the problem. When
you start the SQL Server Setup, you will find a
Rebuild Registry Option in the Advanced Setup Options.
Cheers,
Herbert
"Sam Jaarsma" <sam@.grupoamengual.com.nospam> schrieb im Newsbeitrag
news:2bb101c3e191$e3a27c10$a001280a@.phx.gbl...
> Hi,
> We had to back-up and restore a server due to an error
> during installation regarding disk partitioning.
> The server is completely restored where rights to files
> have been restred and all files are in the same location
> (MS Back-up). Everything seems to be working fine, except
> for MS SQL server.
> No MS SQL servers are available to log-on to.
> Event messages 322, 19011, 208, 203, 17177 etc. appear
> sample of event 322:
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: (4)
> Event ID: 322
> Date: 1/22/2004
> Time: 12:50:14 PM
> User: N/A
> Computer: BLUE
> Description:
> The description for Event ID ( 322 ) in Source (
> SQLSERVERAGENT ) cannot be found. The local computer may
> not have the necessary registry information or message DLL
> files to display messages from a remote computer. The
> following information is part of the event: 19002,
> MSSQLSERVER.
> ---
> So the question is: he registry seems to be restored
> properly, but somehow SQL server entries are not found. I
> did not take a copy of the registry. Prior to deleting it.
> Am I suffering a rights problem or a registry restore
> problem?
> Any ideas are very much appreciated!
> Thanks,
> Sam
>
We had to back-up and restore a server due to an error
during installation regarding disk partitioning.
The server is completely restored where rights to files
have been restred and all files are in the same location
(MS Back-up). Everything seems to be working fine, except
for MS SQL server.
No MS SQL servers are available to log-on to.
Event messages 322, 19011, 208, 203, 17177 etc. appear
sample of event 322:
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: (4)
Event ID: 322
Date: 1/22/2004
Time: 12:50:14 PM
User: N/A
Computer: BLUE
Description:
The description for Event ID ( 322 ) in Source (
SQLSERVERAGENT ) cannot be found. The local computer may
not have the necessary registry information or message DLL
files to display messages from a remote computer. The
following information is part of the event: 19002,
MSSQLSERVER.
---
So the question is: he registry seems to be restored
properly, but somehow SQL server entries are not found. I
did not take a copy of the registry. Prior to deleting it.
Am I suffering a rights problem or a registry restore
problem?
Any ideas are very much appreciated!
Thanks,
SamYou can try to rebuild the registry entries, if this is the problem. When
you start the SQL Server Setup, you will find a
Rebuild Registry Option in the Advanced Setup Options.
Cheers,
Herbert
"Sam Jaarsma" <sam@.grupoamengual.com.nospam> schrieb im Newsbeitrag
news:2bb101c3e191$e3a27c10$a001280a@.phx.gbl...
> Hi,
> We had to back-up and restore a server due to an error
> during installation regarding disk partitioning.
> The server is completely restored where rights to files
> have been restred and all files are in the same location
> (MS Back-up). Everything seems to be working fine, except
> for MS SQL server.
> No MS SQL servers are available to log-on to.
> Event messages 322, 19011, 208, 203, 17177 etc. appear
> sample of event 322:
> Event Type: Error
> Event Source: SQLSERVERAGENT
> Event Category: (4)
> Event ID: 322
> Date: 1/22/2004
> Time: 12:50:14 PM
> User: N/A
> Computer: BLUE
> Description:
> The description for Event ID ( 322 ) in Source (
> SQLSERVERAGENT ) cannot be found. The local computer may
> not have the necessary registry information or message DLL
> files to display messages from a remote computer. The
> following information is part of the event: 19002,
> MSSQLSERVER.
> ---
> So the question is: he registry seems to be restored
> properly, but somehow SQL server entries are not found. I
> did not take a copy of the registry. Prior to deleting it.
> Am I suffering a rights problem or a registry restore
> problem?
> Any ideas are very much appreciated!
> Thanks,
> Sam
>
Sunday, February 19, 2012
After Restore Master DB, User can't logon
Dear all,
My Lab has one SQL Server which used by ApplicationA, during
the installation process of ApplicationA, ApplicationA will
add New Logins for one local user group, and add one domain
useraccount to be a member of this local user group, i want
to simulate disaster rescovery of ApplicationA, so i do the
steps listed bellow:
(1) backup all related SQL database, inclued Master DB Full Backup
(2) Install one new Windows 2003 Server
(3) create local user group used by ApplicationA
(4) Install SQL Server and SP3a in this new Server, and every
installation options is the same as old server
(5) Install ApplicationA
(6) Restore all Database from backup media
(7) make sure no error happend when restore
after restore database, domain user account which is a member
of that local user group can't logon go SQL Server, when use SQL
Query Analyzer, error message appear:
can't connect to server SQLServerName:
Server:Message18456,Level16,Status1
Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
if i delete SQL logins for that local user group, and then new logins
for that local user group, the domain user account can logon successfully,
so i think although the name of local user gorup is the same, but
the sid of local user gorup is different, because this is the new Windows
2003 Server.
Am i right? if i'm right, anything i can do to resolve this problem
thanks for any reply
Rico
Problems about orphaned users ?
http://msdn.microsoft.com/library/de...tabse_0ttf.asp
http://vyaskn.tripod.com/troubleshoo...phan_users.htm
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Rico" <rico_chang@.msn.com> schrieb im Newsbeitrag
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right? if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>
|||Hi
Yes, the SID is different.
You are in a domain, so why are you using local groups? As you see, in a DR
scenario, it becomes difficult to work with. If this was a cluster, you
would have the same problems.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rico" <rico_chang@.msn.com> wrote in message
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right? if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>
|||Dear Mike,
thanks for your reply, in fact, ApplicationA means MOM Server 2005,
MOM Server will create some local groups
Rico
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> glsD:uKfxmfhWFHA.3584@.TK2MSFTNGP14.phx.g bl...
> Hi
> Yes, the SID is different.
> You are in a domain, so why are you using local groups? As you see, in a
> DR scenario, it becomes difficult to work with. If this was a cluster, you
> would have the same problems.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Rico" <rico_chang@.msn.com> wrote in message
> news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
>
My Lab has one SQL Server which used by ApplicationA, during
the installation process of ApplicationA, ApplicationA will
add New Logins for one local user group, and add one domain
useraccount to be a member of this local user group, i want
to simulate disaster rescovery of ApplicationA, so i do the
steps listed bellow:
(1) backup all related SQL database, inclued Master DB Full Backup
(2) Install one new Windows 2003 Server
(3) create local user group used by ApplicationA
(4) Install SQL Server and SP3a in this new Server, and every
installation options is the same as old server
(5) Install ApplicationA
(6) Restore all Database from backup media
(7) make sure no error happend when restore
after restore database, domain user account which is a member
of that local user group can't logon go SQL Server, when use SQL
Query Analyzer, error message appear:
can't connect to server SQLServerName:
Server:Message18456,Level16,Status1
Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
if i delete SQL logins for that local user group, and then new logins
for that local user group, the domain user account can logon successfully,
so i think although the name of local user gorup is the same, but
the sid of local user gorup is different, because this is the new Windows
2003 Server.
Am i right? if i'm right, anything i can do to resolve this problem
thanks for any reply
Rico
Problems about orphaned users ?
http://msdn.microsoft.com/library/de...tabse_0ttf.asp
http://vyaskn.tripod.com/troubleshoo...phan_users.htm
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Rico" <rico_chang@.msn.com> schrieb im Newsbeitrag
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right? if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>
|||Hi
Yes, the SID is different.
You are in a domain, so why are you using local groups? As you see, in a DR
scenario, it becomes difficult to work with. If this was a cluster, you
would have the same problems.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rico" <rico_chang@.msn.com> wrote in message
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right? if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>
|||Dear Mike,
thanks for your reply, in fact, ApplicationA means MOM Server 2005,
MOM Server will create some local groups
Rico
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> glsD:uKfxmfhWFHA.3584@.TK2MSFTNGP14.phx.g bl...
> Hi
> Yes, the SID is different.
> You are in a domain, so why are you using local groups? As you see, in a
> DR scenario, it becomes difficult to work with. If this was a cluster, you
> would have the same problems.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Rico" <rico_chang@.msn.com> wrote in message
> news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
>
Thursday, February 16, 2012
After Restore Master DB, User can't logon
Dear all,
My Lab has one SQL Server which used by ApplicationA, during
the installation process of ApplicationA, ApplicationA will
add New Logins for one local user group, and add one domain
useraccount to be a member of this local user group, i want
to simulate disaster rescovery of ApplicationA, so i do the
steps listed bellow:
(1) backup all related SQL database, inclued Master DB Full Backup
(2) Install one new Windows 2003 Server
(3) create local user group used by ApplicationA
(4) Install SQL Server and SP3a in this new Server, and every
installation options is the same as old server
(5) Install ApplicationA
(6) Restore all Database from backup media
(7) make sure no error happend when restore
after restore database, domain user account which is a member
of that local user group can't logon go SQL Server, when use SQL
Query Analyzer, error message appear:
can't connect to server SQLServerName:
Server:Message18456,Level16,Status1
Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon fai
led
if i delete SQL logins for that local user group, and then new logins
for that local user group, the domain user account can logon successfully,
so i think although the name of local user gorup is the same, but
the sid of local user gorup is different, because this is the new Windows
2003 Server.
Am i right' if i'm right, anything i can do to resolve this problem
thanks for any reply
RicoProblems about orphaned users ?
http://msdn.microsoft.com/library/d...
tabse_0ttf.asp
http://vyaskn.tripod.com/troublesho...rphan_users.htm
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Rico" <rico_chang@.msn.com> schrieb im Newsbeitrag
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon f
ailed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right' if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>|||Hi
Yes, the SID is different.
You are in a domain, so why are you using local groups? As you see, in a DR
scenario, it becomes difficult to work with. If this was a cluster, you
would have the same problems.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rico" <rico_chang@.msn.com> wrote in message
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon f
ailed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right' if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>|||Dear Mike,
thanks for your reply, in fact, ApplicationA means MOM Server 2005,
MOM Server will create some local groups
Rico
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> glsD:uKfxmfhWFHA.3584@.TK2MSFTNGP14.p
hx.gbl...
> Hi
> Yes, the SID is different.
> You are in a domain, so why are you using local groups? As you see, in a
> DR scenario, it becomes difficult to work with. If this was a cluster, you
> would have the same problems.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Rico" <rico_chang@.msn.com> wrote in message
> news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
>
My Lab has one SQL Server which used by ApplicationA, during
the installation process of ApplicationA, ApplicationA will
add New Logins for one local user group, and add one domain
useraccount to be a member of this local user group, i want
to simulate disaster rescovery of ApplicationA, so i do the
steps listed bellow:
(1) backup all related SQL database, inclued Master DB Full Backup
(2) Install one new Windows 2003 Server
(3) create local user group used by ApplicationA
(4) Install SQL Server and SP3a in this new Server, and every
installation options is the same as old server
(5) Install ApplicationA
(6) Restore all Database from backup media
(7) make sure no error happend when restore
after restore database, domain user account which is a member
of that local user group can't logon go SQL Server, when use SQL
Query Analyzer, error message appear:
can't connect to server SQLServerName:
Server:Message18456,Level16,Status1
Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon fai
led
if i delete SQL logins for that local user group, and then new logins
for that local user group, the domain user account can logon successfully,
so i think although the name of local user gorup is the same, but
the sid of local user gorup is different, because this is the new Windows
2003 Server.
Am i right' if i'm right, anything i can do to resolve this problem
thanks for any reply
RicoProblems about orphaned users ?
http://msdn.microsoft.com/library/d...
tabse_0ttf.asp
http://vyaskn.tripod.com/troublesho...rphan_users.htm
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Rico" <rico_chang@.msn.com> schrieb im Newsbeitrag
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon f
ailed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right' if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>|||Hi
Yes, the SID is different.
You are in a domain, so why are you using local groups? As you see, in a DR
scenario, it becomes difficult to work with. If this was a cluster, you
would have the same problems.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rico" <rico_chang@.msn.com> wrote in message
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon f
ailed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right' if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>|||Dear Mike,
thanks for your reply, in fact, ApplicationA means MOM Server 2005,
MOM Server will create some local groups
Rico
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> glsD:uKfxmfhWFHA.3584@.TK2MSFTNGP14.p
hx.gbl...
> Hi
> Yes, the SID is different.
> You are in a domain, so why are you using local groups? As you see, in a
> DR scenario, it becomes difficult to work with. If this was a cluster, you
> would have the same problems.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Rico" <rico_chang@.msn.com> wrote in message
> news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
>
After Restore Master DB, User can't logon
Dear all,
My Lab has one SQL Server which used by ApplicationA, during
the installation process of ApplicationA, ApplicationA will
add New Logins for one local user group, and add one domain
useraccount to be a member of this local user group, i want
to simulate disaster rescovery of ApplicationA, so i do the
steps listed bellow:
(1) backup all related SQL database, inclued Master DB Full Backup
(2) Install one new Windows 2003 Server
(3) create local user group used by ApplicationA
(4) Install SQL Server and SP3a in this new Server, and every
installation options is the same as old server
(5) Install ApplicationA
(6) Restore all Database from backup media
(7) make sure no error happend when restore
after restore database, domain user account which is a member
of that local user group can't logon go SQL Server, when use SQL
Query Analyzer, error message appear:
can't connect to server SQLServerName:
Server:Message18456,Level16,Status1
Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
if i delete SQL logins for that local user group, and then new logins
for that local user group, the domain user account can logon successfully,
so i think although the name of local user gorup is the same, but
the sid of local user gorup is different, because this is the new Windows
2003 Server.
Am i right' if i'm right, anything i can do to resolve this problem
thanks for any reply
RicoProblems about orphaned users ?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servdatabse_0ttf.asp
http://vyaskn.tripod.com/troubleshooting_orphan_users.htm
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Rico" <rico_chang@.msn.com> schrieb im Newsbeitrag
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right' if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>|||Hi
Yes, the SID is different.
You are in a domain, so why are you using local groups? As you see, in a DR
scenario, it becomes difficult to work with. If this was a cluster, you
would have the same problems.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rico" <rico_chang@.msn.com> wrote in message
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right' if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>|||Dear Mike,
thanks for your reply, in fact, ApplicationA means MOM Server 2005,
MOM Server will create some local groups
Rico
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> ¼¶¼g©ó¶l¥ó·s»D:uKfxmfhWFHA.3584@.TK2MSFTNGP14.phx.gbl...
> Hi
> Yes, the SID is different.
> You are in a domain, so why are you using local groups? As you see, in a
> DR scenario, it becomes difficult to work with. If this was a cluster, you
> would have the same problems.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Rico" <rico_chang@.msn.com> wrote in message
> news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
>> Dear all,
>> My Lab has one SQL Server which used by ApplicationA, during
>> the installation process of ApplicationA, ApplicationA will
>> add New Logins for one local user group, and add one domain
>> useraccount to be a member of this local user group, i want
>> to simulate disaster rescovery of ApplicationA, so i do the
>> steps listed bellow:
>> (1) backup all related SQL database, inclued Master DB Full Backup
>> (2) Install one new Windows 2003 Server
>> (3) create local user group used by ApplicationA
>> (4) Install SQL Server and SP3a in this new Server, and every
>> installation options is the same as old server
>> (5) Install ApplicationA
>> (6) Restore all Database from backup media
>> (7) make sure no error happend when restore
>> after restore database, domain user account which is a member
>> of that local user group can't logon go SQL Server, when use SQL
>> Query Analyzer, error message appear:
>> can't connect to server SQLServerName:
>> Server:Message18456,Level16,Status1
>> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
>> if i delete SQL logins for that local user group, and then new logins
>> for that local user group, the domain user account can logon
>> successfully,
>> so i think although the name of local user gorup is the same, but
>> the sid of local user gorup is different, because this is the new Windows
>> 2003 Server.
>> Am i right' if i'm right, anything i can do to resolve this problem
>> thanks for any reply
>> Rico
>
My Lab has one SQL Server which used by ApplicationA, during
the installation process of ApplicationA, ApplicationA will
add New Logins for one local user group, and add one domain
useraccount to be a member of this local user group, i want
to simulate disaster rescovery of ApplicationA, so i do the
steps listed bellow:
(1) backup all related SQL database, inclued Master DB Full Backup
(2) Install one new Windows 2003 Server
(3) create local user group used by ApplicationA
(4) Install SQL Server and SP3a in this new Server, and every
installation options is the same as old server
(5) Install ApplicationA
(6) Restore all Database from backup media
(7) make sure no error happend when restore
after restore database, domain user account which is a member
of that local user group can't logon go SQL Server, when use SQL
Query Analyzer, error message appear:
can't connect to server SQLServerName:
Server:Message18456,Level16,Status1
Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
if i delete SQL logins for that local user group, and then new logins
for that local user group, the domain user account can logon successfully,
so i think although the name of local user gorup is the same, but
the sid of local user gorup is different, because this is the new Windows
2003 Server.
Am i right' if i'm right, anything i can do to resolve this problem
thanks for any reply
RicoProblems about orphaned users ?
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_servdatabse_0ttf.asp
http://vyaskn.tripod.com/troubleshooting_orphan_users.htm
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Rico" <rico_chang@.msn.com> schrieb im Newsbeitrag
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right' if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>|||Hi
Yes, the SID is different.
You are in a domain, so why are you using local groups? As you see, in a DR
scenario, it becomes difficult to work with. If this was a cluster, you
would have the same problems.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Rico" <rico_chang@.msn.com> wrote in message
news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
> Dear all,
> My Lab has one SQL Server which used by ApplicationA, during
> the installation process of ApplicationA, ApplicationA will
> add New Logins for one local user group, and add one domain
> useraccount to be a member of this local user group, i want
> to simulate disaster rescovery of ApplicationA, so i do the
> steps listed bellow:
> (1) backup all related SQL database, inclued Master DB Full Backup
> (2) Install one new Windows 2003 Server
> (3) create local user group used by ApplicationA
> (4) Install SQL Server and SP3a in this new Server, and every
> installation options is the same as old server
> (5) Install ApplicationA
> (6) Restore all Database from backup media
> (7) make sure no error happend when restore
> after restore database, domain user account which is a member
> of that local user group can't logon go SQL Server, when use SQL
> Query Analyzer, error message appear:
> can't connect to server SQLServerName:
> Server:Message18456,Level16,Status1
> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
> if i delete SQL logins for that local user group, and then new logins
> for that local user group, the domain user account can logon successfully,
> so i think although the name of local user gorup is the same, but
> the sid of local user gorup is different, because this is the new Windows
> 2003 Server.
> Am i right' if i'm right, anything i can do to resolve this problem
> thanks for any reply
> Rico
>|||Dear Mike,
thanks for your reply, in fact, ApplicationA means MOM Server 2005,
MOM Server will create some local groups
Rico
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> ¼¶¼g©ó¶l¥ó·s»D:uKfxmfhWFHA.3584@.TK2MSFTNGP14.phx.gbl...
> Hi
> Yes, the SID is different.
> You are in a domain, so why are you using local groups? As you see, in a
> DR scenario, it becomes difficult to work with. If this was a cluster, you
> would have the same problems.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Rico" <rico_chang@.msn.com> wrote in message
> news:%23MSOGZhWFHA.1152@.tk2msftngp13.phx.gbl...
>> Dear all,
>> My Lab has one SQL Server which used by ApplicationA, during
>> the installation process of ApplicationA, ApplicationA will
>> add New Logins for one local user group, and add one domain
>> useraccount to be a member of this local user group, i want
>> to simulate disaster rescovery of ApplicationA, so i do the
>> steps listed bellow:
>> (1) backup all related SQL database, inclued Master DB Full Backup
>> (2) Install one new Windows 2003 Server
>> (3) create local user group used by ApplicationA
>> (4) Install SQL Server and SP3a in this new Server, and every
>> installation options is the same as old server
>> (5) Install ApplicationA
>> (6) Restore all Database from backup media
>> (7) make sure no error happend when restore
>> after restore database, domain user account which is a member
>> of that local user group can't logon go SQL Server, when use SQL
>> Query Analyzer, error message appear:
>> can't connect to server SQLServerName:
>> Server:Message18456,Level16,Status1
>> Microsoft][ODBC SQL Server][SQL Server]User'Test\testuser' logon failed
>> if i delete SQL logins for that local user group, and then new logins
>> for that local user group, the domain user account can logon
>> successfully,
>> so i think although the name of local user gorup is the same, but
>> the sid of local user gorup is different, because this is the new Windows
>> 2003 Server.
>> Am i right' if i'm right, anything i can do to resolve this problem
>> thanks for any reply
>> Rico
>
After MSDE SP4 installation SQL Agent is set to manual
I have over 500 PC's with a named instance of MSDE installed that I need to
install SP4 on. These PC's have the SQL Agent set to automatic. After
installing SP4 on a test box, this service was changed to manual by the
service pack. replication will not work if this service is not running.
Is there a way to have the service pack set this service to be set to
automatic? Is there a way to set it to automatic with a batch program or VB
script?
I can not manually change this service on over 500 PC's.
hi,
andersos wrote:
> I have over 500 PC's with a named instance of MSDE installed that I
> need to install SP4 on. These PC's have the SQL Agent set to
> automatic. After installing SP4 on a test box, this service was
> changed to manual by the service pack. replication will not work if
> this service is not running.
> Is there a way to have the service pack set this service to be set to
> automatic? Is there a way to set it to automatic with a batch
> program or VB script?
> I can not manually change this service on over 500 PC's.
I do think via WMI, but never tried it... perhaps you have to ask in some
dev's newsgroup
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Check out this article.
http://groups-beta.google.com/group/...e67c802edd178a
There is a registry key for this service. If you change the 'start'
property of this key, you can change the service from manual to automatic.
There are a number of ways to do this through code. These are the values for
this property.
Boot = 0,
System = 1,
Automatic = 2,
Manual = 3,
Disabled = 4
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent
|||It is cool that you even got msde upgraded on 500 users. I can't get one
installed to upgrade my default instance sp3a to sp4. You are a hero.
In BOL look up - scm Utility
If you can find the -StartupOptions for autostart, it looks like you can do
it with a bat file or xp_cmdshell.
We replicate a table with a trigger to dynamically execute sql on insert to
propagate fixes and procs.
My test install of sp4 ran well, then the status bar backed up and it
finished like all is well but .760 still shows in the version. Did you have
anything similar ? Care to share your command line secret? I have 150 users
to push to.
andersos wrote:
>Check out this article.
>http://groups-beta.google.com/group/...e67c802edd178a
>There is a registry key for this service. If you change the 'start'
>property of this key, you can change the service from manual to automatic.
>There are a number of ways to do this through code. These are the values for
>this property.
> Boot = 0,
> System = 1,
> Automatic = 2,
> Manual = 3,
> Disabled = 4
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\SQLAgent
|||C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7 -Service
sqlserveragent -SvcStartT
ype 2
This does the job. Note this path may differ
andersos wrote:
>I have over 500 PC's with a named instance of MSDE installed that I need to
>install SP4 on. These PC's have the SQL Agent set to automatic. After
>installing SP4 on a test box, this service was changed to manual by the
>service pack. replication will not work if this service is not running.
>Is there a way to have the service pack set this service to be set to
>automatic? Is there a way to set it to automatic with a batch program or VB
>script?
>I can not manually change this service on over 500 PC's.
Mike Street
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...-msde/200507/1
install SP4 on. These PC's have the SQL Agent set to automatic. After
installing SP4 on a test box, this service was changed to manual by the
service pack. replication will not work if this service is not running.
Is there a way to have the service pack set this service to be set to
automatic? Is there a way to set it to automatic with a batch program or VB
script?
I can not manually change this service on over 500 PC's.
hi,
andersos wrote:
> I have over 500 PC's with a named instance of MSDE installed that I
> need to install SP4 on. These PC's have the SQL Agent set to
> automatic. After installing SP4 on a test box, this service was
> changed to manual by the service pack. replication will not work if
> this service is not running.
> Is there a way to have the service pack set this service to be set to
> automatic? Is there a way to set it to automatic with a batch
> program or VB script?
> I can not manually change this service on over 500 PC's.
I do think via WMI, but never tried it... perhaps you have to ask in some
dev's newsgroup
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Check out this article.
http://groups-beta.google.com/group/...e67c802edd178a
There is a registry key for this service. If you change the 'start'
property of this key, you can change the service from manual to automatic.
There are a number of ways to do this through code. These are the values for
this property.
Boot = 0,
System = 1,
Automatic = 2,
Manual = 3,
Disabled = 4
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent
|||It is cool that you even got msde upgraded on 500 users. I can't get one
installed to upgrade my default instance sp3a to sp4. You are a hero.
In BOL look up - scm Utility
If you can find the -StartupOptions for autostart, it looks like you can do
it with a bat file or xp_cmdshell.
We replicate a table with a trigger to dynamically execute sql on insert to
propagate fixes and procs.
My test install of sp4 ran well, then the status bar backed up and it
finished like all is well but .760 still shows in the version. Did you have
anything similar ? Care to share your command line secret? I have 150 users
to push to.
andersos wrote:
>Check out this article.
>http://groups-beta.google.com/group/...e67c802edd178a
>There is a registry key for this service. If you change the 'start'
>property of this key, you can change the service from manual to automatic.
>There are a number of ways to do this through code. These are the values for
>this property.
> Boot = 0,
> System = 1,
> Automatic = 2,
> Manual = 3,
> Disabled = 4
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\SQLAgent
|||C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7 -Service
sqlserveragent -SvcStartT
ype 2
This does the job. Note this path may differ
andersos wrote:
>I have over 500 PC's with a named instance of MSDE installed that I need to
>install SP4 on. These PC's have the SQL Agent set to automatic. After
>installing SP4 on a test box, this service was changed to manual by the
>service pack. replication will not work if this service is not running.
>Is there a way to have the service pack set this service to be set to
>automatic? Is there a way to set it to automatic with a batch program or VB
>script?
>I can not manually change this service on over 500 PC's.
Mike Street
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...-msde/200507/1
Subscribe to:
Posts (Atom)