Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
Installation Fails @ Server and Client Monitoring

Unanswered Installation Fails @ Server and Client Monitoring

  • Wednesday, February 27, 2008 5:06 PM
     
     
    Sign In to Vote
    0
    The system exceeds minimum requirements.
    Installing on a fresh Windows Server 2003 Standard x86 R2 - fully updated.
    Using SQLExpress 2005 Instance.

    I am prepared to send logs if requested.
    Any help will be GREATLY appreciated.
     

All Replies

  • Friday, February 29, 2008 6:16 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi, 
     

    Firstly, I would like to share some documents about SCE installation and some similiar examples. Hope they are helpful.
     

    About System Center Essentials Deployment
    http://technet.microsoft.com/en-us/library/bb437287.aspx


    The installation of System Center Essentials 2007 fails during the Reporting part of Setup and the following information is logged: "The specified domain does not exist or cannot be contacted"
    http://support.microsoft.com/kb/937831/en-us


    SCE failure during reporting
    http://forums.microsoft.com/technet/showpost.aspx?postid=1779770&siteid=17
     

    Also, if the above cannot help, some more information is needed to move on.


    1. The topology that SCE was installed.

     

    2. The screenshot where the installation failed, which would show us the exact problem.

     

    3. The installation log files. Generally, they are located in %temp% folder and the names are:

     

        SCESetupx.log (x stands for different numbers)

        WSUSSetup.log

        SCEReportingx.log

        SCEx.log

     

    Please send all the information to SCEDATA@microsoft.com, with the following there lines in the E-mail.

     

    Installation Fails @ Server and Client Monitoring

    http://forums.microsoft.com/TechNet/ShowPost.aspx?siteid=17&PostID=2915436

    For Yog.Li - MSFT

     

    Thanks.

     

                                                    

    Sincerely,
    Yog Li
    Microsoft Online Community Support

     
  • Friday, February 29, 2008 3:46 PM
     
     
    Sign In to Vote
    0
    Yog, thank you for responding.
    I have exahusted the existing resources that I could find in this forum.
    I sent the email with all of the requested information with the exception of the topology SCE is being installed.

    Topology:
    Windows Server 2003 Standard R2 - SP2 and all updates.
    HP Proliant ML350 G5
    Dual Intel Xeon E5335 2.0GHz Quad Core CPU's
    4GB PC2-5300 CL5 ECC RAM
    3X 36GB 15K RPM Serial Attached SCSI HDD in RAID5

    The SCE media has been patched using the SCE2007RTMHotfixRollup.exe and is being run from a directory located on the local machine.

    I hope this is all of the informaiton you needed.
    Thank you for your help.
     
  • Monday, March 03, 2008 10:15 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi John,

     

    From the log files, I learned that the error 1603 was returned by SCE.msi. 

     

    The error code 1603 is a common message for exception and it just means "Fatal error during installation". Here are some general suggestions for your reference.

     

    1. Make sure the following software(latest versions) are installed on the server.

     

    Internet Information Services 6.0

    .NET Framework 2.0 and 3.0

     

    2. Delete all the files in %temp% folder.

     

    3. It's better to use a clean server to install SCE. At this time, we can run MSCONFIG to disable some un-necessary services/startup programs to boot the system into a clean environment and then perform the installation.

     

     

    Besides, the log files indicate that you are using an existing Local SQL. So I'd like to suggest the following steps which tell us how to create a new SQL instance before install SCE. Please check if any step that you didn't perform. 

     

    1. If SQL server isn't exist, please launch SQLEXPR_ADV.exe in SCE setup media.

     

    2. Create a new named instance, including DB and SRS component. You can use the following steps:

     

    1)  Launch SQL installation.

    2)  On the Installing Prerequisites page, click Next when the installation of the required components completes.

    3)  On the "Welcome To The Microsoft SQL Server Installation Wizard" page, click Next.

    4)  Select the appropriate components to install by checking the box next to the Component (choose DB and Reporting Services), and then click next.

    5)  Install a named instance.

    6)  Configure the service account information and the component startup information by selecting domain admin account and then click next.

    7)  In next screen, configure the service account information and the component startup information by selecting windows authentication mode. Then click next.

    8)  Select "Install the default configuration" (Recommended).

    9)  At last, confirm which components will be installed and click install. 

     

    3.  After installing a new instance, please use the following steps to configure SQL Server Reporting Service:

     

    1) Open Start->Programs->Microsoft SQL Server 2005->Configuration Tools->Reporting services configuration. Choose the new instance you created and then click "Connect".

    2)  Follow the wizard to finish all the configurations one by one listed on the left pane.  

     

     

    Hope this helps.  

                                                    

    Sincerely, 

    Yog Li 

    Microsoft Online Community Support

     

     
  • Monday, March 03, 2008 7:58 PM
     
     
    Sign In to Vote
    0
     Yog Li - MSFT wrote:

    Hi John,

     

    From the log files, I learned that the error 1603 was returned by SCE.msi. 

     

    The error code 1603 is a common message for exception and it just means "Fatal error during installation". Here are some general suggestions for your reference.

     I understand 1603 very well. It is a VERY generic error.

    1. Make sure the following software(latest versions) are installed on the server.

     

    Internet Information Services 6.0

    .NET Framework 2.0 and 3.0

    I already mentioned this in my first post:
    Installing on a fresh Windows Server 2003 Standard x86 R2 - fully updated.
    Using SQLExpress 2005 Instance. As I'm sure you're aware, the latest versions of both .NET Framework 2.0 & 3.0 are included with Windows Update.

    Also, I can get to the reports instance of SQL through IIS6.0 by typing "http://localhost/ReportServer$SQLexpress" into the browser.

     

    2. Delete all the files in %temp% folder.

    Tried that.

     

    3. It's better to use a clean server to install SCE. At this time, we can run MSCONFIG to disable some un-necessary services/startup programs to boot the system into a clean environment and then perform the installation.

     Again, I already stated this is a CLEAN, FRESH, NEW, OUT OF THE BOX, install.

     

    Besides, the log files indicate that you are using an existing Local SQL. So I'd like to suggest the following steps which tell us how to create a new SQL instance before install SCE. Please check if any step that you didn't perform. 

     The following steps ARE the steps that I took to install a NEW SQL instance, before I tried to install SCE.

    Also, it's obvious that the SQL server instance is functioning correctly since the install does not fail while creating database objects, but AFTER the SQL step in the installation process.


    1. If SQL server isn't exist, please launch SQLEXPR_ADV.exe in SCE setup media.

     

    2. Create a new named instance, including DB and SRS component. You can use the following steps:

     

    1)  Launch SQL installation.

    2)  On the Installing Prerequisites page, click Next when the installation of the required components completes.

    3)  On the "Welcome To The Microsoft SQL Server Installation Wizard" page, click Next.

    4)  Select the appropriate components to install by checking the box next to the Component (choose DB and Reporting Services), and then click next.

    5)  Install a named instance.

    6)  Configure the service account information and the component startup information by selecting domain admin account and then click next.

    7)  In next screen, configure the service account information and the component startup information by selecting windows authentication mode. Then click next.

    8)  Select "Install the default configuration" (Recommended).

    9)  At last, confirm which components will be installed and click install. 

     

    3.  After installing a new instance, please use the following steps to configure SQL Server Reporting Service:

    I previously did NOT configure the Reporting Services as the next two steps instruct. I have, however, attempted this and found that this had NO IMPACT on the process.

    1) Open Start->Programs->Microsoft SQL Server 2005->Configuration Tools->Reporting services configuration. Choose the new instance you created and then click "Connect".

    2)  Follow the wizard to finish all the configurations one by one listed on the left pane.  

     

     

    Hope this helps.  

                                                    

    Sincerely, 

    Yog Li 

    Microsoft Online Community Support

    Please see the above quote with added responses.
    For the most part, I performed all of your suggestions before creating this thread.
    Everything you posted is already somewhere in the forums.
    Please trust that I have read EVERYTHING I can find in these forums, nothing pertains to my particular situation.

    Also, I'm not sure if this is by design, but the "Loading Management Packs" step seems to take considerably longer than any other step of the installation; It is just after this step that the installation fails.

    Please advise.

     
  • Tuesday, March 04, 2008 9:32 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi John,


    If the previous steps cannot help you, it's maybe a potential bug. As far as I know, this bug should be solved in SCE SP1, which will be released soon in this month.


    Thanks.
     

                                                    

    Sincerely,
    Yog Li
    Microsoft Online Community Support

     
  • Tuesday, March 11, 2008 7:19 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi John,

     

    System Center Essentials 2007 Service Pack 1 is now available. You can download the evaluation copy and try it again.

     

    System Center Essentials 2007 Service Pack 1 Evaluation copy
    http://www.microsoft.com/downloads/details.aspx?FamilyId=246DF207-F051-47C3-BD64-C9072281C3C8&displaylang=en

     

    Hope it helps.

     
  • Wednesday, March 12, 2008 6:21 PM
     
     
    Sign In to Vote
    0
    I downloaded the SP1 Eval from the link above, and attempted to install.

    Same exact results.

    I have emailed you the new logs requested in the 2nd post.
     
  • Thursday, March 13, 2008 11:37 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi John,

     

    I got the log files and see the same error. I'll keep you informed.

     

    Thanks.

     
  • Thursday, March 20, 2008 4:53 PM
     
     
    Sign In to Vote
    0

    Hi, I'd just like to add that I've had exactly the same bad experience.

    I just retried with the Eval SP1 slipstreamed version, same problem again.

     

    I've worked with Windows, SMS, MOM etc for quite a while in the sort of environment where security often gets in the way of vanilla installs out of the box. I'm pretty well experienced with working around and solving all sorts of integration issues. I hate to say it, but I don't think I've ever come across a Microsoft product that is quite as bad as this. I hope you can find a solution quickly as I don't have the time to mess around for much longer. If it doesn't install in a predictable/repeatable way, I won't be using it nor recommending it.

     
  • Friday, March 21, 2008 8:55 PM
     
     
    Sign In to Vote
    0

    John:

     

    I apologize for the poor experience you are having with SCE - it seems the failure you've been experiencing has been misdiagnosed.

     

    The failure here is in access to your WSUS environment as 'unauthorized' in IIS, likely due to permissions settings in IIS itself.  Could you install WSUS prior to SCE (it will be used as installed later in SCE) using the option to place on 8530?  Using the SQL Express you preinstalled prior in the thread would give the best experience.  After setup of WSUS, you should be able to better determine the access problem which is occurring. 

     

    This KB may be useful:  http://support.microsoft.com/kb/332167 .

     

    For MRGB:

     

    Can you start a new thread on your issue for further investigation?
     
  • Tuesday, March 25, 2008 2:24 PM
     
     
    Sign In to Vote
    0
     Stephanie Drenchen [MSFT] wrote:

     

    The failure here is in access to your WSUS environment as 'unauthorized' in IIS, likely due to permissions settings in IIS itself.

    This is a fresh install of Windows Server 2003 R2 and IIS6 with default permissions & configuration.


    Could you install WSUS prior to SCE (it will be used as installed later in SCE) using the option to place on 8530?

    I've completed this task, now what?

     
  • Friday, March 28, 2008 9:07 PM
     
     
    Sign In to Vote
    0

    Stephanie, I think you misunderstood. I have experienced exactly the same problem that John has described both before and after SP1. I don't think we need a new thread, if you fix John's problems, you'll fix mine at the same time. The reason I posted was to make sure that you realise this isn't a single isolated problem.

    MRGB