7 Replies Latest reply on Jun 3, 2008 12:07 PM by dportillo

    OS Deployment Button in Toolbox Unresponsive after Migration MSDE to Oracle

    Specialist

      Hi!

       

      We just switched Landesk 8.8 from MSDE to Oracle.

       

      Now we have the Problem, that when we click at the OS Deployment Button in the Toolbox at the left side, landesk becomes unresponsive and the only Solution is to shut down the task. Is it possible ,that something inside the Directorys will produce that failure, maybe an old config file?

       

      Can anybody help with this?

       

      Regards

       

       

      Troga

       

       

      UPDATE: Hier noch ein Log Auszug, wie man sehen kann, gibt es ein ORA-00942 Fehler

       

       

      5/27/2008 8:14:25 AM : FormMain: OpenTool http://LANDesk.ManagementSuite.WinConsole.AMTPlug.AMTPlug

      5/27/2008 8:14:25 AM : FormMain: OpenTool http://LANDesk.ManagementSuite.AlertUI.AlertForm

      5/27/2008 8:14:25 AM : FormMain: OpenTool http://LANDesk.ManagementSuite.SoftwareDistribution.WinUI.DeliveryMethods.DeliveryMethodForm

      5/27/2008 8:14:25 AM : FormMain: OpenTool http://LANDesk.ManagementSuite.SoftwareDistribution.WinUI.PackageManager.PackageManagerForm

      5/27/2008 8:14:26 AM : FormMain: OpenTool http://LANDesk.ManagementSuite.SoftwareDistribution.WinUI.TaskScheduler.TaskSchedulerForm

      5/27/2008 8:14:26 AM : FormMain: OpenTool http://LANDesk.ManagementSuite.LDHM.WinConsolePlugins.CabWizard.FileListToolForm

      5/27/2008 8:14:26 AM : FormMain: OpenTool http://LANDesk.ManagementSuite.PatchManagement.PatchForm

      5/27/2008 8:14:27 AM : Database.ExecuteDataTable: System.Data.OleDb.OleDbException: ORA-00942: table or view does not exist

         at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(tagDBPARAMS dbParams, Object& executeResult)

         at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)

         at System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult)

         at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

         at System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior)

         at System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)

         at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

         at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)

         at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)

         at LANDesk.ManagementSuite.Database.Database.x8e22f767813aabeb(OleDbDataAdapter x3fb957f455708171, DataTable x5a0a63955c2bb77f)

         at LANDesk.ManagementSuite.Database.Database.ExecuteDataTableP(String sql, Boolean schemaOnly, Object[] parameters)

         at LANDesk.ManagementSuite.Database.Database.ExecuteDataTable(String sql, Boolean schemaOnly)

      5/27/2008 8:14:27 AM : Sql statement SELECT PatchSettings_Idn, PatchSettings.Value FROM PatchSettings WHERE PatchSettings.Name = 'AVAlertMask'

      5/27/2008 8:14:27 AM : ExecuteNonQuery error for sql: insert into PatchSettings (Name, Value) values ('AVAlertMask', '0')

      System.Data.OleDb.OleDbException: ORA-00942: table or view does not exist

         at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForMultpleResults(tagDBPARAMS dbParams, Object& executeResult)

         at System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult)

         at System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult)

         at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

         at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

         at LANDesk.ManagementSuite.Database.Database.ExecuteNonQueryP(String sql, Int32 timeoutSeconds, Object[] parameters)

         at LANDesk.ManagementSuite.Database.Database.ExecuteNonQuery(String sql, Int32 timeoutSeconds, ArrayList oleDbParameters)

      5/27/2008 8:14:27 AM : ORA-00942: table or view does not exist

      5/27/2008 8:14:27 AM : Checking whether to enable rollup menu option

      5/27/2008 8:14:27 AM : FormMain: OpenTool http://LANDesk.ManagementSuite.WinConsole.Ldsm.LdsmContextMenu

      5/27/2008 8:14:27 AM : FormMain: Begin DeSerialize

      5/27/2008 8:14:27 AM : FormMain: DisplayToolBox

      5/27/2008 8:14:27 AM : FormMain: Set Column Widths

      5/27/2008 8:14:27 AM : Object reference not set to an instance of an object.

      5/27/2008 8:14:27 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.SoftwareDistribution.WinUI.DeliveryMethods.DeliveryMethodForm, Text: Delivery methods

      5/27/2008 8:14:27 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.SoftwareDistribution.WinUI.PackageManager.PackageManagerForm, Text: Distribution packages

      5/27/2008 8:14:27 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.SoftwareDistribution.WinUI.TaskScheduler.TaskSchedulerForm, Text: Scheduled tasks

      5/27/2008 8:14:27 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.WinConsole.Tools.Scripts.ScriptForm, Text: Manage Scripts

      5/27/2008 8:14:27 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.WinConsole.Tools.PxeMenuForm, Text: PXE Boot Menu

      5/27/2008 8:14:28 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.WinConsole.Tools.ClientReconciliation, Text: Unmanaged Device Discovery

      5/27/2008 8:14:28 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.WinConsole.Tools.DirManForm, Text: Directory Manager

      5/27/2008 8:14:28 AM : Information: User (Domain\USER) can add/remove LDAP directories.

      5/27/2008 8:14:28 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.LDHM.WinConsolePlugins.ClientWizard.WizardToolForm, Text: Windows CE agent configuration

      5/27/2008 8:14:28 AM : FormMain: PreLoadTool LANDesk.ManagementSuite.ClientConfigUI.ClientConfigForm, Text: Agent Configuration

      5/27/2008 8:14:28 AM : FormMain: PreLoadTool http://LANDesk.ManagementSuite.WinConsole.Utility.XPExplorerBar.TaskPane

      5/27/2008 8:14:28 AM : FormMain: _dockManager.LoadConfigFromFile

      5/27/2008 8:14:28 AM : FormMain: LoadLayoutNames

      5/27/2008 8:14:28 AM : FormMain: Leaving LoadLayout http://\\Servername\ldmain\layouts\Domain\USER\Current.vw

      5/27/2008 8:14:29 AM : FormMain: NagForDeliquency

      5/27/2008 8:14:29 AM : FormMain: Leave LoadUserData()

      5/27/2008 8:14:29 AM : FormMain: Load User Data (layouts, etc) end

      5/27/2008 8:14:29 AM : FormMain: Leave FormMain_Load

        • 1. Re: OS Deployment Button in Toolbox Unresponsive after Migration MSDE to Oracle
          phoffmann SupportEmployee

          Well - the oracle-error speaks for itself pretty much. "Table or view does not exist" ... means just that - the table/view we're trying to access doesn't exist.

           

          What exactly did you do when you "migrated" - my guess is that you've left out some of the needed additional steps (such as provisioning tables) when you did this.

           

          Paul Hoffmann

          LANDesk EMEA Technical Lead.

          • 2. Re: OS Deployment Button in Toolbox Unresponsive after Migration MSDE to Oracle
            Specialist

             

            We used the following Steps:

             

            1. Open Regedit on the Core Server

            2. Go to HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local

            3. Change the IsOracle to true.

            4. Change the Database to the oracle database.

            5. Change the Database server to the Oracle Server name

            6. Change the User to the Oracle user.

            7. Change the PWD Encryped to 0

            8. Change the Password string to your password. (This doesn't have to stay plain text so you can change it later.)

            9. Now browse to where you installed LANDesk and go to the ManagementSuite directory.

            10. Double-click on Coredbutil.exe.

            11. Click Build Components to build the tables in the new Oracle database.

            12. Once done, open the console on the Core, go to Configure | Services and re-input the data there. That should set the password back to encrypted.

             

            In the meanwhile we tried also the DBRepair Util (Clean) and the Coredbutil with Build Components again, but the failure is the same

             

             

            What other steps are required, that we may have forgotten?

             

             

            Best Regards

             

             

            Troga

             

             

            PS:

             

             

            Other things in the Log: (In Our Database is no Patch Settings Table)!?

             

             

            5/27/2008 2:16:24 PM : Sql statement SELECT PatchSettings_Idn, PatchSettings.Value FROM PatchSettings WHERE PatchSettings.Name = 'AVAlertMask'

            5/27/2008 2:16:24 PM : ExecuteNonQuery error for sql: insert into PatchSettings (Name, Value) values ('AVAlertMask', '0')

            System.Data.OleDb.OleDbException: ORA-00942: table or view does not exist

             

             

            5/27/2008 2:16:23 PM : FormMain: OpenTool http://LANDesk.ManagementSuite.PatchManagement.PatchForm

            5/27/2008 2:16:24 PM : Database.ExecuteDataTable: System.Data.OleDb.OleDbException: ORA-00942: table or view does not exist

             

             

            • 3. Re: OS Deployment Button in Toolbox Unresponsive after Migration MSDE to Oracle
              phoffmann SupportEmployee

              Yep - you've forgotten a few things - namely all of the provisioning + patch stuff. They're in separate XML-files - all you've created is the "basic" LDMS tables.

               

              You want to do the following.

               

              1 - Stop all the Intel/LANDesk services on your Core.

              2 - open up a CMD-promt.

              3 - Go to your Core's ManagementSuite directory.

               

              4 - Run

              ""

              coredbutil /patchmanager

              ""

               

              => This will create the patch manager tables. you will NOT see a UI for this - check TASKMON to watch for COREDBUTIL to finish.

               

              5 - When that's done, run the following:

              ""

              coredbutil /xml="provisioning.xml"

              ""

               

              and press "build components" when the window comes up - this will add the provisioning tables + stuff to your DB (rather important).

               

              6 - When it's done, close COREDBUTIL and reboot your Core.

               

              Now go and have a look (clear your CONSOLE.EXE.LOG and check it if you run into problems). That'll get you a bit further down the route :).

               

              P.S.: The DBREPAIR tool is for cleaning up DB corruption - you're missing tables, which is an entirely different problem :).

               

              Paul Hoffmann

              LANDesk EMEA Technical Lead.

              • 4. Re: OS Deployment Button in Toolbox Unresponsive after Migration MSDE to Oracle
                Specialist

                 

                Thank you very much.....that worked!!!

                 

                 

                Btw. is there a Document for that additional steps, available? We found only the Basic Steppings inside the Knowledge Base.

                 

                 

                Best Regards

                 

                 

                Troga

                 

                 

                • 5. Re: OS Deployment Button in Toolbox Unresponsive after Migration MSDE to Oracle
                  phoffmann SupportEmployee

                  There isn't - because things change depending on version, and for stuff like this it's usually recommended to contact either LANDesk support or your ESP. Specifically because this is NOT straight forward stuff, and there's other things that may or may not apply - there's a plethora of "IF"-s involved. Such things do not make for good public documents, really.

                   

                  Glad to have been of help.

                   

                  Paul Hoffmann

                  LANDesk EMEA Technical Lead.

                  • 6. Re: OS Deployment Button in Toolbox Unresponsive after Migration MSDE to Oracle
                    Specialist

                    Hi Paul Hoffmann!

                     

                    Are their maybe other Steps, that we missing?

                     

                    Because, now we have the problem, that we can not import our exported templates (Internal Error Occurred - Database Error) and some Devices are not shown under my devices, but if we make an IP Report for example, the missing Devices are inside, some of them more than one time (with IP 0.0.0.0 and the real IP)

                     

                     

                    Best Regards

                    Troga

                     

                     

                    PS: And we have some 4100 in the Event Logs:

                    Database exception: SCA53F9.SCN, LDInv.dll

                    -2147217833

                    ORA-12899: value too large for column "LANDESK"."FILEINFOINSTANCE"."SCM_LASTUSER" (actual: 91, maximum: 90)

                    Commit, Thread ID: 5740.

                     

                    Database exception: SCA5300.SCN, LDInv.dll

                    -2147217833

                    ORA-12899: value too large for column "LANDESK"."FLOPPYDRIVES"."DRIVETYPE" (actual: 61, maximum: 60)

                    Commit, Thread ID: 296.

                    • 7. Re: OS Deployment Button in Toolbox Unresponsive after Migration MSDE to Oracle
                      SupportEmployee

                      Troga,

                       

                       

                      It looks like a couple of your database columns are too small. You need to increase their size my modifying the datamart.xml file and running coredbutil to make the changes on the database.

                       

                       

                       

                       

                       

                      Detailed steps (from the core) 1- Open \Program Files\LANDesk\ManagementSuite\datamart.xml with notepad 2- Locate the following line and change the value "Char(90)" to "Char(100)":

                      <column name="SCM_LastUser" type="Char(90)" displayName="Current User" />

                       


                      3- Locate the following line and change the value "Char(60)"
                      to "Char(75)"

                      <column name="DriveType" type="Char(60)" displayName="Type" />

                       

                      4- Save changes to the file and close Notepad.

                       

                      5- Stop the LANDesk Inventory Server service

                       

                      6- Run \Program Files\LANDesk\ManagementSuite\coredbutil.exe and click on the 'Build Components' button. Let this process complete.

                       

                      7- Restart the LANDesk Inventory Server service