Prev: Email Capture
Next: Normal users can install and use windows updates due to templates
From: Jeff on 19 May 2010 10:16
We have been trying to install an instance of SQL 2005 workgroup (from
Premium CD 2 media) on a SBS 2003 SP2 server that had SharePoint MSDE & SBS
MSDE Monitoring installed. When installing SQL 2005, there were no prompts
as to instance name, collation, or other SQL defaults. After installation of
SQL 2005 & SP2 & SP3, SQL Management Studio About Help showed V9 was
installed, but the SharePoint instance indicated V80.

We followed various instructions
(http://www.smallbizserver.net/Articles/tabid/266/Id/211/PageID/285/SBS-2003-R2--Upgrading-the-Sharepoint-MSDE-instance-to-SQL-2005.aspx
and
http://download.microsoft.com/download/4/0/8/40860507-c351-4308-a876-e1b83ee4e77a/sqlinstallsteps.htm)
in an attempt to upgrade SharePoint to Workgroup Edition however they failed.
On initial upgrade attempts, we kept getting the message to reinstall from
the source DVDs with SKUUPGRADE=1 and after we did so, we kept only being
offered to install the client components and documentation that was already
installed. We were unable to upgrade the MSDE instance of SharePoint to
Workgroup V9.

We then removed all SQL 2005 via Add/Remove programmes and also ran
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\arpwrapper /REMOVE.

No errors on program removal were displayed.

We tried reinstalling SQL 2005 but were only offered the client components
and documentation, even though there was no SharePoint or MSDE or 2005
instance.


We then totally removed other SharePoint components, SBS Monitoring MSDE,
SharePoint references in IIS by reference to
http://support.microsoft.com/kb/909967 & Microsoft KB article 829114. to
ensure all versions of MS-SQL was removed. Neither SharePoint nor
Monitoring are required.

There are no MSSQL services visible or running.

But still after uninstalling after removing all visible references MSSQL, we
still cannot install a new instance. On every attempt to reinstall SQL, we
are never offered to install an instance and after the standard configuration
checks that are all reported as being successful, the installation still only
offers to install client components and documentation.

No errors on program installation were displayed.

Can someone please let me know why we cannot properly install SQL 2005 with
an instance and let me know how to overcome this problem?


 | 
Pages: 1
Prev: Email Capture
Next: Normal users can install and use windows updates due to templates