can SP4 be uninstalled?

We are currently at SP3a but are having some issues that we **hope and pray**
are fixed by installing SP4. But if we run into other problems can SP4 be
uninstalled?
Brad,
In the simplest terms, you cannot uninstall SP4 from SQL Server 2000. But
there is a workaround. It is documented in section 3.8 of this document:
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_uninstalling_sp4
The thing to know: SP4 modifies the structure of master, msdb, and model
databases, which makes them incompatible with SP3a.
Action to take: Make a good backup of master, msdb, and model before going
to SP4.
If SP4 does not work out for you, you will have to uninstall SQL Server and
reinstall SQL Server all the way back up to SP3a. Then you must restore
your backups of master, msdb, and model. (It is ugly, but not impossibly
so. Read the article noted above.)
RLF
"Brad Ashforth" <BradAshforth@.discussions.microsoft.com> wrote in message
news:CC4CD50D-54F3-4B10-85F5-2DAF6D05001E@.microsoft.com...
> We are currently at SP3a but are having some issues that we **hope and
> pray**
> are fixed by installing SP4. But if we run into other problems can SP4 be
> uninstalled?

can SP4 be uninstalled?

We are currently at SP3a but are having some issues that we **hope and pray**
are fixed by installing SP4. But if we run into other problems can SP4 be
uninstalled?Brad,
In the simplest terms, you cannot uninstall SP4 from SQL Server 2000. But
there is a workaround. It is documented in section 3.8 of this document:
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_uninstalling_sp4
The thing to know: SP4 modifies the structure of master, msdb, and model
databases, which makes them incompatible with SP3a.
Action to take: Make a good backup of master, msdb, and model before going
to SP4.
If SP4 does not work out for you, you will have to uninstall SQL Server and
reinstall SQL Server all the way back up to SP3a. Then you must restore
your backups of master, msdb, and model. (It is ugly, but not impossibly
so. Read the article noted above.)
RLF
"Brad Ashforth" <BradAshforth@.discussions.microsoft.com> wrote in message
news:CC4CD50D-54F3-4B10-85F5-2DAF6D05001E@.microsoft.com...
> We are currently at SP3a but are having some issues that we **hope and
> pray**
> are fixed by installing SP4. But if we run into other problems can SP4 be
> uninstalled?

can SP4 be uninstalled?

We are currently at SP3a but are having some issues that we **hope and pray*
*
are fixed by installing SP4. But if we run into other problems can SP4 be
uninstalled?Brad,
In the simplest terms, you cannot uninstall SP4 from SQL Server 2000. But
there is a workaround. It is documented in section 3.8 of this document:
http://download.microsoft.com/downl...ninstalling_sp4
The thing to know: SP4 modifies the structure of master, msdb, and model
databases, which makes them incompatible with SP3a.
Action to take: Make a good backup of master, msdb, and model before going
to SP4.
If SP4 does not work out for you, you will have to uninstall SQL Server and
reinstall SQL Server all the way back up to SP3a. Then you must restore
your backups of master, msdb, and model. (It is ugly, but not impossibly
so. Read the article noted above.)
RLF
"Brad Ashforth" <BradAshforth@.discussions.microsoft.com> wrote in message
news:CC4CD50D-54F3-4B10-85F5-2DAF6D05001E@.microsoft.com...
> We are currently at SP3a but are having some issues that we **hope and
> pray**
> are fixed by installing SP4. But if we run into other problems can SP4 be
> uninstalled?

can someone login as "NT AUTHORITY\SYSTEM "

Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
one of our servers. I log both the failed and successful logins and both of
the above logins were used recently. Do they have passwords that can be set?
What would be the implications if I removed both of them from
"security/logins"? I'm running both the server service and agent service with
a different login so it wouldn't affect the jobs.
Thanks,
Dan D.
Hi Dan
These are the name of the accounts when you specify local system or network
service as the accounts in which a service runs under see
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
John
"Dan D." wrote:

> Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> one of our servers. I log both the failed and successful logins and both of
> the above logins were used recently. Do they have passwords that can be set?
> What would be the implications if I removed both of them from
> "security/logins"? I'm running both the server service and agent service with
> a different login so it wouldn't affect the jobs.
> Thanks,
> --
> Dan D.
|||I came across an article today about how someone could log in as NT AUTHORITY
through the cmd window using the task scheduler and I got a little concerned.
Thanks for the article.
Dan D.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Dan
> These are the name of the accounts when you specify local system or network
> service as the accounts in which a service runs under see
> http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> John
> "Dan D." wrote:
|||Hi Dan
Could you can post a link to the article?
John
"Dan D." wrote:
[vbcol=seagreen]
> I came across an article today about how someone could log in as NT AUTHORITY
> through the cmd window using the task scheduler and I got a little concerned.
> Thanks for the article.
> --
> Dan D.
>
> "John Bell" wrote:
|||Sometimes the page doesn't render correctly. You may have to scroll down to
see the beginning of the article.
http://www.ozzu.com/ftopic1337.html
Dan D.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Dan
> Could you can post a link to the article?
> John
> "Dan D." wrote:
|||Hi Dan
The article is talking about a vunerability highlighted in
http://support.microsoft.com/?kbid=823980 that can be exploited by a specific
worm, rather than something actually logging in a the account. You should
make sure that your system is patched to a level which does not have this
issue. Tools like Microsoft Baseline Security Advisor will help you configure
your systems check out http://msdn2.microsoft.com/en-us/library/aa302360.aspx
John
"Dan D." wrote:
[vbcol=seagreen]
> Sometimes the page doesn't render correctly. You may have to scroll down to
> see the beginning of the article.
> http://www.ozzu.com/ftopic1337.html
> --
> Dan D.
>
> "John Bell" wrote:
|||Thanks. I do run the Baseline Security Analyzer.
Dan D.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Dan
> The article is talking about a vunerability highlighted in
> http://support.microsoft.com/?kbid=823980 that can be exploited by a specific
> worm, rather than something actually logging in a the account. You should
> make sure that your system is patched to a level which does not have this
> issue. Tools like Microsoft Baseline Security Advisor will help you configure
> your systems check out http://msdn2.microsoft.com/en-us/library/aa302360.aspx
> John
> "Dan D." wrote:
|||Hi Dan
Hopefully you have patched this, make sure that you keep your MBSA up to date.
John
"Dan D." wrote:
[vbcol=seagreen]
> Thanks. I do run the Baseline Security Analyzer.
> --
> Dan D.
>
> "John Bell" wrote:

