Collection Server Installation Failure

모든 응답

• 2008년 4월 17일 목요일 오후 10:03chrisw_uk

   
  

  0

  로그인하여 투표

  Hi,

   

  It's been a while since i've played with a setup like this, but i do seem to remember hitting a silly error caused by a wrong name when everything is split, where i didn't read it carefully

   

  You quite probably didn't make the same mistake, but have a check anyhow...

   

  Take a look at http://technet.microsoft.com/en-us/library/bb404240.aspx which describes the steps you would have taken, as it states on many of the steps, the names it has listed are not correct. Therefore you must change them. During the collection server install, it will need to talk back to the collection database for sure.

  
  It sounds otherwise like everything you have done is OK, you can definitely install FCS without SQL on the collection server, so no worries there... You shouldn't need any special SQL components at all on that server either. Most of the installs i've done are split onto 3 servers with collection/mgmt server on 1, collection/reporting DB on 2, and distribution role on the 3rd, so pretty similar to you, except for the reporting role, and they have worked OK.

   

  Do you see any entries on your Collection DB Server to show any errors in the logs (event viewer) in terms of a connection attempt made that has failed or anything ?

   

  Is there anything else of detail in the log created when you ran the MSI manually to get the detailed logging >

   

  Hope this may help,

  Chris

  • 응답
  • 인용

   
• 2008년 4월 17일 목요일 오후 11:30Huggy Bear

   
  

  0

  로그인하여 투표

  Chris,

   

  Thank you for the timely response...it is appreciated!!  To answer your questions:

   

  1.  The link that you provided is the exact one that I have been using to setup this configuration.

   

  2.  I keep thinking that I may have placed the wrong name some where, but I've got a diagram in front of me and have attempted this at least 30+ times now.  I hope that I'm not missing something that obvious, but it has happened before.  I don't think that I am though due to the following verification steps completing successfully when installing the Collection Server (it seems to verify where everything is at):

   

  Number of verifications started: [4/17/2008 5:38:05 PM]

  [4/17/2008 5:38:05 PM] Verification(Verifying operating system requirements)

  [4/17/2008 5:38:06 PM] Verification(Verifying hardware requirements)

  [4/17/2008 5:38:06 PM] Verification(Verifying software prerequisites)

  [4/17/2008 5:38:06 PM] Verification(Verifying collection database)

  [4/17/2008 5:38:07 PM] Verification(Verifying access to collection server)

  [4/17/2008 5:38:07 PM] Verification(Verifying DAS account)

  [4/17/2008 5:38:08 PM] Verification(Verifying access to reporting server)

  [4/17/2008 5:38:08 PM] Verification(Verifying reporting database configuration)

  [4/17/2008 5:38:09 PM] Verification(Verifying URLs for reports)

  [4/17/2008 5:38:09 PM] Verification(Verifying action account)

  Number of verifications completed: [4/17/2008 5:38:09 PM]

   

  I changed the location (bogus server locations) of the Collection Database, the Reporting Database, and the Reporting Server just to see what the above results would be (see below in red).  As I thought, it failed the verification process...which tells me that all of my initial parameteres are correct.

   

  Number of verifications started: [4/17/2008 6:22:37 PM]
  [4/17/2008 6:22:37 PM] Verification(Verifying operating system requirements)
  [4/17/2008 6:22:38 PM] Verification(Verifying hardware requirements)
  [4/17/2008 6:22:40 PM] Verification(Verifying software prerequisites)
  [4/17/2008 6:22:57 PM] Verification(Verifying collection database)
  Error: The following database could not be contacted.
  Database: OnePoint
  SQL Server instance: Server C\S5P01
  [4/17/2008 6:22:57 PM] Verification(Verifying access to collection server)
  [4/17/2008 6:22:58 PM] Verification(Verifying DAS account)
  [4/17/2008 6:23:05 PM] Verification(Verifying access to reporting server)
  Error: This host could not be contacted: Server C.
  [4/17/2008 6:23:21 PM] Verification(Verifying reporting database configuration)
  Error: Could not contact SQL Server Server C\S5P01.
  [4/17/2008 6:23:22 PM] Verification(Verifying URLs for reports)
  [4/17/2008 6:23:22 PM] Verification(Verifying action account)
  Number of verifications completed: [4/17/2008 6:23:22 PM]

   

  3.  Myself and the DBA have checked the Collection Database Server and do not see any failed attemps.  We utilized "SQLCMD" to connect to the collection database (on port 1433) without any issues.

   

  4.  Here is the detailed logging information from when I ran the MSI manually:

   

  I just did a search for "ERR" in this log file and found the following lines:

   

  Property(C): PIDErrorDlg_Desc1 = You have not entered a valid product key.
  Property(C): PIDErrorDlg_Desc2 = Please check the number located on your Certificate of Authenticity or the yellow sticker on the back of the CD case.

   

  Property(C): AccountVerificationErrDlg_Title = Account Verification Error
  Property(C): AccountVerificationErrDlg_Text1 = Setup is unable to validate the account you provided.

   

  I'm really not sure what to do here.  I see the product key when I ran the MSI manually, but I don't know how you would enter that information if you didn't have the manual option.  I hope this isn't the cause...I will attempt to research this further.  If someone else could run the "MOMServer.msi" with the command line below, and see if they get the same error in the "forefront.log" file...that might be helpful.

   

  msiexec.exe /i "[ForeFront Install Location]\Server\MOMServer.msi" /l* c:\forefront.txt

   

  Anyway Chris, thank you for your help...I'll keep hammering away at this...I refuse to be beaten down by a Microsoft product.

   

  Huggy Bear

   

  • 응답
  • 인용

   
