I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
I was able to complete the installation of the "released" version of Visual
Studio. During the install, I did receive a few error messages about SQL
Server but proceeded with the install. VS completed its installation and
appears to OK.
However, whe I treid to continue with the SQL Server 2005 installation, my
real problems started. First, I had to "uninstall" the CTP components. I
started with "Add/Remove Programs" but the only SQL CTP components that were
listed would NOT uninstall. In fact, trying to uninstall them just resulted
in their entries disappearing from the "Add/Remove Programs" list. There is
nothing left in that list related to the VS or SQL CTP programs.
I was then able to install the SQL 2005 "native client" successfully but
cannot install SQL 2005 itself. I receive an error that "beta" compoents were
detected and must be removed before installing SQL 2005. I cannot uninstall
them through "Add/Remove Programs" so it looks like they'll have to be
uninstalled manually, assuming this is doable, of course. I have no idea how
to accomplish this.
Any help with removing the SQL Server 2005 Apr CTP components and/or
proceeding with the SQL 2005 installation would be "greatly" appreciated.
Thank you.
Denis W. Repke
Try running this MS uninstall utility...should do the trick for you.
http://go.microsoft.com/fwlink/?LinkId=47598
|||Gregg,
Thanks for the quick reply. However...
Doesn't this program just uninstall the Visual Studio components? If so,
that's not my problem.
I have already uninstalled all of the Visual Studio CTP components and
completed installation of the Visual Studio 2005 "released" version. My
problem is removing the SQL Server 2005 CTP components so that I can install
the "released" version of SQL Server 2005. I cannot do this using "Add/Remove
Programs".
Denis W. Repke
"Gregg Walker" wrote:
> Try running this MS uninstall utility...should do the trick for you.
> http://go.microsoft.com/fwlink/?LinkId=47598
>
>
|||Denis,
Given what you have done I think you need to go back a step in order
to have a chance of going forward successfully.
I suggest you do the following:
1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
it fairly straightforwardly)
2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
you could re-install it and try to uninstall April CTP components
using Add/Remove Programs.
3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
See http://support.microsoft.com/default...b;en-us;290301 for
further information. It's wise to back up important files.
4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
then install SQL Server 2005 RTM (it should be installed before Visual
Studio). This is the moment of truth - if SQL Server RTM installs
cleanly you should be in good shape to go on to Step 5.
5. Install Visual Studio 2005 RTM again.
Good luck.
Andrew Watt
MVP - InfoPath
On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
<DenisRepke@.discussions.microsoft.com> wrote:
>I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
>Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
>mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
>I was able to complete the installation of the "released" version of Visual
>Studio. During the install, I did receive a few error messages about SQL
>Server but proceeded with the install. VS completed its installation and
>appears to OK.
>However, whe I treid to continue with the SQL Server 2005 installation, my
>real problems started. First, I had to "uninstall" the CTP components. I
>started with "Add/Remove Programs" but the only SQL CTP components that were
>listed would NOT uninstall. In fact, trying to uninstall them just resulted
>in their entries disappearing from the "Add/Remove Programs" list. There is
>nothing left in that list related to the VS or SQL CTP programs.
>I was then able to install the SQL 2005 "native client" successfully but
>cannot install SQL 2005 itself. I receive an error that "beta" compoents were
>detected and must be removed before installing SQL 2005. I cannot uninstall
>them through "Add/Remove Programs" so it looks like they'll have to be
>uninstalled manually, assuming this is doable, of course. I have no idea how
>to accomplish this.
>Any help with removing the SQL Server 2005 Apr CTP components and/or
>proceeding with the SQL 2005 installation would be "greatly" appreciated.
>Thank you.
|||Andrew,
I guess I'll have to try your suggestions. Nothing else is working. I did
also try running the "build unistall" program from the Sept CTP. That did NOT
work. Thanks for the help.
Denis W. Repke
"Andrew Watt [MVP - InfoPath]" wrote:
> Denis,
> Given what you have done I think you need to go back a step in order
> to have a chance of going forward successfully.
> I suggest you do the following:
> 1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
> it fairly straightforwardly)
> 2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
> you could re-install it and try to uninstall April CTP components
> using Add/Remove Programs.
> 3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
> See http://support.microsoft.com/default...b;en-us;290301 for
> further information. It's wise to back up important files.
> 4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
> then install SQL Server 2005 RTM (it should be installed before Visual
> Studio). This is the moment of truth - if SQL Server RTM installs
> cleanly you should be in good shape to go on to Step 5.
> 5. Install Visual Studio 2005 RTM again.
> Good luck.
> Andrew Watt
> MVP - InfoPath
> On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
> <DenisRepke@.discussions.microsoft.com> wrote:
>
>
Showing posts with label upgrade. Show all posts
Showing posts with label upgrade. Show all posts
Friday, March 30, 2012
Problems installing SQL Server 2005
I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
I was able to complete the installation of the "released" version of Visual
Studio. During the install, I did receive a few error messages about SQL
Server but proceeded with the install. VS completed its installation and
appears to OK.
However, whe I treid to continue with the SQL Server 2005 installation, my
real problems started. First, I had to "uninstall" the CTP components. I
started with "Add/Remove Programs" but the only SQL CTP components that were
listed would NOT uninstall. In fact, trying to uninstall them just resulted
in their entries disappearing from the "Add/Remove Programs" list. There is
nothing left in that list related to the VS or SQL CTP programs.
I was then able to install the SQL 2005 "native client" successfully but
cannot install SQL 2005 itself. I receive an error that "beta" compoents were
detected and must be removed before installing SQL 2005. I cannot uninstall
them through "Add/Remove Programs" so it looks like they'll have to be
uninstalled manually, assuming this is doable, of course. I have no idea how
to accomplish this.
Any help with removing the SQL Server 2005 Apr CTP components and/or
proceeding with the SQL 2005 installation would be "greatly" appreciated.
Thank you.
--
Denis W. RepkeTry running this MS uninstall utility...should do the trick for you.
http://go.microsoft.com/fwlink/?LinkId=47598|||Gregg,
Thanks for the quick reply. However...
Doesn't this program just uninstall the Visual Studio components? If so,
that's not my problem.
I have already uninstalled all of the Visual Studio CTP components and
completed installation of the Visual Studio 2005 "released" version. My
problem is removing the SQL Server 2005 CTP components so that I can install
the "released" version of SQL Server 2005. I cannot do this using "Add/Remove
Programs".
--
Denis W. Repke
"Gregg Walker" wrote:
> Try running this MS uninstall utility...should do the trick for you.
> http://go.microsoft.com/fwlink/?LinkId=47598
>
>|||Denis,
Given what you have done I think you need to go back a step in order
to have a chance of going forward successfully.
I suggest you do the following:
1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
it fairly straightforwardly)
2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
you could re-install it and try to uninstall April CTP components
using Add/Remove Programs.
3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 for
further information. It's wise to back up important files.
4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
then install SQL Server 2005 RTM (it should be installed before Visual
Studio). This is the moment of truth - if SQL Server RTM installs
cleanly you should be in good shape to go on to Step 5.
5. Install Visual Studio 2005 RTM again.
Good luck.
Andrew Watt
MVP - InfoPath
On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
<DenisRepke@.discussions.microsoft.com> wrote:
>I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
>Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
>mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
>I was able to complete the installation of the "released" version of Visual
>Studio. During the install, I did receive a few error messages about SQL
>Server but proceeded with the install. VS completed its installation and
>appears to OK.
>However, whe I treid to continue with the SQL Server 2005 installation, my
>real problems started. First, I had to "uninstall" the CTP components. I
>started with "Add/Remove Programs" but the only SQL CTP components that were
>listed would NOT uninstall. In fact, trying to uninstall them just resulted
>in their entries disappearing from the "Add/Remove Programs" list. There is
>nothing left in that list related to the VS or SQL CTP programs.
>I was then able to install the SQL 2005 "native client" successfully but
>cannot install SQL 2005 itself. I receive an error that "beta" compoents were
>detected and must be removed before installing SQL 2005. I cannot uninstall
>them through "Add/Remove Programs" so it looks like they'll have to be
>uninstalled manually, assuming this is doable, of course. I have no idea how
>to accomplish this.
>Any help with removing the SQL Server 2005 Apr CTP components and/or
>proceeding with the SQL 2005 installation would be "greatly" appreciated.
>Thank you.|||Andrew,
I guess I'll have to try your suggestions. Nothing else is working. I did
also try running the "build unistall" program from the Sept CTP. That did NOT
work. Thanks for the help.
--
Denis W. Repke
"Andrew Watt [MVP - InfoPath]" wrote:
> Denis,
> Given what you have done I think you need to go back a step in order
> to have a chance of going forward successfully.
> I suggest you do the following:
> 1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
> it fairly straightforwardly)
> 2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
> you could re-install it and try to uninstall April CTP components
> using Add/Remove Programs.
> 3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
> See http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 for
> further information. It's wise to back up important files.
> 4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
> then install SQL Server 2005 RTM (it should be installed before Visual
> Studio). This is the moment of truth - if SQL Server RTM installs
> cleanly you should be in good shape to go on to Step 5.
> 5. Install Visual Studio 2005 RTM again.
> Good luck.
> Andrew Watt
> MVP - InfoPath
> On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
> <DenisRepke@.discussions.microsoft.com> wrote:
> >I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
> >Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
> >mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
> >I was able to complete the installation of the "released" version of Visual
> >Studio. During the install, I did receive a few error messages about SQL
> >Server but proceeded with the install. VS completed its installation and
> >appears to OK.
> >
> >However, whe I treid to continue with the SQL Server 2005 installation, my
> >real problems started. First, I had to "uninstall" the CTP components. I
> >started with "Add/Remove Programs" but the only SQL CTP components that were
> >listed would NOT uninstall. In fact, trying to uninstall them just resulted
> >in their entries disappearing from the "Add/Remove Programs" list. There is
> >nothing left in that list related to the VS or SQL CTP programs.
> >
> >I was then able to install the SQL 2005 "native client" successfully but
> >cannot install SQL 2005 itself. I receive an error that "beta" compoents were
> >detected and must be removed before installing SQL 2005. I cannot uninstall
> >them through "Add/Remove Programs" so it looks like they'll have to be
> >uninstalled manually, assuming this is doable, of course. I have no idea how
> >to accomplish this.
> >
> >Any help with removing the SQL Server 2005 Apr CTP components and/or
> >proceeding with the SQL 2005 installation would be "greatly" appreciated.
> >Thank you.
>
Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
I was able to complete the installation of the "released" version of Visual
Studio. During the install, I did receive a few error messages about SQL
Server but proceeded with the install. VS completed its installation and
appears to OK.
However, whe I treid to continue with the SQL Server 2005 installation, my
real problems started. First, I had to "uninstall" the CTP components. I
started with "Add/Remove Programs" but the only SQL CTP components that were
listed would NOT uninstall. In fact, trying to uninstall them just resulted
in their entries disappearing from the "Add/Remove Programs" list. There is
nothing left in that list related to the VS or SQL CTP programs.
I was then able to install the SQL 2005 "native client" successfully but
cannot install SQL 2005 itself. I receive an error that "beta" compoents were
detected and must be removed before installing SQL 2005. I cannot uninstall
them through "Add/Remove Programs" so it looks like they'll have to be
uninstalled manually, assuming this is doable, of course. I have no idea how
to accomplish this.
Any help with removing the SQL Server 2005 Apr CTP components and/or
proceeding with the SQL 2005 installation would be "greatly" appreciated.
Thank you.
--
Denis W. RepkeTry running this MS uninstall utility...should do the trick for you.
http://go.microsoft.com/fwlink/?LinkId=47598|||Gregg,
Thanks for the quick reply. However...
Doesn't this program just uninstall the Visual Studio components? If so,
that's not my problem.
I have already uninstalled all of the Visual Studio CTP components and
completed installation of the Visual Studio 2005 "released" version. My
problem is removing the SQL Server 2005 CTP components so that I can install
the "released" version of SQL Server 2005. I cannot do this using "Add/Remove
Programs".
--
Denis W. Repke
"Gregg Walker" wrote:
> Try running this MS uninstall utility...should do the trick for you.
> http://go.microsoft.com/fwlink/?LinkId=47598
>
>|||Denis,
Given what you have done I think you need to go back a step in order
to have a chance of going forward successfully.
I suggest you do the following:
1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
it fairly straightforwardly)
2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
you could re-install it and try to uninstall April CTP components
using Add/Remove Programs.
3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 for
further information. It's wise to back up important files.
4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
then install SQL Server 2005 RTM (it should be installed before Visual
Studio). This is the moment of truth - if SQL Server RTM installs
cleanly you should be in good shape to go on to Step 5.
5. Install Visual Studio 2005 RTM again.
Good luck.
Andrew Watt
MVP - InfoPath
On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
<DenisRepke@.discussions.microsoft.com> wrote:
>I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
>Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
>mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
>I was able to complete the installation of the "released" version of Visual
>Studio. During the install, I did receive a few error messages about SQL
>Server but proceeded with the install. VS completed its installation and
>appears to OK.
>However, whe I treid to continue with the SQL Server 2005 installation, my
>real problems started. First, I had to "uninstall" the CTP components. I
>started with "Add/Remove Programs" but the only SQL CTP components that were
>listed would NOT uninstall. In fact, trying to uninstall them just resulted
>in their entries disappearing from the "Add/Remove Programs" list. There is
>nothing left in that list related to the VS or SQL CTP programs.
>I was then able to install the SQL 2005 "native client" successfully but
>cannot install SQL 2005 itself. I receive an error that "beta" compoents were
>detected and must be removed before installing SQL 2005. I cannot uninstall
>them through "Add/Remove Programs" so it looks like they'll have to be
>uninstalled manually, assuming this is doable, of course. I have no idea how
>to accomplish this.
>Any help with removing the SQL Server 2005 Apr CTP components and/or
>proceeding with the SQL 2005 installation would be "greatly" appreciated.
>Thank you.|||Andrew,
I guess I'll have to try your suggestions. Nothing else is working. I did
also try running the "build unistall" program from the Sept CTP. That did NOT
work. Thanks for the help.
--
Denis W. Repke
"Andrew Watt [MVP - InfoPath]" wrote:
> Denis,
> Given what you have done I think you need to go back a step in order
> to have a chance of going forward successfully.
> I suggest you do the following:
> 1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
> it fairly straightforwardly)
> 2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
> you could re-install it and try to uninstall April CTP components
> using Add/Remove Programs.
> 3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
> See http://support.microsoft.com/default.aspx?scid=kb;en-us;290301 for
> further information. It's wise to back up important files.
> 4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
> then install SQL Server 2005 RTM (it should be installed before Visual
> Studio). This is the moment of truth - if SQL Server RTM installs
> cleanly you should be in good shape to go on to Step 5.
> 5. Install Visual Studio 2005 RTM again.
> Good luck.
> Andrew Watt
> MVP - InfoPath
> On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
> <DenisRepke@.discussions.microsoft.com> wrote:
> >I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
> >Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
> >mistake of uninstalling the Visual Studio CTP "first". After uninstalling it,
> >I was able to complete the installation of the "released" version of Visual
> >Studio. During the install, I did receive a few error messages about SQL
> >Server but proceeded with the install. VS completed its installation and
> >appears to OK.
> >
> >However, whe I treid to continue with the SQL Server 2005 installation, my
> >real problems started. First, I had to "uninstall" the CTP components. I
> >started with "Add/Remove Programs" but the only SQL CTP components that were
> >listed would NOT uninstall. In fact, trying to uninstall them just resulted
> >in their entries disappearing from the "Add/Remove Programs" list. There is
> >nothing left in that list related to the VS or SQL CTP programs.
> >
> >I was then able to install the SQL 2005 "native client" successfully but
> >cannot install SQL 2005 itself. I receive an error that "beta" compoents were
> >detected and must be removed before installing SQL 2005. I cannot uninstall
> >them through "Add/Remove Programs" so it looks like they'll have to be
> >uninstalled manually, assuming this is doable, of course. I have no idea how
> >to accomplish this.
> >
> >Any help with removing the SQL Server 2005 Apr CTP components and/or
> >proceeding with the SQL 2005 installation would be "greatly" appreciated.
> >Thank you.
>
Problems installing SQL Server 2005
I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
mistake of uninstalling the Visual Studio CTP "first". After uninstalling it
,
I was able to complete the installation of the "released" version of Visual
Studio. During the install, I did receive a few error messages about SQL
Server but proceeded with the install. VS completed its installation and
appears to OK.
However, whe I treid to continue with the SQL Server 2005 installation, my
real problems started. First, I had to "uninstall" the CTP components. I
started with "Add/Remove Programs" but the only SQL CTP components that were
listed would NOT uninstall. In fact, trying to uninstall them just resulted
in their entries disappearing from the "Add/Remove Programs" list. There is
nothing left in that list related to the VS or SQL CTP programs.
I was then able to install the SQL 2005 "native client" successfully but
cannot install SQL 2005 itself. I receive an error that "beta" compoents wer
e
detected and must be removed before installing SQL 2005. I cannot uninstall
them through "Add/Remove Programs" so it looks like they'll have to be
uninstalled manually, assuming this is doable, of course. I have no idea how
to accomplish this.
Any help with removing the SQL Server 2005 Apr CTP components and/or
proceeding with the SQL 2005 installation would be "greatly" appreciated.
Thank you.
--
Denis W. RepkeTry running this MS uninstall utility...should do the trick for you.
http://go.microsoft.com/fwlink/?LinkId=47598|||Gregg,
Thanks for the quick reply. However...
Doesn't this program just uninstall the Visual Studio components? If so,
that's not my problem.
I have already uninstalled all of the Visual Studio CTP components and
completed installation of the Visual Studio 2005 "released" version. My
problem is removing the SQL Server 2005 CTP components so that I can install
the "released" version of SQL Server 2005. I cannot do this using "Add/Remov
e
Programs".
Denis W. Repke
"Gregg Walker" wrote:
> Try running this MS uninstall utility...should do the trick for you.
> http://go.microsoft.com/fwlink/?LinkId=47598
>
>|||Denis,
Given what you have done I think you need to go back a step in order
to have a chance of going forward successfully.
I suggest you do the following:
1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
it fairly straightforwardly)
2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
you could re-install it and try to uninstall April CTP components
using Add/Remove Programs.
3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
See http://support.microsoft.com/defaul...kb;en-us;290301 for
further information. It's wise to back up important files.
4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
then install SQL Server 2005 RTM (it should be installed before Visual
Studio). This is the moment of truth - if SQL Server RTM installs
cleanly you should be in good shape to go on to Step 5.
5. Install Visual Studio 2005 RTM again.
Good luck.
Andrew Watt
MVP - InfoPath
On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
<DenisRepke@.discussions.microsoft.com> wrote:
>I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
>Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
>mistake of uninstalling the Visual Studio CTP "first". After uninstalling i
t,
>I was able to complete the installation of the "released" version of Visual
>Studio. During the install, I did receive a few error messages about SQL
>Server but proceeded with the install. VS completed its installation and
>appears to OK.
>However, whe I treid to continue with the SQL Server 2005 installation, my
>real problems started. First, I had to "uninstall" the CTP components. I
>started with "Add/Remove Programs" but the only SQL CTP components that wer
e
>listed would NOT uninstall. In fact, trying to uninstall them just resulted
>in their entries disappearing from the "Add/Remove Programs" list. There is
>nothing left in that list related to the VS or SQL CTP programs.
>I was then able to install the SQL 2005 "native client" successfully but
>cannot install SQL 2005 itself. I receive an error that "beta" compoents we
re
>detected and must be removed before installing SQL 2005. I cannot uninstall
>them through "Add/Remove Programs" so it looks like they'll have to be
>uninstalled manually, assuming this is doable, of course. I have no idea ho
w
>to accomplish this.
>Any help with removing the SQL Server 2005 Apr CTP components and/or
>proceeding with the SQL 2005 installation would be "greatly" appreciated.
>Thank you.|||Andrew,
I guess I'll have to try your suggestions. Nothing else is working. I did
also try running the "build unistall" program from the Sept CTP. That did NO
T
work. Thanks for the help.
Denis W. Repke
"Andrew Watt [MVP - InfoPath]" wrote:
> Denis,
> Given what you have done I think you need to go back a step in order
> to have a chance of going forward successfully.
> I suggest you do the following:
> 1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
> it fairly straightforwardly)
> 2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
> you could re-install it and try to uninstall April CTP components
> using Add/Remove Programs.
> 3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
> See http://support.microsoft.com/defaul...kb;en-us;290301 for
> further information. It's wise to back up important files.
> 4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
> then install SQL Server 2005 RTM (it should be installed before Visual
> Studio). This is the moment of truth - if SQL Server RTM installs
> cleanly you should be in good shape to go on to Step 5.
> 5. Install Visual Studio 2005 RTM again.
> Good luck.
> Andrew Watt
> MVP - InfoPath
> On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
> <DenisRepke@.discussions.microsoft.com> wrote:
>
>
Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
mistake of uninstalling the Visual Studio CTP "first". After uninstalling it
,
I was able to complete the installation of the "released" version of Visual
Studio. During the install, I did receive a few error messages about SQL
Server but proceeded with the install. VS completed its installation and
appears to OK.
However, whe I treid to continue with the SQL Server 2005 installation, my
real problems started. First, I had to "uninstall" the CTP components. I
started with "Add/Remove Programs" but the only SQL CTP components that were
listed would NOT uninstall. In fact, trying to uninstall them just resulted
in their entries disappearing from the "Add/Remove Programs" list. There is
nothing left in that list related to the VS or SQL CTP programs.
I was then able to install the SQL 2005 "native client" successfully but
cannot install SQL 2005 itself. I receive an error that "beta" compoents wer
e
detected and must be removed before installing SQL 2005. I cannot uninstall
them through "Add/Remove Programs" so it looks like they'll have to be
uninstalled manually, assuming this is doable, of course. I have no idea how
to accomplish this.
Any help with removing the SQL Server 2005 Apr CTP components and/or
proceeding with the SQL 2005 installation would be "greatly" appreciated.
Thank you.
--
Denis W. RepkeTry running this MS uninstall utility...should do the trick for you.
http://go.microsoft.com/fwlink/?LinkId=47598|||Gregg,
Thanks for the quick reply. However...
Doesn't this program just uninstall the Visual Studio components? If so,
that's not my problem.
I have already uninstalled all of the Visual Studio CTP components and
completed installation of the Visual Studio 2005 "released" version. My
problem is removing the SQL Server 2005 CTP components so that I can install
the "released" version of SQL Server 2005. I cannot do this using "Add/Remov
e
Programs".
Denis W. Repke
"Gregg Walker" wrote:
> Try running this MS uninstall utility...should do the trick for you.
> http://go.microsoft.com/fwlink/?LinkId=47598
>
>|||Denis,
Given what you have done I think you need to go back a step in order
to have a chance of going forward successfully.
I suggest you do the following:
1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
it fairly straightforwardly)
2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
you could re-install it and try to uninstall April CTP components
using Add/Remove Programs.
3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
See http://support.microsoft.com/defaul...kb;en-us;290301 for
further information. It's wise to back up important files.
4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
then install SQL Server 2005 RTM (it should be installed before Visual
Studio). This is the moment of truth - if SQL Server RTM installs
cleanly you should be in good shape to go on to Step 5.
5. Install Visual Studio 2005 RTM again.
Good luck.
Andrew Watt
MVP - InfoPath
On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
<DenisRepke@.discussions.microsoft.com> wrote:
>I am trying to upgrade my computer from Visual Studiio 2005 Apr CTP and SQL
>Server 2005 Apr CTP to the "released" versions. Unfortunately, I made the
>mistake of uninstalling the Visual Studio CTP "first". After uninstalling i
t,
>I was able to complete the installation of the "released" version of Visual
>Studio. During the install, I did receive a few error messages about SQL
>Server but proceeded with the install. VS completed its installation and
>appears to OK.
>However, whe I treid to continue with the SQL Server 2005 installation, my
>real problems started. First, I had to "uninstall" the CTP components. I
>started with "Add/Remove Programs" but the only SQL CTP components that wer
e
>listed would NOT uninstall. In fact, trying to uninstall them just resulted
>in their entries disappearing from the "Add/Remove Programs" list. There is
>nothing left in that list related to the VS or SQL CTP programs.
>I was then able to install the SQL 2005 "native client" successfully but
>cannot install SQL 2005 itself. I receive an error that "beta" compoents we
re
>detected and must be removed before installing SQL 2005. I cannot uninstall
>them through "Add/Remove Programs" so it looks like they'll have to be
>uninstalled manually, assuming this is doable, of course. I have no idea ho
w
>to accomplish this.
>Any help with removing the SQL Server 2005 Apr CTP components and/or
>proceeding with the SQL 2005 installation would be "greatly" appreciated.
>Thank you.|||Andrew,
I guess I'll have to try your suggestions. Nothing else is working. I did
also try running the "build unistall" program from the Sept CTP. That did NO
T
work. Thanks for the help.
Denis W. Repke
"Andrew Watt [MVP - InfoPath]" wrote:
> Denis,
> Given what you have done I think you need to go back a step in order
> to have a chance of going forward successfully.
> I suggest you do the following:
> 1. Uninstall the Visual Studio 2005 RTM (hopefully you can uninstall
> it fairly straightforwardly)
> 2. If you still have the .NET 2.0 Framework for April CTP (2.0.50215)
> you could re-install it and try to uninstall April CTP components
> using Add/Remove Programs.
> 3. Use msicuu2.exe to try to clean up any residual April CTP stuff.
> See http://support.microsoft.com/defaul...kb;en-us;290301 for
> further information. It's wise to back up important files.
> 4. Assuming that Steps 2 and 3 get rid of all the April CTP stuff,
> then install SQL Server 2005 RTM (it should be installed before Visual
> Studio). This is the moment of truth - if SQL Server RTM installs
> cleanly you should be in good shape to go on to Step 5.
> 5. Install Visual Studio 2005 RTM again.
> Good luck.
> Andrew Watt
> MVP - InfoPath
> On Wed, 2 Nov 2005 11:49:03 -0800, "Denis Repke"
> <DenisRepke@.discussions.microsoft.com> wrote:
>
>
Tuesday, March 20, 2012
Problems by upgrading MS SQL 2005 with SP 1
Hi, I have 3 servers running MS SQL 2005. The other 2 servers upgradet fine, but the last one failed on the databasepart. I am running the upgrade as administrator. And I am able to start the databases after the failed upgrade, but the maintanance plans and so on doesn't work. This is a production server, and I would be happy to get feedback saying it is OK to keep running producton on this machine?
We have desided to reinstall the software thursday if we don't manage to solve the problem.
Thanks for your help. :-)
The error thas was provided was:
02/04/2007 22:15:18.750 ================================================================================
02/04/2007 22:15:18.750 Hotfix package launched
02/04/2007 22:15:19.468 Product discovery successfully completed during the install process for MSSQLSERVER
02/04/2007 22:15:19.484 SP Level check successfully completed during the install process for MSSQLSERVER
02/04/2007 22:15:19.500 Product language check successfully completed during the install process for MSSQLSERVER
02/04/2007 22:15:19.515 Product version check successfully completed during the install process for MSSQLSERVER
02/04/2007 22:15:19.515 Command-line instance name check completed during the install process
02/04/2007 22:15:19.531 Baseline build check completed during the install process
02/04/2007 22:16:04.515 Attempting to install instance: MSSQLSERVER
02/04/2007 22:16:04.531 Attempting to install target: TD-SQL
02/04/2007 22:16:04.578 Attempting to stop service: MSSQLServer
02/04/2007 22:16:07.609 Successfully stopped service: MSSQLServer
02/04/2007 22:16:07.625 Attempting to check for locked files: sqlrun_sql.msp
02/04/2007 22:16:07.671 Attempting to check for locked files: \\TD-SQL\d$\a09b3d4743342a544b\HotFixSQL\Files\sqlrun_sql.msp
02/04/2007 22:16:07.687 Creating MSP locked file check log at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.out
02/04/2007 22:16:17.562 MSP returned 1602: The user cancels installation.
02/04/2007 22:16:17.718 Successfully checked file: \\TD-SQL\d$\a09b3d4743342a544b\HotFixSQL\Files\sqlrun_sql.msp
02/04/2007 22:16:17.734 Successfully opened registry key: System\CurrentControlSet\Control\Session Manager
02/04/2007 22:16:17.750 Failed to read registry key: PendingFileRenameOperations
02/04/2007 22:16:17.750 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlfilt.dll
02/04/2007 22:16:17.765 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ThaWBrkr.dll
02/04/2007 22:16:17.796 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\query.dll
02/04/2007 22:16:17.843 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nls400.dll
02/04/2007 22:16:17.843 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\nlhtml.dll
02/04/2007 22:16:17.859 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msir5jp.dll
02/04/2007 22:16:17.875 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msftesql.exe
02/04/2007 22:16:17.890 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msftepxy.dll
02/04/2007 22:16:17.890 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msftefd.exe
02/04/2007 22:16:17.906 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\msfte.dll
02/04/2007 22:16:17.921 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\LangWrbk.dll
02/04/2007 22:16:17.937 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\korwbrkr.dll
02/04/2007 22:16:17.937 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\infosoft.dll
02/04/2007 22:16:17.953 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\FTERef\FTERef.dll
02/04/2007 22:16:17.968 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\CHTBRKR.DLL
02/04/2007 22:16:17.984 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\ChsBrkr.dll
02/04/2007 22:16:18.000 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\Resources\1033\REPLRES.rll
02/04/2007 22:16:18.015 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\replrec.dll
02/04/2007 22:16:18.015 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\rplisapi.dll
02/04/2007 22:16:18.031 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.Replication\9.0.242.0__89845dcd8080cc91\Repl.dll
02/04/2007 22:16:18.046 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DataStorage\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.DataStorage.dll
02/04/2007 22:16:18.062 Failed to read version information for the following file: C:\Program Files\Common Files\Microsoft Shared\Database Replication\Resources\1033\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\rplhtfin.sql
02/04/2007 22:16:18.078 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\
C:\Program Files\Microsoft SQL Server\90\COM\qrdrsvc.exe
02/04/2007 22:16:18.078 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\snapshot.exe
02/04/2007 22:16:18.093 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\replmerg.exe
02/04/2007 22:16:18.109 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\tablediff.exe
02/04/2007 22:16:18.125 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\COM\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\COM\DISTRIB.exe
02/04/2007 22:16:18.140 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\DatabaseMail90.exe
02/04/2007 22:16:18.140 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\3082\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\2052\sqlevn70.rll
02/04/2007 22:16:18.156 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1042\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1041\sqlevn70.rll
02/04/2007 22:16:18.171 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1040\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1036\sqlevn70.rll
02/04/2007 22:16:18.187 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1031\sqlevn70.rll
02/04/2007 22:16:18.203 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1028\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\XPStar90.RLL
02/04/2007 22:16:18.218 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlaccess.dll
02/04/2007 22:16:18.234 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlaccess.dll
02/04/2007 22:16:18.234 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlaccess.dll
02/04/2007 22:16:18.250 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\6.6.3.5
C:\Program Files\Microsoft SQL Server\90\Shared\msxmlsql.dll
02/04/2007 22:16:18.265 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\2.0.3609.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xmlrw.dll
02/04/2007 22:16:18.281 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlsvc90.dll
02/04/2007 22:16:18.296 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlsvc90.dll
02/04/2007 22:16:18.312 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlsvc90.dll
02/04/2007 22:16:18.312 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLBOOT.dll
02/04/2007 22:16:18.328 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\xplog70.dll
02/04/2007 22:16:18.343 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\batchp~1.dll
02/04/2007 22:16:18.359 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAgentMail90.rll
02/04/2007 22:16:18.375 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAgentMail90.rll
02/04/2007 22:16:18.375 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAgentMail90.rll
02/04/2007 22:16:18.390 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAGENT90.RLL
02/04/2007 22:16:18.406 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAGENT90.RLL
02/04/2007 22:16:18.421 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033\SQLAGENT90.RLL
02/04/2007 22:16:18.437 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAgentMail90.dll
02/04/2007 22:16:18.437 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAgentMail90.dll
02/04/2007 22:16:18.453 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAgentMail90.dll
02/04/2007 22:16:18.468 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAGENT90.EXE
02/04/2007 22:16:18.484 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAGENT90.EXE
02/04/2007 22:16:18.500 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLAGENT90.EXE
02/04/2007 22:16:18.515 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\Resources\1033\9.0.2047.0
C:\Program Files\Microsoft SQL Server\90\Shared\msmdrdir.dll
02/04/2007 22:16:18.531 Failed to read version information for the following file: C:\Program Files\Common Files\System\ole db\2.0.3609.0
C:\Program Files\Common Files\System\ole db\xmlrw.dll
02/04/2007 22:16:18.531 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msmdlocal.dll
02/04/2007 22:16:18.546 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msmdlocal.dll
02/04/2007 22:16:18.562 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msmdlocal.dll
02/04/2007 22:16:18.578 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe
02/04/2007 22:16:18.593 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe
02/04/2007 22:16:18.593 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe
02/04/2007 22:16:18.609 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msasxpress.dll
02/04/2007 22:16:18.625 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msasxpress.dll
02/04/2007 22:16:18.640 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\msasxpress.dll
02/04/2007 22:16:18.656 Failed to read version information for the following file: C:\Program Files\Microsoft.NET\ADOMD.NET\90\en\Microsoft.AnalysisServices.AdomdClient.xml
02/04/2007 22:16:18.671 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft.NET\ADOMD.NET\90\Microsoft.AnalysisServices.AdomdClient.dll
02/04/2007 22:16:18.687 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.AnalysisServices.AdomdClient\9.0.242.0__89845dcd8080cc91\Microsoft.AnalysisServices.AdomdClient.dll
02/04/2007 22:16:18.703 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\sqlcm.xml
02/04/2007 22:16:18.718 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\SqlManager.rll
02/04/2007 22:16:18.718 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\SqlManager.rll
02/04/2007 22:16:18.734 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\SqlManager.rll
02/04/2007 22:16:18.750 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SqlManager.dll
02/04/2007 22:16:18.765 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SqlManager.dll
02/04/2007 22:16:18.781 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SqlManager.dll
02/04/2007 22:16:18.781 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\batchparser90.dll
02/04/2007 22:16:18.828 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\batchparser90.dll
02/04/2007 22:16:18.843 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\batchparser90.dll
02/04/2007 22:16:18.859 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\Resources\1033\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Install\sysdbupg.sql
02/04/2007 22:16:18.875 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLSVC90.DLL
02/04/2007 22:16:18.890 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLSVC90.DLL
02/04/2007 22:16:18.906 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLSVC90.DLL
02/04/2007 22:16:18.906 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\2.0.3609.0
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\SQLdiag.exe
02/04/2007 22:16:18.921 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Tools\Binn\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\Shared\sqlsvc~1.dll
02/04/2007 22:16:18.937 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlsecacctchg.dll
02/04/2007 22:16:18.953 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlsecacctchg.dll
02/04/2007 22:16:18.968 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlsecacctchg.dll
02/04/2007 22:16:18.984 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlftacct.dll
02/04/2007 22:16:18.984 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlftacct.dll
02/04/2007 22:16:19.000 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\sqlftacct.dll
02/04/2007 22:16:19.015 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\isacctchange.dll
02/04/2007 22:16:19.031 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\isacctchange.dll
02/04/2007 22:16:19.046 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\isacctchange.dll
02/04/2007 22:16:19.046 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\svrenumapi.dll
02/04/2007 22:16:19.062 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\svrenumapi.dll
02/04/2007 22:16:19.078 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\svrenumapi.dll
02/04/2007 22:16:19.093 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\2005.90.2047.0
C:\Program Files\Microsoft SQL Server\90\Shared\sqlsqm.exe
02/04/2007 22:16:19.109 Failed to read version information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\9.0.2047.0
C:\Program Files\Microsoft SQL Server\90\Shared\dbghelp.dll
02/04/2007 22:16:19.109 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\SqlDumper.exe
02/04/2007 22:16:19.125 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\SqlDumper.exe
02/04/2007 22:16:19.140 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\SqlDumper.exe
02/04/2007 22:16:19.156 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.Rmo\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.Rmo.dll
02/04/2007 22:16:19.171 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.AnalysisServices\9.0.242.0__89845dcd8080cc91\Microsoft.AnalysisServices.DLL
02/04/2007 22:16:19.187 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.DataWarehouse.Interfaces\9.0.242.0__89845dcd8080cc91\Microsoft.DataWarehouse.Interfaces.DLL
02/04/2007 22:16:19.203 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.RegSvrEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.RegSvrEnum.dll
02/04/2007 22:16:19.203 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
02/04/2007 22:16:19.218 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
02/04/2007 22:16:19.234 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.BatchParser\9.0.242.0__89845dcd8080cc91\microsoft.sqlserver.batchparser.dll
02/04/2007 22:16:19.250 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ServiceBrokerEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.ServiceBrokerEnum.dll
02/04/2007 22:16:19.265 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.WmiEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.WmiEnum.dll
02/04/2007 22:16:19.265 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SqlEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SqlEnum.dll
02/04/2007 22:16:19.281 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.SmoEnum\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.SmoEnum.dll
02/04/2007 22:16:19.296 Failed to read associated hotfix build information for the following file: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.Smo\9.0.242.0__89845dcd8080cc91\Microsoft.SqlServer.Smo.dll
02/04/2007 22:16:19.312 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\SqlSAC.exe
02/04/2007 22:16:19.328 Failed to read associated hotfix build information for the following file: C:\Program Files\Microsoft SQL Server\90\Shared\Microsoft.SqlSac.Public.dll
02/04/2007 22:16:19.390 Attempting to install file: sqlrun_sql.msp
02/04/2007 22:16:19.421 Attempting to install file: \\TD-SQL\d$\a09b3d4743342a544b\HotFixSQL\Files\sqlrun_sql.msp
02/04/2007 22:16:19.437 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log
02/04/2007 22:16:19.453 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
02/04/2007 22:16:19.468 Failed to read registry key: Debug
02/04/2007 22:17:48.656 MSP returned 1603: A fatal error occurred during installation.
02/04/2007 22:17:48.812 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
02/04/2007 22:17:48.828 Failed to read registry key: Debug
02/04/2007 22:17:48.843 Unable to install MSP file: \\TD-SQL\d$\a09b3d4743342a544b\HotFixSQL\Files\sqlrun_sql.msp
02/04/2007 22:17:48.859 The following exception occurred: Unable to install Windows Installer MSP file Date: 02/04/2007 22:17:48.859 File: \depot\sqlvault\setupmain\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
02/04/2007 22:17:48.906
02/04/2007 22:17:48.921 Product Status Summary:
02/04/2007 22:17:48.937 Product: SQL Server Native Client
02/04/2007 22:17:48.953 SQL Server Native Client (RTM ) - Success
02/04/2007 22:17:48.968
02/04/2007 22:17:48.984 Product: Setup Support Files
02/04/2007 22:17:49.000 Setup Support Files (RTM ) - Success
02/04/2007 22:17:49.015
02/04/2007 22:17:49.031 Product: Database Services
02/04/2007 22:17:49.046 Database Services (SP1 2047 ENU) - Failure
02/04/2007 22:17:49.062 Details: Unable to install Windows Installer MSP file
02/04/2007 22:17:49.062
02/04/2007 22:17:49.078 Product: Integration Services
02/04/2007 22:17:49.093 Integration Services (SP1 2047 ENU) - Not Applied
02/04/2007 22:17:49.109
02/04/2007 22:17:49.125 Product: Client Components
02/04/2007 22:17:49.140 Client Components (SP1 2047 ENU) - Not Applied
02/04/2007 22:17:49.156
02/04/2007 22:17:49.171 Product: MSXML 6.0 Parser
02/04/2007 22:17:49.187 MSXML 6.0 Parser (RTM ) - Not Applied
02/04/2007 22:17:49.203
02/04/2007 22:17:49.203 Product: SQLXML4
02/04/2007 22:17:49.234 SQLXML4 (RTM ) - Not Applied
02/04/2007 22:17:49.234
02/04/2007 22:17:49.250 Product: Backward Compatibility
02/04/2007 22:17:49.265 Backward Compatibility (RTM ) - Not Applied
02/04/2007 22:17:49.281
02/04/2007 22:17:49.296 Product: Microsoft SQL Server VSS Writer
02/04/2007 22:17:49.312 Microsoft SQL Server VSS Writer (RTM ) - Not Selected
02/04/2007 22:17:49.328
Can you search through the log files for the text string "value 3" and post the 10-20 lines above that? The log location appears to be here:
02/04/2007 22:16:19.437 Creating MSP install log file at: C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log
This will give us a more descriptive error message to work with.
Thanks,
Sam Lester (MSFT)
We have desided to reinstall the software thursday if we don't manage to solve the problem.
Thanks for your help. :-)
Hanne
*****************************************************************
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CommitSqlUpgrade
PerfTime Start: CommitSqlUpgrade : Sun Feb 04 22:17:47 2007
<Func Name='ComponentUpgrade'>
There was a failure during installation search up in this log file for this message:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Unable to open the physical file "D:\MSSQL\Data\braArkiv_Arendal.mdf". Operating system error 32: "32(error not found)".. To continue, correct the problem, and then run SQL Server Setup again.
<EndFunc Name='ComponentUpgrade' Return='5120' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Sun Feb 04 22:17:47 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='5120' GetLastError='0'>
MSI (s) (6C:68) [22:17:48:109]: Transforming table InstallExecuteSequence.
MSI (s) (6C:68) [22:17:48:109]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (6C:68) [22:17:48:109]: Transforming table InstallExecuteSequence.
MSI (s) (6C:68) [22:17:48:109]: Transforming table InstallExecuteSequence.
MSI (s) (6C:68) [22:17:48:109]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (6C:68) [22:17:48:109]: Transforming table InstallExecuteSequence.
MSI (s) (6C:68) [22:17:48:109]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (6C:68) [22:17:48:109]: Transforming table InstallExecuteSequence.
MSI (s) (6C:68) [22:17:48:109]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 22:17:48: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3
********************************************************************|||
Does the referenced file exist?
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Unable to open the physical file "D:\MSSQL\Data\braArkiv_Arendal.mdf". Operating system error 32: "32(error not found)".. To continue, correct the problem, and then run SQL Server Setup again.
Thanks,
Sam
|||Yes, the file exist. It seems to me that Operatin system error 32 means: The process cannot access the file because it is being used by
another process. (From this site: http://search.stilegal.com/main/R10307.htm ) We have got this error message from time to time, but the database seems to work normal?
Friday, March 9, 2012
Problem writing data after upgrading
Hello,
I was using for years an application that had an MSDE database.
Recently. I've upgraded my computer to Windows Vista, so I had to upgrade MSDE to SQL Express.
I've managed to attach the old MSDE database of the application to SQL Express, and I am able to retrieve my data from within the application.
My problem is that I can not write or update data from within the application anymore. However, If I open a table in SQL Management Studio Express I can write/ update data with no problem.
The company that build the application I was using doesnt exist any more so I cant take any support from them.
The only thing I know for a fact is that the application is connecting to the database using the sa user.
Any ideas?
Thanks a lot in advance!!!
Tassos
hi,
that would need some deeper investigation. What are you experiencing during trying to update the database ? Do you get an error ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Just an error within the application saying "Update failed"|||That is a wrapped error of the application not a SQL Server error, you will either have to use the SQL Server profiler (which is NOT included in SQL Server Express) or change the application to expose the error messages which come directly from the server.HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
Problem writing data after upgrading
Hello,
I was using for years an application that had an MSDE database.
Recently. I've upgraded my computer to Windows Vista, so I had to upgrade MSDE to SQL Express.
I've managed to attach the old MSDE database of the application to SQL Express, and I am able to retrieve my data from within the application.
My problem is that I can not write or update data from within the application anymore. However, If I open a table in SQL Management Studio Express I can write/ update data with no problem.
The company that build the application I was using doesnt exist any more so I cant take any support from them.
The only thing I know for a fact is that the application is connecting to the database using the sa user.
Any ideas?
Thanks a lot in advance!!!
Tassos
hi,
that would need some deeper investigation. What are you experiencing during trying to update the database ? Do you get an error ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Just an error within the application saying "Update failed"|||That is a wrapped error of the application not a SQL Server error, you will either have to use the SQL Server profiler (which is NOT included in SQL Server Express) or change the application to expose the error messages which come directly from the server.HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
Subscribe to:
Posts (Atom)