Hello Mike, I had quite a problem with this but I decided to install the full sql2005 on the local server and it seemed to work ok. Make sure you are a local admin and ensure that IIS is set up fesh before running the install.   if the install fails, check the error as well as the event log because you should be able to get a good idea of where the install is failing. I managed to get it runnning on a VM as well although it is really slow. I am going to try and move the VM to a better server and give it a full 4GB RAM and 2 cores of a processor to see if it imporves things a bit...great software once its working although slow (I guess IT asst was too though). Cant complain if its fee :P   Chris

 

Hi Chris, thanks for the post.

If your DMC server is in a lab network (not on the public internet), your UI performance may be improved by turning on CRL checking.  Have a look at section 17 of the FAQ.

Good luck,

Rob

Hi All,

 

I think I'm in the same boat as a lot of you. I initially tried installing the DMC (from a bundled DVD) onto a domain-member server with explicit local admin rights as well as Domain admin membership, onto a newly imaged server and a remote SQL DB, no joy. I'm getting the 'configuration failed' error message. I tried a million different things, making sure that the prerequisites were all fulfilled (no .NET service packs etc.etc.etc.etc.etc.etc.) and in the end put a Win2k3 R2 SP2 std CD in the server and went back to absolute basics. My server has:

 

• Windows 2003 R2 Server Std., SP2 integrated.
• In a workgroup
• 2 x Dual core CPUs, 4GB RAM in an HP BL460c
• Default group policies (i.e., NONE)
• IE7
• SQL Express (from the install DVD)
• A dedicated local admin account to install and run the services
• Loads of local disk space
• IIS with a default website, no SSL
• "Update Root Certificates" off (in Windows Components)
• Internet access (i.e., the latest files are automagically downloaded during install)
• All Windows patches except .NET & SQL patches
• All prerequisite minimum requirement checks are met (I use the link to configure IIS/ASP.NET)
• The crl.microsoft.com access is NOT displayed (because I have 'net access).

 

The log file "a.log" has a sev 2 error containing "Exception encountered whle verifying webservice: System.Net.WebException: The operation timed out at System.Net.HttpWebRequest.GetResponse()|

at Symantec.Installation.WebServiceFactory.ServiceAvailable(Type t, String webServiceRootUrl)]]

The DMC install guide points me to an Altiris KB article: Article ID: 46797 "Getting "Exception encountered while verifying web service:

System.Net.WebException: The operation has timed out" warnings during Symantec Installation Manager 7 installation process."

KB article here: https://kb.altiris.com/display/1n/index.asp?c=&cpc=&cid=&cat=&catURL=&r=0.6992151

 

In a nutshell, the article suggests restarting IIS or the server itself. Neither of these have worked for me, repeatedly, and I am now ready to throw this thing in the bin. 

Some more info:

• The SQL DB doesn't get created; (the 'give this account admin rights' box was checked during SQL Express install by the same user account)
• The 'Altiris' virtual directory in IIS DOES get created.

 

Please tell me someone else is having the same problem and there's a fix!

Cheers.

 

Hi, sorry this is giving you trouble.  Thanks for hanging in there.

This seems similar to a crl error, but you indicate that you are green on this pre-req check.  For some reason, some folks in ANZ seem to run into this. Farther away? :)

Anyway, the workaround is to manually apply the crl fix in your machine.config file as described in the install guide and/or the FAQ section 17.2.  Unfortunately, you may need to uninstall/clean up DMC first before you can change the machine.config and do a re-install.  The uninstall cleanup doc is here.  The install guide is here.

Thanks again and good luck,

Rob

Hi Rob,

I finally have success!!! The CRL fix made it work, but for anyone else reading and want more details.......:

 

Reading FAQ section 17.2 was actually a little confusing - I'm not a big XML guy but I thought it was weird that when I was searching for the tag in machine.config (which is in the CONFIG subdir, i.e., C:\Windows\Microsoft .NET\Framework\v2.0.xxxx\CONFIG\machine.config where the xxxxx relates to patch version etc.) all I could find was (not a typo) on line 122. I think the FAQ could possibly be updated to say something along the lines of "edit your machine.config file and paste in the following lines here:" or something like that. 

The first MS KB article listed made mention of editing the .exe.config file so I just ignored that. I didn't request that patch either because I assumed that Dell would say to download (or have bundled) the patch.

SO....to get it installed I did this:

 

