Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
dbthj
Posting Yak Master
143 Posts |
Posted - 2012-01-18 : 12:15:24
|
SQL 2005 on Windows 2003 R2 SP2 VMware.SQL 2005 was installed on C: drive contrary to shop standards. So I wanted to uninstalland reinstall on the D: drive.Uninstall seemed to go ok the first time (not subsequent times - notes below)On reinstall, the install wizard would let me put the database on the D: drive, butwould not let me put the client and doc anywhere but C:. Path was greyed out and it said,"The SQL Server shared path has already been configured". First reinstall seemed to work ok, but failed to install SSMS and bol.-- ================================================I tried several Add-Remove/reinstall cycles and here is how it goes:1. Add/Remove delivers errors. See Errors at bottom of post. But Services are gone and functionality is gone.2. Restart Server Then remove Microsoft SQL Server folders on C: and D: drives3. Restart Server. SQL DB and Native client still show up in Add/Remove. Both can be removed almost instantaneously with no wizard invoked.4. Restart Server. All SQL components gone from Add/Remove except SP2 which has note that it cannot be removed. Reinstall SQL. DB on D:. Client Components and Doc on C: (still won't let me put it on D:) Reinstall finished without errors.5. Restart Sql BUT SSMS and "Documentation and Tutorials" do not show up in START/Programs/SQL C:\Program Files\Microsoft SQL Server\90\Tools\Binn does not seem to have all the stuff it should.DATABASE IS OPERATIONAL (if I access it from SSMS from another server) But SSMS is not thereon this server.08/06/2009 : 17:29:55 post to 2005 forum says similar problem solved by installing from a DVD and suggests that his problem was from installing from CD2 rather than CD1. I did install from CD1 but see the problems above.I don't have DVD.-- ========== ERRORS FROM ADD/REMOVE =============---------------------------Microsoft SQL Server 2005 Setup---------------------------The setup has encountered an unexpected error in datastore. The action is SetInstanceProperty. The error is : Source File Name: datastore\cachedpropertycollection.cppCompiler Timestamp: Wed Jun 14 16:27:59 2006 Function Name: CachedPropertyCollection::findPropertySource Line Number: 138----------------------------------------------------------Failed to read property "InstallIds" {"MachineConfiguration", "", "SBMDB003"} from cache Source File Name: datastore\cachedpropertycollection.cpp Compiler Timestamp: Wed Jun 14 16:27:59 2006 Function Name: CachedPropertyCollection::setProperty Source Line Number: 164 ---------------------------------------------------------- Unable to write property into cache: IsClustered Source File Name: datastore\datastorecacheschema.cpp Compiler Timestamp: Wed Jun 14 16:28:00 2006 Function Name: DataStoreCacheSchema::writeProperty Source Line Number: 115 ---------------------------------------------------------- Unable to write property into cache: "IsClustered" Source File Name: datastore\datastorecachexmlschema.cpp Compiler Timestamp: Wed Jun 14 16:28:00 2006 Function Name: DataStoreCacheXMLSchema::initScopeRecord Source Line Number: 81 ---------------------------------------------------------- XmlRW Error: Failure loading xmlrw.dll Source File Name: datastore\datastorecachexmlschema.cpp Compiler Timestamp: Wed Jun 14 16:28:00 2006 Function Name: DataStoreCacheXMLSchema::initScopeRecord Source Line Number: 80 ---------------------------------------------------------- CheckAllProcedures() returned: 2 |
|
dbthj
Posting Yak Master
143 Posts |
Posted - 2012-01-19 : 10:43:42
|
The CD1/CD2 thing from the 2009 post was the key. After the install from CD1 was partially successful (DB installed but Workstation Components failed to install) I went to Add/Remove and uninstalled the workstation components. Restarted. Then installed the workstation components from CD2 . This went well. I still had the issue of being unable to put them on the D: drive, but they installed. They show on Start/Programs/SQL Server. And they are functional. |
|
|
|
|
|