can someone login as "NT AUTHORITY\SYSTEM "

Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
one of our servers. I log both the failed and successful logins and both of
the above logins were used recently. Do they have passwords that can be set?
What would be the implications if I removed both of them from
"security/logins"? I'm running both the server service and agent service with
a different login so it wouldn't affect the jobs.
Thanks,
--
Dan D.Hi Dan
These are the name of the accounts when you specify local system or network
service as the accounts in which a service runs under see
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
John
"Dan D." wrote:
> Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> one of our servers. I log both the failed and successful logins and both of
> the above logins were used recently. Do they have passwords that can be set?
> What would be the implications if I removed both of them from
> "security/logins"? I'm running both the server service and agent service with
> a different login so it wouldn't affect the jobs.
> Thanks,
> --
> Dan D.|||I came across an article today about how someone could log in as NT AUTHORITY
through the cmd window using the task scheduler and I got a little concerned.
Thanks for the article.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> These are the name of the accounts when you specify local system or network
> service as the accounts in which a service runs under see
> http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> John
> "Dan D." wrote:
> > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > one of our servers. I log both the failed and successful logins and both of
> > the above logins were used recently. Do they have passwords that can be set?
> >
> > What would be the implications if I removed both of them from
> > "security/logins"? I'm running both the server service and agent service with
> > a different login so it wouldn't affect the jobs.
> >
> > Thanks,
> > --
> > Dan D.|||Hi Dan
Could you can post a link to the article?
John
"Dan D." wrote:
> I came across an article today about how someone could log in as NT AUTHORITY
> through the cmd window using the task scheduler and I got a little concerned.
> Thanks for the article.
> --
> Dan D.
>
> "John Bell" wrote:
> > Hi Dan
> >
> > These are the name of the accounts when you specify local system or network
> > service as the accounts in which a service runs under see
> > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> >
> > John
> >
> > "Dan D." wrote:
> >
> > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > one of our servers. I log both the failed and successful logins and both of
> > > the above logins were used recently. Do they have passwords that can be set?
> > >
> > > What would be the implications if I removed both of them from
> > > "security/logins"? I'm running both the server service and agent service with
> > > a different login so it wouldn't affect the jobs.
> > >
> > > Thanks,
> > > --
> > > Dan D.|||Sometimes the page doesn't render correctly. You may have to scroll down to
see the beginning of the article.
http://www.ozzu.com/ftopic1337.html
--
Dan D.
"John Bell" wrote:
> Hi Dan
> Could you can post a link to the article?
> John
> "Dan D." wrote:
> > I came across an article today about how someone could log in as NT AUTHORITY
> > through the cmd window using the task scheduler and I got a little concerned.
> > Thanks for the article.
> > --
> > Dan D.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi Dan
> > >
> > > These are the name of the accounts when you specify local system or network
> > > service as the accounts in which a service runs under see
> > > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> > >
> > > John
> > >
> > > "Dan D." wrote:
> > >
> > > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > > one of our servers. I log both the failed and successful logins and both of
> > > > the above logins were used recently. Do they have passwords that can be set?
> > > >
> > > > What would be the implications if I removed both of them from
> > > > "security/logins"? I'm running both the server service and agent service with
> > > > a different login so it wouldn't affect the jobs.
> > > >
> > > > Thanks,
> > > > --
> > > > Dan D.|||Hi Dan
The article is talking about a vunerability highlighted in
http://support.microsoft.com/?kbid=823980 that can be exploited by a specific
worm, rather than something actually logging in a the account. You should
make sure that your system is patched to a level which does not have this
issue. Tools like Microsoft Baseline Security Advisor will help you configure
your systems check out http://msdn2.microsoft.com/en-us/library/aa302360.aspx
John
"Dan D." wrote:
> Sometimes the page doesn't render correctly. You may have to scroll down to
> see the beginning of the article.
> http://www.ozzu.com/ftopic1337.html
> --
> Dan D.
>
> "John Bell" wrote:
> > Hi Dan
> >
> > Could you can post a link to the article?
> >
> > John
> >
> > "Dan D." wrote:
> >
> > > I came across an article today about how someone could log in as NT AUTHORITY
> > > through the cmd window using the task scheduler and I got a little concerned.
> > > Thanks for the article.
> > > --
> > > Dan D.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Dan
> > > >
> > > > These are the name of the accounts when you specify local system or network
> > > > service as the accounts in which a service runs under see
> > > > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> > > >
> > > > John
> > > >
> > > > "Dan D." wrote:
> > > >
> > > > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > > > one of our servers. I log both the failed and successful logins and both of
> > > > > the above logins were used recently. Do they have passwords that can be set?
> > > > >
> > > > > What would be the implications if I removed both of them from
> > > > > "security/logins"? I'm running both the server service and agent service with
> > > > > a different login so it wouldn't affect the jobs.
> > > > >
> > > > > Thanks,
> > > > > --
> > > > > Dan D.|||Thanks. I do run the Baseline Security Analyzer.
--
Dan D.
"John Bell" wrote:
> Hi Dan
> The article is talking about a vunerability highlighted in
> http://support.microsoft.com/?kbid=823980 that can be exploited by a specific
> worm, rather than something actually logging in a the account. You should
> make sure that your system is patched to a level which does not have this
> issue. Tools like Microsoft Baseline Security Advisor will help you configure
> your systems check out http://msdn2.microsoft.com/en-us/library/aa302360.aspx
> John
> "Dan D." wrote:
> > Sometimes the page doesn't render correctly. You may have to scroll down to
> > see the beginning of the article.
> >
> > http://www.ozzu.com/ftopic1337.html
> >
> > --
> > Dan D.
> >
> >
> > "John Bell" wrote:
> >
> > > Hi Dan
> > >
> > > Could you can post a link to the article?
> > >
> > > John
> > >
> > > "Dan D." wrote:
> > >
> > > > I came across an article today about how someone could log in as NT AUTHORITY
> > > > through the cmd window using the task scheduler and I got a little concerned.
> > > > Thanks for the article.
> > > > --
> > > > Dan D.
> > > >
> > > >
> > > > "John Bell" wrote:
> > > >
> > > > > Hi Dan
> > > > >
> > > > > These are the name of the accounts when you specify local system or network
> > > > > service as the accounts in which a service runs under see
> > > > > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> > > > >
> > > > > John
> > > > >
> > > > > "Dan D." wrote:
> > > > >
> > > > > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > > > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > > > > one of our servers. I log both the failed and successful logins and both of
> > > > > > the above logins were used recently. Do they have passwords that can be set?
> > > > > >
> > > > > > What would be the implications if I removed both of them from
> > > > > > "security/logins"? I'm running both the server service and agent service with
> > > > > > a different login so it wouldn't affect the jobs.
> > > > > >
> > > > > > Thanks,
> > > > > > --
> > > > > > Dan D.|||Hi Dan
Hopefully you have patched this, make sure that you keep your MBSA up to date.
John
"Dan D." wrote:
> Thanks. I do run the Baseline Security Analyzer.
> --
> Dan D.
>
> "John Bell" wrote:
> > Hi Dan
> >
> > The article is talking about a vunerability highlighted in
> > http://support.microsoft.com/?kbid=823980 that can be exploited by a specific
> > worm, rather than something actually logging in a the account. You should
> > make sure that your system is patched to a level which does not have this
> > issue. Tools like Microsoft Baseline Security Advisor will help you configure
> > your systems check out http://msdn2.microsoft.com/en-us/library/aa302360.aspx
> >
> > John
> >
> > "Dan D." wrote:
> >
> > > Sometimes the page doesn't render correctly. You may have to scroll down to
> > > see the beginning of the article.
> > >
> > > http://www.ozzu.com/ftopic1337.html
> > >
> > > --
> > > Dan D.
> > >
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Dan
> > > >
> > > > Could you can post a link to the article?
> > > >
> > > > John
> > > >
> > > > "Dan D." wrote:
> > > >
> > > > > I came across an article today about how someone could log in as NT AUTHORITY
> > > > > through the cmd window using the task scheduler and I got a little concerned.
> > > > > Thanks for the article.
> > > > > --
> > > > > Dan D.
> > > > >
> > > > >
> > > > > "John Bell" wrote:
> > > > >
> > > > > > Hi Dan
> > > > > >
> > > > > > These are the name of the accounts when you specify local system or network
> > > > > > service as the accounts in which a service runs under see
> > > > > > http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> > > > > >
> > > > > > John
> > > > > >
> > > > > > "Dan D." wrote:
> > > > > >
> > > > > > > Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> > > > > > > AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access to
> > > > > > > one of our servers. I log both the failed and successful logins and both of
> > > > > > > the above logins were used recently. Do they have passwords that can be set?
> > > > > > >
> > > > > > > What would be the implications if I removed both of them from
> > > > > > > "security/logins"? I'm running both the server service and agent service with
> > > > > > > a different login so it wouldn't affect the jobs.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > --
> > > > > > > Dan D.

