Re: Failed upgrade to SCCM

Sorry; that reply was meant for another post! Someone with only 2 actions in
their client Actions pane.

It looks like you've already found your own answer to your own question; let
us know how it goes! (Sorry about the confusing post)
--
Standarize. Simplify. Automate.


"Chris" wrote:

Thanks Sherry, I'm not sure how your suggestions are relevant to my
situation as there are no clients involved at this stage.

From reading a few threads I just found with a new Google search, it looks I
need to completely uninstall SCCM components, then perform a full
installation of SCCM on the server with the same name and site code and
then do a "site repair" using the backup of our existing SCCM database.

Does anyone foresee any issues with this method after the problems mentioned
in my original post?

Cheers,
Chris


"Chris" <csw@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4933538A-205B-4622-880A-EE89315F1B17@xxxxxxxxxxxxxxxx
Sorry for the long post, I just wanted to get as much detail in as
possible.

I recently started the upgrade our SMS 2003 SP3 Server to SCCM. Our setup
is a single site / server with one child site although the child site had
recently failed so I removed it from the SMS Console before starting the
upgrade. The SQL Server is a remote server that is shared with other
applications.

The prerequisite checker passed for everything except inactive clients and
SQL Server security mode and as we require the SQL server to be in SQL &
Windows Authentication mode we cannot change this. I started the
installation and everything seemed to be going well until the very end
where everything completed successfully except "Install management point"
and (I think) "Install site control manager" with status "Unknown" I
pressed finish and attempted to open the ConfigMgr Console however it hung
on loading.

I have tried re-running the upgrade again however it now pops up an error
message saying it cannot deinstall SMS components from the server in the
failed child site that was removed. If I ignore that, it continues on
however fails at "Install SMS provider components".
I have done plenty of reading and the error points to either WMI or SPN's
however if either of these were an issue, wouldn't it have picked it up
during the original failed install? I have double checked the SPN's and
re-registered WMI components however SCCM will not reinstall. After a
couple of failed upgrade attempts, I tried the Site Repair Wizard however
it has started returning a Provider Load Error so it does look like WMI,
I'm just not sure what caused WMI to fail after the first upgrade attempt.

I'm done with trying to recover this install so I need to know what my
options are for recovering the Site with our existing data? Can I
uninstall the single site completely and then reuse our existing SQL
database with a fresh SCCM installation. I have SQL backups from both
before and after the upgrade so I could even return to SMS if I had to.
Unfortunately, I discovered after the fact that we don't have any backups
of the SMS Site server itself as the previous IT guys had never installed
the backup agents on the server.

Thanks in advance,
Chris

.

Relevant Pages

  • RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not instal
    ... The DSRestore Filter failed to connect to local SAM server. ... registry keys of the Microsoft SQL server and mail to me for analyze. ... This newsgroup only focuses on SBS technical issues. ... SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not install ...
    (microsoft.public.windows.server.sbs)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... Can I reinstall the files from another SBS2003 server I manage? ... On my install of SLQ2005, I told it to upgrade all instances. ... Installing SQL Server 2005 WorkGroup Edition in Windows Small Business ... <The server-based applications that were running fine are: McAFee EPO, ...
    (microsoft.public.windows.server.sbs)
  • Re: Installed VS 2005 want to Manage SQL 2005 Server
    ... I Guess I didn't copy it to the Install Source on the Server. ... To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter. ... The Following Components that you chose to install are already installed onthe machine. ...
    (microsoft.public.sqlserver.setup)
  • Re: Clearer version of my earlier question re sp_grantlogin and sp_grantdbaccess
    ... > Server, doesn't have the right to grant DB access to Domain Groups. ... I didn't know that an SQL Server login as ... > I did the install about a month ago as Domain Admin (default install - mixed ... > site where they let me login as Domain Admin. ...
    (microsoft.public.sqlserver.msde)
  • Re: Problems installing Security Scan and Office Scan
    ... I have been to the MS Managing SMS 2003 class. ... > I have installed SMS 2003 on a Win2003 server and placed the database on ... > installed the SMS Provider on the SQL server. ... > I initially had some problem getting the reports to install. ...
    (microsoft.public.sms.tools)
Loading