DCM 3.0 Intall failed
Updated: 01 Jul 2010 | 7 comments
I was trying to install the DCM standard into a Windows server 2003 with v 3.5 framework. It has sql 2005 and this comes right after I unzip the download. I looked for any log files but didnt find one. Where are these log files and what could have caused this?
the error message msgbox says:
Symantech Installation Manager has encountered a fatal exception and cannot continue. please see the log file for more information.
discussion Filed Under:
Comments
See if this helps: http://forums.altiris.com/mess...54287&messageid=262068
The logs will be in the location where the Symantec Installation Manager was setup.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
my problem is little different than that because in my situation the Symantech Installation Manager doesn't even start.
From the error message it appears that the system is attempting to perform the configuration of the databases.
When you extracted the components everything should have been placed in an Altiris folder in the same directory that the program was ran from. In my case the folder was created on the root of C.
Go to Altiris\Components folder and attempt to run the following executable symantec_sim_7_0.exe. This should complete the installation of the Symantec Installation Manager. Once this completes you should then be able to continue the installation.
HTH
That is when it crashes when i run that Setup file.
take a look at the pic when it prepares to launch it fails
I'm also getting this problem..
I'm also getting this problem, downloaded and ran the file "symantec_sim_7_0_kb45011_sp2.exe" and it fails with the same error as mentioned above
Symantec Installation Manager has encountered a fatal exception and cannot continue. please see the log file for more information.
Is there any solution to this?
Its a freshly built server, Windows 2003 Ent SP2
Mick.
Solution
https://kb.altiris.com/display/1/articleDirect/index.asp?aid=47381&r=0.2836115
Same symptoms, slightly different problem...
I've got a clean install of DCM that was working OK until a few moments ago. DCM is still OK, but whenever I try to run SIM I get the fatal exception error. The associated Altiris log entries are:
Priority: 1
Date: 30/12/2009 1:22:05 AM
Tick Count: 2315875
Host Name: <servername>
Process: SymantecInstallationManager (4148)
Thread ID: 12
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.Automation.Output.ReportError
Description: Symantec Installation Manager has encountered a fatal exception and cannot continue. Please see the log file for more information.
Priority: 1
Date: 30/12/2009 1:22:05 AM
Tick Count: 2315875
Host Name: <servername>
Process: SymantecInstallationManager (4148)
Thread ID: 12
Module: SymantecInstallationManager.exe
Source: Symantec.Installation.SimApplication.CurrentDomain_UnhandledException
Description: Uncaught Exception in Application
( Exception Details: System.Net.WebException: The remote server returned an error: (407) Proxy Authentication Required.
at System.Net.HttpWebRequest.GetResponse()
at System.Xml.XmlDownloadManager.GetNonFileStream(Uri uri, ICredentials credentials)
at System.Xml.XmlDownloadManager.GetStream(Uri uri, ICredentials credentials)
at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)
at System.Xml.XmlTextReaderImpl.OpenStream(Uri uri)
at System.Xml.XmlTextReaderImpl.DtdParserProxy_PushExternalSubset(String systemId, String publicId)
at System.Xml.XmlTextReaderImpl.DtdParserProxy.System.Xml.IDtdParserAdapter.PushExternalSubset(String systemId, String publicId)
at System.Xml.DtdParser.ParseExternalSubset()
at System.Xml.DtdParser.ParseInDocumentDtd(Boolean saveInternalSubset)
at System.Xml.DtdParser.Parse(Boolean saveInternalSubset)
at System.Xml.XmlTextReaderImpl.ParseDoctypeDecl()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at Symantec.Installation.Xml.Reader.ReadXml()
at Symantec.Installation.Context.ProductListingManager.ReadProductListingFile(String plXml, ProcessorType filterPlatform)
at Symantec.Installation.Context.ProductListingManager.ValidatePlFile(String plXml, ProcessorType filterPlatform)
at Symantec.Installation.Context.ProductListingManager.GetAndValidateLatestPlFile(String source, ProductListingInfo& plInfo, Boolean& nofileretrieved)
at Symantec.Installation.Context.ProductListingManager.GetAndLoadProductListings(String source, ProductListingInfo& info)
at Symantec.Installation.Context.ProductListingManager.LoadCurrentProductListings()
at Symantec.Installation.Context.ProductListingManager.LoadAndUpdateProductListings()
at Symantec.Installation.Context.ProductListingManager.<BeginLoadAndUpdateProductListings>b__0()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart() )
( Exception logged from:
at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
at Altiris.Diagnostics.Logging.EventLog.ReportException(String strMessage, Exception exception)
at Symantec.Installation.SimApplication.CurrentDomain_UnhandledException(Object sender, UnhandledExceptionEventArgs e)
at System.Xml.XmlTextReaderImpl.DtdParserProxy_PushExternalSubset(String systemId, String publicId)
at System.Xml.XmlTextReaderImpl.DtdParserProxy.System.Xml.IDtdParserAdapter.PushExternalSubset(String systemId, String publicId)
at System.Xml.DtdParser.ParseExternalSubset()
at System.Xml.DtdParser.ParseInDocumentDtd(Boolean saveInternalSubset)
at System.Xml.DtdParser.Parse(Boolean saveInternalSubset)
at System.Xml.XmlTextReaderImpl.ParseDoctypeDecl()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at Symantec.Installation.Xml.Reader.ReadXml()
at Symantec.Installation.Context.ProductListingManager.ReadProductListingFile(String plXml, ProcessorType filterPlatform)
at Symantec.Installation.Context.ProductListingManager.ValidatePlFile(String plXml, ProcessorType filterPlatform)
at Symantec.Installation.Context.ProductListingManager.GetAndValidateLatestPlFile(String source, ProductListingInfo& plInfo, Boolean& nofileretrieved)
at Symantec.Installation.Context.ProductListingManager.GetAndLoadProductListings(String source, ProductListingInfo& info)
at Symantec.Installation.Context.ProductListingManager.LoadCurrentProductListings()
at Symantec.Installation.Context.ProductListingManager.LoadAndUpdateProductListings()
at Symantec.Installation.Context.ProductListingManager.<BeginLoadAndUpdateProductListings>b__0()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
)
( Extra Details: Type=System.Net.WebException Src=System )
I've checked the Altiris KB article and the registry settings all look OK. User name and password are binary, so I can't tell what they are actually set to. Anyhow, this was working fine until a short while ago. We've not made any changes to our Web proxy, also. It seems that once you have set your proxy settings for SIM your stuck with them; right or wrong!!??
Would you like to reply?
Login or Register to post your comment.