4 Replies Latest reply on Nov 9, 2007 3:21 PM by bspies

    EPO 3.6.1 upgrade fails

    bmumph
      I am trying to upgrade my EPO server from 3.5.0 to 3.6.1. Half way through the installation it errors out and gives me the error: An Unexpected error occured while running DBInit.exe troubleshooting code 333. Does anyone know what is causing this error and how I can fix it?

      Also now I can't log into the EPO console.
        • 1. RE: EPO 3.6.1 upgrade fails
          Cant remember at what stage my upgrade failed. But what I found was that if I didnt extract the ZIP file with something like 7-zip rather than the Windows self extractor, it would not work,


          Have you tried to unzip this using a non MS self extractor ?
          • 2. RE: EPO 3.6.1 upgrade fails
            i think the install has got much further than this point.

            dbinit is the process that does the SQL - builds the DB tables, etc

            when the install fails, it will offer to show you the logs, can you send in the last page of the dbinit log and trace.log please ?
            • 3. Logs
              bmumph
              Here are the logs.

              trace.log:

              20070209095156 importNAPs: C:\Program Files\Network Associates\ePO\3.6.1\NAP\ALERTMNG4700\4.7.0\AMG470.NAP
              20070209095156 File to extract: [C:\Program Files\Network Associates\ePO\3.6.1\NAP\ALERTMNG4700\4.7.0\AMG470.NAP] - Destination: [Z:\TEmp\1\NAILogs\Extracted]
              20070209095156 File to extract has been opened so extracting all files.
              20070209095157 Failed to extract the files from [C:\Program Files\Network Associates\ePO\3.6.1\NAP\ALERTMNG4700\4.7.0\AMG470.NAP]. Error code: 3
              20070209095157 FindFirstFile returned code [3].
              20070209095157 The Ver.js files was not found in the NAP file so checking in anyway.
              20070209095157 Calling InstallSoftware2 for NAP file C:\Program Files\Network Associates\ePO\3.6.1\NAP\ALERTMNG4700\4.7.0\AMG470.NAP
              20070209095157 ----- Fail -----
              20070209095158 An unexpected internal error occurred while running DBInit.Exe.

              Please see the TRACE.LOG or DBINIT.LOG files for more details.

              Windows error code 80100012: The action was cancelled by the system, presumably to log off or shut down.
              Error API: importNAP (&Connection, files.path, CurrentProductFolder, DatabaseConnectString)
              Troubleshooting code: 333

              Troubleshooting logs have been saved in this folder: "Z:\TEmp\1\NAILogs". Have the TRACE.LOG file and other logs available if you contact McAfee Support for assistance.

              Resolve any errors, then run Setup again to continue from this point.
              20070209095158 RevertToSelf () successful. Impersonation was stopped.
              20070209095158 RevertToSelf () successful. Impersonation was stopped.
              20070209095158 DBInit.Exe execution complete. Return code: 1. Running CoUninitialize
              20070209095158 CoUninitialize completed successfully.
              20070209095159 Exiting DBInit.Exe normally with return code 1
              20070209095159 exit code 1 (0x1)
              20070209095159 openRead: Z:\TEmp\1\NAILogs\dbiniterror.txt
              20070209095159 Licensing Tracing is being turned OFF.
              20070209095159 reg open: 0x80000002\SOFTWARE\Network Associates\Licensing\TraceAPI
              20070209101958 Starting command [explorer "Z:\TEmp\1\NAILogs"]
              20070209101958 Create executed successfully. Setup is NOT going to wait for process to finish.


              DBInit.log:

              20070209093826 E #2484 DAL RunSQL statement failed!
              20070209093826 E #2484 DAL COM Error :80040e14 RunSQL while invoking ADODB::Execute
              20070209093826 E #2484 DAL Meaning = IDispatch error #3092
              20070209093826 E #2484 DAL Source = Microsoft OLE DB Provider for SQL Server
              20070209093826 E #2484 DAL Description = There is already an object named 'EPOPolicy_BranchNode_OnDelete' in the database.
              20070209093826 E #2484 DAL
              20070209093826 E #2484 DAL RunSQL statement failed!
              20070209093826 E #2484 DAL COM Error :80040e14 RunSQL while invoking ADODB::Execute
              20070209093826 E #2484 DAL Meaning = IDispatch error #3092
              20070209093826 E #2484 DAL Source = Microsoft OLE DB Provider for SQL Server
              20070209093826 E #2484 DAL Description = There is already an object named 'EPOPolicy_LeafNode_OnDelete' in the database.
              20070209093826 E #2484 DAL
              20070209093826 E #2484 DAL RunSQL statement failed!
              20070209093827 E #2484 DAL COM Error :80040e14 RunSQL while invoking ADODB::Execute
              20070209093827 E #2484 DAL Meaning = IDispatch error #3092
              20070209093827 E #2484 DAL Source = Microsoft OLE DB Provider for SQL Server
              20070209093827 E #2484 DAL Description = There is already an object named 'AvertTaskLog' in the database.
              20070209093827 E #2484 DAL
              20070209093827 E #2484 DAL RunSQL statement failed!
              20070209093831 E #2484 DAL COM Error :80040e14 RunSQL while invoking ADODB::Execute
              20070209093831 E #2484 DAL Meaning = IDispatch error #3092
              20070209093831 E #2484 DAL Source = Microsoft OLE DB Provider for SQL Server
              20070209093831 E #2484 DAL Description = Column names in each table must be unique. Column name 'ServerKeyHash' in table 'LeafNode' is specified more than once.
              20070209093831 E #2484 DAL
              20070209093831 E #2484 DAL RunSQL statement failed!
              20070209093933 E #2484 DAL COM Error :80040e14 RunSQL while invoking ADODB::Execute
              20070209093933 E #2484 DAL Meaning = IDispatch error #3092
              20070209093933 E #2484 DAL Source = Microsoft OLE DB Provider for SQL Server
              20070209093933 E #2484 DAL Description = Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is wrong.
              20070209093934 E #2484 DAL
              20070209093934 E #2484 DAL RunSQL statement failed!
              • 4. RE: Logs
                I am getting the same failure in our 3.6.1 install over 3.6.0. Can you post what you did to fix this?