• Enabled a proxy in my IE settings;
• Fired up the install wrapper (SIM)
• It did it's check for new versions or whatever on the web
• All prerequisites were met, including the crl.microsoft.com one.
• Disabled the proxy
• Re-ran the prerequsites check - the crl.microsoft.com one had FAILED (as you'd expect)
• Ran the crl fix
• Enabled the proxy
• Successfull install!!!

I even managed to get it installed using a remote SQL 2008 SP1 server....I don't know if it's supported or not, but it seems to be working.

 

Regards, 

Alex.

 

Alex,

That's great news.  Thanks for the additional information.  I will tweak the FAQ later this week.  Good idea on the proxy workaround.

Cheers,

Rob

I have been failing miserably for 2 days at this, I am told by the installer to check the logfiles for errors - does this mean the Altiris Log Viewer, or are there specific log files to look for - and if so, where are they?

Where are the detailed troubleshooting docs for this?

I have been failing miserably for 2 days at this, I am told by the installer to check the logfiles for errors - does this mean the Altiris Log Viewer, or are there specific log files to look for - and if so, where are they? Where are the detailed troubleshooting docs for this?

 

Hi Steve, thanks for the post.

The most important thing on Install trouble is to review the FAQ Sections 2.1, 17.2 and the Install Guide.  The Install Quickstart Movie has a lot of good information in it as well.

During the install readiness checks, you will need to review the CRL warning check.  If it shows up as a warning, click the Fix hyperlink.  If it shows up as ‘green’, you may need to make the manual change to the machine.config file as indicated in the FAQ references above and install guide.  Install (SIM) logfiles are under the %temp% directory.  You can usually look at the a0 file to get an idea of what problems you may be running into.  If you see timeout errors, that often indicates a CRL problem.  Other common problems are not having local admin permissions on the server.

 

 Thanks,

Rob

Ok, I watched the video and I was trying it with .NET 3.5SP1, and I wasn't enabling TCP/IP in SQL2005Lite.  I am disappointed that the prerequisite check passed like that.

So I re-deplyed this server from a sysprepped image.  I removed .NET3.5SP1, and created a local user named Dell as a local admin.  Rebooted, installed SQL2005Lite from the DVD, enabled TCP/IP and restarted the service, installed .NET3.5 from the DVD, installed IIS/ASP.NET from the "manage your server" applet as per the video, then installed MSIE7 and rebooted.

Logged back in as administrator, ran the installer (specifying the local "Dell" user as the system account), fixed the prereq for the ASP.NET script mapping, and proceeded with install.  It failed at exactly the same point.

I added the following to the bottom of my machine.config:

 
   
 

I rebooted and fired up the install again.  Fail.

Fired up MSIE, entered my proxy information to establish a connection to the Internet, thinking that may be it (apparently the prereq check does not verify internet connectivity, or offer a place to enter proxy information)... made sure to tell IE to bypass proxy for localhost and the server's name.  Fired up the installer again.  Guess what?  FAIL.

:sigh:

Now what?  Install fresh from CD, and do it all over again on a system that never had .NET 3.5SP1 on it, and put in the proxy information BEFORE trying the installer?

 

Ok, I wiped and reloaded the server.  Here are the details...

PowerEdge 1950 III dual quad-core 8GB RAM
Booted to Dell System Build Utility 5.5
Install Windows Server 2003 SP2 (x86 Std)
Install utility partition, OMSA, SNMP, 40GB C:\ drive
Reboot, Windows setup runs
Left it as a DHCP address
Enable remote desktop - everything from here down is run in mstsc /admin from vista, logged in as the local administrator
install server administrator - typical
copy i386 to c:\i386
run IE7-WindowsServer2003-x86-enu.exe, no updates or malicious software removal tool
restart
set proxy, told to ignore localhost;servername
download and install daemon tools lite
reboot
Mount DMC_1.0_A01.ISO as E:\ for the rest of this procedure
install IIS and ASP.NET from "Manage your Server" as per the video
create a local account named "Dell" and add to local administrators group
install dotnetfx35.exe from E:\
reboot
install SQLEXPR32.EXE from E:\
enable TCP/IP and restart the sql service as per video
Begin DMC setup - say yes to increase # of ports, reboot
start DMC install again, launch symantec installation manager
could not contact the product download verification server, continue
select Dell Management Console, review selected products
next, accept license terms, next
readiness check - click to automatically install and configure ASP.NET for IIS
continue, readiness fix installs
yellow icons - powervault, naviCLI, sql 2005, HTTPS, SQL memory
NEXT
apply my dell management console license
NEXT
servername\Dell, password, default website, next
Defaults on database configuration page
BEGIN INSTALL
verifying connection, I get a timeout (always got this) ... say Ok, try again, it works
popup about capacity of SQL vs SQL Express, say OK
Installation begins

installation complete - 31 of 31 components - overall progress 4% - hangs here for a while
Error during installation - configuration of one or more products failed; see the log for details.  To attempt configuration again, reinstall the product.

Looking at the logs in the %TEMP% directory, it seems to not be able to read or write to the webserver running on http://SERVERNAME.

I am leaving the server in this state and going home.  If anyone has any ideas, I'd love to hear them.

Hi Steve,

 

I had similar issues but the clincher for me as the CRL fix. After you've got everything ready right before you run the DMC setup, try this:

• Enable a proxy in IE settings;
• Start the DMC setup - it should be faster now that you have a proxy
• Make sure all prerequisites were met, including the crl.microsoft.com one.
• Disable the proxy
• Re-ran the prerequsites check - the crl.microsoft.com one should FAIL.
• Hit the CRL fix link near the failure message
• Enable the proxy
• Finish the install

I spent an exorbitant number of hours getting this going and like you I "went home" in frustration quite a lot! I read the FAQ article about adding those lines to the machine.config file but it wasn't quite clear as to where it needed to go as far as nesting goes.

Good luck!

Thank you AStuart!

Altered my install to include the following:

• Proxy has been enabled
• Run windowsupdate, apply all updates except .NET3.5SP1 and IE8
• reboot
• run the DMC installer
• at the prerequisite check, leave that screen up and open IE, disable proxy.
• Click the button on the DMC screen to re-check prerequisites
• NOW you see the prereq fail for crl.microsoft.com, click to automatically fix it
• open IE, turn the proxy back on, close IE
• check prerequisites again, proceed with install

Looking at the FAQ's I thought I had to manually edit the machine.config file.  The prerequisite fix actually does this - or at least it says it does.

I am now installed and looking at the console.