• 2008년 4월 29일 화요일 오후 8:13Velcroturf

   
  

  0

  로그인하여 투표

  WOW!!  How much fun can one person ask for when installing FCS.  Honestly, I don't think that there is any better thrill than watching for green check marks to appear that are in fact replaced with red "X's".

   

  I'm the original creator of this post (Huggy Bear), but everytime that I login, I'm asked for a new username (Velcroturf).  Hopefully this is the last time that I have to login.

   

  Anyway, I finally got everything installed, and I thought that I would update what I had to do to complete the process.

   

  I was getting stuck installing the Collection Server.  To finally determine where the problem resided, I created a "batch" file (below) and executed this batch to have it manually launch the MSI and to create a log file.

   

  msiexec /qb /lime c:\mom.txt INSTALLDIR="D:\Program Files\Microsoft Forefront\Client Security\Server\Microsoft Operations Manager 2005" CONFIG_GROUP="ForefrontClientSecurity" ADDLOCAL="MOMXServer,MOMXUI" ACTIONSUSER="forefront" ACTIONSDOMAIN="**********" ACTIONSPASSWORD="*****" MOM_DB_SERVER="SERVER C\S5P01" SQLSVR_INSTANCE="SERVER C\S5P01" MOM_SERVER="SERVER A" DAS_ACCOUNT="forefront" DAS_PASSWORD="*****" DAS_DOMAIN="**********"

   

  pause

   

  I was able to quickly determine that there was a permissions issue on the SQL database.  I raised the permissions to DBO.  This was my fault…I thought that I had the permissions set.  After that change was made, the Collection Server continued to install as normal.

   

  Until...I got the “Adjusting MOM Parameters” section of the installation.  Here it kept throwing an error at me.  The log file indicated the following error:

   

  [4/29/2008 11:35:05 AM] Task(Adjusting MOM Parameters)

  Exception thrown during SQL command.

  Exception: Cannot drop the procedure 'dbo.fcs_ChangeMomParam', because it does not exist or you do not have permission.

  Near line: 57

  SQL command: -- finally clean up our sproc

  drop procedure [dbo].[fcs_ChangeMomParam]

   

   

  After investigating the error, I decided to edit the last couple of lines of the “MOM_setup_tasks” SQL file where the error was being thrown.  The last couple of lines make a definitive statement about the cleaning up of a stored procedure; instead, I changed it to an “if” statement (the statement was found in the earlier lines of the same SQL script).  Once the change was made, the installation completed successfully.

   

  Original Lines:

  -- finally clean up our sproc

  drop procedure [dbo].[fcs_ChangeMomParam]

  GO

   

  New Lines:

  -- finally clean up our sproc

  if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[fcs_ChangeMomParam]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)

  drop procedure [dbo].[fcs_ChangeMomParam]

  GO

   

  Again, does it really have to be this difficult?  I sure hope the “Stirling” release is much smoother to install.

   

  • 응답
  • 인용

   
• 2009년 11월 19일 목요일 오후 9:45Faiz Farazi

   
  

  0

  로그인하여 투표
  What I do if there is a installation issue on sql server:
  
  1. Restart the Server.
  2. Uninstall ( sql server installed comp..)
  3. Click > Run > type > msconfig.> select services> select hide microsoft services>select disable all>Appaly> OK.
  4.Restart the server and start installation for your SQL server .
  
  Note: Make sure you have enough disk space/permission/memory on the server.
  
  

  ---

  Thanks Faiz Farazi MCDBA,MCSA

  • 답변으로 제안됨Faiz Farazi 2009년 11월 19일 목요일 오후 9:46
  •  
  • 응답
  • 인용