can someone login as "NT AUTHORITY\SYSTEM "

Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access t
o
one of our servers. I log both the failed and successful logins and both of
the above logins were used recently. Do they have passwords that can be set?
What would be the implications if I removed both of them from
"security/logins"? I'm running both the server service and agent service wit
h
a different login so it wouldn't affect the jobs.
Thanks,
--
Dan D.Hi Dan
These are the name of the accounts when you specify local system or network
service as the accounts in which a service runs under see
http://msdn2.microsoft.com/en-us/library/ms191543.aspx
John
"Dan D." wrote:

> Using SS2000 SP4. Can someone login as either NT AUTHORITY\SYSTEM or NT
> AUTHORITY\NETWORK SERVICE? I'm trying to figure out how someone got access
to
> one of our servers. I log both the failed and successful logins and both o
f
> the above logins were used recently. Do they have passwords that can be se
t?
> What would be the implications if I removed both of them from
> "security/logins"? I'm running both the server service and agent service w
ith
> a different login so it wouldn't affect the jobs.
> Thanks,
> --
> Dan D.|||I came across an article today about how someone could log in as NT AUTHORIT
Y
through the cmd window using the task scheduler and I got a little concerned
.
Thanks for the article.
--
Dan D.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Dan
> These are the name of the accounts when you specify local system or networ
k
> service as the accounts in which a service runs under see
> http://msdn2.microsoft.com/en-us/library/ms191543.aspx
> John
> "Dan D." wrote:
>|||Hi Dan
Could you can post a link to the article?
John
"Dan D." wrote:
[vbcol=seagreen]
> I came across an article today about how someone could log in as NT AUTHOR
ITY
> through the cmd window using the task scheduler and I got a little concern
ed.
> Thanks for the article.
> --
> Dan D.
>
> "John Bell" wrote:
>|||Sometimes the page doesn't render correctly. You may have to scroll down to
see the beginning of the article.
http://www.ozzu.com/ftopic1337.html
Dan D.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Dan
> Could you can post a link to the article?
> John
> "Dan D." wrote:
>|||Hi Dan
The article is talking about a vunerability highlighted in
http://support.microsoft.com/?kbid=823980 that can be exploited by a specifi
c
worm, rather than something actually logging in a the account. You should
make sure that your system is patched to a level which does not have this
issue. Tools like Microsoft Baseline Security Advisor will help you configur
e
your systems check out [url]http://msdn2.microsoft.com/en-us/library/aa302360.aspx[/url
]
John
"Dan D." wrote:
[vbcol=seagreen]
> Sometimes the page doesn't render correctly. You may have to scroll down t
o
> see the beginning of the article.
> http://www.ozzu.com/ftopic1337.html
> --
> Dan D.
>
> "John Bell" wrote:
>|||Thanks. I do run the Baseline Security Analyzer.
--
Dan D.
"John Bell" wrote:
[vbcol=seagreen]
> Hi Dan
> The article is talking about a vunerability highlighted in
> http://support.microsoft.com/?kbid=823980 that can be exploited by a speci
fic
> worm, rather than something actually logging in a the account. You should
> make sure that your system is patched to a level which does not have this
> issue. Tools like Microsoft Baseline Security Advisor will help you config
ure
> your systems check out [url]http://msdn2.microsoft.com/en-us/library/aa302360.aspx[/u
rl]
> John
> "Dan D." wrote:
>|||Hi Dan
Hopefully you have patched this, make sure that you keep your MBSA up to dat
e.
John
"Dan D." wrote:
[vbcol=seagreen]
> Thanks. I do run the Baseline Security Analyzer.
> --
> Dan D.
>
> "John Bell" wrote:
>

