|
|
|
|
||||||
| ms.sqlserver.setup Questions about SQL Server. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hi Folks,
Wonder if this problem has been resolved? I'm sure it must have been, I've noticed many posts on the internet dating back to 2005. The problem is, I haven't been able to find the solution. I have several environments at Windows Server 2000 SP4, and a clean installation is failing every time on the second CD with this error (Subject). I can do an in-place upgrade without issue, only a clean install fails. Nearing the end of the installation the following error popped up “The wrong volume is in the drive. Please insert volume SQLSRVRS into the driveâ€. After searching the discussion groups, one workaround is to reinstall Client Components only. This workaround did not work for me – SQL Server installation complained that it was already installed. I noticed that SQL Server Management Studio was not available on the Program menu of the OS, so I tried to reinstall that component – no success. Your is appreciated. -- Thanks, Scott H. |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Hello Scott,
If there is a newer version of Workstation Components is already installed you can't install the RTM version to overwrite the newer one. What I mean by saying a newer version, I mean the Workstation Components that are already installed may be SP2 applied. And the SQL Server 2005 Instance that you are installing from your media is the RTM version which was released before any SP or update. So, you can try uninstalling current installed Workstation Components and then try installing Workstation Components using your SQL Server 2005 media. You can run the "SqlRun_Tools.msi" file which is in the second CD's Setup folder for this purpose. P.S. SSMS is under the Client Tools which is covered by Workstation Components. -- Ekrem Önsoy "Scott H." <ScottH@discussions.microsoft.com> wrote in message news:0D9FDB5B-EDDF-404F-A4FE-A39A249A3DA9@microsoft.com... > Hi Folks, > > Wonder if this problem has been resolved? I'm sure it must have been, I've > noticed many posts on the internet dating back to 2005. The problem is, I > haven't been able to find the solution. I have several environments at > Windows Server 2000 SP4, and a clean installation is failing every time on > the second CD with this error (Subject). I can do an in-place upgrade > without > issue, only a clean install fails. > > Nearing the end of the installation the following error popped up “The > wrong > volume is in the drive. Please insert volume SQLSRVRS into the driveâ€. > After > searching the discussion groups, one workaround is to reinstall Client > Components only. This workaround did not work for me – SQL Server > installation complained that it was already installed. I noticed that SQL > Server Management Studio was not available on the Program menu of the OS, > so > I tried to reinstall that component – no success. > > Your is appreciated. > -- > Thanks, > > Scott H. |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Ekrem,
Thank-you for your reply. This worked for me. By the way, I wasn't attempting to install SP 1 over RTM. At the time I had only RTM. Do you know if Microsoft have fixed this issue with the install? -- Thanks, Scott H. "Ekrem Önsoy" wrote: > Hello Scott, > > If there is a newer version of Workstation Components is already installed > you can't install the RTM version to overwrite the newer one. > > What I mean by saying a newer version, I mean the Workstation Components > that are already installed may be SP2 applied. And the SQL Server 2005 > Instance that you are installing from your media is the RTM version which > was released before any SP or update. > > So, you can try uninstalling current installed Workstation Components and > then try installing Workstation Components using your SQL Server 2005 media. > You can run the "SqlRun_Tools.msi" file which is in the second CD's Setup > folder for this purpose. > > P.S. > SSMS is under the Client Tools which is covered by Workstation Components. > > -- > Ekrem Önsoy > > > > "Scott H." <ScottH@discussions.microsoft.com> wrote in message > news:0D9FDB5B-EDDF-404F-A4FE-A39A249A3DA9@microsoft.com... > > Hi Folks, > > > > Wonder if this problem has been resolved? I'm sure it must have been, I've > > noticed many posts on the internet dating back to 2005. The problem is, I > > haven't been able to find the solution. I have several environments at > > Windows Server 2000 SP4, and a clean installation is failing every time on > > the second CD with this error (Subject). I can do an in-place upgrade > > without > > issue, only a clean install fails. > > > > Nearing the end of the installation the following error popped up “The > > wrong > > volume is in the drive. Please insert volume SQLSRVRS into the driveâ€. > > After > > searching the discussion groups, one workaround is to reinstall Client > > Components only. This workaround did not work for me – SQL Server > > installation complained that it was already installed. I noticed that SQL > > Server Management Studio was not available on the Program menu of the OS, > > so > > I tried to reinstall that component – no success. > > > > Your is appreciated. > > -- > > Thanks, > > > > Scott H. > > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
Well, I don't think there is something to get fixed here. Or maybe you meant
something different and I got it wrong. Simply, you can't install an older version to overwrite a newer one. And you can't install a component if it's already exists. -- Ekrem Önsoy "Scott H." <ScottH@discussions.microsoft.com> wrote in message news:95A02DFC-3ED8-4D2D-97B1-D9BE7C502D14@microsoft.com... > Ekrem, > > Thank-you for your reply. This worked for me. > > By the way, I wasn't attempting to install SP 1 over RTM. At the time I > had > only RTM. > > Do you know if Microsoft have fixed this issue with the install? > > -- > Thanks, > > Scott H. > > > "Ekrem Önsoy" wrote: > >> Hello Scott, >> >> If there is a newer version of Workstation Components is already >> installed >> you can't install the RTM version to overwrite the newer one. >> >> What I mean by saying a newer version, I mean the Workstation Components >> that are already installed may be SP2 applied. And the SQL Server 2005 >> Instance that you are installing from your media is the RTM version which >> was released before any SP or update. >> >> So, you can try uninstalling current installed Workstation Components and >> then try installing Workstation Components using your SQL Server 2005 >> media. >> You can run the "SqlRun_Tools.msi" file which is in the second CD's Setup >> folder for this purpose. >> >> P.S. >> SSMS is under the Client Tools which is covered by Workstation >> Components. >> >> -- >> Ekrem Önsoy >> >> >> >> "Scott H." <ScottH@discussions.microsoft.com> wrote in message >> news:0D9FDB5B-EDDF-404F-A4FE-A39A249A3DA9@microsoft.com... >> > Hi Folks, >> > >> > Wonder if this problem has been resolved? I'm sure it must have been, >> > I've >> > noticed many posts on the internet dating back to 2005. The problem is, >> > I >> > haven't been able to find the solution. I have several environments at >> > Windows Server 2000 SP4, and a clean installation is failing every time >> > on >> > the second CD with this error (Subject). I can do an in-place upgrade >> > without >> > issue, only a clean install fails. >> > >> > Nearing the end of the installation the following error popped up “The >> > wrong >> > volume is in the drive. Please insert volume SQLSRVRS into the driveâ€. >> > After >> > searching the discussion groups, one workaround is to reinstall Client >> > Components only. This workaround did not work for me – SQL Server >> > installation complained that it was already installed. I noticed that >> > SQL >> > Server Management Studio was not available on the Program menu of the >> > OS, >> > so >> > I tried to reinstall that component – no success. >> > >> > Your is appreciated. >> > -- >> > Thanks, >> > >> > Scott H. >> >> |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Ekram,
Let me see if I can do a better job explaining. There is definately something wrong with the installation. Objective: Upgrade to SQL Server 2005 Standard Edition SP2 from SQL Server 2000 Enterprise Edition SP3 by way of uninstall SQL2K and installing S2K5. Environment: OS: Windows Server 2000 Standard Edition SP4 (fresh install) Pre-SQL: SQL Server 2000 SP3 Enterprise Edition (fresh install) Post-SQL: SQL Server 2005 SP2 Standard Edition Upgrade Procedure: Uninstall SQL Server 2000 Enterprise Edition SP3 by way of Control Panel Install SQL Server 2005 Standard Edition SP2 Results/Observations: The installation failed on the second disk, reporting: “The wrong volume is in the drive. Please insert volume SQLSvr2005StdCD1 into drive D:". The error window has 3 options Cancel, Try Again, and Continue. Selecting either of these does nothing – I am stuck in the window. I am able to cancel the setup though. Am I missing something? This is a clean install, after first removing SQL2k. -- Thanks, Scott H. "Ekrem Önsoy" wrote: > Well, I don't think there is something to get fixed here. Or maybe you meant > something different and I got it wrong. > > Simply, you can't install an older version to overwrite a newer one. And you > can't install a component if it's already exists. > > -- > Ekrem Önsoy > > > > "Scott H." <ScottH@discussions.microsoft.com> wrote in message > news:95A02DFC-3ED8-4D2D-97B1-D9BE7C502D14@microsoft.com... > > Ekrem, > > > > Thank-you for your reply. This worked for me. > > > > By the way, I wasn't attempting to install SP 1 over RTM. At the time I > > had > > only RTM. > > > > Do you know if Microsoft have fixed this issue with the install? > > > > -- > > Thanks, > > > > Scott H. > > > > > > "Ekrem Önsoy" wrote: > > > >> Hello Scott, > >> > >> If there is a newer version of Workstation Components is already > >> installed > >> you can't install the RTM version to overwrite the newer one. > >> > >> What I mean by saying a newer version, I mean the Workstation Components > >> that are already installed may be SP2 applied. And the SQL Server 2005 > >> Instance that you are installing from your media is the RTM version which > >> was released before any SP or update. > >> > >> So, you can try uninstalling current installed Workstation Components and > >> then try installing Workstation Components using your SQL Server 2005 > >> media. > >> You can run the "SqlRun_Tools.msi" file which is in the second CD's Setup > >> folder for this purpose. > >> > >> P.S. > >> SSMS is under the Client Tools which is covered by Workstation > >> Components. > >> > >> -- > >> Ekrem Önsoy > >> > >> > >> > >> "Scott H." <ScottH@discussions.microsoft.com> wrote in message > >> news:0D9FDB5B-EDDF-404F-A4FE-A39A249A3DA9@microsoft.com... > >> > Hi Folks, > >> > > >> > Wonder if this problem has been resolved? I'm sure it must have been, > >> > I've > >> > noticed many posts on the internet dating back to 2005. The problem is, > >> > I > >> > haven't been able to find the solution. I have several environments at > >> > Windows Server 2000 SP4, and a clean installation is failing every time > >> > on > >> > the second CD with this error (Subject). I can do an in-place upgrade > >> > without > >> > issue, only a clean install fails. > >> > > >> > Nearing the end of the installation the following error popped up “The > >> > wrong > >> > volume is in the drive. Please insert volume SQLSRVRS into the driveâ€. > >> > After > >> > searching the discussion groups, one workaround is to reinstall Client > >> > Components only. This workaround did not work for me – SQL Server > >> > installation complained that it was already installed. I noticed that > >> > SQL > >> > Server Management Studio was not available on the Program menu of the > >> > OS, > >> > so > >> > I tried to reinstall that component – no success. > >> > > >> > Your is appreciated. > >> > -- > >> > Thanks, > >> > > >> > Scott H. > >> > >> > |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
This time your scenario was told pretty clear.
However one thing lingers in my mind. You said that you can perform an in place upgrade without any issue. And you draw your upgrade path from 2000's Enterprise Edition to Standard Edition of 2005. This is odd because this is not a valid upgrade path according to http://technet.microsoft.com/en-us/l.../ms143393.aspx I personally have not met this wrong volume problem in SQL Server Setup yet so I don't have an experience to share about this. But this problem looks like a generic Windows application problem rather than SQL Server related problem. Although I have not experienced this while installing SQL Server, I kind of remember this error while installing other products. This suggestion may sound stupid but did you try placing the first CD when it says "Please insert volume SQLSvr2005StdCD1 into drive D:" ? If so, what happens when you put the first media into the cd-tray? -- Ekrem Önsoy "Scott H." <ScottH@discussions.microsoft.com> wrote in message news:C37E16DD-AC81-4B98-B71B-BBA29E1980E7@microsoft.com... > Ekram, > > Let me see if I can do a better job explaining. There is definately > something wrong with the installation. > > Objective: > > Upgrade to SQL Server 2005 Standard Edition SP2 from SQL Server 2000 > Enterprise Edition SP3 by way of uninstall SQL2K and installing S2K5. > > Environment: > > OS: Windows Server 2000 Standard Edition SP4 (fresh install) > Pre-SQL: SQL Server 2000 SP3 Enterprise Edition (fresh install) > Post-SQL: SQL Server 2005 SP2 Standard Edition > > Upgrade Procedure: > > Uninstall SQL Server 2000 Enterprise Edition SP3 by way of Control Panel > Install SQL Server 2005 Standard Edition SP2 > > Results/Observations: > > The installation failed on the second disk, reporting: “The wrong volume > is > in the drive. Please insert volume SQLSvr2005StdCD1 into drive D:". The > error > window has 3 options Cancel, Try Again, and Continue. Selecting either of > these does nothing – I am stuck in the window. I am able to cancel the > setup > though. > > Am I missing something? This is a clean install, after first removing > SQL2k. > > -- > Thanks, > > Scott H. > > > "Ekrem Önsoy" wrote: > >> Well, I don't think there is something to get fixed here. Or maybe you >> meant >> something different and I got it wrong. >> >> Simply, you can't install an older version to overwrite a newer one. And >> you >> can't install a component if it's already exists. >> >> -- >> Ekrem Önsoy >> >> >> >> "Scott H." <ScottH@discussions.microsoft.com> wrote in message >> news:95A02DFC-3ED8-4D2D-97B1-D9BE7C502D14@microsoft.com... >> > Ekrem, >> > >> > Thank-you for your reply. This worked for me. >> > >> > By the way, I wasn't attempting to install SP 1 over RTM. At the time I >> > had >> > only RTM. >> > >> > Do you know if Microsoft have fixed this issue with the install? >> > >> > -- >> > Thanks, >> > >> > Scott H. >> > >> > >> > "Ekrem Önsoy" wrote: >> > >> >> Hello Scott, >> >> >> >> If there is a newer version of Workstation Components is already >> >> installed >> >> you can't install the RTM version to overwrite the newer one. >> >> >> >> What I mean by saying a newer version, I mean the Workstation >> >> Components >> >> that are already installed may be SP2 applied. And the SQL Server 2005 >> >> Instance that you are installing from your media is the RTM version >> >> which >> >> was released before any SP or update. >> >> >> >> So, you can try uninstalling current installed Workstation Components >> >> and >> >> then try installing Workstation Components using your SQL Server 2005 >> >> media. >> >> You can run the "SqlRun_Tools.msi" file which is in the second CD's >> >> Setup >> >> folder for this purpose. >> >> >> >> P.S. >> >> SSMS is under the Client Tools which is covered by Workstation >> >> Components. >> >> >> >> -- >> >> Ekrem Önsoy >> >> >> >> >> >> >> >> "Scott H." <ScottH@discussions.microsoft.com> wrote in message >> >> news:0D9FDB5B-EDDF-404F-A4FE-A39A249A3DA9@microsoft.com... >> >> > Hi Folks, >> >> > >> >> > Wonder if this problem has been resolved? I'm sure it must have >> >> > been, >> >> > I've >> >> > noticed many posts on the internet dating back to 2005. The problem >> >> > is, >> >> > I >> >> > haven't been able to find the solution. I have several environments >> >> > at >> >> > Windows Server 2000 SP4, and a clean installation is failing every >> >> > time >> >> > on >> >> > the second CD with this error (Subject). I can do an in-place >> >> > upgrade >> >> > without >> >> > issue, only a clean install fails. >> >> > >> >> > Nearing the end of the installation the following error popped up >> >> > “The >> >> > wrong >> >> > volume is in the drive. Please insert volume SQLSRVRS into the >> >> > driveâ€. >> >> > After >> >> > searching the discussion groups, one workaround is to reinstall >> >> > Client >> >> > Components only. This workaround did not work for me – SQL Server >> >> > installation complained that it was already installed. I noticed >> >> > that >> >> > SQL >> >> > Server Management Studio was not available on the Program menu of >> >> > the >> >> > OS, >> >> > so >> >> > I tried to reinstall that component – no success. >> >> > >> >> > Your is appreciated. >> >> > -- >> >> > Thanks, >> >> > >> >> > Scott H. >> >> >> >> >> |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
Ekrem,
I have confused the issue yet again :-). Yes, SQL 2K EE -> SQL 2K5 SE is not a valid upgrade path - no question. I can use the same installation disks (SQL2K5 SE) to upgrade an instance of SQL2000 SE without issue. What I've really been trying to explain is that these installation disks (SQL2K5 SE) fail during an install (not upgrade). However, I have been able to apply the workaround mentioned. Which is, after the failure, find out what is missing, and install it. It's a pain, and I would have thought that there would be more information out there. Yes, I have tried your suggestion, it didn't work, but the actual error escapes me. I will try this again and let you know. By the way, I'm doing this all in a virtual environment on my laptop. Love VMWare (I think). -- Thanks for your and interest, Scott H. "Ekrem Önsoy" wrote: > This time your scenario was told pretty clear. > > However one thing lingers in my mind. You said that you can perform an in > place upgrade without any issue. And you draw your upgrade path from 2000's > Enterprise Edition to Standard Edition of 2005. This is odd because this is > not a valid upgrade path according to > http://technet.microsoft.com/en-us/l.../ms143393.aspx > > I personally have not met this wrong volume problem in SQL Server Setup yet > so I don't have an experience to share about this. But this problem looks > like a generic Windows application problem rather than SQL Server related > problem. Although I have not experienced this while installing SQL Server, I > kind of remember this error while installing other products. > > This suggestion may sound stupid but did you try placing the first CD when > it says "Please insert volume SQLSvr2005StdCD1 into drive D:" ? If so, what > happens when you put the first media into the cd-tray? > > -- > Ekrem Önsoy > > > > "Scott H." <ScottH@discussions.microsoft.com> wrote in message > news:C37E16DD-AC81-4B98-B71B-BBA29E1980E7@microsoft.com... > > Ekram, > > > > Let me see if I can do a better job explaining. There is definately > > something wrong with the installation. > > > > Objective: > > > > Upgrade to SQL Server 2005 Standard Edition SP2 from SQL Server 2000 > > Enterprise Edition SP3 by way of uninstall SQL2K and installing S2K5. > > > > Environment: > > > > OS: Windows Server 2000 Standard Edition SP4 (fresh install) > > Pre-SQL: SQL Server 2000 SP3 Enterprise Edition (fresh install) > > Post-SQL: SQL Server 2005 SP2 Standard Edition > > > > Upgrade Procedure: > > > > Uninstall SQL Server 2000 Enterprise Edition SP3 by way of Control Panel > > Install SQL Server 2005 Standard Edition SP2 > > > > Results/Observations: > > > > The installation failed on the second disk, reporting: “The wrong volume > > is > > in the drive. Please insert volume SQLSvr2005StdCD1 into drive D:". The > > error > > window has 3 options Cancel, Try Again, and Continue. Selecting either of > > these does nothing – I am stuck in the window. I am able to cancel the > > setup > > though. > > > > Am I missing something? This is a clean install, after first removing > > SQL2k. > > > > -- > > Thanks, > > > > Scott H. > > > > > > "Ekrem Önsoy" wrote: > > > >> Well, I don't think there is something to get fixed here. Or maybe you > >> meant > >> something different and I got it wrong. > >> > >> Simply, you can't install an older version to overwrite a newer one. And > >> you > >> can't install a component if it's already exists. > >> > >> -- > >> Ekrem Önsoy > >> > >> > >> > >> "Scott H." <ScottH@discussions.microsoft.com> wrote in message > >> news:95A02DFC-3ED8-4D2D-97B1-D9BE7C502D14@microsoft.com... > >> > Ekrem, > >> > > >> > Thank-you for your reply. This worked for me. > >> > > >> > By the way, I wasn't attempting to install SP 1 over RTM. At the time I > >> > had > >> > only RTM. > >> > > >> > Do you know if Microsoft have fixed this issue with the install? > >> > > >> > -- > >> > Thanks, > >> > > >> > Scott H. > >> > > >> > > >> > "Ekrem Önsoy" wrote: > >> > > >> >> Hello Scott, > >> >> > >> >> If there is a newer version of Workstation Components is already > >> >> installed > >> >> you can't install the RTM version to overwrite the newer one. > >> >> > >> >> What I mean by saying a newer version, I mean the Workstation > >> >> Components > >> >> that are already installed may be SP2 applied. And the SQL Server 2005 > >> >> Instance that you are installing from your media is the RTM version > >> >> which > >> >> was released before any SP or update. > >> >> > >> >> So, you can try uninstalling current installed Workstation Components > >> >> and > >> >> then try installing Workstation Components using your SQL Server 2005 > >> >> media. > >> >> You can run the "SqlRun_Tools.msi" file which is in the second CD's > >> >> Setup > >> >> folder for this purpose. > >> >> > >> >> P.S. > >> >> SSMS is under the Client Tools which is covered by Workstation > >> >> Components. > >> >> > >> >> -- > >> >> Ekrem Önsoy > >> >> > >> >> > >> >> > >> >> "Scott H." <ScottH@discussions.microsoft.com> wrote in message > >> >> news:0D9FDB5B-EDDF-404F-A4FE-A39A249A3DA9@microsoft.com... > >> >> > Hi Folks, > >> >> > > >> >> > Wonder if this problem has been resolved? I'm sure it must have > >> >> > been, > >> >> > I've > >> >> > noticed many posts on the internet dating back to 2005. The problem > >> >> > is, > >> >> > I > >> >> > haven't been able to find the solution. I have several environments > >> >> > at > >> >> > Windows Server 2000 SP4, and a clean installation is failing every > >> >> > time > >> >> > on > >> >> > the second CD with this error (Subject). I can do an in-place > >> >> > upgrade > >> >> > without > >> >> > issue, only a clean install fails. > >> >> > > >> >> > Nearing the end of the installation the following error popped up > >> >> > “The > >> >> > wrong > >> >> > volume is in the drive. Please insert volume SQLSRVRS into the > >> >> > driveâ€. > >> >> > After > >> >> > searching the discussion groups, one workaround is to reinstall > >> >> > Client > >> >> > Components only. This workaround did not work for me – SQL Server > >> >> > installation complained that it was already installed. I noticed > >> >> > that > >> >> > SQL > >> >> > Server Management Studio was not available on the Program menu of > >> >> > the > >> >> > OS, > >> >> > so > >> >> > I tried to reinstall that component – no success. > >> >> > > >> >> > Your is appreciated. > >> >> > -- > >> >> > Thanks, > >> >> > > >> >> > Scott H. > >> >> > >> >> > >> > |
|
![]() |
| Outils de la discussion | |
|
|