Hi All,
I have a client who last night attempted to install sql 2000 Enterprise
Edition SP4. When running the first time through it got past the Password
Validation and moved to the Analysing and Preparing stage of the
installation. At this point it completely hung - after an hour there was
still no activity.
Now when attempting to re-install SP3a it states that a later version is
already installed and when attempting to reinstall SP4 it hangs on password
validation everytime.
This is a production server, does anyone know if it is possible to recover
from the above scenario?
Thanks
LarryJosh
I have been istalling SP4 mamy times and have never got the situation. Hmmm,
try tirn off (from the network) the server and re-install SP4
"Josh Lawrence" <someone@.microsoft.com> wrote in message
news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
> Hi All,
> I have a client who last night attempted to install sql 2000 Enterprise
> Edition SP4. When running the first time through it got past the Password
> Validation and moved to the Analysing and Preparing stage of the
> installation. At this point it completely hung - after an hour there was
> still no activity.
> Now when attempting to re-install SP3a it states that a later version is
> already installed and when attempting to reinstall SP4 it hangs on
> password validation everytime.
> This is a production server, does anyone know if it is possible to recover
> from the above scenario?
> Thanks
> Larry
>|||I have experienced this issue previously but can't recall the solution. I
have the awful feeling it may require a complete reinstallation of SQL2000
from the ground up.
Thanks
Josh
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
> Josh
> I have been istalling SP4 mamy times and have never got the situation.
> Hmmm, try tirn off (from the network) the server and re-install SP4
>
>
> "Josh Lawrence" <someone@.microsoft.com> wrote in message
> news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
>|||Hi --
I have run into the exact same issue, where SP4 installation hangs on
password validation. It worked for me on number of other servers but it
doesn't work on this server.
I have tried using Windows and SQL Server authentication, sa without
password but it didn't make any difference.
Did anyone find a solution?
The funny thing is that @.@.version shows SP4, however it is Not SP4.
Thanks
Gurpreet
"Josh Lawrence" wrote:
> I have experienced this issue previously but can't recall the solution. I
> have the awful feeling it may require a complete reinstallation of SQL2000
> from the ground up.
> Thanks
> Josh
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
>
>
Showing posts with label failed. Show all posts
Showing posts with label failed. Show all posts
Friday, March 30, 2012
Is it possible to recover from failed sp4 installation?
Hi All,
I have a client who last night attempted to install sql 2000 Enterprise
Edition SP4. When running the first time through it got past the Password
Validation and moved to the Analysing and Preparing stage of the
installation. At this point it completely hung - after an hour there was
still no activity.
Now when attempting to re-install SP3a it states that a later version is
already installed and when attempting to reinstall SP4 it hangs on password
validation everytime.
This is a production server, does anyone know if it is possible to recover
from the above scenario?
Thanks
LarryJosh
I have been istalling SP4 mamy times and have never got the situation. Hmmm,
try tirn off (from the network) the server and re-install SP4
"Josh Lawrence" <someone@.microsoft.com> wrote in message
news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
> Hi All,
> I have a client who last night attempted to install sql 2000 Enterprise
> Edition SP4. When running the first time through it got past the Password
> Validation and moved to the Analysing and Preparing stage of the
> installation. At this point it completely hung - after an hour there was
> still no activity.
> Now when attempting to re-install SP3a it states that a later version is
> already installed and when attempting to reinstall SP4 it hangs on
> password validation everytime.
> This is a production server, does anyone know if it is possible to recover
> from the above scenario?
> Thanks
> Larry
>|||I have experienced this issue previously but can't recall the solution. I
have the awful feeling it may require a complete reinstallation of SQL2000
from the ground up.
Thanks
Josh
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
> Josh
> I have been istalling SP4 mamy times and have never got the situation.
> Hmmm, try tirn off (from the network) the server and re-install SP4
>
>
> "Josh Lawrence" <someone@.microsoft.com> wrote in message
> news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
>> Hi All,
>> I have a client who last night attempted to install sql 2000 Enterprise
>> Edition SP4. When running the first time through it got past the
>> Password Validation and moved to the Analysing and Preparing stage of the
>> installation. At this point it completely hung - after an hour there was
>> still no activity.
>> Now when attempting to re-install SP3a it states that a later version is
>> already installed and when attempting to reinstall SP4 it hangs on
>> password validation everytime.
>> This is a production server, does anyone know if it is possible to
>> recover from the above scenario?
>> Thanks
>> Larry
>|||Hi --
I have run into the exact same issue, where SP4 installation hangs on
password validation. It worked for me on number of other servers but it
doesn't work on this server.
I have tried using Windows and SQL Server authentication, sa without
password but it didn't make any difference.
Did anyone find a solution?
The funny thing is that @.@.version shows SP4, however it is Not SP4.
Thanks
Gurpreet
"Josh Lawrence" wrote:
> I have experienced this issue previously but can't recall the solution. I
> have the awful feeling it may require a complete reinstallation of SQL2000
> from the ground up.
> Thanks
> Josh
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
> > Josh
> > I have been istalling SP4 mamy times and have never got the situation.
> > Hmmm, try tirn off (from the network) the server and re-install SP4
> >
> >
> >
> >
> >
> > "Josh Lawrence" <someone@.microsoft.com> wrote in message
> > news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
> >> Hi All,
> >> I have a client who last night attempted to install sql 2000 Enterprise
> >> Edition SP4. When running the first time through it got past the
> >> Password Validation and moved to the Analysing and Preparing stage of the
> >> installation. At this point it completely hung - after an hour there was
> >> still no activity.
> >>
> >> Now when attempting to re-install SP3a it states that a later version is
> >> already installed and when attempting to reinstall SP4 it hangs on
> >> password validation everytime.
> >>
> >> This is a production server, does anyone know if it is possible to
> >> recover from the above scenario?
> >>
> >> Thanks
> >> Larry
> >>
> >
> >
>
>sql
I have a client who last night attempted to install sql 2000 Enterprise
Edition SP4. When running the first time through it got past the Password
Validation and moved to the Analysing and Preparing stage of the
installation. At this point it completely hung - after an hour there was
still no activity.
Now when attempting to re-install SP3a it states that a later version is
already installed and when attempting to reinstall SP4 it hangs on password
validation everytime.
This is a production server, does anyone know if it is possible to recover
from the above scenario?
Thanks
LarryJosh
I have been istalling SP4 mamy times and have never got the situation. Hmmm,
try tirn off (from the network) the server and re-install SP4
"Josh Lawrence" <someone@.microsoft.com> wrote in message
news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
> Hi All,
> I have a client who last night attempted to install sql 2000 Enterprise
> Edition SP4. When running the first time through it got past the Password
> Validation and moved to the Analysing and Preparing stage of the
> installation. At this point it completely hung - after an hour there was
> still no activity.
> Now when attempting to re-install SP3a it states that a later version is
> already installed and when attempting to reinstall SP4 it hangs on
> password validation everytime.
> This is a production server, does anyone know if it is possible to recover
> from the above scenario?
> Thanks
> Larry
>|||I have experienced this issue previously but can't recall the solution. I
have the awful feeling it may require a complete reinstallation of SQL2000
from the ground up.
Thanks
Josh
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
> Josh
> I have been istalling SP4 mamy times and have never got the situation.
> Hmmm, try tirn off (from the network) the server and re-install SP4
>
>
> "Josh Lawrence" <someone@.microsoft.com> wrote in message
> news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
>> Hi All,
>> I have a client who last night attempted to install sql 2000 Enterprise
>> Edition SP4. When running the first time through it got past the
>> Password Validation and moved to the Analysing and Preparing stage of the
>> installation. At this point it completely hung - after an hour there was
>> still no activity.
>> Now when attempting to re-install SP3a it states that a later version is
>> already installed and when attempting to reinstall SP4 it hangs on
>> password validation everytime.
>> This is a production server, does anyone know if it is possible to
>> recover from the above scenario?
>> Thanks
>> Larry
>|||Hi --
I have run into the exact same issue, where SP4 installation hangs on
password validation. It worked for me on number of other servers but it
doesn't work on this server.
I have tried using Windows and SQL Server authentication, sa without
password but it didn't make any difference.
Did anyone find a solution?
The funny thing is that @.@.version shows SP4, however it is Not SP4.
Thanks
Gurpreet
"Josh Lawrence" wrote:
> I have experienced this issue previously but can't recall the solution. I
> have the awful feeling it may require a complete reinstallation of SQL2000
> from the ground up.
> Thanks
> Josh
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:OryZZ2rtGHA.4752@.TK2MSFTNGP02.phx.gbl...
> > Josh
> > I have been istalling SP4 mamy times and have never got the situation.
> > Hmmm, try tirn off (from the network) the server and re-install SP4
> >
> >
> >
> >
> >
> > "Josh Lawrence" <someone@.microsoft.com> wrote in message
> > news:%23DgeHurtGHA.4544@.TK2MSFTNGP04.phx.gbl...
> >> Hi All,
> >> I have a client who last night attempted to install sql 2000 Enterprise
> >> Edition SP4. When running the first time through it got past the
> >> Password Validation and moved to the Analysing and Preparing stage of the
> >> installation. At this point it completely hung - after an hour there was
> >> still no activity.
> >>
> >> Now when attempting to re-install SP3a it states that a later version is
> >> already installed and when attempting to reinstall SP4 it hangs on
> >> password validation everytime.
> >>
> >> This is a production server, does anyone know if it is possible to
> >> recover from the above scenario?
> >>
> >> Thanks
> >> Larry
> >>
> >
> >
>
>sql
Monday, March 19, 2012
Is it possible to audit Failed Insert, Update and Delete statements?
Auditors want us to track when Insert, Update and Delete failures occur. Is this possible in SQL 2000?
They also want us to track schema changes. Is this possible?
Thanks, DaveWhat constitutes a "failure" for the purpose of the audit?
-PatP|||The statement does not execute and returns an error. I believe I can trap this failures in Profiler, but I'm not sure what type of overhead this would create. Several people have suggested triggers, but I'm not sure a trigger will execute on failed attempts, only successfull insert, updates and deletes.
If I take the Profiler approach I'm not sure it will show schema changes.
Dave|||If you tell it to, SQL Profiler can track ANYTHING that goes to SQL Server. DML that works or fails, schema changes, and everything else. The question is: How much disk are you willing to dedicate to making this happen?
With the Profiler running "wide open" on a moderately busy server you are looking at 2-3 Tb of data in a 24 hour period... Once you've collected the data, you need to figure out what (if anything) you are going to do with it!
The old Chinese adage applies: Be careful what you wish for, you might get it!
-PatP|||We will only be monitoring two or three ids. Not sure if a domain group can be monitored, but if so we will monitor at the group level. This is for Sarbanes-Oxley complaince, which is basically very strict management of database systems for financial institutions. My thanks to Enron. Our DBAs are allowed to manage development and model office environments and a consulting company gets to manage production. Sarbanes-Oxley requires we keep an eye on the production DBAs by monitoring their activity. Profiler may not be the best approach. Even though we will be monitoring a small number of ids, SQL Server still needs to perform conditional logic against all user activity to see if the filter criteria is being met. A software tool may produce less overhead.
Thanks, Dave|||Everybody loves the joy of SOX!
If you really, really need to, you can get C2 (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_config_09yd.asp) auditing from SQL-2000. There are thousands of auditing combinations, many of which are pretty much designed for exactly what you want to do.
I'd be hard pressed to recommend a third party product for this use... At least in my opinion, it is likely to be more work than it is worth in the long run.
-PatP
They also want us to track schema changes. Is this possible?
Thanks, DaveWhat constitutes a "failure" for the purpose of the audit?
-PatP|||The statement does not execute and returns an error. I believe I can trap this failures in Profiler, but I'm not sure what type of overhead this would create. Several people have suggested triggers, but I'm not sure a trigger will execute on failed attempts, only successfull insert, updates and deletes.
If I take the Profiler approach I'm not sure it will show schema changes.
Dave|||If you tell it to, SQL Profiler can track ANYTHING that goes to SQL Server. DML that works or fails, schema changes, and everything else. The question is: How much disk are you willing to dedicate to making this happen?
With the Profiler running "wide open" on a moderately busy server you are looking at 2-3 Tb of data in a 24 hour period... Once you've collected the data, you need to figure out what (if anything) you are going to do with it!
The old Chinese adage applies: Be careful what you wish for, you might get it!
-PatP|||We will only be monitoring two or three ids. Not sure if a domain group can be monitored, but if so we will monitor at the group level. This is for Sarbanes-Oxley complaince, which is basically very strict management of database systems for financial institutions. My thanks to Enron. Our DBAs are allowed to manage development and model office environments and a consulting company gets to manage production. Sarbanes-Oxley requires we keep an eye on the production DBAs by monitoring their activity. Profiler may not be the best approach. Even though we will be monitoring a small number of ids, SQL Server still needs to perform conditional logic against all user activity to see if the filter criteria is being met. A software tool may produce less overhead.
Thanks, Dave|||Everybody loves the joy of SOX!
If you really, really need to, you can get C2 (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_config_09yd.asp) auditing from SQL-2000. There are thousands of auditing combinations, many of which are pretty much designed for exactly what you want to do.
I'd be hard pressed to recommend a third party product for this use... At least in my opinion, it is likely to be more work than it is worth in the long run.
-PatP
Subscribe to:
Posts (Atom)