can not view DTS Packages and Jobs

I have SQL 2k SP4 on Windows 2003
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
RK
Yes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK
|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
RK
"Russell Fields" wrote:

> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, but
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package, as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>
>
|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...[vbcol=seagreen]
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:

can not view DTS Packages and Jobs

I have SQL 2k SP4 on Windows 2003
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
--
RKYes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
--
RK
"Russell Fields" wrote:

> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, b
ut
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them
as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package,
as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>
>|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...[vbcol=seagreen]
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:
>

can not view DTS Packages and Jobs

I have SQL 2k SP4 on Windows 2003
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
--
RKYes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
--
RK
"Russell Fields" wrote:
> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, but
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package, as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
> >I have SQL 2k SP4 on Windows 2003
> > Can A sqlserver user, with out having SA role, see the DTS packages, Job
> > and
> > their status ?
> > --
> > RK
>
>|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:
>> Yes, partially, through some workarounds.
>> If you make a SQL Server user a member of the msdb database
>> TargetServersRole, they will be able to see all jobs and their statuses,
>> but
>> will not be able to create or modify jobs. (So this does not work for
>> someone who should be able to create his own jobs. This is an
>> undocumented
>> sideeffect of the role and will not work in SQL Server 2005. But 2005
>> has
>> specific new roles for granting various degrees of access to SQL Agent
>> jobs.)
>> If, instead of storing DTS packages as SQL Server objects, you store them
>> as
>> files on a file share, then anyone who has rights to the file share
>> (read/only if you want that) can examine the contents of the DTS package,
>> as
>> well. (If there is a workaround for examining DTS packages stored on the
>> server, I don't know it.)
>> RLF
>> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>> >I have SQL 2k SP4 on Windows 2003
>> > Can A sqlserver user, with out having SA role, see the DTS packages,
>> > Job
>> > and
>> > their status ?
>> > --
>> > RK
>>

Can not send mail with xp_sendmail procedure

Hallo!
Environment:
Windows 2000 domain (2 x win2000 sp4 domain conrollers)
Exchange 5.5 running on winnt4.0 member server
SQL 2000 sp3 running on Windows 2000 member server.
I have SQL server running under domain administrator account (both services)
and Outlook 2000 on the same server profile set with the same account and
Exchange 5.5.
SQL agent is set to use that profile and also SQL mail (under support
services in SQL manager). When I test that profile it works OK. I can send
test mail to the operator and all my alerts can send mail fine.
Problem is, that my new application uses xp_sendmail procedure to send mail,
and it doesn't work. I get this error when running the procedure:
Server: Msg 18025, Level 16, State 1, Line 0
xp_sendmail: failed with mail error 0x80070005
I found an article Q293422 that descibes this problem but the solution did
not solve the problem. Besides, this article is about Exchange 2000 mailbox
and I'm using 5.5 mailbox.
I just managed to temporary fix this problem. I created new domain user in
AD and it's mailbox in Exchange 5.5. After seting SQL service, SQL agent
service, mail settings in Enterprise manager and new profile in Outlook to
use that new account, everything was working OK. xp_sandmail was working
too. But the next day same problem repaired. xp_sendmail reported same
errors again.
I suspect there are some security isues with SQL service account, but what?
Why is it working OK for one day and then stops the next?
Any ideas would be appreciated! Thanks.
DanSome links to KB articles and other resources helping with config issues, as
well as alternatives to xp_sendmail: http://www.aspfaq.com/2403
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Dan" <mcseman2002@.hotmail.com> wrote in message
news:OT1exV42DHA.2336@.TK2MSFTNGP09.phx.gbl...

quote:

---

> Hallo!
> Environment:
> Windows 2000 domain (2 x win2000 sp4 domain conrollers)
> Exchange 5.5 running on winnt4.0 member server
> SQL 2000 sp3 running on Windows 2000 member server.
> I have SQL server running under domain administrator account (both

---

services)

quote:

---

> and Outlook 2000 on the same server profile set with the same account and
> Exchange 5.5.
> SQL agent is set to use that profile and also SQL mail (under support
> services in SQL manager). When I test that profile it works OK. I can send
> test mail to the operator and all my alerts can send mail fine.
> Problem is, that my new application uses xp_sendmail procedure to send

---

mail,

quote:

---

> and it doesn't work. I get this error when running the procedure:
> Server: Msg 18025, Level 16, State 1, Line 0
> xp_sendmail: failed with mail error 0x80070005
> I found an article Q293422 that descibes this problem but the solution did
> not solve the problem. Besides, this article is about Exchange 2000

---

mailbox

quote:

---

> and I'm using 5.5 mailbox.
> I just managed to temporary fix this problem. I created new domain user in
> AD and it's mailbox in Exchange 5.5. After seting SQL service, SQL agent
> service, mail settings in Enterprise manager and new profile in Outlook to
> use that new account, everything was working OK. xp_sandmail was working
> too. But the next day same problem repaired. xp_sendmail reported same
> errors again.
> I suspect there are some security isues with SQL service account, but

---

what?

quote:

---

> Why is it working OK for one day and then stops the next?
> Any ideas would be appreciated! Thanks.
> Dan
>
>

---

Can not install SP4 for SQL Server 7.0 on Win2k

In my case this is a SP4 install on a reinstall of SQL 7.0 with no user data
bases.
I have followed all the tips about turning off all non-essential services, e
tc., per the kb article and various other docs, but the 7.0 sp4 installation
still fails with the message
"One or more of your user databases have been marked read only, offline or s
uspect (not recovered). Correct the problem and restart setup."
The log files seem to show everything is ok but the install still fails.
I did try one additional test -- running the scm and osql commands shown at
the end of the sqlsp.log file.
When I ran the osql command, I get the expected results of 0 but also get an
additional message for the ODBC driver manager: "The driver doesn't support
the version of ODBC behavior that the application requested (see SQLSetEnvA
ttr)."
I suspect that this additional message is causing the failure.
(Running on W2k / SP4).
-- Vikram Jayaram [MS] wrote: --
* Look at the sqlsp.log for error messages
* It's a good idea to turn off all 3rd party and non-essential services
before you prform the Service Pack upgrade.
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.How are you installing the setup for sp4. What does the sqlsp.log say? Are
you sure there are no other sql70 instances on the box?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Can not install SP4 for SQL Server 7.0 on Win2k

Our client applications have being generating timeout
exceptions persistently whiles connecting to SQL Server
7.0. I gathered from the web the problem is a known issue
with SQL Server 7.0 and is fixed in SP4. However,
whenever I try installing the service pack it gets stuck
in the first step and would not continue.
Could somebody offer me some assistance.
Thanks advance.* Look at the sqlsp.log for error messages
* It's a good idea to turn off all 3rd party and non-essential services
before you prform the Service Pack upgrade.
Thanks,
Vikram
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||In my case this is a SP4 install on a reinstall of SQL 7.0 with no user databases
I have followed all the tips about turning off all non-essential services, etc., per the kb article and various other docs, but the 7.0 sp4 installation still fails with the messag
"One or more of your user databases have been marked read only, offline or suspect (not recovered). Correct the problem and restart setup.
The log files seem to show everything is ok but the install still fails
I did try one additional test -- running the scm and osql commands shown at the end of the sqlsp.log file.
When I ran the osql command, I get the expected results of 0 but also get an additional message for the ODBC driver manager: "The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr).
I suspect that this additional message is causing the failure
(Running on W2k / SP4)
-- Vikram Jayaram [MS] wrote: --
* Look at the sqlsp.log for error message
* It's a good idea to turn off all 3rd party and non-essential services
before you prform the Service Pack upgrade
Thanks
Vikra
Vikram Jayara
Microsoft, SQL Serve
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups|||How are you installing the setup for sp4. What does the sqlsp.log say? Are
you sure there are no other sql70 instances on the box?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Can not install service pack

Hi,
I have a win2k server running SQL2000. I have tried to install SP4 for SQL.
Evertything looks normal, but when I check the version it is still SP2. I
have compared the log file with another and there is a major differnce:
problem server:
09:57:26 Start Process...updating reg entries for SP
09:57:26 No Server -> Tools
Succesfully updated server:
14:46:11 Start Process...updating reg entries for SP
14:46:11 Default instance
Could this be the problem, and if so, how to solve this ?
Regards,
PanjoHi
The most common reasons for a SP not installing are either
Using the wrong download file
SQL2000-KB884525-SP4-x86-LLL.exe (Database Components SP4)
SQL2000.AS-KB884525-SP4-x86-LLL.exe (Analysis Services SP4)
SQL2000.MSDE-KB884525-SP4-x86-LLL.exe (Desktop Engine (MSDE 2000) SP4)
SQL2000-KB884525-SP4-ia64-LLL.exe (SQL Server 2000 SP4 (64-bit))
Unzipping the download but not running it
http://tinyurl.com/nbc9v
or Updating the wrong instance.
http://tinyurl.com/pmsvc
You also may want to stop/restart the server as a matter of course even if
you are not prompted to do so.
From the message it looks like SQL Server is not actually running on this
server, use NET START at a command prompt to verify this.
John
"panjo" wrote:

> Hi,
> I have a win2k server running SQL2000. I have tried to install SP4 for SQL
.
> Evertything looks normal, but when I check the version it is still SP2. I
> have compared the log file with another and there is a major differnce:
> problem server:
> 09:57:26 Start Process...updating reg entries for SP
> 09:57:26 No Server -> Tools
> Succesfully updated server:
> 14:46:11 Start Process...updating reg entries for SP
> 14:46:11 Default instance
> Could this be the problem, and if so, how to solve this ?
> Regards,
> Panjo
>|||Hi,
I am quite sure I have the right downloadfile, my testserver is updated
succesfully. There is only one instance, so I can not update the wrong one.
Using net start confirms that mssqlserver and sqlserveragent are running.
I think some reg entry's are missing or wrong. I had some problems with this
server in the past. Then I run the SQL setup again, and did a registry
rebuild. Everything is working fine after that, except that I can not instal
l
SP4.
Any idea which reg key's are checked during the install of SP4 ?
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> The most common reasons for a SP not installing are either
> Using the wrong download file
> SQL2000-KB884525-SP4-x86-LLL.exe (Database Components SP4)
> SQL2000.AS-KB884525-SP4-x86-LLL.exe (Analysis Services SP4)
> SQL2000.MSDE-KB884525-SP4-x86-LLL.exe (Desktop Engine (MSDE 2000) SP4)
> SQL2000-KB884525-SP4-ia64-LLL.exe (SQL Server 2000 SP4 (64-bit))
> Unzipping the download but not running it
> http://tinyurl.com/nbc9v
> or Updating the wrong instance.
> http://tinyurl.com/pmsvc
> You also may want to stop/restart the server as a matter of course even if
> you are not prompted to do so.
> From the message it looks like SQL Server is not actually running on this
> server, use NET START at a command prompt to verify this.
> John
> "panjo" wrote:
>|||Hi
I am not sure what keys would be checked, but you may want to try another
registry rebuilt. If you have group policies being applied you may want to
check what they are doing.
John
"panjo" wrote:
[vbcol=seagreen]
> Hi,
> I am quite sure I have the right downloadfile, my testserver is updated
> succesfully. There is only one instance, so I can not update the wrong one
.
> Using net start confirms that mssqlserver and sqlserveragent are running.
> I think some reg entry's are missing or wrong. I had some problems with th
is
> server in the past. Then I run the SQL setup again, and did a registry
> rebuild. Everything is working fine after that, except that I can not inst
all
> SP4.
> Any idea which reg key's are checked during the install of SP4 ?
> "John Bell" wrote:
>

Can not install service pack

Hi,
I have a win2k server running SQL2000. I have tried to install SP4 for SQL.
Evertything looks normal, but when I check the version it is still SP2. I
have compared the log file with another and there is a major differnce:
problem server:
09:57:26 Start Process...updating reg entries for SP
09:57:26 No Server -> Tools
Succesfully updated server:
14:46:11 Start Process...updating reg entries for SP
14:46:11 Default instance
Could this be the problem, and if so, how to solve this ?
Regards,
PanjoHi
The most common reasons for a SP not installing are either
Using the wrong download file
SQL2000-KB884525-SP4-x86-LLL.exe (Database Components SP4)
SQL2000.AS-KB884525-SP4-x86-LLL.exe (Analysis Services SP4)
SQL2000.MSDE-KB884525-SP4-x86-LLL.exe (Desktop Engine (MSDE 2000) SP4)
SQL2000-KB884525-SP4-ia64-LLL.exe (SQL Server 2000 SP4 (64-bit))
Unzipping the download but not running it
http://tinyurl.com/nbc9v
or Updating the wrong instance.
http://tinyurl.com/pmsvc
You also may want to stop/restart the server as a matter of course even if
you are not prompted to do so.
From the message it looks like SQL Server is not actually running on this
server, use NET START at a command prompt to verify this.
John
"panjo" wrote:
> Hi,
> I have a win2k server running SQL2000. I have tried to install SP4 for SQL.
> Evertything looks normal, but when I check the version it is still SP2. I
> have compared the log file with another and there is a major differnce:
> problem server:
> 09:57:26 Start Process...updating reg entries for SP
> 09:57:26 No Server -> Tools
> Succesfully updated server:
> 14:46:11 Start Process...updating reg entries for SP
> 14:46:11 Default instance
> Could this be the problem, and if so, how to solve this ?
> Regards,
> Panjo
>|||Hi,
I am quite sure I have the right downloadfile, my testserver is updated
succesfully. There is only one instance, so I can not update the wrong one.
Using net start confirms that mssqlserver and sqlserveragent are running.
I think some reg entry's are missing or wrong. I had some problems with this
server in the past. Then I run the SQL setup again, and did a registry
rebuild. Everything is working fine after that, except that I can not install
SP4.
Any idea which reg key's are checked during the install of SP4 ?
"John Bell" wrote:
> Hi
> The most common reasons for a SP not installing are either
> Using the wrong download file
> SQL2000-KB884525-SP4-x86-LLL.exe (Database Components SP4)
> SQL2000.AS-KB884525-SP4-x86-LLL.exe (Analysis Services SP4)
> SQL2000.MSDE-KB884525-SP4-x86-LLL.exe (Desktop Engine (MSDE 2000) SP4)
> SQL2000-KB884525-SP4-ia64-LLL.exe (SQL Server 2000 SP4 (64-bit))
> Unzipping the download but not running it
> http://tinyurl.com/nbc9v
> or Updating the wrong instance.
> http://tinyurl.com/pmsvc
> You also may want to stop/restart the server as a matter of course even if
> you are not prompted to do so.
> From the message it looks like SQL Server is not actually running on this
> server, use NET START at a command prompt to verify this.
> John
> "panjo" wrote:
> > Hi,
> >
> > I have a win2k server running SQL2000. I have tried to install SP4 for SQL.
> > Evertything looks normal, but when I check the version it is still SP2. I
> > have compared the log file with another and there is a major differnce:
> >
> > problem server:
> > 09:57:26 Start Process...updating reg entries for SP
> > 09:57:26 No Server -> Tools
> >
> > Succesfully updated server:
> > 14:46:11 Start Process...updating reg entries for SP
> > 14:46:11 Default instance
> >
> > Could this be the problem, and if so, how to solve this ?
> >
> > Regards,
> > Panjo
> >
> >|||Hi
I am not sure what keys would be checked, but you may want to try another
registry rebuilt. If you have group policies being applied you may want to
check what they are doing.
John
"panjo" wrote:
> Hi,
> I am quite sure I have the right downloadfile, my testserver is updated
> succesfully. There is only one instance, so I can not update the wrong one.
> Using net start confirms that mssqlserver and sqlserveragent are running.
> I think some reg entry's are missing or wrong. I had some problems with this
> server in the past. Then I run the SQL setup again, and did a registry
> rebuild. Everything is working fine after that, except that I can not install
> SP4.
> Any idea which reg key's are checked during the install of SP4 ?
> "John Bell" wrote:
> > Hi
> >
> > The most common reasons for a SP not installing are either
> >
> > Using the wrong download file
> > SQL2000-KB884525-SP4-x86-LLL.exe (Database Components SP4)
> > SQL2000.AS-KB884525-SP4-x86-LLL.exe (Analysis Services SP4)
> > SQL2000.MSDE-KB884525-SP4-x86-LLL.exe (Desktop Engine (MSDE 2000) SP4)
> > SQL2000-KB884525-SP4-ia64-LLL.exe (SQL Server 2000 SP4 (64-bit))
> >
> > Unzipping the download but not running it
> > http://tinyurl.com/nbc9v
> >
> > or Updating the wrong instance.
> > http://tinyurl.com/pmsvc
> >
> > You also may want to stop/restart the server as a matter of course even if
> > you are not prompted to do so.
> >
> > From the message it looks like SQL Server is not actually running on this
> > server, use NET START at a command prompt to verify this.
> >
> > John
> >
> > "panjo" wrote:
> >
> > > Hi,
> > >
> > > I have a win2k server running SQL2000. I have tried to install SP4 for SQL.
> > > Evertything looks normal, but when I check the version it is still SP2. I
> > > have compared the log file with another and there is a major differnce:
> > >
> > > problem server:
> > > 09:57:26 Start Process...updating reg entries for SP
> > > 09:57:26 No Server -> Tools
> > >
> > > Succesfully updated server:
> > > 14:46:11 Start Process...updating reg entries for SP
> > > 14:46:11 Default instance
> > >
> > > Could this be the problem, and if so, how to solve this ?
> > >
> > > Regards,
> > > Panjo
> > >
> > >